Buy the cheapest tool that covers the job, subscribe to the closest fit if nothing free will do, and build only when you have already tried the first two and hit a wall a generic tool cannot get past. That order is not a slogan, it is the order that loses you the least money if you are wrong. Most companies do it backwards: they hear "app" and go straight to build, because building feels like the serious, grown-up choice. It rarely is.
Why the order matters
Every option in this decision has a different failure mode. Buy a free or one-time tool and get it wrong, and you have lost an afternoon. Subscribe to the wrong SaaS and you have lost a few months of a manageable bill, cancel and move on. Build the wrong custom app and you have lost a specification meeting, a deposit, and weeks of a developer's time, and you own the mistake outright because nobody else is going to maintain it for you. Starting cheap is not caution for its own sake; it is how you find out what you actually need before you pay to have it built.
"What can you offer us?" is the wrong opening question
We get this a few times a year, in some form: a company comes with no written process, just "tell us what you have" or "what would you build for a business like ours". It sounds like a reasonable opener, and it is actually unproductive. It is your business, with your own workflow and your own data moving between your own people, and we do not know any of that from outside. We could spend an hour walking through everything we have built and none of it would fit, because the question was never about our catalog. It is usually a sign of one of two things: the process itself has not been studied or measured yet, or the company does not know what outcome it actually wants, and if neither is settled, it is not even clear that development, web or mobile, is the right tool at all.
The starting point of any project, ours or anyone else's, is a written description: what needs automating, what the result should look like, and what specifically did not work in anything already tried. We study that gladly, but it takes someone from your side who actually runs the process, answering our questions. Nobody outside your company can write that description for you.
Two more questions before you write a spec
Is your process actually different from everyone else's? Accounting, scheduling, basic invoicing: a thousand companies need exactly what you need, and excellent subscription software already exists for a monthly price no custom build competes with. Custom development earns its cost only where your process is genuinely your own, the thing that makes clients pick you over the company down the street.
Have you run the process by hand first? If a workflow has not survived a month in a spreadsheet or a shared folder, no app will save it. It will just make the confusion permanent and a lot more expensive to change. Run it manually, find the actual steps that repeat and the actual numbers that matter, and only then decide what deserves to be built.
Where subscribing quietly becomes the expensive option
SaaS pricing is per seat, per month, forever. It looks small on the first invoice and large on the third year. The math that flips the decision is simple: take the monthly bill, multiply by 36, and compare that number to a fixed quote for owning the equivalent tool outright. We have seen companies paying more for three years of a five-seat subscription than for a custom app that does exactly what they use and nothing they do not. If the tool is core to daily work and the team is not shrinking, run this number before renewing on autopilot.
There is a second cost subscriptions hide well: your data lives on someone else's server, under someone else's pricing and someone else's shutdown risk. For client lists, financial records or anything you would not want to explain losing, that is not a footnote, it is a real part of the decision.
The one honest reason to build
Build when you have already tried buying and subscribing, found the specific gap, and confirmed the gap costs you real money or real trust every week it stays open. That is a narrow bar on purpose. A custom app built to close a genuine, measured gap gets used every day. A custom app built because "we should have an app" gets opened once by the person who approved it and then never again.
Where we fit in this framework
We are the "build" option, and the first step before any quote is the same one described above: a written description of the process through the contact form, from someone who actually runs it. We ask clarifying questions, and if the answers show that something smaller than a custom build covers it, including one of our own free apps, we say so before we say a price. What we will not do is claim to know every tool on the market and hand you a recommendation for something we have not built or used ourselves; that search is yours to run. When custom is the right call, the next step is a fixed quote built from that written description, not an hourly estimate that grows with the project.