What a product design studio costs in Europe: reviews, sprints, builds, and support
Gideon Awolesi ·
A lot of product design studios don't publish their prices, so you only find out what a project costs after a few calls. We publish ours. This page goes through what each stage of a project costs with us, in euros, what's included, and what changes the price, so you can budget before you talk to anyone.
01Our prices
Every price below is a starting price, and it's fixed for the scope we agree on in writing before any work starts.
| Stage | Service | Price | Length |
|---|---|---|---|
| Diagnose | Accessibility Audit | from €2,500 | 2 weeks |
| Diagnose | AI Feature Review | from €2,500 | 2 weeks |
| Diagnose | Product Readiness Review | from €2,500 | 2 weeks |
| Diagnose | Usability Review (IEC 62366-1) | from €6,000 | 4 weeks |
| Prove | Evidence Sprint | from €9,500 | 3 to 4 weeks |
| Build | Build | from €25,000 | 6 to 16 weeks |
| Keep | Keep | €2,500 a month | 3-month minimum |
02How the stages fit together
You don't have to start at the beginning. If you already know what's wrong, you can skip the review. If you already know the flow works, you can skip the sprint. Each stage ends with a document you keep, and you're free to stop after any of them.
- A review tells you what to fix first, in a ranked list.
- An Evidence Sprint builds the flow you're least sure about as a working app, tests it with 5 to 8 people from your user group, and ends with a fixed price for the build, or a recommendation to stop.
- A Build is designed and built by the same team that ran the research, so the reasons behind each decision make it into the code.
- Keep is for after launch, so every new feature gets the same usability checks as the first release.
03What changes the price
- The number of flows or journeys in scope. A review of three flows is a different job from a review of a whole product.
- The number of platforms. Web, iOS, and Android each need their own design and testing.
- Regulation. Work that has to hold up in front of a notified body or the FDA needs traceable documentation, and that takes longer.
- Integrations. A build that connects to systems you don't control, like KSeF or a bank, needs time for the error states as well as the happy path.
04How to compare studio quotes
Ask every studio the same things: what's in scope, what isn't, if the price is fixed or an estimate, who does the work, how many rounds of testing with real users are included, and what you get at the end. If one quote is much lower, the answers usually show what's been left out.
It's also worth asking what happens if the scope changes. With us, the price only changes if the scope changes, and we quote anything new before we start on it.
05Get a fixed quote
Tell us what your product does and where you're stuck. We reply within one business day, and after our first call, we send you a fixed price for your scope.