Validate your AI product in two weeks.
Not six months.

Validate your AI product in two weeks. Not six months.

BLUPRT runs a two-week Validation Sprint for funded founders. You walk away with a working prototype your customers have tested, and a clear answer on what to build next.

Book a call

Three months in, still no real users.

Building the prototype was never the hard part.

The roadmap is a stack of guesses.

You build features no one asked for.

AI demos look great, then die in production.

Engineering burns a quarter on the wrong thing.

Investors want proof you do not have.

PRICING

One sprint. One price.

Most founders are not sure whether to build, wait, or talk to more users first. The sprint answers that, and hands you a working prototype to prove it.

The Validation Sprint

£15,000

/fixed

~$19,000 USD

For funded founders who need to know what to build, before engineering spends a quarter building it.

Includes:

Two weeks, start to finish

50% to start, 50% on delivery

Discovery with 5 to 7 of your customers

A live prototype on a real URL, not a Figma file

Validation findings from 5 real users

A one-page build plan your team can start Mondaye build plan your team can start Monday

A recorded 90-minute readout with your team

You get a senior operator who has run discovery behind real raises. Two weeks of focused work, a prototype your users can break, and a clear answer on what to build next.

Book a call

Limited sprints per month. Currently booking.

The Validation Sprint

£15,000

/fixed

~$19,000 USD

For funded founders who need to know what to build, before engineering spends a quarter building it.

Includes:

Two weeks, start to finish

50% to start, 50% on delivery

Discovery with 5 to 7 of your customers

A live prototype on a real URL, not a Figma file

Validation findings from 5 real users

A one-page build plan your team can start Mondaye build plan your team can start Monday

A recorded 90-minute readout with your team

You get a senior operator who has run discovery behind real raises. Two weeks of focused work, a prototype your users can break, and a clear answer on what to build next.

Book a call

Limited sprints per month. Currently booking.

The Validation Sprint

£15,000

/fixed

~$19,000 USD

For funded founders who need to know what to build, before engineering spends a quarter building it.

Includes:

Two weeks, start to finish

50% to start, 50% on delivery

Discovery with 5 to 7 of your customers

A live prototype on a real URL, not a Figma file

Validation findings from 5 real users

A one-page build plan your team can start Monday

A recorded 90-minute readout with your team

You get a senior operator who has run discovery behind real raises. Two weeks of focused work, a prototype your users can break, and a clear answer on what to build next.

Book a call

Limited sprints per month. Currently booking.

THE HONEST COMPARISON

Three ways to find out

Build It Yourself
in Lovable

Fast and cheap. But you're guessing what to build, and a wrong guess can cost months of engineering time.

Cost

£0–£500

Tool subscriptions

Time To Outcome

Days

Customer Research

✕ Not Included

User Validation

✕ Assumptions Only

Output

Prototype

Best For

Exploring Ideas

BLUPRT

A working AI prototype tested with real users, delivered in two weeks by one senior operator.

Cost

£15,000 Fixed Fee

Time To Outcome

10 Days

Customer Research

✓ Included

User Validation

✓ Real Users

Output

Working Prototype

+ validation report + build plan

Best For

AI Products & Features

Discovery
Agency

Six weeks, £25k or more, a team of five, and you still get static screens, not something users can touch.

Cost

£25k–£60k+

Time To Outcome

4–8 Weeks

Customer Research

✓ Included

User Validation

Limited

Output

Static Screens

Best For

Corporate Innovation

Five deliverables. Every sprint.

Discovery Report

The real problem, defined from 5 to 7 customer interviews, with a clear recommendation: build, wait, or stop.

Discovery Report

The real problem, defined from 5 to 7 customer interviews, with a clear recommendation: build, wait, or stop.

Discovery Report

The real problem, defined from 5 to 7 customer interviews, with a clear recommendation: build, wait, or stop.

Working Prototype

A live, deployable prototype on a real URL. Not a Figma file. A thing your team can click and break.

Working Prototype

A live, deployable prototype on a real URL. Not a Figma file. A thing your team can click and break.

Working Prototype

A live, deployable prototype on a real URL. Not a Figma file. A thing your team can click and break.

Validation Findings

What 5 real users did with the prototype, what worked, and what to change.

Validation Findings

What 5 real users did with the prototype, what worked, and what to change.

Validation Findings

What 5 real users did with the prototype, what worked, and what to change.

Build Plan

A one-page roadmap your engineers can sprint-plan from on Monday.

Build Plan

A one-page roadmap your engineers can sprint-plan from on Monday.

Build Plan

A one-page roadmap your engineers can sprint-plan from on Monday.

Final Readout

A 90-minute walkthrough with your team, recorded, yours to keep.

Final Readout

A 90-minute walkthrough with your team, recorded, yours to keep.

Final Readout

A 90-minute walkthrough with your team, recorded, yours to keep.

PROCESS

How the sprint runs

Kickoff (before we start)

A 90-minute call to learn your business, your hypothesis, and your constraints. We agree on the one thing worth validating.

Discovery (week one)

I interview 5 to 7 of your customers, synthesise what they actually need, and bring you a sharp problem definition by Friday.

Build and validate (week two)

I build a live prototype, put it in front of 5 real users, and learn what holds up. You get the prototype, the findings, and the build plan.

Handover

A 90-minute readout with your founder, product, and engineering leads. You leave knowing exactly what to build, and what not to.

Kickoff (before we start)

