Module 1
Choose what to build
Three scored candidate ideas and one you have chosen on the record.
Most founders choose an idea the wrong way round. They start from a trend, work backwards to a problem, and end up with something that sounds good in a pitch and dies in a sales call.
This module does the opposite. You start from work you have seen up close, test whether it removes a real cost, check whether it survives being easy to copy, and score three candidates against the same criteria before you commit to one.
Sign in below to save your answers
Source ideas from work you have watched up close
The best ideas are boring to everyone except the people who have lived them. They come from a job where you watched the same thing go wrong every week, from a process you had to work around, or from a market you know well enough to know what nobody says out loud.
A trends list gives you the opposite: problems you have never seen, in markets you cannot get a meeting in, with competitors you do not understand. You will spend your first six months learning what an insider already knows.
So start from your own record. Write down the work you have actually seen at close range. Not what you find interesting, what you have watched happen. The unfair advantage is that you know which parts are painful and which parts only look painful from outside.
Your turn
What good looks like
- Where: three years running operations for a car subscription business in the Gulf.
- Weekly friction: every handover produced a paper condition report, photographed and emailed, then re-typed into the system by an agent.
- Insider knowledge: the cost is not the typing. It is the disputes. About 6% of handovers turned into a damage argument that took 40 minutes and often ended in a goodwill refund.
The cost test
A business removes a cost that someone is paying right now. Hours, headcount, error rates, refunds, churn, cash tied up. If you cannot name the cost, name who pays it, and say how it is measured, you have an interest, not a business.
Be specific about the unit. 'Saves time' is not a cost. 'Forty minutes per disputed handover, about 90 disputes a month, handled by an agent on 8,000 dirhams' is a cost. The second version tells you what you can charge and who signs the invoice.
Do this for each candidate. The ones that survive are the ones where you can write the arithmetic on one line.
Your turn
| Candidate idea | Cost removed | Who pays it today | How it is measured |
|---|---|---|---|
What good looks like
- Candidate: automated vehicle condition capture.
- Cost removed: dispute handling time and goodwill refunds.
- Who pays: the operations manager's budget, signed off by the COO.
- Measured by: disputes per 100 handovers, minutes per dispute, refunds issued per month.
- One line: 90 disputes x 40 min x $12 = $720, plus $2,400 refunds. Call it $3,100 a month for a 400-car fleet.
The commodity test
Assume the build is free. With current tools a competent person can put a working version of most software on a real URL inside a week. So the interesting question is not whether you can build it. It is what stops the next person doing the same thing in week two.
There are only a few honest answers: proprietary data that accumulates, distribution you already own, a regulated or credentialled position, deep workflow integration that is painful to rip out, or a brand and trust position in a narrow market. Being first is not one of them. Nor is being cheaper.
Write your answer plainly. If the honest answer is 'nothing', that is useful information, not a failure. It usually means you should pick a narrower market where trust and service are the moat, or move to the next candidate.
Your turn
What good looks like
- Nothing stops a copy of the software. What is hard to copy is 60,000 labelled damage photos from Gulf fleets, and being the format the three biggest local insurers already accept.
- Narrower market that makes it true: start with car subscription fleets in the UAE, not global rental.
Score three candidates against the same criteria
Founders compare ideas on enthusiasm, which is why the newest idea always wins. Score them instead, on the same criteria, on the same day.
Six criteria, one to five each: how close you are to the problem, size of the cost removed, ease of reaching the buyer, how defensible it is in a year, how fast you can prove demand, and whether you would still want to work on it in three years.
The score is not the decision. It is a way of making your reasoning visible so you can argue with it later, and so a second reader can see what you weighted.
Your turn
| Candidate | Proximity | Cost size | Reach buyer | Defensible | Speed to proof | 3-year appetite |
|---|---|---|---|---|---|---|
What good looks like
- Condition capture: 5, 4, 5, 4, 4, 4 = 26.
- Fleet maintenance scheduling: 4, 3, 4, 2, 3, 3 = 19.
- Consumer car-cost app: 2, 2, 2, 2, 4, 3 = 15.
- What the score misses: condition capture needs insurer relationships I do not have yet. That is a two-month risk, not a blocker.
Commit to one
Write down the one you are building, the date, and the reason. Not because the decision is irreversible, but because a written reason is the only way to tell later whether you changed your mind on evidence or on mood.
Also write your kill condition now, while you are calm: the specific thing that would make you stop. It is much cheaper to define that today than in week nine.
Your turn
What good looks like
- Building: automated vehicle condition capture for UAE subscription fleets.
- Because: I have run the operation, the cost is measurable at $3,100 a month per 400 cars, and the buyer is one person I can reach.
- Kill condition: if by 30 November no operator has paid a deposit for a pilot, I stop and reopen candidate two.
The judgment call
Two ideas scoring within a point or two of each other is a judgment call, not an information gap. More research will not separate them, because the difference sits in things you cannot measure yet: which buyer will actually answer your emails, and which problem you will still care about in year three.
How to think about it
- Prefer the one where you can reach the buyer this week without an introduction.
- Prefer the one where being wrong is cheap to discover, not the one with the biggest theoretical market.
- Discount any advantage that only exists after you have raised money.
- If they are still tied, pick the one you would be embarrassed to see someone else launch.
Questions worth sitting with
- Who is the first person you would sell this to, and do you have their number today?
- What would have to be true in twelve weeks for you to know you were right?
- Which of the two would you still work on if it grew slowly for two years?
- What are you avoiding by not deciding?
Common questions
How many startup ideas should I compare before choosing?
Three is enough. Fewer and you have no comparison, more and you are avoiding the decision. Score the same three on the same criteria on the same day, then commit.
Is it a problem if my idea already has competitors?
No. Competitors prove someone pays for the outcome. The risk is the opposite case: nobody has built it because nobody wants it. What matters is whether you can win a specific slice of the market rather than the whole thing.
What if the honest answer to the commodity test is nothing?
Then narrow the market until something becomes true: a segment you can serve better, a dataset that accumulates, or an integration nobody else will bother building. A narrow defensible business beats a broad copyable one.