Blog
Lessons

Buy or build your infrastructure: the leverage decision

Tools laid out on a workshop bench
Photo: Wolfgang Staudt from Saarbruecken, Germany · CC BY 2.0 · Source: Wikimedia Commons

Every solo operator spends time on tooling decisions that do not move revenue. The mistake is not in choosing wrong; it is in pretending the choice is technical when it is really capital allocation.

Build is appealing because you understand it

A solo operator who can code looks at a SaaS tool and thinks: I could build this in a week. And they probably can. So they build it. They save themselves 30 a month. They feel smart. Six months later, the tool broke in production because of a library update they did not know about. Now they are debugging it at 3 AM instead of filing an issue with support.

The appeal of building is practical; it is also psychological. You understand your own code more than you understand someone else's product. Building feels like control. Buying feels like dependency. Both feelings are real; only one of them is relevant to the decision.

The real cost of building

Building a tool takes time. Consider a hypothetical calculation: an operator estimates five hours to build a customer database, but the total comes to thirty hours: five for the initial build, ten for making it reliable, five for basic security, five for fixing edge cases, and five for documentation so you remember how it works six months later.

If you bill at 150 an hour, thirty hours costs you 4,500 in foregone revenue (or the 4,500 you did not earn because you were building instead of selling). In this hypothetical comparison, an off-the-shelf option costs 20 to 100 a month. If you keep the tool for five years, you spend 1,200 to 6,000 on the SaaS. At the lower end of that hypothetical vendor price range, buying costs less than the initial build alone; at the upper end, the comparison depends on ongoing maintenance and other costs.

Most solo operators do not calculate this. They see a monthly SaaS bill and think "waste." They see a weekend spent building and think "investment." Calculate the full comparison before deciding.

Maintenance is the real cost

Building is not done. Maintaining is the job. A custom database works fine until the day your hosting company changes their PHP version and your code no longer compiles. Now you have an urgent problem on your hands. A SaaS tool? The vendor handled it.

Security updates. Scaling issues. Data backups. Performance degradation when you have more customers. All of these are someone else's problem if you buy. All of them are your problem if you build.

A solo operator who built their own payment processing system now has to stay current on PCI compliance. A solo operator who uses Stripe does not. That 30 a month isn't just a charge; it is an insurance policy against having to understand something that could break your business if you get it wrong.

The legitimate reason to build

There is one: the tool does not exist or all existing versions have a deal-breaker problem. If your business model requires something off-market, you build it. If you have found that Stripe cannot do what you need and you have evaluated Paddle, Square, and every other processor, then maybe you have a reason. Do not pretend it is a reason if you have not looked.

The other legitimate reason is that the tool is your competitive moat. If you are selling analytics software and your analytics engine is yours to own, you cannot outsource it. But notice: that is different from "I can build this faster." Moat tools are things your customer cares about. Build-vs-buy infrastructure tools are things only you care about.

How to think about the decision

A framework for solo operators

If you are a solo operator and thinking about building a tool: ask whether this tool is your product or infrastructure for your product. If it is infrastructure, compare buying with the full cost of building and maintaining it; a revenue percentage alone does not establish payback. If it is your product, build it, but understand that you are now maintaining it forever. Do not pretend infrastructure is product so you can justify building when you just like the engineering work.

Buy the boring stuff. Database, email, hosting, payment processing, analytics, CRM. Your time is better spent on something a customer cares about.

Build only when buying is impossible or when the price of buying is threatening your business model. Every other time, the decision is capital allocation. And for a solo operator, the capital you should allocate to revenue is always worth more than the capital you allocate to code that does not earn it.

Common questions

Is it ever worth building my own instead of using a SaaS?

Yes, but only in specific cases. Compare the vendor's total cost with the time and money needed to build and maintain an alternative. Calculate payback from those estimates. If the SaaS has changed its terms three times in five years or is disappearing, building might be the safe choice. If the tool is your competitive moat because no off-the-shelf option does what you need, then building is not optional. Most of the time, the answer is buy. Building is expensive in time, and time is what solo operators cannot replace.

How do I know if I am building because I need to or because I like building?

Track the outcome: Did building this tool improve the business or just move the work around? Compare the value of time saved with development time, recurring maintenance, and the vendor fees avoided over the same period. Include migration and support costs on both sides. The measure is the full cost and business benefit, not the satisfaction of having built something.

What if I build it and then need to maintain it forever?

You will. Building is not a one-time cost. It is a commitment to maintain, update, secure, and debug that code until you retire the tool or the business. A SaaS tool means the vendor maintains it. When you build, you maintain it or pay someone else to. Include that continuing work in the comparison before choosing to build.

Every property in the Don Gastón portfolio is independently live; it is built, deployed, and operated by one person.

See what's live in the portfolio