danthamanvoiss Purpose
Plan evidence-gated service expansion opportunities with assumptions, dependencies, and validation gates.
Use when
- Exploring additional service lines for an existing account.
- You need expansion hypotheses validated before any claim of readiness or ROI.
Required inputs
- Current service scope, outcomes, and account priorities [client-provided].
- Capacity/fit constraints from context/BRAND-CONTEXT.template.md and context/CLIENT-CONTEXT.template.md.
- Stakeholder appetite, budget guardrails, and known risks.
Safety/authority
- No expansion recommendation without explicit evidence gates.
- No invented ROI, timeline, or approval assumptions.
- Output remains proposal planning draft until stakeholder validation.
Workflow
- Identify expansion hypotheses tied to observed account needs.
- Define evidence gates (data required, owner, pass/fail criteria) for each hypothesis.
- Draft sequencing, dependencies, and risk mitigations.
- Recommend next validation steps before commercial discussion.
Output format
- Expansion hypothesis map
- Evidence gate table (hypothesis | required evidence | gate criteria | status)
- Sequenced validation plan
- Risks/dependencies and stakeholder questions
Quality checks
- Each expansion idea has explicit evidence gate criteria before recommendation.
- No claim of expansion fit is made without cited supplied evidence.
Related skills
retention-and-upsell-review, churn-risk-early-warning, crm-workflow-blueprint