AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

posthog-inbound-leads

Evaluate and respond to inbound PostHog sales leads from Salesforce. Use this skill when any PostHog TAE needs to triage an inbound lead — deciding whether to qualify for a call, route to self-serve, or disqualify — and then draft an appropriate response email. Checks Vitally for existing account context before qualifying. Triggers on "respond to this lead", "triage this inbound", "write a response to this lead", "disposition this lead", "evaluate this Salesforce lead", or any request involving an inbound sales inquiry that needs qualification and a reply. Also trigger when a TAE pastes or describes lead details and asks what to do with them.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read posthog--posthog-inbound-leads at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 5

SKILL.md · 24000

evaluating PostHog for purchase.

  • Existing customer inquiry: Already a PostHog customer with a product/billing question - not a new sales opportunity.
  • No Product Fit: What they need isn't something PostHog does well (e.g. self-hosted requirement, industry mismatch).

Disqualification notes must be specific and copy-pasteable. Include the key data points that justify the disqualification, including relevant findings from company research.

Good DQ notes:

  • "30-employee e-commerce agency, $1M-$10M revenue. Marketing role, no engineer. 250K MAUs on free tier. Feature flag question answered, routed to self-serve."
  • "Bay Area nonprofit, 20K MAUs, ICP -5. Sr Dir Product, strong use case but well below $20K threshold. BAA available via Boost ($250/mo). Routed to self-serve with HIPAA + funnel guidance."
  • "15-person seed startup. Developer asking about feature flags. Free tier covers their needs. Pointed to docs + in-app support."
  • "5-person pre-revenue startup, no funding found. 2K MAU. Vague 'want to learn more.' Routed to self-serve, suggested startup plan application."

Bad DQ notes:

  • "Not a good fit" (too vague)
  • "Small company" (which signal matters?)
  • "Routed to self-serve" (why?)
  • "Low MAU" (did you check if the company is actually small, or is the product just early?)

Step 4: Write the Response Email

Read references/writing-style.md before drafting. Key rules:

  • Get to the point. No long intros, no fluff, no corporate jargon.
  • Be helpful, not sales-y. Solve their problem with specific guidance.
  • Be opinionated. Don't hedge with "it depends" — recommend a path.
  • Frame around their use case, not PostHog products. Talk about solving their problem, not about product names.
  • Use company research to personalize. If you know what they build, reference it. "Since you're building AI tools for manufacturing" is better than "Since you're evaluating analytics."
  • Embed links in anchor text. Never paste bare URLs or use "click here."
  • Minimal formatting. Use bullet points only when listing resources or steps. Keep it conversational.
  • One question max per email to avoid overwhelming the recipient.

Email Structure

  1. Brief, friendly greeting
  2. Acknowledge their specific situation and use case (informed by company research)
  3. Provide the answer, guidance, or resources mapped to their use case
  4. Clear next step (self-serve action, schedule link, or "reply if you have questions")
  5. Simple sign-off

Step 5: Validate All URLs

This step is mandatory. Before presenting the draft email, fetch every URL included in the email using web_fetch to verify:

  1. The URL resolves — It returns a 200 status, not a 404 or redirect to a generic page
  2. The content matches the intent — The page actually covers what you're linking it for (e.g., a link labeled "Feature Flags getting started" should land on the Feature Flags getting started page, not a generic docs index)

If a URL fails validation:

  • Search posthog.com for the correct page using web_search (e.g., "posthog docs feature flags getting started")
  • Replace the broken link with the correct one
  • If no valid page exists for that resource, remove the link rather than send a broken one

Why this matters: PostHog's docs structure changes. URLs from the resource list below are a starting point, but they may have moved. A broken link in a sales email undermines credibility. Always verify before sending.

Use-Case-Specific Resources to Link

Product Intelligence

Release Engineering

Observability

Growth & Marketing

AI/LLM Observability

Data Infrastructure

General (all use cases)

BAA / HIPAA Pricing Reference

When a lead mentions HIPAA, BAA, or healthcare data, use this pricing info:

Standard BAA (no redlines):

  • Available on the Boost add-on at $250/month + usage-based pricing
  • Also available on Scale and Enterprise add-ons
  • The BAA can be generated at posthog.com/baa for PostHog to countersign

