Buy vs build
Definition
Buy vs build is the choice between acquiring a business or product that already exists and creating one yourself. Buying costs money and gives you customers, revenue and a record from the first day. Building costs time and gives you full control with no customers. The real comparison is certainty against cost.
Buy vs build is the choice between acquiring something that already exists and making it yourself. For someone who wants to own a small online business, it means paying for a product with customers or spending months writing one and looking for the first customer afterwards.
What you are comparing
It looks like a comparison of two prices: the asking price against the cost of your own time. That misses most of it. The code is usually the cheapest part of a small online business to reproduce. What takes the time is everything around it: the search rankings, the store reviews, the customers who already pay, the pricing that has been tested, the bugs that real users have already found.
| Buy | Build | |
|---|---|---|
| Main cost | Money, upfront | Time, spread out |
| Customers on day one | Yes | No |
| What you know in advance | Past revenue and costs, which you can check | Your own estimate |
| Main risk | The record is wrong, or revenue depends on the seller | Nobody wants it |
| Code | Someone else's, with their decisions in it | Yours |
| When income starts | At handover | Unknown |
A worked example
Take a developer weighing two options.
Build: they estimate 500 hours to make the product. At $60 an hour, which is what they could earn freelancing in that time, that is $30,000 of their own labour. At the end they have a product and no customers.
Buy: a similar product is listed at $30,000 with $10,000 of profit over the last twelve months. That is 3 times trailing annual profit, inside Indiemaker's guide range of 2.7 to 3.2 times for SaaS and tools. The range is a guide, not a valuation.
The outlay is the same. The difference is what is known. The bought product has a year of figures to check. The built one has a forecast. The $30,000 of labour is its replacement cost, and it tells you what the code is worth to rewrite, not what the business is worth to own.
The estimate is also the weak point on the build side. If 500 hours turns out to be 800, the build has cost $48,000 before the first sale.
Where it bites
Buying has its own ways to go wrong. The code may carry technical debt that makes every change slow. The revenue may rest on the seller's personal audience. The figures may be owner-declared and unchecked. On Indiemaker, revenue shown as Revenue Verified comes from a payment provider the seller has connected. Anything typed in by the seller is owner-declared, and you confirm it yourself in due diligence.
Building goes wrong more quietly. The product gets finished and nothing happens.
Why it matters when you acquire
The choice is not all or nothing. Many buyers acquire a small product that already has customers and then build on top of it, which is called buy then build. If you are leaning towards buying, how to acquire a micro-SaaS covers the steps, and current listings are at /browse/.
Related: buy-then-build, replacement-cost, how-to-acquire-a-micro-saas, technical-debt
See what a business at this level is listed at.
Everything on sale between $50,000 and $150,000, on the same fields.