The spreadsheet test: how to tell in thirty seconds whether your idea is buildable fast

Owners usually ask 'how hard is this to build' and get an answer that depends on the developer's mood. There is a better question, and you can answer it yourself before you talk to anyone.

Does your business currently run on a spreadsheet, a group text, and a PDF that gets emailed?

If the answer is yes, your application is almost certainly a fast build. What you are describing is records, roles, statuses, file attachments and a document generated at the end. That is the most well-understood shape in all of software. It is also the shape AI coding tools handle best, which is why the economics work.

If the answer is no — if the thing that would make the software useful is a live connection to a system somebody else controls — you are in a different category entirely, and it is worth knowing that before you start rather than after.

The tell is usually a single sentence in how the owner describes it. 'I want my techs to fill out the inspection on their phone and have it email the customer a report' is a fast build. 'I want it to pull the policy data from our agency management system' is not, and no amount of AI changes that, because the difficulty is not in writing the code — it is in the other system's terms, uptime, data model and release schedule.

This is also the most useful thing you can do to make your own project cheaper. Almost every idea has a version that avoids the integration and still delivers most of the value: build alongside the legacy system, export to it rather than sync with it, and revisit the integration once the software has proven it is worth integrating.

Run the test on your own idea before your next conversation with a developer. If you land in the fast category, you should be getting a price in one call. If you land in the slow category, you should be talking about phasing, not about a total.