First Version Build
A real AI product v1 in 4 weeks.
For founders and teams who need working software, not a throwaway MVP. We scope it in Product Proof Week, then build one focused first version past the demo.
- Build time
- 4 weeks
- Warranty
- 30 days
- First step
- Proof Week
- Build slot
- One v1 at a time
01 — What you get
The first version is the product starting properly.
The build is fixed around one valuable workflow, but the handover is serious: foundations, docs, measured AI where needed, and a clear next-build map.
Deliverable / 01
The v1 itself
Working software, deployed and demoed on your own data. Real enough to use, test, sell, or run inside the business.
Production foundations
Architecture and scope decisions meant to carry the next phases, not a prototype waiting to be rebuilt.
Owner's Manual
Documentation for the people who will run the product after handover: what exists, what is parked, and how to operate it.
AI Scorecard
Where AI exists, it is measured on real examples so the limits and behaviour are visible instead of hand-waved.
02 — The route to live
Proof Week first. Then four focused build weeks.
Product Proof Week is mandatory for new builds because it gives the v1 a real finish line.
You leave the presentation with
- A build-ready v1 scope
- A feasibility verdict with risks named
- A working proof artifact you own
- A fixed quote for the First Version Build
The Proof Week guarantee
If you do not leave the presentation with the four deliverables, the Proof Week fee comes back.
Proof Week
Scope the v1 for real use
A paid first week turns the idea, spec, or workflow into a build-ready v1 scope, feasibility verdict, working proof, and fixed quote.
Week 1
Lock the workflow and foundations
We make the core product decisions, set up the technical base, and start with the riskiest part of the product.
Week 2
Get the product usable
The v1 starts behaving like software, not slides: screens, flows, data, AI behaviour, and edge cases get pulled together.
Week 3
Polish the real path
We tighten the most valuable workflow, measure AI where needed, and prepare the handover assets while the build is still moving.
Week 4
Ship, demo, and hand over
The scoped v1 goes live, gets demoed with your data, and leaves with training, warranty, and a build-out map.
03 — V1, not MVP
An MVP is what most agencies hand over. Here it is only the halfway mark.
A First Version Build is still tightly scoped. It just does not stop at the shiny demo. The v1 is built for the day after: real users, data, support, and the next product phase.
- Built on foundations meant to survive the next phase
- Documented for the people who will run it
- Measured where AI is involved
- Handed over with a build-out map and 30-day warranty
04 — Proof
The four-week promise rests on products already in market.
The deposit platform and the utility-bill audit engine both started as focused first versions and kept becoming the product. The point is not speed theatre. It is a serious first version that can carry what comes next.
Client build
Rental deposit proptech platform
Cash deposits replaced with secure pre-authorisation, with tenants moving in without a lump sum and landlords keeping protection.
Started as a first version · in market
AI with a real job
Utility-bill audit engine
Electricity bills checked the day they land, with tariff mismatches and landlord recharge disputes turned into refund-ready reports.
Started as a first version · in market
Money-back Proof Week
Start with the week that makes the build real.
Product Proof Week gives you a scope, proof artifact, feasibility verdict, and fixed quote. If those four things are not on the table, the fee comes back.