Custom/redlined BAA:

  • Requires the Enterprise plan at $2K/month (paid annually) + usage-based pricing
  • Only needed if the customer wants to modify the standard BAA terms

Key framing: Lead with Boost as the standard path. $250/month is accessible for most organizations, including nonprofits and smaller companies. Don't default to "enterprise pricing" - that scares off leads who could easily afford Boost.

Practical note for leads with mixed PHI/non-PHI data: If only some of their funnels or data flows touch PHI, they can start tracking non-PHI activity on the free tier immediately while sorting out the BAA for the PHI-touching portions.

Non-Profit Discount Reference

PostHog offers non-profit discounts on credit purchases:

  • Credit purchases below $25K: 15% discount
  • Credit purchases $25K-$100K: additional 5% on top of standard volume discount
  • Credit purchases above $100K: standard volume discounts apply (no additional non-profit discount)

To qualify, the customer needs to provide proof they fit their country's definition of a non-profit entity (tax law in country of origin).

Note: At low MAU volumes where usage stays within the free tier, the non-profit discount won't matter yet - their main cost would be the platform add-on (e.g. Boost for BAA). Mention the discount so they know it exists for when they grow into it.

Output Format

When responding to the TAE, always provide:

  1. Vitally findings — Whether the lead or their company was found in Vitally, and what that means
  2. Company research — Brief profile from web research: what they do, funding, headcount, growth trajectory, multi-product signals, AI-native flag
  3. Use case assessment — Which of the six use cases this lead maps to, and why (based on persona, company research, and message)
  4. Disposition recommendation — Qualify / Self-serve / Startup plan / Disqualify
  5. Disqualification reason — From the available list (required for all dispositions except Qualify for Call)
  6. Disqualification notes — 250 characters or fewer, specific and copy-pasteable (required for all dispositions except Qualify for Call)
  7. Draft email — The response to send, framed around the identified use case and informed by company research

Reference Files

Read these before drafting responses:

  • references/email-examples.md — Example emails for common inbound scenarios
  • references/sales-context.md — Sales process, thresholds, qualification criteria
  • references/writing-style.md — PostHog tone, formatting, and style rules

Critical Reminders

  1. Always check Vitally first — Search for the lead's email and email domain before doing anything else. An existing customer changes everything about the response.
  2. Always research the company — Never qualify or disqualify based solely on stated MAU and the lead's message. A 5-minute web search can turn a "pass" into a whale.
  3. Growth trajectory can override the $20K threshold — An accelerating company with strong signals should be qualified even if current MAU is low. Document the override reasoning.
  4. Multi-product signals are spend multipliers — "Some of our products" means the stated MAU is a floor, not a ceiling. Adjust your estimate.
  5. AI-native companies get AI/LLM Obs as a secondary use case — Even if they didn't mention it. It's almost always relevant.
  6. Vague requests from high-value companies need discovery, not self-serve — Don't punt a $6B startup to the docs because they didn't write a detailed form submission.
  7. $20K threshold is firm for non-override cases — Do not offer calls below this for companies with steady/flat trajectories and no high-value signals.
  8. Always identify the use case — This is the foundation for everything: the disposition, the framing, and the resources you link.
  9. Always recommend a disposition — Don't just write an email; state the qualification decision explicitly so the TAE can update Salesforce.
  10. Always mention in-app support for product questions — it's the fastest path to help.
  11. PostHog is built for product engineers — If no engineer is involved, that's a red flag for qualification.
  12. Frame around problems, not products — "Here's how to understand why users drop off" not "Here's our Product Analytics feature."
  13. Use company research to personalize the email — Reference what they build, not just what they asked. It shows you did your homework.
  14. Match specificity to specificity — Vague inbound gets pointed to resources with a clarifying question; specific technical questions get specific answers tied to their use case.
  15. Always validate URLs before presenting the draft — Fetch every link to confirm it resolves and points to the right content. Never send a broken link.
  16. Always provide a DQ reason and DQ notes — For every disposition except Qualify for Call, include the disqualification reason from the available list and copy-pasteable notes (250 chars or fewer). Be specific — name concrete signals from both the lead's message AND your company research.