Off-the-shelf software is the right answer for most businesses most of the time. It is cheaper, faster to start and maintained by someone else. But there is a point where working around a tool costs more than building one that fits. Here is how to recognise that point, and how to approach a custom web application sensibly.
Signs you may have outgrown your tools
- A spreadsheet has quietly become the system everyone depends on, and only one person fully understands it.
- Your team re-enters the same information into the website, the CRM and the accounting system.
- You have stacked several plugins or apps together, and they conflict or break after updates.
- Customers, dealers or staff need their own login, with different permissions and views.
- The way you quote, schedule or fulfil work is genuinely different from your competitors, and that difference is part of your value.
When you probably don't need one
If your process is standard, such as invoicing, appointment booking or a typical online store, a well-chosen SaaS product will usually serve you better. And if the real problem is that two existing tools don't talk to each other, an integration or automation with n8n, Make, Zapier or a direct API connection may solve it for a fraction of the cost of a new application.
What building one actually involves
- Discovery: mapping the workflow, the people involved and the data that moves between them.
- Data model and permissions: deciding what the system stores and who can see or change it.
- A first version: the smallest useful slice of the workflow, built and put in front of real users.
- Integrations: connecting to the CRM, ERP, payment, email or WhatsApp tools already in use.
- Hosting, security and maintenance: backups, updates and monitoring once people rely on it.
Start small and prove the value
The most successful custom projects I've seen don't start by replacing everything. They start with one painful workflow, such as order intake, job scheduling or a dealer portal, and solve it well. Once that version is in daily use, you have real feedback and a clear case for what to build next. It also keeps the budget tied to results rather than to a long feature list.
Questions to ask before you commit
- Which single workflow causes the most wasted time or errors today?
- Could an existing product plus an integration solve 80% of it?
- Who will own the application, and who maintains it after launch?
- What does success look like in three months: fewer errors, faster turnaround, less manual entry?
If your answers point to a real, recurring problem that existing tools can't handle, a focused custom application is often one of the best investments a growing business can make.