How to Choose What to Build When You Can Build Anything Fast
When Building Costs Nothing, Picking the Wrong Idea Costs Everything#
Three ideas. One week to ship any of them. So you picked the one that felt right and started building yesterday.
That moment right there is the problem.
Startup idea selection feels easy when building is cheap#
You told yourself you'd validate as you built. Cheap and fast means low stakes, right? If this idea doesn't work, you'll pivot. Try the next one.
That logic sounds reasonable. It isn't.
When building took six months and real money, founders thought hard before they started. The cost forced them to. They talked to people. They looked for evidence. They asked uncomfortable questions before writing a line of code.
Now that cost is gone. So is the deliberation it forced.
You didn't slow down to choose better. You sped up to skip choosing at all.
What founders actually do when building is cheap#
They pick the idea they find most exciting.
Not the idea with the strongest external evidence. Not the idea someone is already paying badly to solve. The one that feels good. The one they'd want to use themselves.
Excitement is not evidence. It never was.
The problem is that cheap building used to be corrected by expensive building. You'd ship fast, hit a wall, and the cost of continuing would force you to ask whether this was the right call. Now there's no wall. You can keep building indefinitely. Three weeks in. A month in. Still not sure if this is the right one, but too close to stop.
The speed removed the gate. Nothing replaced it.
How to pick the right idea before you start building#
Before you write a single line of code, rank your candidate ideas by one external signal.
Which idea has someone already tried to solve with money, time, or a workaround they hate?
That's it. That's the question.
Not which one excites you most. Not which one feels most technically interesting. Which one has prior evidence of pain someone paid for before your product existed.
Look for these things:
- People spending money on a partial solution that barely works
- A workaround someone describes with real frustration
- A task that takes hours per week that clearly shouldn't
- A tool people bought and still complain about constantly
The idea where you find that signal beats every other idea on your list. No matter how much you like the others.
What this looks like when you have real options#
Say you have three ideas: a scheduling tool for freelancers, a customer feedback platform for product teams, and a compliance tracker for small law firms.
Excitement points to the scheduling tool. You've lived that problem. You know it well.
External signal points somewhere else. You find three small law firms paying for a compliance tool that barely does what they need. Each one describes the same workaround. The tool costs them real money every month and still doesn't solve it fully.
Nobody is paying for a better scheduling tool yet. They're complaining about it. That's different.
Build the compliance tracker.
Your personal familiarity with a problem is not evidence the market is ready to pay for a solution. Prior spend is evidence. Documented workarounds are evidence. Frustration at a tool they already bought and use anyway is evidence.
Build toward the signal. Not toward the feeling.
The one thing cheap building changed that nobody is saying clearly#
Fast and cheap used to mean low risk. Ship and see what sticks.
That was true when the bottleneck was building. The bottleneck is not building anymore.
The bottleneck is choosing well before you start. And cheap building made that harder because it removed the only thing that used to slow founders down long enough to choose carefully.
The founders who get this right are not the fastest shippers. They are the ones who noticed, before they opened their code editor, that someone was already losing money or time to this problem. Before any tool existed to solve it.
That's your gate. External evidence of prior pain. Everything else is preference.
If you have two or three real ideas and aren't sure which one deserves to exist, Acrein Lab works through that decision with founders before a single line of code gets written.