Most organizations don’t choose to end up with a dozen software subscriptions. It happens slowly. A CRM here, a help desk there, a tool to connect the two, and a spreadsheet to cover whatever falls between them. Eventually, someone asks whether custom software would serve you better.
Each one made sense when you signed up. But at some point the question changes from “which tool should we use?” to “why does this feel so hard?”
We’ve been asking ourselves that question this year. Here’s what we’ve learned, and how to tell whether it’s time to rethink your own tools.
The signs your tools don’t fit anymore
Off-the-shelf software is built for the average organization. That’s its strength, and it’s also the catch. The further your work drifts from “average,” the more your team bends around the tool instead of the other way around.
A few signs we see often:
- The same information lives in three places. Someone updates a client’s contact in one system and forgets the other two. Nobody is sure which one is right.
- You’re paying for connections between tools. If you rely on automation services just to make your software talk to itself, that’s a cost on top of a cost.
- Your team keeps side spreadsheets. Those spreadsheets usually hold the thing the official tool can’t do. They’re a map of where it falls short.
- New staff need a guided tour of workarounds. If onboarding means explaining “we don’t use that button, we do this instead,” your process and your tools have drifted apart.
None of these mean you need custom software. But they do mean it’s worth asking the question honestly.
When subscribing is still the right call
We’ll be upfront: for most needs, a good subscription is the better choice. It’s faster to start, someone else maintains it, and it improves without you lifting a finger.
Subscribing makes sense when:
- Your process is fairly standard for your sector
- The tool is used by a small part of your team
- You’d rather adapt your workflow than maintain software
- The cost of switching later is low
Email, accounting and file storage almost always belong in this category. There’s little to gain from rebuilding them.
When custom software starts to make sense
Building earns its place when the tool sits at the centre of how you work, and your way of working is part of what makes you good at it.
That usually looks like:
- Your process is your edge. How you serve members, manage programs or support clients is specific to you, and generic tools flatten it.
- Everything revolves around one record. A client, a member or a project touches every team, and you want one place that tells the whole story.
- You’re already paying for the patchwork. Add up the subscriptions, the connectors and the staff time spent copying data between them. The number is often bigger than expected.
What we’d tell anyone considering it
If you do decide to build, a few lessons have stuck with us:
Start smaller than feels comfortable. The first version should replace one painful thing really well. Trying to replace everything at once is how custom software projects stall.
Release often and listen closely. Small, frequent improvements shaped by the people actually using the tool beat a big launch built on assumptions.
Bring your data with you. Years of notes, history and context live in your old tools. Planning how to move it is as important as anything you build.
Plan for ownership. Custom software isn’t “done” at launch. Someone needs to care for it, the same way you’d care for a website.
The real question
Build or subscribe isn’t really a technology decision. It’s a question about how your organization works best, and whether your tools are helping or getting in the way.
If you’re not sure where you land, we’re always happy to talk it through. Sometimes the answer is a better subscription. Sometimes it’s something built for you. Either way, it should fit the way your team actually works.
