Question 1

What is a UX Sprint?

Accepted Answer

A five-day rapid product design service. You get production-ready designs, an interactive prototype and user testing results in one week — fixed price, fixed timeline. Everything your developers need to build the right thing first time.

Question 2

Can you really design something meaningful in 5 days?

Accepted Answer

Yes — because the week is designed around one thing. Two senior designers, one project, no juggling. We've run 100+ sprints and the constraint is the point: decisions get made, work gets tested, and on Friday you have dev-ready designs rather than a plan for designs.

Question 3

How much does a UX Sprint cost?

Accepted Answer

£10,000 + VAT for two senior designers across five days. Larger or more complex products run across multiple sprints, each £10,000 + VAT, with the number agreed in the pre-flight call.

Question 4

What do we need to prepare before the sprint?

Accepted Answer

Very little. We run a pre-flight call to agree the scope, and we ask you to nominate one decision-maker who is available for a 15-minute standup each morning. Bring whatever exists — a brief, an old product, a back-of-envelope sketch. We handle the rest.

Question 5

How long does a UX Sprint take?

Accepted Answer

Five working days, Monday to Friday, with a pre-flight scoping call on the Friday before.

Question 6

What exactly do we get at the end of the week?

Accepted Answer

A Figma file with full design files, a design system and UI kit, a clickable prototype with a detailed index, user testing feedback with recommendations, and a video walkthrough of everything. Developer-ready, with nothing held back.

Question 7

What do I get from a UX Sprint?

Accepted Answer

Production-ready Figma files (every screen, every state), an interactive clickable prototype covering all flows, user testing with real users, a design system (colours, typography, spacing, components), and a live handover session.

Question 8

How much of our time does it take during the week?

Accepted Answer

About 15 minutes a day. A short morning standup to review progress and make decisions, then we get on with it. Each evening you get a show-and-tell link to review whenever suits you.

Question 9

What's included in the price?

Accepted Answer

The pre-flight scoping call, five days of two senior designers, a daily show-and-tell every evening, the interactive prototype, user testing, the design system, the production-ready Figma files and the handover session.

Question 10

What's not included in a UX Sprint?

Accepted Answer

Development or coding (that's a V1 Sprint), ongoing design support after handover (that's the Subscription), brand identity or logo design, content and copywriting, and market or competitive research.

Question 11

What if the designs aren't right?

Accepted Answer

You see the work every single day, so there are no Friday surprises — course corrections happen in the morning standups while they're cheap. And because designs are tested with real users during the week, what you get is evidence-based, not taste-based.

Question 12

What does the week look like, day by day?

Accepted Answer

Day 1: architecture, key screens, navigation. Day 2: all screens, all states, edge cases. Day 3: interactive prototype and refinement. Day 4: user testing with real users. Day 5: final refinements, design system, and a 4pm handover call. There's a show-and-tell video every evening at 6pm.

Question 13

How far in advance do we need to book?

Accepted Answer

Sprints are scheduled in fixed weeks, one project at a time, so availability depends on the calendar. Typically we can start within two to three weeks — book an intro call and we will confirm the next open slot.

Question 14

Can you really design something meaningful in five days?

Accepted Answer

Yes. We designed 100+ screens for Navmii — an app used by 30 million people — in five days. The speed comes from process and exclusive focus, not shortcuts.

Question 15

Is a UX Sprint a workshop?

Accepted Answer

No. We design independently — it's not a workshop where you sit in a room with us all week. Your total time investment is roughly five hours across the week.

Question 16

How much of my time does a UX Sprint take?

Accepted Answer

About five hours over the week: the pre-flight call, occasional morning calls if a decision is needed, and reviewing the evening show-and-tells. We design; you steer.

Question 17

Do you test the designs with real users?

Accepted Answer

Yes. User testing is included. We test the prototype with real users during the sprint, record the sessions and report the findings, so you never ship untested designs.

Question 18

What if users don't like the designs?

Accepted Answer

That's exactly why we test during the sprint. If something isn't working we know by around Day 3 and fix it before handover.

Question 19

Will my developers be able to build from your designs?

Accepted Answer

Yes — that's the whole point. You get pixel-perfect Figma files with every state covered and a design system, so your team builds the right thing first time without guesswork.

Question 20

Do you work with our existing design system?

Accepted Answer

Yes. We either work within your existing design system or create one you can extend. Either way the output is consistent and maintainable.

Question 21

Will you design every screen and state?

Accepted Answer

Yes — every screen, every state, every edge case and icon. Developers waste cycles on rework when states are missing; we cover them.

Question 22

Who is the UX Sprint for?

Accepted Answer

Product teams with developers waiting, innovation leads who need stakeholder buy-in, and founders who need to brief a development team. Anyone who needs validated, build-ready designs fast.

Question 23

Who is the UX Sprint not for?

Accepted Answer

Anyone needing extensive discovery before design can begin, anyone who needs ongoing retained design (that's the Subscription), or anyone who thinks "five days" means rough sketches.

Question 24

Why not just build it and iterate after launch?

Accepted Answer

Because iteration after launch costs around ten times more than iteration in design. A week of design saves months of developer rework.

Question 25

Couldn't we do this ourselves in Figma?

Accepted Answer

You could — but will you, and will it be tested with users? The sprint guarantees production-ready, validated output in five days. The real question is the opportunity cost of doing it slowly.

Question 26

What happens after a UX Sprint?

Accepted Answer

Three common paths: your team builds from the designs, we build them in a V1 Sprint, or you move to the Subscription for ongoing design and development.

Question 27

Can a UX Sprint roll straight into a build?

Accepted Answer

Yes. Many clients go UX Sprint then V1 Sprint — validated designs to deployed software in about 10 days.

Question 28

Is the UX Sprint guaranteed?

Accepted Answer

Yes. If at the end of Day 5 you don't have production-ready designs that match what we agreed in the pre-flight call, we keep designing at no extra charge until you do.

Question 29

How many screens can you design in a UX Sprint?

Accepted Answer

It varies by complexity, but as a benchmark we delivered 100+ screens for Navmii in five days and 200+ screens for Big Motoring World across 10 days.

Question 30

Can you do user research as well as testing?

Accepted Answer

The sprint focuses on design and validation with real users. Extensive upfront research or competitive analysis sits outside the sprint, and we'll flag it in the pre-flight call if your project needs it.

Question 31

What format are the designs delivered in?

Accepted Answer

Figma — production-ready files plus a clickable interactive prototype, transferred to your account at handover.

Question 32

Do you cover mobile, web, or both?

Accepted Answer

Whatever the product needs — responsive web, web apps, mobile apps, tablet, desktop or kiosk. We confirm the platforms in the pre-flight call.

The 5-day UX Sprint