The length of our walk changes what I need to bring. A quick neighborhood loop is straightforward. A longer trail requires more water, more time, and a reasonable assessment of whether everyone has the energy.
I cannot announce a two-hour adventure, pack for twenty minutes, and then act surprised when Dusty and Tanner stop cooperating. Growth plans do that surprisingly often.
Leadership approves an ambitious revenue goal. The team proposes several growth motions. Then the budget covers media and software while the people required to deliver the customer experience remain completely booked.
The ambition may be real. The preparation is not.
In Orchestrate, the O in my G-R-O-W-T-H Framework, we connect the growth direction selected during Reframe to the operating design required to execute it. That includes the route to market, the channels, the information flows, the team handoffs, and the full resource requirement.
A growth plan is not ready because leadership agrees with the destination. It is ready when the organization understands what the trip requires.
Start With the Growth Outcome
Begin by writing the growth outcome at the top of the whiteboard. Then list the motions expected to contribute to it. For example, imagine a hypothetical software company planning to move into larger enterprise accounts. Its proposed plan includes account-based marketing, executive events, and partner selling.
That combination may sound reasonable. It is still incomplete. Larger accounts may require technical validation, engagement across more stakeholders, procurement support, a stronger implementation plan, and more customer-success capacity.
If those resources are missing, generating more interest can create a longer queue rather than healthier growth. The first question is not simply, “How much should we spend on demand?” The more useful question is, “What must be true across the entire customer route for this growth motion to work?”
Map the Work From First Contact to Sustained Value
Under each growth motion, map the work required to move a customer from first contact to sustained value. Do not stop at lead generation or opportunity creation. Include every function that contributes to the experience:
🐕 Marketing: Account insight, messaging, content, events, media, follow-up, and orchestration
🐕 Sales: Account coverage, discovery, buying-group coordination, commercial progression, and negotiation
🐕 Solution engineering: Technical discovery, validation, demonstrations, evaluations, and risk reduction
🐕 Product: Product readiness, integrations, usability, and gaps that affect the proposed motion
🐕 Customer success: Onboarding, adoption, value realization, retention, and expansion support
🐕 Partner support: Recruitment, enablement, joint planning, technical support, and commercial coordination
🐕 Data foundation: Account data, customer signals, integrations, measurement, and reporting
This is where a plan that looked affordable can become more honest. The media line may be funded. The executive event may be funded. The partner program may have a target.
But who prepares the technical proof? Who supports the evaluation? Who coordinates the buying group? Who handles implementation if the first wave converts?
If the answer is the same fully booked person in every row, the plan has a capacity problem.
Calculate Capacity Before Demand Arrives
Now estimate how much work the team can complete properly. Ask practical questions:
🐕 How many target accounts can the team work with the promised level of relevance?
🐕 How many executive events can the team support without weakening follow-up?
🐕 How many technical evaluations can run at the same time?
🐕 How many partner opportunities can receive meaningful enablement and support?
🐕 How many customers can begin implementation without service quality slipping?
🐕 How many customer-success plans can the team manage while protecting existing accounts?
These questions expose the practical limits of the plan. Suppose the company can generate ten qualified evaluations a month, but solution engineering can support only four. That is not merely an execution detail. It is a design decision.
The company might:
🐕 Narrow the target segment so the available capacity is focused on the accounts most likely to fit.
🐕 Standardize part of the evaluation so fewer activities require custom support.
🐕 Add capacity through hiring, reassignment, or another deliberately chosen resource model.
🐕 Phase the investment so demand does not arrive faster than the organization can respond.
What the company should not do is ignore the constraint until the queue is full.
Choose deliberately before the demand arrives.
Subscribe for more resources on this topic here
Capacity Is Part of the Customer Experience
Capacity planning can sound like an internal operating exercise. The customer experiences the consequences directly.
When capacity is misaligned, response time grows. Technical questions sit unanswered. Evaluations stall. Implementation dates slip. Customers repeat context to new people. Existing accounts receive less attention because the team is chasing new demand.
The company may report healthy top-of-funnel activity while the buying and adoption experience deteriorates. More demand is not automatically better if the system cannot convert and support it. This is why the full route matters. The team must be able to deliver the experience it is creating demand for.
Connect Spending to Growth Economics
Once the work and capacity are visible, connect spending to the economics of the priority segment. For each segment, consider:
🐕 Acquisition cost: What does it take to identify, reach, engage, sell to, and win the customer?
🐕 Expected contract value: What revenue is reasonably associated with the account or segment?
🐕 Gross margin: How much economic value remains after the direct cost of delivering the product or service?
🐕 Implementation effort: How much technical, operational, and customer-facing work is required to get the customer live?
🐕 Retention: How likely is the customer to continue if the promised value is delivered?
🐕 Expansion potential: Is there credible evidence that the relationship can grow?
Use the evidence available. If a number is uncertain, show a range and state the assumption. Do not convert uncertainty into false precision merely because the budget template expects one number.
A large contract can look attractive until the organization accounts for extensive customization, long technical evaluations, implementation complexity, and ongoing support. A smaller account can be attractive when adoption is efficient, retention is strong, and expansion is credible. The channel budget alone cannot tell leadership which route creates healthier growth.
Organize Investment Into Three Types of Commitments
Not every investment deserves the same level of commitment on day one. Organize the plan into three categories.
1. Required Commitments
These are the investments that must exist for the route to be viable. For an enterprise growth motion, technical proof and implementation readiness may be required commitments. Without them, the company may create interest that it cannot convert or support.
2. Limited Tests
These are ideas the team can test at a controlled scale. A new executive event format might begin as a limited test. The purpose is to learn whether it reaches the right people, supports the intended decision, and creates a useful next step.
3. Evidence-Gated Expansion
These are investments that receive additional funding only after defined evidence appears. A broader media program might depend on whether the first target accounts engage and progress. Expansion should follow evidence, not enthusiasm alone.
Each test needs a decision date and an evidence threshold. Otherwise, a small experiment can quietly become a permanent expense. For every test, write down:
🐕 What assumption are we testing?
🐕 What evidence would support continued investment?
🐕 What evidence would cause us to stop or redesign it?
🐕 When will the decision be made?
🐕 Who owns the decision?
This gives leadership a disciplined way to learn without treating every idea as a permanent budget line.
Account for Shared Foundations
Some investments support several growth motions. Data cleanup can improve account selection, sales coordination, customer onboarding, and measurement. Integration work can support multiple customer routes.
Messaging development can improve events, sales conversations, partner enablement, and digital experiences. Partner enablement can support several segments or offers. These shared foundations should appear in the plan.
Assign their costs thoughtfully rather than pretending they belong entirely to one campaign. If shared work disappears inside a campaign budget, leadership may underestimate its strategic importance or fund it inconsistently.
Check the Timing, Not Just the Annual Total
An annual budget can balance on paper while the first quarter is impossible. The sequence matters. If the partner program requires enablement in January and customer onboarding capacity in March, those dependencies belong on the roadmap.
If technical validation must be standardized before a media program expands, show that order. If a new segment requires messaging, sales training, product support, and implementation readiness, do not pretend those activities can all begin at full scale on the same day. Ask:
🐕 What must be ready first?
🐕 Which resource is required in each period?
🐕 Where is the same person's time committed twice?
🐕 Which activity should wait until a dependency is complete?
🐕 What happens if hiring, integration, or enablement takes longer than expected?
Preparation includes sequence, not just totals.
Invite Finance and Functional Leaders to Challenge the Plan
A growth budget improves when the people responsible for delivery challenge the assumptions before approval. Bring finance and the functional leaders into the working session. Ask:
🐕 Which assumptions are optimistic?
🐕 Where is someone's time counted twice?
🐕 What happens if conversion is lower than expected?
🐕 Which customer experience will weaken if demand is higher than expected?
🐕 What gets deferred if the priority changes?
🐕 Which costs are missing because they sit in another function?
This is not an invitation to reduce every plan to the safest possible version. It is a way to distinguish an informed bet from an underfunded promise.
Assign Owners to the Unresolved Questions
Before everyone leaves, assign owners and dates to the open economics and capacity questions. For example:
🐕 Marketing revises the growth assumptions and maps the complete motion.
🐕 Sales validates account coverage and the workload required to coordinate the buying group.
🐕 Solution engineering confirms evaluation capacity and standardization options.
🐕 Customer success checks onboarding and adoption capacity.
🐕 Finance helps establish investment gates and tests the economic ranges.
🐕 Product identifies dependencies that could affect validation or implementation.
Everyone contributes, but one person must own the completed plan and reconcile the answers. Then send the recap with decisions, owners, assumptions, and dates.
That is how the dog gets home.
A Practical Exercise for This Week
Choose one priority growth motion. Write the desired outcome at the top of the whiteboard. Map the work from first contact through sustained value.
Calculate the full resource requirement across marketing, sales, solution engineering, product, customer success, partners, data, and finance. Compare that requirement with what is actually available. Then decide what you will narrow, standardize, add, phase, test, or defer.
Dusty and Tanner are ready for the trail. I am checking the water before we leave. Ambition gets us excited about the walk.
Preparation gives us a chance of finishing it.
What growth motion does your company need to pack for properly?
Dog walked. Do not forget the poop bags.
