ThinkWithPrompt by SynotticThinkWithPrompt

Define product-qualified leads and when sales should reach out

PQL criteria based on product usage and fit, with routing rules and outreach that helps self-serve users instead of annoying them.

SalesFew-ShotStandardPlanFill-in Template

The prompt

Help me define product-qualified leads (PQLs) for my product-led SaaS business. Self-serve motion: [free plan / free trial / both, length of trial] Key product actions: [the events we track - e.g. invited teammates, connected an integration, hit a usage limit] Activation or retention data: [which actions correlate with paying or retaining, if known] Firmographic data we have: [company size, domain, industry, enrichment tool] What sales sells that self-serve doesn't: [enterprise plan, SSO, annual contracts, volume pricing] Sales capacity: [number of reps and how many PQLs they can work per week] Build: 1. A PQL definition combining usage signals (depth, breadth, frequency, limits hit) and fit signals (company size, role, domain). Give 2-3 tiers, e.g. hot, warm, nurture. 2. A scoring table: signal | points or threshold | why it matters. 3. Exclusions: personal email domains, students, competitors, existing customers. 4. Routing rules: which tier goes to sales, which gets automated in-app or email help, and the response-time target. 5. Outreach guidance: open with help tied to what the user actually did in the product; no generic demo requests. Give 2 example first messages. 6. How to measure whether the PQL definition works: PQL-to-paid conversion, sales-assisted vs self-serve deal size, and false positives. 7. A review cadence to recalibrate thresholds. If I have no data on what predicts conversion, give me starting thresholds labeled as hypotheses and the analysis to run to validate them.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Sales prompts

What to fill in

  • free plan / free trial / both, length of trial
  • which actions correlate with paying or retaining, if known
  • company size, domain, industry, enrichment tool
  • enterprise plan, SSO, annual contracts, volume pricing
  • number of reps and how many PQLs they can work per week

How this prompt is built

This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.

Related prompts

Find more prompts like this