When to build custom software, and when not to

Most businesses don’t need custom software on day one. Spreadsheets, a good CRM and a handful of SaaS tools will carry a young company a long way. The question isn’t “custom or not?” in the abstract. It’s whether the tools you have are starting to shape your business more than your business shapes them.

Start with what you already have

Before building anything, it’s worth asking a few blunt questions:

• Is the problem a tool problem or a process problem? If nobody agrees on how leads should be followed up, new software will just automate the confusion.
• Has an off-the-shelf product been configured properly? A lot of “we need custom software” turns out to be “our CRM was never set up for how we sell.”
• Can two existing tools be connected instead? An integration or automation between systems you already pay for is often faster and cheaper than a new build.

If the honest answer to all three is “we’ve tried that,” custom software starts to make sense.

Signs you’ve outgrown off-the-shelf tools

Your team works around the software. People keep side spreadsheets, copy data between systems by hand or follow a checklist that exists only because the tool can’t enforce it.

Your workflow is your advantage. If the way you deliver your service is genuinely different, forcing it into a generic tool means giving up the thing that makes you better.

You’re paying for five tools to do one job. Several subscriptions held together with manual steps can cost more, in money and in mistakes, than one system built for the job.

The product is the business. If you’re launching an app or platform, such as a marketplace, a booking tool or an AI-powered service, there’s no off-the-shelf version to buy. You have to build it.

What “custom” should actually mean

Custom software doesn’t have to mean building everything from scratch. Good custom work usually:

1. Uses proven building blocks. Authentication, payments, maps and hosting are solved problems. Use established services and spend your budget on what’s unique to you.
2. Starts small. Build the narrowest version that solves the real problem, put it in front of users, then extend it.
3. Connects to what stays. Your accounting tool, CRM and email platform probably aren’t going anywhere. The new system should talk to them through APIs rather than replace them.
4. Plans for maintenance. Software isn’t finished at launch. Budget for updates, fixes and improvements from the start.

A simple test

Write down the three tasks your team spends the most time on each week. For each one, ask: is this time spent on judgement, or on moving information around?

If most of it is moving information around, between tools, inboxes and spreadsheets, there’s almost certainly a system, automation or piece of software that would give that time back.

If you’d like a second opinion on whether to build, buy or connect, tell us what you’re working on. Sometimes the most useful answer is “you don’t need us to build anything yet.”