Every engagement ships these as concrete artifacts you own — not slides, not hand-waving.
5–8 user interviews, journey mapping, persona refinement (only if it changes a decision). Synthesised into a 1-pager — not a 40-slide deck.
Lo-fi screens for every state (loading / empty / error / success). Click-through prototype for stakeholder sign-off before any pixel polish.
Final Figma with auto-layout, variants, and component-level documentation. Design tokens exported as CSS / Tailwind / Style Dictionary.
Reusable component library (buttons / inputs / cards / tables / modals) with states, variants, a11y notes, and component-to-code mapping.
Interviews, competitor teardowns, audit current product if there is one. Output: a problem statement everyone can recite.
Lo-fi flows for the critical paths, reviewed mid-week. We resolve information architecture before pixels.
Final UI, design system, prototype. Engineers in the room from day one — not at hand-off.
Component-level docs, token export, dev walkthrough, asset handoff. We fix Figma issues for 30 days post-handoff.
Best-in-class where it matters; boring and battle-tested everywhere else.
Cost depends on surface count, research depth, and design-system scope. Typical: 1–2 week single-surface sprint, or a 3–4 week multi-surface engagement. We share a fixed quote within 24 hours of the call.
Not as a primary service. We do product UX and the design system — we'll respect your existing brand or refer you to a brand specialist.
Yes — many engagements are extending or refining an existing system, not greenfield. We treat it as the source of truth and add components conservatively.
Same room, same Slack channel. Engineers join from week 4 onwards. Component contracts (props, states, variants) get reviewed before the Figma is locked.
Yes — that's a separate fixed-bid scoped against your component count. Works best paired with a Web App Development engagement.