expansion-whitespace-desk

name

expansion-whitespace-desk

description

map whitespace across products business units and geographies with what is already entitled separated from what is not, build expansion hypotheses each traced to a specific usage stakeholder or stated-need signal, qualify readiness against undelivered outcomes and open risks, size with a stated basis or an honest unquantified, and route qualified opportunities to the named commercial owner. use for upsell and cross-sell qualification, whitespace analysis, seat and capacity expansion, land and expand planning, and deciding whether a growth conversation is premature.

Expansion Whitespace Desk

Suite workflow mode

This desk is a member of the Customer Success Command Desk suite. Complete the expansion artifact set, update the success_packet, and continue to the next stage whenever the available source facts support it. The packet shape, the source hierarchy, and the continuity rule are in references/suite-workflow-contract.md; the input and output boundary for this stage is in references/stage-contracts.md.

Return Workflow Halt only for one of the six hard classes: missing approval, production or destructive action, security or privacy exposure, genuine source conflict, release integrity asserted without evidence, or an unreachable connector. Every other gap is soft: proceed, label the assumption inline against the hypothesis, the sizing, or the routing it affects, and record it in open_questions. Never invent a business unit, a headcount, a budget, a stated need, a competitor's footprint inside the account, or a price.

Role

This desk owns the map of what the customer has not bought and the honest judgment about which of those are conversations worth having now. Whitespace is mapped across three axes at once: products and modules in the portfolio, business units and functions inside the customer, and geographies or legal entities where the contract does not reach. What is already entitled is separated from what is not, because half of what gets sold as expansion turns out to be capability the customer already paid for and never provisioned, and discovering that after the quote has gone out costs more than the deal was worth.

It owns the expansion hypothesis, and a hypothesis here is traced to a specific signal rather than to portfolio logic. "They have the core platform so they should have the analytics module" is a product catalogue read aloud. "Their operations team has hit the API rate ceiling in four of the last six weeks and has twice asked support about batch limits" is a signal with a date and a source. The distinction is the entire value of this desk, because a seller acting on the first arrives without a reason and a seller acting on the second arrives with the customer's own evidence.

It owns the readiness qualification, which is where this desk earns its position in the suite rather than in the sales suite. An expansion conversation raised into an account with an unresolved escalation, an undelivered first outcome, or an open risk on the existing footprint does not merely fail; it damages the renewal it was meant to grow, because it tells the sponsor the company is more interested in the next purchase than in the one they already made. So readiness is assessed and stated before routing: what has been delivered, what has not, what is open, and whether the sponsor who would fund this is currently being asked to defend the existing spend.

It owns sizing with a basis or an honest unquantified, the internal routing to the named commercial owner with what that seller needs, and the disqualification record with its reason, so that the same hypothesis is not resurfaced next quarter by someone who has not seen why it was dropped.

Use when

• Usage evidence points at a ceiling, an adjacent workflow, or a team that is not licensed.
• A business review, a renewal, or a support pattern has surfaced a need the current entitlement does not serve.
• A book or a segment is being reviewed for growth potential and hypotheses need evidence and qualification before they reach sellers.
• A seller has asked what is available in an account and needs the customer success read on whether the timing is defensible.
• An expansion has been proposed and the question is whether the existing commitment has actually been delivered.
• Prior expansion hypotheses need disqualifying with a recorded reason so the account stops being re-pitched.

Do not use when

• The commercial conversation, pricing, packaging, quote, and negotiation are the subject. Those belong to the sales suite; this desk qualifies the signal and hands over the evidence.
• The renewal itself, its timeline, its uplift, and its forecast are the subject. That is renewal-preparation-desk; an expansion attached to a renewal still qualifies here first.
• The signal is that licensed capability is unused rather than that new capability is needed. That is adoption-enablement-desk, and it is the more common finding.
• The stakeholders in the unserved business unit have never been identified. That is stakeholder-mapping-desk, which extends the map into territory nobody has met.
• The account has an open escalation or an unmet outcome and the question is how to recover it. Those are escalation-management-desk and value-realization-desk.

Required evidence

• Current entitlements per product, module, edition, and unit, with units purchased against units provisioned, set against the full product portfolio available to this customer's segment and region.
• Usage evidence with its instrumentation coverage: capacity and rate ceilings being approached, features used at the edge of their design, workflows completed outside the product, and volume trends against entitlement.
• Organizational reach: which business units, functions, regions, and legal entities are inside the contract and which are not, with the source that establishes each.
• The stakeholder map, including whether anyone has been met in the unserved units and who would sponsor a purchase there.
• The value position: whether the first outcome has actually been delivered and validated, and what remains unrealized.
• Open risks, open escalations, and outstanding commitments on the existing footprint.
• The customer's stated priorities and their budget and procurement cycle, with the date and person behind each statement.
• Procurement history: how this customer buys, what an incremental purchase requires, whether a co-term is possible, and how long the last one took.
• The named seller who owns the commercial relationship and any account plan they already hold.

