Every small company makes the same three decisions a dozen times. Build it. Buy it. Or wait.
Most teams default to one of the three and stick with it. That is usually wrong. The right answer depends on the thing, and on the moment.
The default is buy
If you are a small team, the default should be buy. Almost always. You are not in the business of running your own authentication, your own analytics, your own email delivery, your own payments. Other companies have spent a decade building those things. Pay them.
The argument for buying is not just time. It is that the thing you buy will be better than the thing you built. The company selling it has a team. You have a side project. Their version has five years of edge cases baked in. Yours has the three you thought about last Tuesday.
Buy means you are paying money instead of paying engineering hours. Engineering hours are the scarcer resource in almost every small company. The math is simple. Most teams still get it wrong.
Build when it is your edge
There is a narrow set of things you should build. They have one thing in common. They are the thing you are actually selling.
If you are a payments company, you build payments. If you are a logistics platform, you build routing. If you are a data analytics tool, you build the analytics engine. You cannot buy your product from somebody else, because then you would be selling their product, not yours.
Everything else is infrastructure. Infrastructure you buy.
The test is simple. If the thing failed, would your customers leave you, or would they not notice? If they would not notice, it is not your edge. Buy it.
Wait is the secret third option
A lot of decisions look like build or buy when they are actually build, buy, or wait.
Waiting is underrated because it feels like doing nothing. It is doing something. It is preserving optionality. The longer you wait on a decision, the more information you have when you make it. Sometimes the problem you were about to solve solves itself because the customer goes away. Sometimes a new product comes out that is better than anything you would have built. Sometimes the need you were worried about turns out to be smaller than you thought.
The mistake is waiting by accident. Letting a decision drift because nobody wants to make it. That is not waiting, that is avoiding. Waiting on purpose means saying “we are not doing this for the next sixty days, we will revisit.” It is a decision with a deadline.
A simple rule
Small team, small budget, short runway. The order is wait, buy, build.
If you can wait, wait. If you cannot wait, buy. If you cannot buy, and it is genuinely your edge, build it. If it is not your edge, do not build it.
This rule is not universal. It is a starting point. The details matter. If you want to talk through a specific decision, CTO Connect is exactly this conversation, every month, with people who have been through it.