The Choice Every Expansion Plan Comes To
At some point in a growth conversation, someone asks the question that decides everything else: do we build our own operation in this market, or do we acquire one that already exists?
It sounds like a financial question. It gets treated like one too, with spreadsheets comparing the cost of a greenfield team against the price of a target company. But I have sat on both sides of this decision across very different businesses, and the spreadsheet is rarely what settles it. What settles it is how honest you are about what you actually have time for.
What Buying Really Buys You
Buying a business in a new market gets you three things fast: people who already understand the local rules, relationships that took someone else years to build, and revenue on day one instead of a projection.
What it does not get you is a team that already works the way you work. You inherit habits, loyalties, and a culture that formed without you in the room. Some of that is fine. Some of it will fight you for the next two years. I have watched leaders assume an acquisition is finished the day the deal closes, when the real work of making two groups pull in the same direction is only just starting.
What Building Really Costs You
Building your own operation gives you a team shaped around your standards from the first hire. Nobody is unlearning someone else’s way of doing things. But it is slow, and slow is expensive in ways that do not always show up on a budget line.
While you are hiring, training, and learning a market’s instincts, a competitor who bought their way in is already selling. In a market where timing matters, that gap can cost more than the premium you would have paid for an acquisition.
The Question I Ask Before Either
Before I recommend one path over the other, I ask a narrower question than “build or buy.” I ask: what do we actually not know about this market yet?
If the honest answer is “we don’t know how customers here make decisions, who they trust, or how the category works,” that is a knowledge gap, and acquiring a team that already has that knowledge usually closes it faster than hiring and training your own.
If the honest answer is “we know the market, we just don’t have people on the ground,” that is a capacity gap, and building tends to serve you better, because what you are missing is hands, not judgment.
Most leaders skip this question and go straight to comparing costs. That is how a company ends up acquiring a business to solve a problem that was never really about knowledge at all, and then spends two years discovering the fit was wrong from the start.
My Rule of Thumb
If I cannot describe, specifically, what a new market’s customers expect and why, I lean toward acquiring. Paying for judgment I do not have is usually cheaper than guessing my way to it.
If I already understand the market, and the gap is simply that we are not there yet, I lean toward building. Buying a team in that situation usually means paying a premium for local knowledge I did not need, and then managing a culture clash I did not need either.
Neither path is safer by default. Each one has a different failure mode, and the leaders who get this decision wrong are usually the ones who picked a path before they named which failure they were more willing to risk.
Where I Have Seen This Go Wrong
The clearest mistake I have seen is choosing based on speed alone. Buying feels faster, so it gets picked even when the real gap was capacity, not knowledge. The acquired team then gets asked to operate exactly like the parent company, which defeats the reason you bought local expertise in the first place.
The second mistake runs the other way: building from scratch in a market where the real barrier was never headcount, it was understanding a customer base that behaves nothing like the one back home. No amount of hiring fixes that on its own. You end up with a well staffed team that is still guessing.
Get specific about which gap you are actually closing before you choose how to close it. The method follows the problem. It should never be the other way around.