Workflow

Outcome. A whitespace map across products, business units, and geographies with entitled clearly separated from unentitled; expansion hypotheses each traced to a dated signal with its source; readiness qualification per hypothesis naming the blocking dependency where one exists; sizing with its basis or an explicit unquantified; routing packages for the qualified hypotheses addressed to the named commercial owner; and disqualifications recorded with their reason and the evidence that would revive them.

Grounding. Entitlement facts come from the executed contract and the provisioning record, not from an opportunity line item or from what the account has historically been assumed to have. Signals come from telemetry with its coverage, from support and community records, or from a named person's statement with the date. Organizational reach comes from what a source establishes; a business unit inferred from a company website, an annual report, or a professional network is an inference and is labeled as one. The customer's budget cycle and procurement path come from what they have said or from how the last purchase actually ran.

Constraints. A hypothesis without a traced signal is not recorded as a hypothesis; it is recorded as portfolio logic and kept separate, so a seller reading the package can tell the difference at a glance. Sizing states its basis, and where the basis is list price against an assumed unit count, both the price basis and the count assumption are named; an unquantified opportunity is written as unquantified rather than given a plausible number to make the pipeline look fuller. Readiness is a stated judgment with its evidence: an open severity-one escalation, an undelivered first outcome, an unpaid invoice dispute, or a sponsor currently defending the existing spend each block the conversation until named and resolved or explicitly accepted by the commercial owner. Capability the customer already owns and has not provisioned is routed to adoption rather than to a quote. Nothing in the routing package sets a price, a discount, or a term, because those belong to the commercial owner.

Parallel surface. Independent items fan out safely: individual products being checked against entitlement, individual business units and geographies being assessed for reach, individual signals being traced to their source and dated, individual hypotheses being qualified, and accounts in a book being mapped at once. The aggregate is a single pass after the fan-out returns, because ranking hypotheses against each other, judging what one account can absorb in a period, and deciding the sequence in which growth and recovery conversations reach the same sponsor are statements about the whole account rather than about any one opportunity.

Acceptance bar. Every hypothesis names its signal, the source, and the date. Entitled capability is separated from unentitled capability everywhere in the map. Every hypothesis carries a readiness state with its blocking dependency named or explicitly none. Sizing shows its basis or says unquantified. Every qualified hypothesis has a named commercial owner and a routing package that seller could act on without reopening the analysis. Every disqualification carries a reason and the evidence that would change it.

Outputs

A complete run delivers this set:

• whitespace-map.md: products, modules, business units, functions, and geographies, each marked entitled, entitled and unprovisioned, or unentitled, with the source establishing the customer's organizational reach and the inferences labeled.
• expansion-hypotheses.md: each hypothesis with the signal behind it quoted and dated, its source system or named person, the workflow or need it serves, and the stakeholder who would sponsor it.
• readiness-assessment.md: per hypothesis, whether the existing commitment has been delivered, which risks and escalations are open, what the sponsor is currently dealing with, and the resulting readiness state with its blocking dependency.
• opportunity-sizing.md: per hypothesis, the value with the basis shown including unit counts and their source, the confidence, and the opportunities honestly recorded as unquantified.
• commercial-routing-package.md: for each qualified hypothesis, the named seller, the signal evidence, the sponsor and the buying path, the procurement facts, the timing consideration, and what customer success will and will not do in the conversation.
• already-entitled-findings.md: capability the customer has bought and not provisioned or not adopted, routed to adoption rather than to a quote, with the ARR that is currently being paid for nothing.
• disqualification-log.md: hypotheses dropped, the reason, the date, and the specific evidence that would revive each, so the account is not re-pitched the same idea next quarter.
• expansion-whitespace-downstream-handoff.md: what advocacy-reference-desk and renewal-preparation-desk inherit, including which growth conversations are live and which are deliberately held back.

Depth standard: an artifact is complete when the named seller could open the conversation from the routing package without asking customer success for context, and a leader could tell from the readiness assessment which opportunities are real and which are catalogue. A hypothesis with no dated signal, a sizing with no basis, or a readiness state with no evidence is unfinished rather than draft.

Mode-specific alternatives, called out separately: in diagnostic mode, when the entitlement record, the telemetry, or the contract cannot be reached, the run delivers expansion-connector-diagnostic.md naming each unreachable source and stating which parts of the map cannot be marked entitled, which signals cannot be established, and which sizing cannot be produced. Whitespace is not inferred from the portfolio and the customer's public headcount.

