What Does a Product Design Sprint Cost?
By CodexierPublished 5 min read
A design sprint is sold as a fixed package, and the price on the quote is easy to compare. What quotes rarely show is the other half of the cost: your own people spending most of a week in a room, or on a video call, instead of doing their jobs. This guide breaks down both halves, what you should get for them, and when a sprint is more than the problem needs.
Who is involved and for how long
The classic format runs four or five days: map the problem and pick a target, sketch solutions, decide, prototype, test with real users. The supplier usually brings a facilitator and one or two designers who build the prototype. Your side brings a decider with authority, plus the people who know the customers, the product and the technical limits.
| Role | Supplier or you | Time involved |
|---|---|---|
| Facilitator | Supplier | Full sprint, plus preparation and summary |
| Designer(s) building the prototype | Supplier | Mainly prototype day and test preparation |
| Decider (founder, product owner, manager) | You | The first two days in full, then decision points |
| Experts: sales, support, technical lead | You | Mostly the first two days |
| Test users | Recruited by either side | About an hour each on test day |
Your team's time as a cost
Count your internal hours before you compare quotes. Four people spending two full days and a few check-ins afterwards add up to well over sixty hours of salaried time, and those people are usually your most expensive and most needed. That is the cost a sloppy sprint wastes, whatever the supplier charged.
- List who must attend and for which days
- Multiply their hours by your internal hourly cost, including employer contributions
- Add the cost of what they would otherwise have done that week, if it is revenue-generating
- Compare the total with the cost of building a feature or product that turns out wrong
A good supplier protects that time: clear preparation beforehand, strict timeboxing and a decider who actually decides, so the team is not reconvened the following week.
Deliverables: prototype and test results
A sprint's output should be concrete enough to act on the next Monday. Ask the supplier to list the deliverables before signing.
- A clickable prototype of the key flow, usually in Figma, that you own
- Recordings or notes from each user test
- A summary of what worked, what failed and what surprised
- A recommendation: build, change and retest, or stop
- A shortlist of open questions and risks for the next phase
If the deliverable is only a wall of sticky notes and a good feeling, the money bought a workshop, not a sprint. Our explainer on what a design sprint is describes the full process.
Remote vs on-site
| Aspect | Remote | On-site |
|---|---|---|
| Travel and venue | None | Travel, room, meals |
| Scheduling | Easier to fit around calendars | Needs a blocked week |
| Focus | Harder; email and chat are a click away | Easier; phones away, one room |
| User tests | Easy to recruit across Sweden | Local users, or tests run remotely anyway |
| Best for | Distributed teams, focused problems | Complex problems, teams new to working together |
Many sprints today are hybrid: the problem-mapping days together in a room, the prototype and test days remote.
When a sprint is overkill
A sprint is a heavy tool for a big, uncertain question. It is too much when the problem is a known usability issue that a UX audit would find in days, when the solution is already obvious and only needs design, or when there is no decider available to commit for the week. It is also wasted if nobody will act on the result because the budget or roadmap is already fixed.
It is the right tool when a wrong decision would cost months of development, when the team disagrees about direction, or when you are about to pitch or fund a new product and need evidence from real users.
Price and next step
Our product design sprint starts at 19 990 kr for the facilitated sprint with prototype and user tests; the exact scope depends on the number of flows and test users. The full list is on our pricing page. If you are unsure whether you need a sprint or something lighter, book a call and describe the decision you are facing.
Frequently asked questions
Can a sprint be done in fewer than four days?
Shorter formats exist, but they usually cut testing, which is the part that produces evidence. If time is tight, keep the test day and shorten the workshop days instead.
Who owns the prototype afterwards?
You should. Make sure the agreement transfers the design files and that you get access to the Figma project, not just a PDF export.
Do we need to recruit test users ourselves?
Either side can. You often have the best access to real customers; the supplier can recruit when you need people who have never heard of you. Agree who does it before the sprint starts.
What happens after the sprint?
Usually one of three things: build what tested well, rework and test again, or stop. The summary should make clear which one the evidence supports.
Facing a big product decision?
Describe the decision on a short call and we will tell you whether a design sprint is the right tool, or whether something lighter will do.
Book a free 15-minute call