Screens a developer can build without guessing.
A pretty mockup that ignores states, breakpoints and empty screens is a spec with holes in it — and the developer fills those holes for you, badly. We design in Figma with real components, documented spacing, every interactive state, and mobile drawn alongside desktop rather than after it.
What lands in your Figma file
- Desktop, tablet and mobile artboards for every screen
- Component library with variants, not copy-pasted groups
- Colour, type and spacing tokens ready for CSS variables
- Hover, focus, active, disabled and error states
- Empty, loading and error screens — not just the happy path
- Form validation messaging and field behaviour
- Icon set, consistent grid and stroke weight
- Clickable prototype for stakeholder review
- Developer handover notes on each frame
- Exported assets: SVG, PNG @1x/@2x, favicon set
The five stages, and what happens in each
-
Goals & inventory — days 1–3
What is the one action this page or product exists to produce? We list every screen and every state that action needs, then agree the scope in writing. Surprises later are almost always screens nobody counted at the start.
-
Structure & wireframes — days 4–8
Grey-box layouts with real copy, mobile first. No colour, no imagery — deliberately, so the conversation stays on hierarchy and flow while changes are still cheap. You sign off structure before visual design begins.
-
Visual design — days 9–16
One or two visual directions applied to a key screen, then rolled out across the set once you choose. Everything is built as components from the start, so a change to a button updates every instance.
-
States & prototype — days 17–20
We add every state a real user will hit, wire up a clickable prototype, and check contrast against WCAG AA and tap targets against the 44 px minimum.
-
Developer handover — days 21–22
Tokens named, layers named, assets exported, notes written on every frame, and a call with your developer to walk the file. We stay available for build questions for 30 days afterwards.
Pick the level you need
Landing Page
One page, built to convert.
- 1 page, 3 breakpoints
- 2 revision rounds
- All interactive states
- Assets exported for build
- 8–10 working days
Website
A full marketing site.
- 8 pages, 3 breakpoints each
- Component library + tokens
- Unlimited rounds in-direction
- Clickable prototype
- Developer handover call
- 30 days of build support
- 3–4 weeks
Product / App
Dashboards and multi-state flows.
- Everything in Website
- Full design system in Figma
- Empty / loading / error states
- Dark mode variant
- Accessibility audit to WCAG AA
- 6–10 weeks
Design only. We do not build — but we hand over files your developer will thank you for.
Mobile drawn first
Not scaled down at the end. The hardest layout gets solved while there is still room to change it.
Real components
Variants and auto-layout throughout, so a change propagates instead of needing forty manual edits.
Accessible by default
Contrast checked to WCAG AA, tap targets at 44 px, focus states designed rather than left to the browser.
Before you brief us
Ready to design the screens properly?
Send the page list and platform — fixed price and delivery date within one business day.