Skip to content
Back to Design & Validate
Design & ValidateDesign & Validate · Productized process, skin in the game both ways

3-Day AI Design Sprint

Validate a product direction in days, not months. Working prototype, real user feedback, signed 90-day roadmap. Three live days plus delivery.

Open-ended service-design engagements drift. Scope expands, weeks turn into months, no decision-maker is steering the calendar. The 3-Day AI Design Sprint replaces that pattern with a defined process: fixed timeline, fixed scope, fixed price, and a half-back guarantee. If the agreed assets aren't delivered and you're not happy with what was, you pay 25% instead of 100%.

Expectations were high, and they were met. The Design Sprint went really well. We received feedback internally that it was exceptionally well facilitated.

Samuli RantanenProduct Designer, Tocoman/Admicom, Admicom
From Uncertainty to Validated Prototype
Signals from shipped work
Design SprintDashboardSaaS

Admicom

From Uncertainty to Validated Prototype

Validated dashboard concept in 5 days

Read the case study
Workshop or product outcome from previous work
Project context

Artifacts, interfaces, and workshop material from the kind of work this page is about.

Vitali Gusatinsky working with a team
Who leads it

Vitali facilitates the room, frames the decision, and keeps the work close to the evidence instead of presentation theatre.

Admicom

5-day validation

From Uncertainty to Validated Prototype

FCG / Kuntarekry

500,000 applications/year

Design Sprint for 1.5 Million Users

Big Four Professional-Services Firm

5 auditors. 90 minutes. One rename.

The Week Before the Build

Trusted by teams at

Where this starts to hurt

What starts showing up

These are the patterns that usually appear before a team admits the direction is under-questioned.

Service-design projects start open-ended, then drift past the original timeline.

Two workshops in, the prototype direction is clear but the next steps aren't scoped or scheduled.

Validation 'in a few weeks' has been the answer for months.

The team wants certainty before building but has no defined mechanism to get it.

Fit check

This is for the team that wants a real answer

The work is useful when there is an expensive decision ahead and enough honesty in the room to let evidence change direction.

Good fit

+

You have a product direction roughly defined and want to validate it without a 6-week discovery.

+

A decision-maker can clear three days and be in the room Day 1 morning + Day 3 afternoon.

+

You can introduce 5 qualified users for testing (we help you screen and recruit).

+

You're a B2B product team, a regulated-industry product owner, or a service-design partner offering this to your own clients as a fixed-scope alternative to open-ended engagements.

Not the right format

-

You're still figuring out which problem to solve. That's a Discovery engagement, not a sprint.

-

You can't get a decision-maker in the room for Day 1 morning and Day 3 afternoon.

-

You need a production build at the end. Sprint outputs go into engineering, not the App Store.

-

You want a workshop with no deliverables. This produces signed artifacts you can hand to a team Monday morning.

What changes

Outcomes you can point to

The point is not abstract insight. It is a smaller and more confident next move.

A Figma design system library (~12 components, light + dark tokens, named in your product's domain vocabulary).

A working prototype at a declared tier (Facade / Simulated-data / Spike / Production-stub), chosen on Day 0 for fit, same price across tiers.

Synthesised user research from 5+ qualified sessions: top 5 themes, verbatim quotes, recording clips.

A signed 90-day phased roadmap (3 phases, one A4 page).

A signed decision log. Every decision made and every direction discarded, with reasons.

How the work moves

A short decision cycle, not a research maze

This is structured to surface signal early, while the cost of changing course is still low.

Day 0

90-min prep session. Lock the Outcome Contract together (components, screens, prototype tier, sessions, roadmap shape) and confirm Recruitment SLA + tool access.

Monday (Day 1)

Frame the problem with a sailboat retro, vote on the direction to test, lock the prototype scope. Afternoon: live AI build. You watch Lovable, v0, Figma Make, and the prompt patterns work in the room.

Tuesday (Day 2)

Morning prototype iteration. Afternoon: five user-test sessions back to back, you watch live, we capture observations.

Wednesday (Day 3)

Research synthesis. Decision workshop on impact × effort matrix. 90-day roadmap workshop. Final prototype demo + signed decision log.

Friday or following Monday

Polished asset bundle delivered. Figma library, prototype URL, research synthesis PDF, signed roadmap PDF, signed decision log.

Quick fit check

If this page sounds uncomfortably familiar, take the quiz before you commit more budget.

The quiz is the fastest way to tell whether this is the right format, whether another route makes more sense, or whether the team simply needs execution support.

You have a product direction roughly defined and want to validate it without a 6-week discovery.

A decision-maker can clear three days and be in the room Day 1 morning + Day 3 afternoon.

You can introduce 5 qualified users for testing (we help you screen and recruit).

What it looks like

The artefact you'd carry into the room

A click-through prototype of the validated path — the deliverable, not a deck about it.

3-day-ai-design-sprint · validated-flow.protoday 5 · final
welcomeprofileconnectdone
Proof

Evidence from shipped work

These offers are anchored in actual projects, real stakeholder rooms, and visible change afterward.

FCG / Kuntarekry

Design Sprint for 1.5 Million Users

Validated prototype and concrete development proposals backed by real user feedback. FCG now runs their own Design Sprints. Cross-functional alignment that continued beyond the sprint.

Design SprintGovernmentJob Portal
Anonymized · Big Four Professional-Services Firm

The Week Before the Build

The firm walked out of the week with a tested direction, a decision log, and a handful of small, specific changes that came directly out of the sessions. The redesign went into the build with the friction already named and the riskiest assumptions already retired. A sprint will not ship a finished product. It will not replace the discovery a long-running team does over a year of close contact with users. What it does is point the next quarter of build at the right thing. On a screen every auditor touches every cycle, that is what the week buys.

Design SprintDesign ThinkingUser Research
FAQ

Questions that usually come up

The practical questions tend to be less about process and more about timing, scope, and how much certainty a team actually needs.

Curious if we're a fit?

A short quiz. Takes 2 minutes. Helps us both figure out what kind of help might work for your situation.

If there's a fit, you'll be able to book a time immediately. Sometimes the answer is "you don't need me" — and I'll tell you that too.