Custom web app or off-the-shelf software? How to decide

Most growing businesses hit the same question sooner or later. The spreadsheet has quietly become the system, the software you pay for does most of what you need but not the part that matters, and someone spends hours each week copying data between tools. Do you keep adapting to off-the-shelf software, or build a custom web app around how you actually work?

There's no universal answer. Build vs buy is a trade-off between speed and fit, and between renting and owning. This guide sets out the honest pros and cons of each, a middle path that often beats both, and a checklist to help you decide.

Website, web application or software subscription?

These get mixed up, so it's worth being precise.

• A website mainly presents information: who you are, what you offer, how to get in touch. Visitors read it; they don't log in to do their work there.
• A web application is software that runs in a browser. Users log in and do things: book appointments, place orders, track jobs, approve requests, see their own records. Customer portals, admin dashboards and order systems are all web apps.
• Off-the-shelf software, often sold as SaaS, is a web app someone else has built for many customers and rents to you by subscription: a CRM, an accounting package, a booking tool.

If your needs stop at presenting your business and capturing enquiries, a well-built business website is enough. Otherwise, the real question isn't website vs web application. It's whether the web application you need should be one you rent or one you own.

When off-the-shelf software is the right choice

For most common business functions, buying is the sensible default.

• It's available now. You can sign up and start this week.
• Someone else maintains it. Security, hosting, updates and new features are the vendor's job.
• It's proven. Many other businesses have already found and reported the bugs.
• Costs are predictable at the start: a subscription per user or per month.

Accounting, payroll, email, general CRM, video calls and standard appointment booking are solved problems. If your process looks like most businesses' process, a good product will do it better than something built from scratch.

Where off-the-shelf starts to hurt

The warning signs build slowly:

• Your team works around the software. Data is exported to spreadsheets, fixed and re-entered. Steps happen on WhatsApp because the tool has nowhere to record them.
• You pay for several tools that don't talk to each other, and someone copies information between them every day.
• Per-user pricing grows faster than the value. Adding staff, partners or customers as users gets expensive.
• The process that makes you different doesn't fit. Your pricing rules, approval steps or service model are exactly what the product can't handle.
• Customers need their own access, such as a portal to see orders, documents or progress, and the tool doesn't offer it in a form that suits them.
• You're exposed to the vendor's decisions: price rises, removed features, or data you can't easily export.

One of these on its own is rarely a reason to build. Several together usually are.

When a custom web app makes sense

A custom web application is built around your workflow, your users and your data. It makes sense when:

• the process is central to how you earn revenue or serve customers, not a back-office routine
• you've tried existing products and can say specifically where they fall short
• the workflow is stable enough to describe: you know the steps, the roles and the exceptions
• the time saved, errors avoided or better customer experience is worth more than the build and its upkeep
• you want to own the software and data rather than rent access to them

Typical examples are customer and partner portals, booking and order systems with unusual rules, internal dashboards that pull data from several tools, and job or quote tracking built around how your team really works.

The honest costs on both sides

Compare the full cost over several years, not the first invoice.

Off-the-shelf

• subscription fees, which usually rise with users, features or usage
• add-ons or higher tiers to unlock the features you need
• the hidden cost of workarounds: staff time spent copying, checking and correcting data
• switching costs later, if you outgrow the product or the vendor changes direction

Custom

• discovery and design: mapping the workflow before anything is built
• the build itself, quoted on scope
• hosting, monitoring and backups
• maintenance: security updates, fixes and small changes for as long as the app is in use
• your team's time for testing, feedback and training

A custom app is not a one-off purchase. If you can't budget for ongoing maintenance, stay with off-the-shelf. Our guide to what a maintenance plan should include is written for websites, but most of it applies to apps too.

Time is a cost as well. Off-the-shelf software can be running within days. A custom app takes longer, with a timeline that depends on scope.

The middle path: integrate first, build second

Often the best answer is neither pure buy nor pure build. Keep the off-the-shelf tools that do their job well, and connect them:

• website enquiries sent straight to your CRM, with the right person notified
• payments, bookings or orders updating a shared sheet or your accounts software automatically
• WhatsApp or email follow-ups triggered by events instead of someone remembering

That's what website integrations and business automation do. They remove the copy-and-paste without replacing systems your team already knows, and they are usually much smaller projects than a full build.

If integration solves most of the problem, stop there. If you find yourself connecting four tools to imitate one process, that's usually the point where a custom app becomes the simpler option.

Ownership: get it in writing

If you do build, ownership matters as much as it does for a website. Agree before work starts:

• that your business owns the source code and data once the project is paid for
• that hosting and third-party accounts are in your business's name
• what documentation and access you receive, so another developer could take over

The same principles for websites and domains are covered in who should own your domain and website.

A build vs buy checklist

Answer each question honestly:

1. Have you tried two or three existing products for this job?
2. Can you point to specific steps they can't handle, rather than a general feeling?
3. Is the process central to how you earn revenue or serve customers?
4. Would connecting your existing tools remove most of the manual work?
5. Is the workflow stable, or still changing every month?
6. Who will use it: your staff, your customers, or both?
7. Do you have a budget for maintenance after launch, not just for the build?
8. Do you need to own the software and data outright?

Mostly "no" to the questions about specific gaps, how central the process is and a maintenance budget: buy, and review again in a year. "Yes" to the question about connecting existing tools: start with integrations. Mostly "yes" to specific gaps, a central process, a maintenance budget and ownership, with a stable workflow: a custom web app is worth scoping properly.

How to start without over-committing

If a custom build looks likely, don't jump straight to a long specification. Start with a short discovery phase that maps the workflow, the users and their roles, the data involved and the systems the app must connect to. Then build the smallest useful version, put it in front of real users, and extend it in agreed phases. That keeps cost and risk proportionate, and you learn what matters before spending on what doesn't.

Talk it through

We build custom web applications such as customer portals, dashboards, booking and order systems and internal tools, and we connect existing software when that's the better answer. Describe the process you want to improve and we'll tell you honestly whether to buy, integrate or build. You can also see how our projects are priced.