Discovery
AuraScore 79/100

Product-Led Inbound Conversion Discovery Brief

Convert high-usage self-serve product accounts into qualified enterprise pipeline through structured product-led discovery.

Apply this prompt when freemium or self-serve product telemetry shows surging usage within a technology account. It guides commercial account executives to uncover enterprise-wide expansion opportunities without disrupting active user adoption.

Template

Role: Strategic Expansion Account Director specializing in Product-Led Growth (PLG) and enterprise sales conversion.

Context

  • Free Tier Account: {{self_serve_account}}
  • Surging Feature Usage: {{primary_product_telemetry}}
  • Active User Count: {{current_seat_count}}
  • Economic Buyer Target: {{target_economic_buyer}}
  • Business Value Hypothesis: {{perceived_expansion_value}}

Task

Generate an Inbound Commercial Discovery Brief for {{self_serve_account}} that leverages {{primary_product_telemetry}} and {{current_seat_count}} to uncover department-wide monetization opportunities with {{target_economic_buyer}}.

Method

  1. Analyze {{primary_product_telemetry}} to deduce team collaboration patterns and workflow bottlenecks.
  2. Quantify organizational risk associated with unmanaged adoption across {{current_seat_count}} self-serve users.
  3. Translate end-user utility into high-level business impact matching {{target_economic_buyer}} priorities.
  4. Design 4 transition questions to shift conversation from end-user features to {{perceived_expansion_value}}.
  5. Identify likely internal procurement and administrative hurdles (SSO, centralized billing, provisioning).
  6. Structure a land-and-expand commercial narrative that safeguards organic bottom-up usage.
  7. Define the primary exit criteria needed to transition the conversation to a formal enterprise proposal.

Constraints

  • MUST reference {{primary_product_telemetry}} as empirical evidence of internal demand.
  • MUST NOT suggest aggressive gating or punitive feature lockdowns for current free users.
  • Must keep executive messaging focused on risk mitigation, ROI, and governance.
  • Must restrict total length to under 500 words for fast mobile review.

Output format

  1. Product Telemetry Summary (3 data-driven observations)
  2. Commercial Expansion Hypothesis (max 90 words)
  3. Discovery Dialogue Framework (4 conversational stage questions: Usage Validation, Workflow Friction, Governance Gap, Budget Authority)
  4. Administrative Blockers (3 bulleted enterprise prerequisites)
  5. Deal Qualification Benchmark (3 go/no-go checks)

Self-review

  • Ensure telemetry data from {{primary_product_telemetry}} is directly tied to business ROI.
  • Verify that questions target {{target_economic_buyer}} rather than individual end-users.
  • Confirm the tone protects end-user trust while advocating for enterprise controls.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-discovery
technology-software
plg
expansion
saas-sales