Where will the growth come from?

Revenue, profit, market share and customer count can move in different directions. Even “revenue growth” needs a defined period and starting point.

Suppose a workflow-software business has $200 million in year-end annual recurring revenue, or ARR. It wants to reach $250 million by the end of next year, a 25% increase.

ARR is the annualised recurring value of the business at a point in time. It is different from the revenue earned across the year. A contract beginning in December can make a substantial contribution to year-end ARR while generating only a small amount of that year's recognised revenue.

That distinction matters when comparing initiatives. Use the metric in the objective consistently, and check whether management also has a profit or cash constraint.

Assume management expects the current plan to produce 8% ARR growth. That would take the business from $200 million to $216 million. The additional growth strategy must therefore close a $34 million gap.

Do not accept the 8% simply because the business grew at that rate last year. Ask what supports it: renewals, customer losses, expansion in existing accounts, signed new contracts and the sales pipeline.

If the forecast already includes a planned price increase, you cannot add the same increase again as a new opportunity. If it assumes customer retention improves, identify the work and resources required to achieve that improvement.

A forecast is a set of operating assumptions. Making those assumptions visible prevents the growth plan from resting on an unexplained number.

For the software company, the useful questions are concrete. Can more employees use the product within existing accounts? Will customers pay for a premium analytics module? Can a partner reach midmarket buyers the current sales team does not serve? Could a new geography support a repeatable sales motion?

A simple map helps keep the possibilities broad:

Use this to generate and organise possibilities. Then narrow the work around the client's starting position and capabilities. An existing customer relationship helps only if it supports selling something those customers value.

Suppose the first estimates are:

The two existing-customer initiatives contribute $18 million together: $12 million plus $10 million, less $4 million of duplicated revenue. Add $12 million from partner acquisition and the on-time portfolio contributes $30 million.

The result is $246 million ARR, leaving $4 million of the target unfilled.

Do not quietly round that up to a successful plan. Say that the current options support 23% growth, and explain what additional evidence or opportunity is needed to reach 25%.

The overlap deduction needs a commercial explanation. Here it removes the same analytics revenue counted under two initiatives. Merely selling two different products to the same customer would not, by itself, be double counting. Ask whether the same spend, contract or volume has entered the model twice.

A spreadsheet can add opportunities that the organisation cannot deliver simultaneously. The enterprise upsell and analytics launch may both require the same implementation team. The partner channel may depend on a product integration that is not yet built.

Translate each attractive initiative into its main requirements: people, product work, sales effort, launch spending and lead time. Then test the combined plan against the resources available.

A $12 million channel opportunity that requires 600 new customers at $20,000 ARR each has a useful operational implication. Can the partner source, close and onboard 600 customers before year-end? What conversion rate and sales cycle does that imply?

If only 300 can become live customers in time, the year's contribution falls to $6 million. That changes the portfolio decision even if the long-run opportunity remains attractive.

Our resource-allocation framework explains how to compare competing uses of a constrained team or budget.

The objective may be ARR, but management still needs to understand what buying that growth costs.

For a simplified comparison, suppose the partner's 600 new customers each produce $20,000 annual revenue and $12,000 annual contribution before acquisition spending. Acquisition costs $18,000 per customer. At a steady contribution rate, acquisition payback is 18 months.

That calculation assumes customers stay and the contribution arrives as expected. A channel with heavy early cancellations or substantial onboarding costs needs a different forecast. If management requires payback within a year, the proposal needs better economics or a deliberate exception to that constraint.

Keep the timelines distinct. Annualised contribution at year-end is not the cash earned during a staggered rollout. Growth can meet an ARR target while consuming more cash than the company can fund.

This is why I would present the amount, timing and economics together. Ranking opportunities solely by their largest revenue estimate hides the most consequential trade-offs.

A useful recommendation from the initial numbers would sound like this:

“Prioritise the existing-customer offer and partner acquisition, subject to validating demand and delivery capacity. Together they add $30 million ARR above the base and take us to $246 million. That leaves a $4 million gap, so the current plan does not yet support the full target. I would first test whether we can improve retention beyond the base forecast or expand the feasible partner opportunity. Geographic expansion may support later years, but it cannot close next year's gap.”

The answer is confident because it distinguishes what the plan delivers from what remains unresolved. It does not need an invented final lever to make the arithmetic look tidy.

If retention is the next question, use the churn framework to identify what is actually causing losses. To practise assessing a single growth route, try EdTech Paid Acquisition and explain how you would connect customer acquisition to the growth target and its economics.