Off-the-shelf software or a custom internal tool? How to tell when it's time to build

Most businesses run on off-the-shelf software, and for good reason. It's quick to set up, someone else maintains it, and it already does what thousands of other companies need. For a lot of work, it's exactly the right choice.

But businesses are rarely as standard as the software they buy. Over time your processes become your own, shaped by your customers, your team and the way you've learned to work. At some point the tools stop fitting, and your team starts working around them instead of with them. That's usually the moment to look at a custom internal tool.

Signs your tools no longer fit

• Your team keeps a spreadsheet next to the system that's supposed to hold the data.
• People copy the same information from one tool into another by hand.
• One process runs through several apps, and nobody can see the whole picture in one place.
• Someone spends part of every day on the same repetitive steps.
• Putting together a simple report means pulling data from three different places.
• You pay for a long list of features, use a handful, and still miss the one you need.

One of these on its own isn't a reason to build anything. Several of them together usually mean your process has outgrown your tools.

When off-the-shelf is still the right call

Custom software isn't the answer to everything. Stick with what you have when:

• The process is standard across most businesses, like payroll, accounting or email.
• The tool fits well and your team is happy using it.
• You're still working out how the process should run. Build once it has settled, not while it's changing every week.

What a custom internal tool can look like

"Custom software" can sound like a huge, risky project. In practice, internal tools are often small and focused on one job. Some common shapes:

• Admin systems that give your team one place to manage customers, orders or records.
• Management tools built around how your team actually assigns and tracks work.
• Workflow applications that move a request from one person to the next without email chains.
• Business dashboards that bring the numbers you check every week into a single view.
• Automation that takes repetitive work off people's plates entirely.

A custom tool doesn't have to replace everything you use either. Often the best result connects to the software you already have and fills the gap between them.

Questions to answer before you build

1. Which process, exactly? Write it down step by step, including the workarounds.
2. Who uses it, and what does each person need to see or do?
3. What does it need to connect to, and where does the data live today?
4. What would "better" look like? Less time on a task, fewer mistakes, faster answers for customers?
5. What's the smallest useful first version? Start with one process, prove it, then grow.

If you can answer these clearly, you're in a good position to build. If you can't yet, that's useful to know too, and it's exactly what the first conversation with a development partner should help with.

How to tell if it's worth building

You don't need a complicated business case. A rough picture of what the current way of working costs you is usually enough.

• Time. How many people do the workaround, and for how long each week? Small tasks add up quickly across a team.
• Mistakes. What happens when data is copied wrong or a step gets missed? Think about rework, unhappy customers and lost orders.
• Speed. How long do customers or colleagues wait for an answer that should take minutes?
• Growth. Will the workaround still hold up if the business doubles, or will it need more people just to keep up?

Write those down next to what you'd want the tool to do. The answer is often clearer than you'd expect, either way.

Common mistakes to avoid

• Trying to replace everything at once. Pick the one process that hurts most and start there.
• Building without the people who'll use it. The team doing the work every day knows where the real problems are.
• Forgetting the unglamorous parts, like who can see what, how existing data gets moved across, and what happens when something goes wrong.
• Treating launch as the finish line. Internal tools get better with use, so plan to keep improving them.

Build, buy, or both

For most businesses the answer is both. Keep off-the-shelf software where it works well, and build custom tools where your business is genuinely different. That way you get proven products for the standard work, and software built around you for the work that's specific to your business.

How we approach internal tools

We start by learning your business goals and how your team actually works. Then we define the right solution, map the workflows and the interface, and build, integrate and test the software. After launch we keep improving it based on your team's feedback. Digital change should be practical, not disruptive, so we shape the work around the size and needs of your business.

Thinking about a tool for your team? See what our internal tools work covers, read more about how we help businesses, or tell us about your process.