What's actually going on
The invoice arrives. The tool renews. The part of the job it was meant to cover is still finished by you, in a spreadsheet, on the side.
That's a normal place to be. Most small businesses pay for several tools that each do most of a job, and a person fills the gaps. Nobody planned it. It accumulated.
Prices move, too. Xero's notice to Australian customers on 1 July 2024 said some on older plans would pay more when moved. Those increases were held until July 2025 (Xero, 1 July 2024).
So wanting to own the thing instead is reasonable, not naive. People who know their own work can now get plain tools built quickly.
The worry that follows is fair too. A home-made tool nobody looks after can be a bigger problem than the invoice. So answer that worry first.
The questions to answer before anyone builds anything
Whether it's built by you, a friend, or someone you pay, the tool is only as safe as these four answers. They go on one page before it exists.
- Who maintains it: a named person, not "whoever's free"? What happens the week they're away?
- What does support cover, what does it cost, and what isn't included? Upkeep exists for all software. The honest version is written down and priced, not hidden in a fee that quietly grows.
- How would you leave? Your data comes out in a format another tool can read, and the code is yours to hand on. If either answer is fuzzy, that's lock-in, not ownership.
- What rules does it follow? If the logic won't fit on one page, only the person who built it can maintain it.
Then four security basics for any small app. Australia's Cyber Security Centre names three starting points for small businesses. These are two-step login (multi-factor authentication), keeping software updated, and backups. The fourth is ours: don't store data you don't need.
- Real logins. One account per person, multi-factor authentication on, no shared password on a sticky note.
- Backups you've tested restoring. A backup nobody has restored from is a hope, not a backup. Same guide, same top three.
- Updates someone owns. The libraries under a small app age like anything else, and patching is two of the Essential Eight. Name who does it and how often.
- Least data. Don't store what you don't need. A tool that never held a customer's date of birth can't leak it.
Handle those four and the "home-made means hackable" fear is mostly answered. Skip them and no clever feature makes up for it.
Keep, clean, connect, or convert, applied to building your own
Keep the tool if it does the job and the gap is a habit, or a setting nobody switched on. A renewal invoice is annoying. It isn't evidence.
Clean the spreadsheet that fills the gap. The real cost is usually the copying and reconciling around the tool, not the subscription itself. Tidy that first, and time it.
Connect the two tools before replacing either. Most "build our own" moments are really "these two should talk to each other", and sometimes the answer is an integration that already exists.
Convert, meaning build your own, only when three things are true at once. The manual gap is stable, so it has looked the same for months. It's written down, so the rules fit on a page. The price you pay is mostly for features you never use. Then build small: one workflow, with the questions above answered first.
What "done" looks like
Done is measured, not felt.
Pick a date. Write down the renewal you didn't pay and the hours the gap used to take each week. Read both on that date.
If the hours are down and the four basics still hold, it worked. If not, that's useful too: it tells you which of keep, clean or connect you skipped.
The invoice lands again either way. What you get to choose is whether you're still finishing the job by hand when it does.