Buy the Commodity, Build the Seam, Never Build What Your Vendor Ships Next Quarter

The clean split

Buy without argument: telephony, e-signature, invoicing, email infrastructure, transcription, payments, scheduling. These are commodities carrying real support obligations and compliance surface you do not want to own.

Build: the glue between systems, scoring and qualification logic, the internal reports your management rhythm depends on, and anything encoding your commercial rules — pricing, matching, prioritisation. That logic is your differentiator and no vendor will model it correctly.

The arithmetic that misleads

A €300-a-month tool is €3,600 a year. The built equivalent might be forty hours of build plus two to four hours a month of maintenance. At loaded cost, breakeven lands around eighteen to twenty-four months — and the purchased tool improves for free while yours does not.

Before building, ask the vendor directly whether the capability is on the roadmap and when. If it ships within two quarters, do not build it. Vendors answer that question more honestly than people expect.

The question to ask first

Who fixes this at eight o'clock on a Monday morning in eighteen months? Ask that before asking what it costs to build. Build cost is now the smallest term in the equation and the one everyone still argues about.

An internal tool with no named owner is not free. It is an unfunded maintenance liability that comes due the week its author goes on leave. And there is a third option people skip: buy the platform and build only the configuration.