When a company commits to a new operating region, one of the CRO’s first responsibilities is to build the commercial plan. They estimate the opportunity, determine where to invest, model the organisation required to execute and translate those assumptions into revenue expectations.

Every one of those planning activities is built on a series of assumptions, many of which are well understood and rigorously tested before the investment is approved. In my experience, one assumption consistently receives less attention than it deserves, despite having a significant influence on whether the expansion succeeds. It is whether the organisation is genuinely ready to operate successfully in that region.

The consequences of getting that assumption wrong rarely appear in the expansion plan itself. They emerge months later, when the regional team begins qualifying opportunities that look commercially attractive but prove impossible to pursue because the business cannot yet support the customer’s requirements. Over the best part of a decade, I’ve seen this pattern repeat across global software companies. Sometimes it was data residency. Sometimes it was product architecture, localisation or engineering priorities that had not kept pace with the company’s ambitions. The specific constraint changed, but the commercial outcome was remarkably consistent. Parts of the territory looked available on paper but were never genuinely executable.

The challenge is that commercial planning often assumes the organisation will be able to support the customers it intends to pursue. In reality, many of the capabilities that determine success are owned by Product, Engineering, Operations and other parts of the business rather than the commercial organisation. Commercial planning depends on organisational capability, even though much of that capability sits elsewhere in the business.

Planning for a new region should therefore include validating organisational capability alongside commercial opportunity. Revenue targets, hiring plans and investment decisions are more credible when they are based on evidence rather than assumptions. Over time, I’ve started referring to this discipline as Expansion Readiness.

When I start an Expansion Readiness review, my first question is simple: What product or technical limitation would force our team to disqualify an otherwise ideal customer in this operating region?

If the answer is unclear, I would not yet be comfortable committing revenue targets to the Board.