Question 1

What does Ordeo actually deliver?

Accepted Answer

One place your product UI is defined, built into your product in 90 days, read by your designers, your engineers and your AI tools. A Design Library of your core components in Figma. The same components as tested code in your repo, on one token layer every brand and platform reads from. And the constraint layer: rules files, a design-system MCP server and CI gates, so your AI builds from your system instead of guessing.

Plus the proof: the Adherence Score, a dashboard that shows, PR by PR, how much of your UI ships from the system. Built by the two founders. No juniors, no long discovery, no agency markup.

Question 2

We already have a design system. What happens to it?

Accepted Answer

It becomes the starting material. The Diagnostic goes through what you have, tokens, components, Figma, and the plan says what gets consolidated, what gets extended and what genuinely can't hold. We don't rebuild what works, and your libraries converge into one instead of gaining a rival.

Nothing moves in a big-bang cutover. Old screens keep shipping alongside new ones, and each team adopts when its roadmap allows. That is how fourteen brands at BSH came onto one token layer in the years Florian ran it there, brand by brand, none of them forced to stop and migrate first.

You won't pay less for having one. Untangling half-migrated libraries without breaking what ships is harder than starting clean. What the money buys is the version where you don't stop and rewrite.

Question 3

How long does it take, and what does it cost?

Accepted Answer

90 days, fixed price. €125–185k, fixed after the Diagnostic. €125,000 is the floor. A portfolio of brands, or carving a system out after an acquisition, is more work and costs more than the top of that range.

50% on signing, 30% at week 6, 20% at week 12. No hourly billing, no day rates, no change orders under €5,000 of new work.

That's the whole cost of the Install. The Monthly afterwards is optional: take it and a first year runs €213–273k, the Install plus nine months of Monthly, then €117,600 a year after that. Skip it and the Install is all you pay. Nothing stops working either way.

Question 4

Who is this for?

Accepted Answer

VPs of Design, CPOs and the CTOs they build with, at European scale-ups between €30M and €250M a year. Series B to PE-owned, usually 50 to 500 people on the product team. Groups with several product lines from acquisitions fit squarely: one token layer carried fourteen brands in the years Florian ran it at BSH. Design usually feels the pain first. Engineering owns the budget and the codebase the guarantee is read on. We're built to be bought by both.

Teams past the size where consistency holds by luck, shipping AI-made UI faster than they can review it, who want it built rather than workshopped.

Not for anyone shopping for hourly billing and weekly status decks. And if you're under €30M, or under about fifty on the product team, the €125,000 floor is the wrong tool right now. The AI Drift Audit is free and will still tell you where you stand.

Question 5

What guarantees do you offer?

Accepted Answer

Two, both written into the contract.

Early exit at week 2. If the direction isn't right, you walk away and get everything back except a flat €12,500 for the two weeks. The work is yours to keep.

70% on the system, or we work free. On day 91 we re-measure how much of your new product UI comes from the system, on your own Git data, against the four-week baseline we read in week 1. A developer survey runs alongside as context, never as the contract. If it hasn't reached 70%, we work free until it does, up to 60 more days.

Miss again at day 151 and we refund the final 20%. You keep every Figma file, every line of code, every governance doc.

Speed is not in the contract, and that's deliberate. PR cycle time is mostly review latency and batch size, and both are yours to set, not ours. Two of us reviewing your pull requests for six weeks would move that number ourselves, then leave on day 91 and take the effect with us. So we guarantee the cause we control and that stays behind: where your new UI comes from. The speed follows, in the same Git data the guarantee is read on.

Question 6

What is the Diagnostic, and what do I get for €9,500?

Accepted Answer

Two weeks before you commit to the Install. We go through the design system you already have, in design and code, measure your real Adherence Score on your own Git, prototype the token setup on your brand, and hand you a 15-page plan to consolidate and extend it. You also get a fixed Install scope, a board-ready investment memo from your own Git data, the one-pager your CFO can sign off, and the vendor pack procurement will ask for.

The work is yours either way. Hand it to your own hire or another vendor, and we'll do a free one-hour handover call.

The full €9,500 comes off the Install if you book within 60 days.

