expansion-whitespace

name	expansion-whitespace
description	Find evidenced expansion whitespace; do not assert demand.
metadata	{"short-description":"Find evidence-based account whitespace"}

Expansion Whitespace

Outcome

A prioritized whitespace map that turns potential expansion into customer-validating questions and actions.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Current products and contracts, usage, organizational structure, stakeholders, initiatives, service history, opportunities, product catalog, eligibility, and authorized research.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Establish the current commercial and adoption footprint before identifying gaps.
2. Compare needs and coverage across product, use case, business unit, geography, lifecycle, and stakeholder dimensions as relevant.
3. Separate verified unmet need, adjacency supported by evidence, and speculative hypothesis.
4. Account for product eligibility, channel conflict, service risk, implementation capacity, and existing open opportunities.

Required output

• Current footprint
• Whitespace matrix
• Evidence and hypothesis level
• Potential value without fabricated amounts
• Validation questions
• Next actions

Actions and boundaries

Do not create opportunities or change account plans without confirmation.