CUSTOM SOFTWARE — MVP DEVELOPMENT
Founders build for months before learning if anyone wants it.
Most first products are too big. Eighteen months go into a set of assumptions nobody checked, and at launch the only question that ever mattered — will anyone pay for this — still has no answer. This is the smallest thing real enough to charge for and small enough to abandon without regret.
Free · 20 minutes · no commitment
WHO THIS IS FOR
Founders and operators about to commit a year to an assumption nobody has tested.
THE PROBLEM
It happens because building is more comfortable than asking. Every additional feature is a way to postpone the conversation in which somebody declines to pay, and the longer that is postponed the more the answer costs.
WHAT IT LOOKS LIKE
MVP readout
EXAMPLE DOCUMENTWeek 6 of 6 · pallet space, booked online
WHAT SELLERS DID, FROM THE PRODUCT’S EVENT LOG · WHAT THEY SAID, FROM INTERVIEWS
Six weeks, one workflow
Weeks 1–2 · the riskiest part first, done
Would sellers pay by card with no sales call? A price-and-pay page went to 40 sellers on the waiting list.
Weeks 3–5 · one workflow, measured, done
Get a price, book, pay, drop off. Every step logged.
Week 6 · decide, in progress
Continue, change direction or stop.
Said they would book online
11 of 12
In interviews, before anything was built.
INTERVIEW NOTES · BEFORE WEEK 1
Opened the price page
31 of 40
Sellers invited from the waiting list.
EVENT LOG · WEEKS 1–6
Booked and paid by card
9 of 40
No sales call with any of the nine.
EVENT LOG · WEEKS 1–6
Still storing in week 6
6 of 9
All six hold 8 pallets or more.
EVENT LOG · WEEK 6
Recommendation
Change direction
Build for sellers with 8 pallets or more. The three with fewer left within two weeks.
Only this one workflow was built. Had the evidence said stop, the build would have stopped here.
What you get.
- A working product, narrow enough to build fast and real enough to charge for.
- The riskiest assumption identified and put in front of users first, not last.
- Instrumentation, so you learn what people did, not what they said in an interview.
- A recommendation at the end: continue, change direction, or stop.
How it works.
Priced against the scope, after a Diagnostic that is small on purpose. The shape of the work we can tell you now.
- THE SHAPE
- A short, time-boxed build ending in a decision, not a launch party.
- WHAT WE NEED FROM YOU
- Access to real potential users. Without them this is just a small build.
- WHAT YOU KEEP
- The code, and the evidence — which is the more valuable half of the two.
What this does not include.
Published because you should know before the call, not after the invoice.
- A finished product. An MVP that does everything is not one.
- Continuing to build after the evidence says stop. We will say so, and it is the most useful thing we can do for you.
QUESTIONS
How small is minimum?
Small enough that being wrong is affordable. Usually one workflow, for one type of user, doing the one thing they would pay for.
What if it works?
Then you have evidence and a foundation, and the next build gets scoped against what real users did instead of what the original plan assumed they would.
MORE UNDER CUSTOM SOFTWARE
Bring us one bad week.
Book a pilot call. Tell us where the week goes wrong, and we’ll tell you what an Operations Diagnostic would map and measure.
The first paid step has a clear scope and an end date, and the pilot after it is one workflow — not a platform, and not an open-ended retainer.
Free · 20 minutes · no commitment