The work is yours either way. Hand it to your own hire or another vendor, and we'll do a free one-hour handover call.

The full €9,500 comes off the Install if you book within 60 days.

Question 7

Will my AI coding tools stay on-brand?

Accepted Answer

Yes, and not by prompting alone. We make your system machine-readable, then enforce it: design tokens as one source, metadata on every component, rules files your coding agents read, a design-system MCP server your tools query, and CI gates that catch drift before it merges.

Left alone, your AI falls back on the generic defaults it was trained on, which is someone else's design system. We replace that default with yours, and the Adherence Score shows it holding, PR by PR.

Question 8

Why not hire a design systems lead, or use an agency?

Accepted Answer

In-house means a real team once you count design, engineering and the pipeline work. Four senior hires run about €500k a year with overheads. Six months to hire, nine to ramp. If someone already runs your system, the question isn't whether they're good. It's whether one underfunded team can build the AI layer and ship the roadmap in the same quarter.

The cheap routes stay cheap by leaving the job unfinished. A €30–60k build hands you Figma files your AI can't read, and a free component library is free because it's everyone's design system. Like for like, design plus tested production code plus the AI layer, agencies run €300–400k over a year and a Big 4 firm around €600k.

Ours is 90 days at €125–185k fixed, with two binding guarantees and senior founders on every piece of work.

Question 9

How is this different from a design-system platform?

Accepted Answer

A platform is software your team subscribes to. You feed it your tokens, components and docs, and your team runs the system through it, month after month. That works if you already have a staffed systems team with the time to do the feeding. The subscription doesn't build the system, and keeping it fed stays your job.

We're not a product you operate. Two senior founders build your system and install it where your product already lives: a Design Library in your Figma, the same components as tested code in your repo, and the constraint layer your AI tools read, wired into your CI. From your baseline to 70% of new UI on the system by day 91, or we work free. Then we leave, and your team runs it, with or without a platform underneath.

Question 10

What happens after day 91?

Accepted Answer

Up to you. The Monthly is €9,800 a month, for past Install clients only, capped at 6 clients at a time. Both founders on every piece of work.

It covers what actually rots: the AI rules that keep your tools on-brand, re-tested each quarter as models change, plus a capped amount of support, small fixes and review when you want it.

Mostly async, one job at a time. The 4-hour rule: we reply on Slack within 4 working hours, or the month is free.

Question 11

How can my team run it afterwards?

Accepted Answer

That's the whole point of the Install. By day 91 your team runs the system without us. Everything lives in your repo and your Figma, owned by you, with no dependency on Ordeo.

You get the rules to extend it, live workshops, a Loom onboarding library and the constraint layer your AI tools read on their own. The Monthly is there if you want ongoing help, but it's optional. Nothing stops working without it. What changes is who keeps the AI rules current as the models move, you or us.

Your design system. Installed. Enforced.

Your AI is already writing your product.

Sound familiar?

Chaos in. Your product out.

The Constraint Framework.

The code library

The Design Library

The constraint layer

Same brief. Two routes to shipped.

Selected work.

Ninety days. Week by week.

Baseline & token architecture

The Design Library

Production code, in your repo

Governance & the constraint layer

The measurement

Handover. Then we're gone.

Four steps. Fixed prices. No discovery theatre.

The Strategy Call

The Diagnostic

The Install

The Monthly

Two binding guarantees behind the price.

A note from the founders

CommonQuestions

Walk into your next board review with proof from your own Git.

Your AI is already writing your product.

Sound familiar?

Chaos in. Your product out.

The Constraint Framework.

The code library

The Design Library

The constraint layer

Same brief. Two routes to shipped.

Selected work.

Ninety days. Week by week.

Baseline & token architecture

The Design Library

Production code, in your repo

Governance & the constraint layer

The measurement

Handover. Then we're gone.

Four steps. Fixed prices. No discovery theatre.

The Strategy Call

The Diagnostic

The Install

The Monthly

Two binding guarantees behind the price.

A note from the founders

CommonQuestions

Walk into your next board review with proof from your own Git.

Your design system.
Installed. Enforced.

Common
Questions

Common
Questions