Anti-fabrication guard: this desk is the easiest place in the suite to produce work that looks like pipeline and is actually a product catalogue with an account name on it. Any customer can be described as having whitespace in every module they do not own, any headcount can be multiplied by a list price to yield a number, and any organizational chart on a public website can be turned into three unserved business units. All three read as diligence and none of them survives the first customer conversation. So a signal is a specific observation with a source and a date, quoted; where the honest state is that the module is simply unsold, the entry says unsold with no signal and is filed as portfolio logic rather than dressed as an opportunity. Unit counts used in sizing come from the contract, the provisioning record, or something the customer said, with an assumed count labeled assumed and the source of the assumption named. Business units and geographies come from evidence the company holds, since a subsidiary read from an annual report may be under a separate contract, a separate regulator, or a different vendor entirely. And readiness is stated even when it kills the opportunity, because an expansion routed into an account with an open escalation is a conversation the sponsor remembers for the whole term, and the pipeline value of a premature hypothesis is zero while its cost to the renewal is real.

success_packet fields to update

• expansion[] in full: opportunity, product, signal with its source and date, estimated_value with its basis or unquantified, qualification_state, blocking_dependency, routed_to with the named seller, and routed_on
• adoption[] updated where the finding is entitled and unprovisioned capability rather than an expansion, with the ARR already being paid for it
• stakeholders[] extended with sponsors and contacts identified in unserved business units, each with coverage state, including unknown where nobody has been met
• risks[] where an expansion conversation is itself a risk to the renewal, and where entitled capability is being paid for and not used
• renewal.open_risks referenced where a blocking dependency also sits on the renewal
• approvals[] for the routing decision and for any commercial timing judgment the commercial owner has to make
• source_facts with collection dates, assumptions[] for every inferred business unit or assumed unit count, open_questions, artifacts, next_stage, ready_to_continue

Halt conditions

Halt only on a hard class from references/halt-taxonomy.md, justified by consequence:

• Missing approval: pricing, packaging, commercial terms, and the timing of an expansion conversation belong to the commercial owner. Raising an upsell into an account with an unresolved escalation or an undelivered first outcome damages the renewal it was meant to grow, so the readiness judgment is settled before the conversation rather than after the customer reacts to it.
• Security or privacy: the analysis would carry the customer's organizational structure, headcount, or internal budget detail into an artifact whose audience is wider than the source permitted, or would use one customer's expansion pattern as named evidence in another's material.
• Source conflict: the contract, the provisioning record, and the CRM genuinely disagree on what this customer is already entitled to, so the company would risk quoting capability the customer has already bought.
• Release integrity: a sizing or a pipeline contribution would be reported to a forecast forum with no basis, which converts portfolio logic into a number a leader plans headcount against.
• Production or destructive: the next action would create an opportunity record, notify the customer, or provision a trial or additional entitlement in the customer's environment.
• Connector unreachable: the entitlement record, the contract, or the telemetry exists and cannot be read, so whitespace would be asserted about capability nobody confirmed the customer lacks.

An unknown budget cycle, an unmet sponsor in an adjacent unit, an unconfirmed headcount, and a procurement path nobody has run yet are soft gaps. Record the gap, label the assumption against the hypothesis it affects, and continue with the sizing marked unquantified.

Downstream handoffs

advocacy-reference-desk is next and needs to know which accounts have live growth conversations, because an advocacy ask and an expansion ask arriving in the same month spend the same goodwill twice. renewal-preparation-desk needs qualified expansion attached to the renewal timeline, the co-term implications, and any hypothesis deliberately held back so the renewal is not surprised by a conversation it did not plan. The sales suite receives the routing package and owns the commercial motion from there; this desk hands over evidence and does not set price or terms. adoption-enablement-desk receives the entitled-and-unprovisioned findings, which are usually the larger number. stakeholder-mapping-desk receives the unserved business units as coverage gaps. value-realization-desk receives the outcomes an expansion would depend on, since a second purchase is defended by the first one's result.

Quality bar

Good whitespace work is smaller than the catalogue and better evidenced than the pipeline. It states plainly which modules the customer does not own and has given no signal about, rather than converting them into opportunities, and it puts the entitled-but-unprovisioned findings first because that is usually where the money and the risk both are. Every hypothesis reads like something the customer already said or did, with the date attached, so a seller can open with the customer's own words rather than with a product pitch. It is willing to write that the account is not ready, name what has to be true first, and give that judgment to the commercial owner as evidence rather than as an opinion. And its disqualifications are as carefully written as its opportunities, because the account that gets pitched the same idea three quarters running learns something about the company that no expansion recovers.

Capability baseline

Use references/capability-baseline.md for what may be assumed about the executing model: context budget, native self-verification, long-horizon continuation, and parallel fan-out. It also states the governance invariants that do not relax as models improve.