Tool sprawl: when one custom platform beats five subscriptions

What tool sprawl actually costs

A booking tool, a forms tool, a shop, a CRM and a spreadsheet to hold it all together: each one made sense when you bought it. Together they cost more than the subscription lines suggest. The visible cost is the monthly fee, usually charged per user. The hidden costs are people retyping the same data between systems, mistakes when two records disagree, time spent finding out which tool holds the latest version and the day someone who understands the connections leaves.

There is also a security side. Every tool has its own logins, its own copy of customer data and its own terms. More tools mean more places where something can go wrong, and more suppliers to check when you do a privacy review.

Signs you have outgrown the stack

One or two of these is normal. Four or five is a pattern:

• The same information is typed or pasted into more than one system.
• A spreadsheet is the glue between tools, and one person understands it.
• A customer asks about the status of an order or booking and three people check three places.
• You pay for features you never use in order to get the one you need.
• Per-user fees rise with each new colleague, even if they use the tool for five minutes a week.
• You have built workarounds for something a tool cannot do, and the workarounds keep breaking.
• Your customers see your seams: separate logins, mismatched branding, confirmation emails from different senders.

When five subscriptions are the right answer

Be honest first. Off-the-shelf tools are cheaper to start, maintained by someone else and improved constantly. If your process is common, such as invoicing, email marketing or standard bookings, a subscription is almost always the better buy. The same goes for a business that is still working out what it needs. Building software around a process you will change next quarter is expensive.

Even for portals and internal tools, check no-code products first. Providers of custom portals say this themselves: look at what a configurable tool can do before you commission anything. If it covers 90 per cent of what you need, the remaining 10 per cent is rarely worth a custom build.

What custom software costs, according to public sources

Public guides from software providers give these indicative figures. They are the providers' own claims, not audited, and shown in the currency they were published in:

A break-even check you can do yourself

Use the published figures to see why subscription savings alone rarely justify a build. Take the low end of a custom portal, GBP 21,000. A no-code portal tool at about GBP 200 a month costs GBP 2,400 a year. Maintenance on the custom build at 15 to 25 per cent is GBP 3,150 to 5,250 a year. On pure subscription cost, the custom build does not win at all.

It wins on other lines, so count those instead. Add up the hours per week spent on double entry, corrections and chasing status, and multiply by a realistic hourly cost. Add revenue lost to things the tools cannot do, such as a booking flow that loses customers or a feature competitors have. Then compare the total with build cost plus yearly maintenance over three to five years. If the result is close, buy. If the hours saved alone cover it, build.

As an illustration only: two hours a day of double entry across a team is roughly 500 hours a year. Put your own hourly cost on that and compare it with the GBP 3,150 to 5,250 a year of maintenance above. The answer can go either way, which is why the sum is worth doing before anyone writes code.

The middle path: connect before you replace

Often the cheapest step is not a new platform but better wiring between the tools you have. A workflow tool such as n8n can pass an enquiry from a form into the CRM, create the booking, send the confirmation and update the spreadsheet, so nobody retypes anything. That costs a fraction of a rebuild and removes a large part of the pain.

Replace a tool only when it is the one holding you back, for example when it cannot model your process, when its fees scale badly or when your customers see its limits. Replacing the worst offender first also gives you a test of whether custom work suits you.

A fair rule: if better wiring removes most of the double entry, wait a year before deciding on a rebuild. If the pain remains, you now have a business case based on what you saw, not on what you feared.

If you do build: what to insist on

A custom platform is an asset only if you control it. Ask for these before you sign:

• A written scope and a fixed price for the first release, not an open-ended hourly estimate.
• Delivery in stages, starting with the process that hurts most, so you see value early.
• Ownership of the code and the data, with the ability to export both.
• A named plan for hosting, backups, updates and security, with a price.
• Documentation that lets another developer take over.

What RAWR has built

RAWR builds custom web apps, client portals, booking systems and dashboards, replacing the mix of booking tool, forms, shop and spreadsheets with one system built around how a business works. Examples include LinkUp, a Swiss services marketplace where customers post requests and providers reply with CHF offers, in four languages; Swiss Meetup, a four-language events and booking platform; and RAKU Sushi in Zug, where the storefront, online ordering and an operator console were built in five weeks.

RAWR starts with a free 20-minute call and sends a fixed quote scoped in writing. Sometimes the right outcome of that call is an existing tool or a simple automation rather than a build.

Questions