Frequently Asked Questions
Straight answers on engagements, process, tools, and track record — the questions founders, CTOs, and hiring managers actually ask before booking a call.
How to work together, what engagements look like, and how to start.
Yes. Jehcy Adorna takes on freelance and contract product design work for startups, with a focus on AI, Web3, and DeFi products. Typical engagements cover MVP design, design systems, and end-to-end product design. The fastest way to start is a 30-minute intro call booked through Calendly.
Book a 30-minute callThree shapes, most often: end-to-end product design for a new MVP, design system work for a team that has outgrown ad-hoc UI, and fractional or contract technical program management covering sprint planning and cross-team delivery. Engagements run from a few weeks to multi-quarter, remote, across global time zones.
See the case studiesYes. Jehcy has held TPM roles at Hub.xyz (2024–2025) and Supra Oracles (2020–2021), running sprint planning, roadmapping, and delivery across design, engineering, and business teams. Many clients hire him for the combination — someone who can run the program and design the product without a handoff between the two.
Career historyBook a 30-minute intro call at calendly.com/jezz/30mins. Come with the problem, the rough timeline, and whatever exists today — a deck, a Figma file, a live product, or nothing at all. The call ends with a clear recommendation on scope and sequencing, whether or not it turns into an engagement.
Book a 30-minute callJehcy is based in the Bicol Region of the Philippines and works remotely with global clients. Past engagements have spanned teams in the United States, Japan, and Europe. Overlap hours are agreed at the start of each engagement, and asynchronous handoffs are the default working mode.
Background, shipped work, and measurable outcomes.
Jehcy Adorna is an AI and Web3 product designer and technical program manager with more than 15 years of experience. He has shipped 12+ products across DeFi, blockchain infrastructure, developer tools, and edtech, working as both a designer and a delivery lead. His portfolio is at jezz.work.
Full backgroundMeasurable outcomes across past roles include contributing to $650M in total value locked and 120K active addresses at Supra Oracles, 35K signups on Sphinx Protocol at Alpha Stack, and 250K+ user signups across shipped products. 17 case studies document the constraints and impact metrics behind each.
Browse case studiesYes — Web3 and DeFi are the deepest part of the portfolio. Relevant work includes cross-chain oracle data feeds at Supra Oracles, DeFi wallet and protocol design at Alpha Stack, and an end-to-end Web3 music platform. The case studies cover wallet onboarding, protocol UX, and bridging Web2 users into Web3 flows.
Web3 case studiesWeb3 and DeFi, blockchain infrastructure, AI and social platforms, developer tools, edtech, fintech, cleantech compliance, and local commerce. The through-line is complex technical products that need to feel simple — systems with real constraints rather than surface-level marketing sites.
All workYes. 22 written LinkedIn recommendations from colleagues, founders, and clients are published on the site, alongside video testimonials. They cover work style, leadership, and delivery under pressure rather than generic praise.
Read testimonialsYes — 7 winning entries across 99designs contests, spanning web page design, brand identity, and marketing collateral. Each award page includes the original client brief, the contest constraints, and the submitted work, so the reasoning behind each design is visible rather than just the final image.
See awardsThe stack, the AI tooling, and what "designer who codes" means in practice.
Both. Jehcy designs in Figma and ships production front-end code in Next.js, React, TypeScript, and Tailwind CSS. This portfolio site is self-built. For startups, that removes the design-to-engineering handoff entirely on front-end work — the spec and the implementation come from the same person.
AI workflowsDesign runs on Figma, with Miro and FigJam for research and workshops. Build runs on Next.js, React, TypeScript, Tailwind CSS, and shadcn/ui. Delivery runs on Jira, Linear, and Notion. AI work runs on Claude Code with custom skills and Model Context Protocol servers.
MCP toolsAI is wired into the daily workflow rather than used ad hoc. Jehcy maintains 11 custom Claude Code skills and builds Model Context Protocol servers that connect AI agents to Figma, browsers, and design systems. The result is faster research, automated design QA, and prototypes that reach code in hours instead of days.
Agent skillsModel Context Protocol is an open standard that lets AI assistants call external tools directly. For design work it means an AI agent can read a live Figma file, inspect a running localhost page, or check design-system tokens — instead of guessing from a screenshot. Jehcy builds and uses several of these.
MCP tools in useYes. Jehcy built a component library from scratch as Director of UX/UI at Alpha Stack and has run cross-team design system engagements since. The work covers token architecture, component APIs, documentation, and — critically — the adoption process that decides whether a design system survives its first quarter.
Design system workHow the work actually runs, from kickoff to handoff.
Four phases: understand the constraints, map the problem, prototype fast, then validate. Every case study on the site is structured the same way — problem, constraints, decisions, impact — because the constraints are what actually shape the design. Prototypes go in front of users early rather than after a long design phase.
Process in the case studiesScrum-based, adapted to team size. That means a groomed and estimated backlog, sprint goals tied to product outcomes rather than ticket counts, and visible cross-team dependencies. At Supra Oracles and Hub.xyz this covered roadmapping, release coordination, and keeping design, engineering, and business aligned on one sequence.
For confidential client work, the case study describes the domain, the role, the design challenge, and anonymized impact metrics, but never the client name. On a call, the same rule applies: the work and the reasoning are open, the client identity is not.
See anonymized workYes. A large share of past work is zero-to-one: brand identity, first product surface, and MVP scope for teams with no in-house designer. Fuzic, a Japanese Web3 music platform, went from no product identity to a launch-ready brand system and site in 16 weeks.
Zero-to-one workBook 30 minutes. Bring the problem and whatever exists today — you will leave with a clear recommendation on scope and sequencing either way.