SERVICE — 05 · Brand & Experience
WHO IT’S FOR
Who it’s for
Ad-hoc product design
Screens designed one at a time, by whoever had time, and the product has grown visibly inconsistent as a result.
The founder doing every screen
The product has outgrown what one person can carry alone without a documented system behind it.
INCLUDED
What’s included
| Research synthesis | Findings from the agreed method, written up — not left as raw notes |
| User flows | Mapped for the key tasks in scope |
| Key screens / prototype | Designed at a fidelity appropriate to the sprint, clickable where useful |
| Design tokens (Foundations) | Colour, type and spacing values documented for engineering handoff |
| Component library (Foundations) | Reusable components with documented states |
| Usage documentation | Written guidance an engineering team can implement directly |
PROCESS
How we deliver it
- 01
Discovery & research
Method agreed, research or review run.
3–5 days
- 02
Flows
Key task flows mapped and agreed.
3–5 days
- 03
Screens / system
Screens or the full token/component system built, one structured revision round.
1–5 weeks
- 04
Documentation & handover
Usage docs finalised, files delivered.
2–3 days
PACKAGES
Packages
Research, flows and key screens — a focused 2-week sprint.
- Research synthesis from the agreed method (interviews or a heuristic/competitive review)
- Mapped user flows for the key tasks in scope
- Key screens or a clickable prototype, at sprint-appropriate fidelity
2 weeks
€2,400 ex. VAT
40% due today: €960 · Balance: €1,440
Documented tokens, components and usage rules your engineers can build from — 7 weeks.
- Design tokens (colour, type, spacing) documented for engineering handoff
- Component library with documented states (default, hover, disabled, error, etc.)
- Usage documentation an engineering team can implement directly
7 weeks
€5,800 ex. VAT
40% due today: €2,320 · Balance: €3,480
Retained product design support, scoped to your team’s actual cadence.
- Recurring design capacity at an agreed cadence
- Ongoing flows/screens/system work as your roadmap requires
- A stated response time and monthly reporting, agreed in scope
Retained, ongoing
Price on request
PROOF
Proof
The component patterns, spacing scale and documented states used across this site follow the same discipline this service builds for a product team — applied here to a marketing and commerce site instead of a product interface.
FAQ
FAQ
What kind of research fits inside 2 weeks?
A short set of user interviews or a competitive/heuristic review, scoped to feed directly into the flows and screens.
Do I get a clickable prototype or static screens?
Whichever suits the task, agreed in discovery; both are within scope at this tier.
Can this lead into Design System Foundations later?
Yes — the flows and screens are a natural input into a later Foundations engagement, without duplicating the work.
Do you build the front-end code, or just document it?
Just document it, to a standard your engineers can implement directly — unless paired with a Webflow Development package, which does build it.
Can Foundations start before the full product is finished?
Yes — it’s commonly started once core flows are stable, even if every screen isn’t built yet.
RELATED