Not every good idea is ready to be built, and paying a developer is a costly way to discover that. I turn away work for this reason regularly, because a project that starts before the owner can describe it ends badly for both of us. Here are the tests I use.
Key Takeaways
- If you cannot describe the first screen, no developer can price it.
- If nobody has asked you for this, you are guessing about demand.
- If a spreadsheet would work for six months, use the spreadsheet.
- Being not ready is temporary and usually cheap to fix.
Test One: Can You Describe the First Screen
Say out loud what someone sees when they open it, and what happens after they tap the main button. If that comes out as a paragraph about your industry rather than a screen and a button, you are not ready. This is not a technical question. It is the difference between an idea and a plan, and a developer cannot supply it for you.
Test Two: Has Anyone Asked You For This
Not "would people like this," but has a specific person asked. If three customers have said some version of "can I do this online," you have demand. If the idea came only from you, build the smallest possible version of it in something you already have, and see whether anyone uses it.
Test Three: Would a Spreadsheet Hold For Six Months
A surprising amount of what people want to build is a shared spreadsheet with better manners. If a spreadsheet, a form and a calendar would carry you for six months, do that first. You will learn what the real rules are, and those rules are exactly the thing that makes custom software expensive to change later.
Test Four: Do You Know What You Would Cut
If everything is essential, nothing has been decided, and the project will grow after the price is agreed. Knowing what you would drop if the cost doubled is the clearest sign you have thought it through.
Test Five: Is There One Person Who Decides
Software projects with two decision makers who disagree quietly are the ones that stall. Not because of the disagreement, but because it surfaces in week six as a change rather than in week one as a choice.
What To Do Instead, This Month
Run the manual version by hand for four weeks. Take the bookings by phone and write them in a shared sheet. Send the reminders yourself. It is tedious on purpose, because every annoyance you hit is a requirement you would otherwise have paid to discover.
Then write one page describing the screens that would have saved you the most time. That page is worth more to a developer than a year of thinking about it.
A Concrete Version
A gym owner came to me wanting a member app with class booking, payments, a progress tracker and a social feed. I asked what members complained about. It was that they could not tell whether a class was full. That is one screen and a number, and it was already sitting in the software he used for payments. He spent nothing, turned on a feature he was already paying for, and came back eleven months later with a real project that had a year of evidence behind it. That second project was worth building.
The Honest Counterpoint
Waiting has a cost too. If a competitor is already doing the thing and taking your customers, a slightly wrong version now beats a perfect version next year. These tests are about avoiding waste, not about delay for its own sake. If you fail a test but the market is moving, build the smallest piece that answers the question and keep going.
Frequently Asked Questions
Is not ready the same as a bad idea?
No, and it usually is not. Most of the ideas that fail these tests are good ideas described too early. Four weeks of running it by hand fixes that.
Can a developer help me figure out what I want?
A good one will ask the right questions, and a scoping conversation is worth paying for. What does not work is hiring someone to build while you both find out what it is.
How do I know when I am ready?
When you can describe the first screen, name what you would cut, and point at a person who asked for it.
What if I fail a test but a competitor is already shipping it?
Then build the smallest piece that answers your riskiest question and ship that. These tests exist to stop waste, not to justify waiting. Speed matters when the market is moving; it just should not mean paying to discover what you wanted.
The Bottom Line
The most useful answer to "should I build this" is often "not yet, and here is what to do for four weeks instead." If you want that answer about your own idea, the honest read gives it in writing at no cost, and it says not yet when not yet is the truth. See also how to build an app without a technical co-founder and hire a developer vs no code.
Roberto Espinoza is CEO of Ruzora, which builds custom software for business owners at a fixed price and places pre-vetted senior LATAM engineers with US teams. Get a free honest read on your idea.
