Consultative POV Inbound Lead Response Framework

Role: Senior Commercial Sales Strategist and Consultative Copywriter.

Context

• Inbound Lead Trigger: {{lead_source_trigger}}
• Prospect Title & Department: {{inbound_prospect_role}}
• Core Business Problem: {{target_business_problem}}
• Strategic POV Angle: {{primary_solution_angle}}
• Proof Metric Case: {{proof_metric_case}}
• Anticipated Friction Point: {{friction_point}}

Task

Generate a consultative Point-of-View (POV) response email sequence that qualifies {{inbound_prospect_role}}, challenges superficial solution requests, and establishes strategic positioning based on {{target_business_problem}}.

Method

1. Review {{lead_source_trigger}} to tailor the opening observation without reciting form submissions.
2. Reframe {{target_business_problem}} from a tactical symptom into an enterprise-wide business consequence.
3. Introduce {{primary_solution_angle}} as an objective operating principle rather than a proprietary feature.
4. Integrate {{proof_metric_case}} as a peer benchmark demonstrating predictable business upside.
5. Pre-empt {{friction_point}} directly to disqualify unqualified leads while building trust with prime buyers.
6. Structure a decisive 2-path call to action (exploratory strategy session vs. async diagnostic review).
7. Produce alternative subject lines calibrated for open rate and high status.

Constraints

• MUST NOT default to "Thanks for reaching out, when are you free for a demo?".
• MUST challenge at least one standard industry assumption about {{target_business_problem}}.
• Total email length MUST be under 200 words.
• Terminology MUST match executive business vocabulary in the prospect's sector.

Output format

• Section 1: 3 Pattern-Interrupt Subject Lines
• Section 2: Consultative Response Email (Body, 140-190 words)
• Section 3: Diagnostic Pre-call Questionnaire (3 high-leverage diagnostic questions for the prospect)
• Section 4: Rep Positioning Rationale (Brief strategic explanation of why this framing converts)

Self-review

• Does the email differentiate our methodology from generic software vendors within the first 40 words?
• Is {{proof_metric_case}} seamlessly integrated without sounding like an overt marketing case study?
• Are the 3 pre-call questions provocative and diagnostic rather than administrative?