I build custom software for a living, and I still tell some clients not to build. If an existing tool does the job, it is usually cheaper, faster and someone else keeps it running.

But there is a point where the off-the-shelf tool starts to cost more than it saves. This is how I help a business find that point.

Buy what makes you the same as everyone else. Build what makes you different.

Start with an existing tool when

  • the process is common: invoicing, payroll, email, a basic shop, a simple CRM
  • your team can live with how the tool works, even if it is not perfect
  • the number of people using it is small
  • you are still figuring out how the process should work

That last one matters most. If the process is still changing every month, a cheap tool lets you learn without paying for software that will be wrong in half a year.

Consider building when

  • your team spends hours a week copying data between tools
  • the process is the thing that makes your business different, and the tool forces you into someone else's way
  • you need several tools glued together with spreadsheets to get one answer
  • per-user pricing keeps growing faster than the value you get
  • you need your data in one place, in a shape you control

The common pattern is a business that started with three or four tools and a shared spreadsheet, and now someone's full-time job is keeping them in sync. That is usually a sign.

The middle path is often the right one

It is rarely all or nothing. Many good setups keep the standard tools and build one small piece around them:

  • an internal tool that pulls data from your existing systems into one screen
  • a small integration that moves data automatically instead of by hand
  • a customer portal on top of a system you already use

This keeps the boring parts boring and puts your money where your process is actually special.

Questions to answer before you decide

# build or buy
what does the process look like today, step by step ✓
where does the time actually go ✓
which tools already hold the data ✓
who uses it and how many people ✓
what happens if the tool's vendor changes price or shuts down ✓
who will look after it after launch ✓

The last question is the one people skip. Custom software needs someone to keep it updated. That can be your team, or someone on a retainer, but it has to be someone. I wrote about what happens when nobody does in why unmaintained apps break on a Tuesday.

What building well looks like

If the answer is build, start small. One process, one group of users, done properly. Write down what done means first. I describe how I do that in from a Notion PRD to a signed-off UAT.

Then grow it once people use it, not before.

Not sure which side you are on

Tell me what the process is and which tools you use today. Describe it on the scope page or get in touch. If an existing tool fits, I will say so.