Commercial Growth Strategy
Many strategy documents describe ambition. They name growth targets, target markets, and initiatives, but leave open what those targets are economically based on and what conditions have to be met.
A strategy only becomes defensible where it’s testable.
It Makes Decisions, Not Just Statements
A commercial strategy decides which segments to prioritize, with what value proposition and through what route to market. Just as important is the flip side of that decision: which segments, inquiries, and paths are deliberately not pursued.
Without that boundary, there’s no prioritization — just a collection of intentions.
It’s Tied to Assumptions You Can Test
Every strategy rests on assumptions about the market, buying behavior, competition, and internal capability. Making those assumptions explicit means they can be tested and corrected along the way.
Left implicit, the strategy becomes a matter of belief — and course corrections start looking like weak leadership instead of learning.
It’s Connected to Organization and Steering
A strategy with no consequence for roles, processes, and metrics changes nothing. Conversely, quality shows up when the strategy makes clear how sales is led and measured.
That makes the strategy testable in day-to-day business — not just at year-end.
Turn the Strategy into a Decision Record
Start with one decision: which customer segment should receive the next share of commercial effort? Describe the customer problem, the people involved in buying, the buying process, the value offered and the route to market. Record the alternative you are deferring and why. This makes the choice specific enough to challenge.
Separate evidence from assumptions. For each important assumption, document what is known, what would disprove it, who will investigate and when it will be reviewed. Customer conversations, won and lost opportunities, delivery records and small tests can all contribute evidence. A positive conversation alone does not establish willingness to buy.
Compare Opportunities Using Explicit Criteria
Customer need: is the problem important enough to prompt action, and is there a recognisable buying process? A stated interest without an owner, budget discussion or next step remains an open question.
Differentiation: does the offering provide a meaningful advantage over the alternatives, including doing nothing? Identify what the customer would actually gain rather than listing features.
Economics: could the expected revenue justify acquisition, onboarding, delivery and support under plausible assumptions? Show missing cost information explicitly and treat the conclusion as provisional until those gaps are addressed.
Ability to deliver: does the team have the capacity and capabilities required? Record dependencies and work that would displace other commitments.
Decision conditions: what evidence would lead you to stop, revise or expand the approach? Keep evidence beside each answer instead of hiding uncertainty in a precise-looking score. These criteria support judgement; they are not a universal pass mark.
An Illustrative Choice Between Two Segments
Consider a hypothetical B2B software provider choosing between smaller buyers and large enterprises. This is an illustrative scenario, not a client case or a report of observed results.
Smaller buyers may be easier to reach, but the relationship between contract value and onboarding or support effort is unproven. Enterprise contracts may be larger, while procurement reviews, security requirements and integration work could exceed the team’s current capacity. Contract size alone does not resolve the choice.
Define a limited test for each segment, record the actual work required and compare the evidence against the agreed criteria. If enterprise requirements exceed available capability, narrow or defer that offer. If support effort undermines the smaller-buyer economics, revise the offer or service model before expanding. The purpose is to learn which assumptions hold, not to make both segments appear attractive.
Connect the Decision to a Review Rhythm
Before a test starts, assign an owner to each unresolved assumption and set a review date. Review customer signals, opportunity progress and delivery effort together. A fuller pipeline is not sufficient evidence if buying decisions stall or delivery becomes uneconomic.
At each review, record whether to continue, change or stop, alongside the evidence for that decision and the next check. Retain the history of rejected options so that new team members can understand the reasoning. This turns strategy into a working decision process rather than a presentation that is only revisited at year-end.
A strategy that rules nothing out decides nothing.