Qualify expansion and manage a pilot
Objective. Qualify an expansion using an unmet objective plus evidence, an identified buyer, data readiness and success criteria - and produce an expansion brief with an included-feature check and a no-expansion alternative, so you grow accounts on real need rather than optimism.
Expansion done well is the natural next step of a realised outcome; done badly it is a feature pitch that burns trust. This lesson teaches you to qualify expansion the way a disciplined AE qualifies a deal - unmet objective, evidence, buyer, data readiness, success criteria - and to check honestly whether the capability is already included before you try to sell it, with a no-expansion alternative ready.
See it in the demo
The customer problem
A CSM under a growth target can slip into pitching the next module because it exists, not because the customer needs it. Customers feel this immediately and it converts a trusted advisor into another salesperson, damaging the relationship that made expansion possible in the first place. The opposite failure is also real: a genuine unmet objective sits unaddressed because the CSM never connected it to a capability. Business impact: mis-qualified expansion wastes the sponsor's internal capital and can stall a renewal; well-qualified expansion compounds value and makes the account stickier. The discipline is to expand only where there is an unmet objective with evidence, a buyer who owns it, data readiness, and agreed success criteria - the same bar as a new deal.
How Time Champ addresses it - qualify before you propose
Qualify against five tests. (1) Unmet objective with evidence: is there a real business objective the current scope does not serve, shown in the data - e.g. the customer has Work Output but intraday delivery keeps slipping, visible as recurring shortfalls that Intraday Management or Real-Time Adherence would address. (2) Buyer: who owns that objective and can fund the expansion - not necessarily today's sponsor. (3) Data readiness: does the new capability have the inputs it needs - e.g. Capacity Planning needs volume history and handling standards; Scheduling needs a forecast version; Quality needs a rubric and sampling. (4) Success criteria: what measurable outcome would make the expansion worth it, baselined the same disciplined way as C01/C08. (5) Included-feature check: confirm whether the capability is already in the customer's entitlement before proposing a purchase - selling something they already own is a credibility disaster. Use the demo apps to show the unmet-objective fit concretely.
What to say / do - the expansion brief
Write an expansion brief: the unmet objective and the evidence for it; the capability that addresses it and why; the buyer and their stake; the data-readiness check (what inputs exist, what is missing); the proposed success criteria and baseline; the included-feature check result (already entitled / needs purchase / confirm with product); and - always - a no-expansion alternative, which is what the customer does if they do not buy, so the conversation is honest rather than coercive. Then follow internal commercial ownership: qualifying and framing is CSM work, but the commercial motion (pricing, quoting) belongs to sales, and you hand over cleanly (this mirrors the S09 handover in reverse). Talk track: 'Your delivery is slipping intraday despite good weekly output - that is an objective your current scope does not cover; before I bring sales in, let me confirm whether intraday is already in your entitlement and what data it would need.'
Managing the pilot
When expansion warrants a pilot, scope it as a test, not a soft launch. Define the smallest useful scope - one team, one process, one client - a testable hypothesis tied to the success criteria, and a fixed window with a decision at the end. Keep the capacity-vs-cash and simulated-vs-executed disciplines from C06/C08: a pilot that shows a simulated intraday fix is not a pilot that proved an executed outcome. Manage data readiness actively - a pilot on incomplete data (C02) will produce an ambiguous result and waste the customer's attention. At the end, judge the pilot against the pre-agreed criteria, not against how enthusiastic everyone feels. An honest 'the pilot did not meet the criteria, here is why and what we would change' protects trust far more than declaring a borderline pilot a success.
Objections and honest limits
'Just send us pricing for everything' - resist the order-taker reflex; qualify the unmet objective first or you will quote scope the customer abandons. 'We want the new module but have no data for it' - data readiness is a gate; propose a readiness step before the pilot, not a pilot doomed to ambiguity. 'Is this already included?' - you must know; proposing a purchase of an entitled feature, or vice versa, is avoidable damage, so run the included-feature check and confirm with product where unsure. Honest limits: you qualify and frame value; pricing and contracting are sales-owned - do not improvise commercial terms. And never manufacture an unmet objective to hit a number; an expansion the evidence does not support is a renewal risk dressed as growth.
Interpretation check
Expansion is qualified by an evidenced unmet objective, a buyer, data readiness and success criteria - not by the existence of another module. Always run the included-feature check and keep a no-expansion alternative so the conversation stays honest.
In the field
OVO's paid POC connecting Salesforce case/AgentWork effort to outcome is itself a qualified pilot - smallest useful scope, testable effort-to-outcome hypothesis, explicit data readiness (read-only OAuth integration) and success criteria; expanding beyond it should clear the same five tests, not ride POC enthusiasm.
Practical task
For your account, write an expansion brief: the evidenced unmet objective (cite the demo screen that shows the fit), the capability and why it fits, the buyer and stake, the data-readiness check, proposed success criteria and baseline, the included-feature-check result (entitled / purchase / confirm with product), and a no-expansion alternative. Note where you hand over to sales.
Self-check
What are the five qualification tests for an expansion?
Unmet objective with evidence, an identified buyer who owns it, data readiness for the new capability, agreed success criteria with a baseline, and an included-feature check confirming whether it is already entitled.
Why is the included-feature check non-negotiable before proposing a purchase?
Proposing to sell a capability the customer already owns (or failing to flag one they need) destroys credibility instantly. You confirm entitlement - with product where unsure - before any commercial framing.
A customer is enthusiastic but has no data for the new module. What do you propose?
A data-readiness step before any pilot. Running a pilot on incomplete data yields an ambiguous result that wastes the customer's attention and undermines the expansion case. Readiness is a gate, not an optional nicety.
Why include a no-expansion alternative in the brief, and where does the commercial motion sit?
The alternative keeps the conversation honest and non-coercive by stating what the customer does if they decline. Qualifying and framing is CSM work; pricing and contracting belong to sales, handed over cleanly per internal commercial ownership.
Verified vs demo. The capability fits and input requirements are demo-shown. Whether a capability is included in a specific entitlement, and all pricing/packaging, are commercial facts to confirm with product and sales - never assert them from the demo.