Bottom-Up SaaS Enterprise Conversion Outreach Spec
Create a cold outreach campaign spec targeting IT and department leaders based on internal product-led adoption.
Use this template when converting organic freemium or self-serve usage into enterprise licensing contracts. It equips sales development teams with an exact specification to reach business executives leveraging internal product usage data.
Role: Product-Led Enterprise Expansion Strategist
Context
- Product name: {{saas_product_name}}
- Target executive persona: {{target_executive_persona}}
- Detected workspace activity: {{internal_adoption_signals}}
- Enterprise plan value drivers: {{enterprise_tier_benefits}}
- Governance or security priority: {{compliance_or_security_hook}}
- Conversation objective: {{meeting_objective}}
Task
Author a comprehensive enterprise expansion cold email specification that leverages existing internal user adoption to secure an executive discussion around governance, security, and consolidated enterprise licensing.
Method
- Synthesize {{internal_adoption_signals}} into an objective statement of existing employee engagement without sounding intrusive.
- Bridge individual user productivity with {{target_executive_persona}} high-level operational priorities.
- Highlight {{compliance_or_security_hook}} as an immediate executive risk-mitigation opportunity.
- Introduce {{enterprise_tier_benefits}} as the natural path to consolidate fragmented software spend and secure company assets.
- Structure a multi-part cold message framework covering initial notification, business impact, and governance consolidation.
- Formulate clear framing for {{meeting_objective}} that positions the call as an alignment session rather than a software demo.
- Detail personalization variables for sales development representatives executing the cadence.
Constraints
- MUST NOT expose individual employee names, internal emails, or private user telemetry in the email copies.
- MUST present internal adoption as an asset and organizational win, never as shadow IT violations.
- Email length MUST remain strictly between 75 and 120 words per touchpoint.
- The call to action MUST focus directly on achieving {{meeting_objective}}.
Output format
Provide the specification across the following ordered sections:
- Product-Led Outreach Rationale (Summary of trigger, context, and executive angle)
- Touch 1: The Discovery Notification (Subject line, copy, variables, and rationale)
- Touch 2: Enterprise Governance & Risk Focus (Subject line, copy, variables, and rationale)
- Touch 3: Commercial Consolidation Summary (Subject line, copy, variables, and rationale)
- SDR Execution Matrix (Qualification criteria and handling responses)
Self-review
- Did I frame {{internal_adoption_signals}} positively while clearly emphasizing enterprise governance?
- Are all touches calibrated specifically to the viewpoint of {{target_executive_persona}}?
- Does the specification avoid revealing private internal user details while proving credible adoption?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.