Build it or buy it, and how to tell

Dear founder,

Every growing store hits this question sooner or later. There's a tool you need — a subscription engine, a loyalty system, a bespoke checkout flow — and you have to decide whether to build it yourself or buy something off the shelf. Founders lean towards building far more often than they should, because building feels like ownership.

What building really costs

The upfront quote is the smallest part of the bill. What you're really signing up for is a lifetime of maintenance, and that cost never appears on the invoice.

• Someone has to fix it when it breaks, forever
• It won't update itself as platforms change
• The person who built it may not be around in two years
• Every hour on it is an hour not spent on your actual product

A bought tool spreads all of that across thousands of other customers. You're renting a whole team's ongoing effort for a monthly fee.

Build the thing that makes you different. Buy the thing that just needs to work.

When building is the right call

Sometimes it genuinely is. If the capability is your competitive edge — the thing customers come to you for and can't get elsewhere — then owning it makes sense. Nobody should build your unique magic for you.

But your inventory sync, your emails, your reviews widget? Those aren't your edge. They're plumbing. Buy the plumbing and pour your energy into the one thing only you can do.

A useful test: if you can name three companies already selling a good version of this, buy it. The market has done your research and your maintenance in advance. If you're weighing up a build and want a straight answer on whether it's worth it, request pricing and I'll help you run the real numbers before you commit.