Prototype in 10 Days
A working, coded prototype of one core journey.
- How long10 working days
- How we workFixed package
What you receive
In ten working days your idea becomes a working, coded prototype you can put in front of users or investors.
What exactly are we proving?
You receiveA kick-off workshop
Ten days is short.
What it is. A half-day session to agree the one journey to build, who it is for and what we want to learn.
Why it matters. Ten days is short. A sharp goal on day one is what makes it possible.
Will it actually work?
You receiveOne core journey, engineered in code
People react honestly to something they can use.
What it is. The single most important journey, engineered as real software, not just pictures of screens.
Why it matters. People react honestly to something they can use. Real code also shows what is hard to build.
Will it feel real?
You receiveRealistic test data
Empty screens hide problems.
What it is. Sample data that looks like the real thing, so the prototype makes sense to users.
Why it matters. Empty screens hide problems. Realistic data lets people judge the product properly.
Can I show it to people?
You receiveA hosted demo link
You can show investors, customers or your team without installing anything.
What it is. A private web address where the prototype runs, ready to share.
Why it matters. You can show investors, customers or your team without installing anything.
What do users think?
You receiveA feedback session with your users
You learn what works and what confuses people before investing in the full product.
What it is. A session where real users try the prototype while we watch and take notes.
Why it matters. You learn what works and what confuses people before investing in the full product.
Should we build it, and how?
You receiveRecommendations for what comes next
You decide your next investment on evidence, not hope.
What it is. A short written note: what we learned, what to change and the next sensible step.
Why it matters. You decide your next investment on evidence, not hope.
From brief to done
- 1
Day 1
Workshop
Agree the journey and the goal.
- 2
Days 2 to 7
Build
The journey in code, shared with you as it grows.
- 3
Day 8
Host
The demo goes live on its own link.
- 4
Days 9 and 10
Test and recommend
Users try it, and you get our recommendations.
Is this quote fair, and what is it missing?
Second opinion on a quote. A plain-English read of a quote or plan from another supplier: what is missing, what is unclear and what to ask.
- Send us the quote or plan
- We mark it up and send it back with the questions worth asking
- It is free. There is nothing to pay and nothing to sign.
- The report is yours to keep and share, whatever you decide.
- No sales call unless you ask for one.
Questions people ask
How much does it cost?
We send a written quote after your request: what it covers and what it does not. The tier, scope and timing set the price.
Could I just use AI for this?
AI drafts code and prototypes quickly, and we use it every day. It cannot decide what to build, prove that it is secure, or answer for it when real people rely on it. That is the part you are hiring us for.
Who owns the work?
You do. Code, designs, files and documents are yours, and the quote says so in writing.
Can we change the scope?
Yes. If something needs adding or removing, we agree it in writing before we do it.
What happens after?
Most people go on to MVP Build, but there is no obligation. You keep everything we made.