Root Key in full, in weeks one to three.
Standing Decisions built into your UI foundation and your live website.
Hold is built for you if:
You’re shipping, and the product is starting to fracture. Three versions of the same component. A team building around the system because going through it is slower. New designers spending their first month on archaeology. Usually Series A and beyond, with a brand already in place.
Twelve weeks. Four stages
Weeks 1 and 2 Audit
What exists, what’s actually used, where teams go around it, and what that’s costing you. Your users and operators take part, as well as your team.
We also check the claim you already make, and if it’s too vague to build decisions from, we sharpen it into one written claim, signed off by your founder.
Weeks 3 to 8 System build
Your product keeps its look. We improve what holds up, put a solid structure underneath what doesn't, and build in the rules that come from your claim, plus our own rules for accessibility and page weight.
All of it in Figma, with data visualisation patterns for your domain and the reasoning behind every rule.
Weeks 9 to 11 Product application
Your highest-value flows, redesigned in Figma on the new system, so your team can see every rule applied to a real screen.
Week 12 Governance and handoff
How the system gets owned, how people contribute to it, and how design and development stay in sync, with three training sessions for your team.
Everything is ready for your backlog, so your engineers build it on their own schedule. We also hand over the count: how far your product sits from its own system, read from the Figma file.
(30 days) Cover after handover
If something is off in the 30 days after we hand over (a component, a rule, the way it fits your team), we fix it at no cost.
* Two rounds of revision in every phase.
Need more?
Extra workshop €1,200. Extra revision round €1,000.
Priced and agreed before work starts.
Why it lasts:
The components are the easy part. Adoption is the hard one. A system your team doesn’t trust starts coming apart within months. The governance, the training and the 30 days of cover are what keep it alive.
At a glance
001
Timeframe 12 weeks, starting the Monday after the agreement is signed and the first payment clears.
002
Investment €48,000. 30% to secure the start date, 40% at the end of the system build, 30% at handoff.
003
Delivered in Figma, with documentation, so your engineers can build it in any stack.
004
Who’s on it The same people, from the first workshop to the handover.
What you might
be wondering
Do we need Open first?
No. Hold works with the brand you already have, whether it came from us or from someone else.
Do you start over?
No. Where a component is well built, we improve it. Where the structure is missing or badly built, our own components go underneath, adjusted to match your design. If the audit shows the system is broken beyond what Hold covers, we tell you before going any further, and agree a bigger scope together.
Do we have to stop shipping?
No. We work in parallel with your team. What we deliver is ready for your backlog, and you build it when it fits your roadmap.
What happens after the 30 days?
New issues, changes or extra work get scoped and priced as a separate piece of work.
Who owns the system after you leave?
You do. Pick someone to own it, from inside the team or as a new hire. They become your Decision Owner. Hold gives them a documented system and a governance model, so they don't start with an audit.
Can you work under NDA?
Yes. We keep the work private until you’re ready, and we only publish it once it’s public and you’ve agreed.