Build or Buy, Decided Before Anyone Codes

28 July 2026 · 2 min read

blog contents
  1. The question is about the process, not the tool
  2. Where buying quietly fails
  3. Where building quietly fails
  4. The middle answer most teams need

read

Build when the process is the thing you compete on. Buy when the process is ordinary and you have just never standardised it. Most requests for custom software are really requests to avoid changing how the company works, which is the most expensive possible reason to build anything. The honest test: could a competitor copy your workflow from a screenshot and gain nothing?

The question is about the process, not the tool

Teams usually arrive with a shortlist of products. The useful conversation happens one step earlier: what does this process do that a standard one does not?

If the answer is a real difference in how you serve customers, build it. If the answer is that the current tool does not match a habit, the habit is cheaper to change than the software.

Where buying quietly fails

Off the shelf breaks down when what you sell has rules nobody else has. Unusual pricing, an approval chain with real consequences, a regulated step that has to be evidenced.

It also breaks when the glue costs more than the tools. Three products joined by someone copying between them is not a bought solution, it is a build with the worst part left to a person.

Where building quietly fails

Building fails when the requirement is still a conversation. A scope that changes weekly does not produce software, it produces invoices.

It also fails when nobody owns it afterwards. Custom software needs a person whose job includes it, or it decays into the thing everyone works around.

  • The requirement is not written down yet
  • Nobody internally will own it after launch
  • The advantage disappears the moment it is copied
  • A standard tool does most of it and the rest is habit

The middle answer most teams need

The usual outcome is neither: buy the ordinary parts, build the one step that is genuinely yours, connect them properly.

That keeps the surface you have to maintain small, which is the real long term cost of any custom system.

questions

How do I know the process is really an advantage?

Describe it to someone outside your company in two minutes. If they say every business does that, it is a workflow, not an advantage. Advantages survive being explained out loud.

Can we start with a tool and build later?

Usually yes, and it is the safer order. A few months on something standard produces the written requirement a build needs anyway, at a fraction of the cost of discovering it in code.

What about building on top of a platform?

A reasonable middle path, with one caution: you inherit that platform's limits and its pricing decisions. Check what happens to you if either changes, before you depend on it.

More on this track

  1. What You Own When a Project Ends Handover is the clause nobody reads until they need it. A complete one is four things: source code in a repository you control, accounts and domains registered to you, documentation a new developer can start from, and a period where the previous team still answers questions. If any of the four is missing, you are renting your own product. 12 August 2026 · 4 min read
  2. Translation Is Not Localisation Translation swaps the words. Localisation changes the assumptions underneath them: currencies, name and address formats, dates, reading direction, what counts as polite, and which examples make sense at all. A perfectly translated page can still feel foreign, and that feeling costs conversions long before anyone can name why. The parts that break are rarely the sentences. 9 July 2026 · 2 min read
  3. Why Your MVP Keeps Growing An MVP grows because nobody wrote down what it was for. Without a single task it has to support, every request sounds equally reasonable and the honest answer to each one is yes. The fix is not discipline, it is a definition: name the one task a real user must be able to finish, then judge every request by whether that task works without it. 24 June 2026 · 2 min read