A 90-minute call to learn your business, your hypothesis, and your constraints. We agree on the one thing worth validating.

Discovery (week one)

I interview 5 to 7 of your customers, synthesise what they actually need, and bring you a sharp problem definition by Friday.

Build and validate (week two)

I build a live prototype, put it in front of 5 real users, and learn what holds up. You get the prototype, the findings, and the build plan.

Handover

A 90-minute readout with your founder, product, and engineering leads. You leave knowing exactly what to build, and what not to.

Kickoff (before we start)

A 90-minute call to learn your business, your hypothesis, and your constraints. We agree on the one thing worth validating.

Discovery (week one)

I interview 5 to 7 of your customers, synthesise what they actually need, and bring you a sharp problem definition by Friday.

Build and validate (week two)

I build a live prototype, put it in front of 5 real users, and learn what holds up. You get the prototype, the findings, and the build plan.

Handover

A 90-minute readout with your founder, product, and engineering leads. You leave knowing exactly what to build, and what not to.

OUTCOMES

What you walk away with

01

Certainty

A clear, evidence-backed answer on what to build, so engineering does not waste a quarter on the wrong thing.

02

Proof

A working prototype real users have touched, ready to put in front of investors or your board.

03

A plan

A build roadmap your team can start the day the sprint ends.

ABOUT

Who runs
your sprint

I am Amadeus. For six years I led product design, most recently as Head of Design running a team of ten at a venture-backed studio. I have run discovery for founders who went on to raise and build real products. I do that work now solo, faster, with a live prototype at the end instead of a static deck. The tools changed. The judgment is the same.

The goal was never to create more prototypes. It was to help founders make better bets. Every sprint is designed to answer a simple question: should this be built, changed, or abandoned? The faster we answer that question, the less time, money, and engineering effort gets wasted chasing the wrong thing.

Amadeus Rennalls

Founder, BLUPRT

Who runs your sprint

I am Amadeus. For six years I led product design, most recently as Head of Design running a team of ten at a leading studio. I have run discovery for founders who went on to raise and build real products. I do that work now solo, faster, with a live prototype at the end instead of a static deck. The tools changed. The judgment is the same.

The goal was never to create more prototypes. It was to help founders make better bets. Every sprint is designed to answer a simple question: should this be built, changed, or abandoned? The faster we answer that question, the less time, money, and engineering effort gets wasted chasing the wrong thing.

Amadeus Rennalls

Founder, BLUPRT

FAQ

Questions founders ask

What exactly is a fractional Head of Design?

Director-level design leadership on a part-time, retained basis. You get the strategic judgment, team direction, and systems thinking of a senior design hire, one to two days a week, without the £150k+ salary or the months-long hiring process.

How is this different from hiring a freelance designer?

A freelancer produces design work. A fractional Head of Design owns the direction: setting the standard, guiding your existing designers, building the systems, and making the calls that keep your product coherent as it scales. It's leadership, not just delivery.

How quickly can we start?

Within a week of our call, in most cases. There's no three-month hiring cycle. Once we agree it's a fit, I embed with your team and set direction in the first few days.

What size company is this for?

Series A to B SaaS startups, roughly 11 to 50 people. The stage where the product is shipping and the team is growing, but nobody senior owns design yet.

Is there a minimum commitment?

No lock-in. It runs month to month on 30 days notice. If you want to test the fit first, the 30-day pilot is a lower-risk way to start.

Do you still do the two-week design sprints?

Yes, for teams with a discrete deliverable rather than an ongoing leadership gap. If you need one specific thing built and shipped, a fixed-scope sprint may be the better fit. Mention it on the call and I'll tell you honestly which one suits you.

What time zone do you work in?

London-based, working US East Coast hours through the sprint. Your weekly founder sync sits in your timezone, not mine.

FAQ

Questions founders ask

What exactly is a fractional Head of Design?

How is this different from hiring a freelance designer?

How quickly can we start?

Within a week of our call, in most cases. There's no three-month hiring cycle. Once we agree it's a fit, I embed with your team and set direction in the first few days.

What size company is this for?

Series A to B SaaS startups, roughly 11 to 50 people. The stage where the product is shipping and the team is growing, but nobody senior owns design yet.

Is there a minimum commitment?

No lock-in. It runs month to month on 30 days notice. If you want to test the fit first, the 30-day pilot is a lower-risk way to start.

Do you still do the two-week design sprints?

What time zone do you work in?

London-based, working US East Coast hours through the sprint. Your weekly founder sync sits in your timezone, not mine.

FAQ

Questions founders ask

What exactly is a fractional Head of Design?

How is this different from hiring a freelance designer?

How quickly can we start?

Within a week of our call, in most cases. There's no three-month hiring cycle. Once we agree it's a fit, I embed with your team and set direction in the first few days.

What size company is this for?

Series A to B SaaS startups, roughly 11 to 50 people. The stage where the product is shipping and the team is growing, but nobody senior owns design yet.

Is there a minimum commitment?

No lock-in. It runs month to month on 30 days notice. If you want to test the fit first, the 30-day pilot is a lower-risk way to start.

Do you still do the two-week design sprints?

What time zone do you work in?

London-based, working US East Coast hours through the sprint. Your weekly founder sync sits in your timezone, not mine.

Book a call

Let's see if it fits.

A 30-minute call to talk through what you are building, who it is for, and whether a sprint is the right next step. If it is not a fit, I will tell you, and point you somewhere better.