[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-posthog-inbound-leads":3,"mdc-bc2g25-key":37,"related-org-posthog-posthog-inbound-leads":3269,"related-repo-posthog-posthog-inbound-leads":3440},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"posthog-inbound-leads","triage and qualify inbound sales 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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png",[12,14,17,20,23],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Triage","triage",{"name":18,"slug":19,"type":13},"CRM","crm",{"name":21,"slug":22,"type":13},"Sales","sales",{"name":24,"slug":25,"type":13},"Lead Enrichment","lead-enrichment",56,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills","2026-04-06T18:46:32.051425",null,4,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"PostHog skills (under construction)","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fteam\u002Fnew-business-sales\u002Finbound-lead","---\nname: posthog-inbound-leads\ndescription: 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.\n---\n\n# PostHog Inbound Lead Disposition\n\nEvaluate inbound leads from Salesforce and either draft a response email or recommend a disposition. This skill is for any PostHog TAE handling inbound sales inquiries.\n\n## Core Workflow\n\n1. **Ingest lead context** — Read whatever the TAE provides (Salesforce fields, email body, notes)\n2. **Check Vitally for existing account context** — Search for the lead's email and email domain (see Step 0 below)\n3. **Research the company** — Web search to understand who they are, their funding, size, and growth trajectory (see Step 1 below)\n4. **Identify the use case** — Map the lead to one or more of PostHog's six use cases, informed by company research (see Step 2 below)\n5. **Qualify the lead** — Apply the disposition framework, informed by company research and growth trajectory (see Step 3 below)\n6. **Recommend a disposition** — State the recommended action and identified use case(s) clearly\n7. **Draft a response** — Write the appropriate email, framed around their use case (see Step 4 below)\n8. **Validate all URLs** — Fetch every link in the draft email to confirm it resolves and points to the intended content (see Step 5 below)\n\n## Step 0: Check Vitally for Existing Account Context\n\nBefore qualifying or drafting anything, check Vitally to see if this lead (or their company) is already a PostHog user. This changes the disposition and email framing significantly — an existing customer asking for help is different from a cold inbound.\n\n### What to check\n\nRun two Vitally lookups using the lead's email address:\n\n1. **Search by exact email** — `vitally:search_users` with `email` set to the lead's email address. This tells you if this specific person already has a PostHog account.\n2. **Search by email domain** — `vitally:search_users` with `emailSubdomain` set to the domain portion of the lead's email (e.g., `acme.com` from `jane@acme.com`). This tells you if anyone at their company is already using PostHog.\n\nIf either search returns results, pull up the associated account with `vitally:get_account_full` using the `accountId` from the user record(s). Use `detailLevel: \"summary\"` for a quick overview.\n\n### How to use what you find\n\n**Lead's email is an existing user:**\n- They're already in PostHog. The email should acknowledge this (\"I can see you're already using PostHog\") and focus on their specific ask rather than onboarding-style resources.\n- Check their account's MRR and health score — this informs whether they're a self-serve user reaching out to grow, or an existing account with an expansion opportunity.\n\n**Different person at the same company is already a user:**\n- Their company is already on PostHog. Reference this in the email (\"I see your team is already using PostHog\") and ask how their request relates to the existing usage.\n- Check who else is on the account — the lead may need to connect with the internal champion rather than start a separate evaluation.\n- If the account already has a TAE assigned, flag this to avoid stepping on someone's book of business.\n\n**No results in Vitally:**\n- Net new lead. Proceed with the standard qualification workflow below.\n\n### What to surface to the TAE\n\nWhen presenting the Vitally findings, include:\n- Whether the person or company was found\n- Account name and current MRR (if applicable)\n- Health score (if applicable)\n- Assigned TAE (if any — important for routing)\n- Number of users on the account\n- A one-line recommendation on how this changes the response (e.g., \"Existing $3K\u002Fmo account, no TAE assigned — this is an expansion opportunity, not a new lead\")\n\n## Step 1: Research the Company\n\n**This step is mandatory for every lead.** The lead's form submission alone is not enough information to qualify or disqualify. A 10K MAU lead from a $6B startup and a 10K MAU lead from a 5-person agency require completely different dispositions.\n\n### What to research\n\nRun 1-3 web searches to understand the company. Start with the company name and domain:\n\n- `web_search` for `[Company Name] [domain]` — Get the basics: what they do, who they are\n- `web_search` for `[Company Name] funding employees` — Get firmographics: funding stage, headcount, growth signals\n- If the company appears to be notable or well-funded, search for recent news: `[Company Name] 2026` or `[Company Name] news`\n\n### What to extract\n\nFrom the research, identify and record:\n\n| Signal | Why It Matters | Example |\n|---|---|---|\n| **What they build** | Determines use case mapping and whether they're ICP | \"AI tools for manufacturing\" → AI\u002FLLM Obs is relevant |\n| **Funding stage and amount** | Proxy for budget and growth trajectory | Series B, $50M → likely has budget for tooling |\n| **Employee count** | Proxy for spend potential and team complexity | 200 employees → multiple teams, multi-project potential |\n| **Engineering team size or ratio** | PostHog's buyer is engineers; more engineers = better fit | \"80% of team is engineering\" → strong ICP signal |\n| **Growth trajectory** | Determines whether current MAU is the ceiling or the floor | Founded 6 months ago, hiring aggressively → MAU will grow fast |\n| **Recent news** | Acquisitions, launches, pivots that change context | Just acquired an AI startup → expanding product surface |\n| **Business model** | SaaS, marketplace, dev tools, agency, etc. | B2B SaaS → classic PostHog ICP |\n\n### Classify the growth trajectory\n\nBased on the research, classify the company into one of four growth trajectories:\n\n- **Accelerating**: Recent large funding round (especially if raised in last 12 months), aggressive hiring, early-stage with significant capital, or clear signs of rapid expansion. Current MAU is almost certainly not the ceiling. Examples: well-funded Series A+ startups, companies that just raised mega-rounds, companies with \"hundreds of open roles.\"\n- **Steady**: Established company, moderate and predictable growth. Current MAU is a reasonable proxy for near-term spend. Examples: mid-market SaaS with stable revenue, mature PLG companies.\n- **Early\u002Funknown**: New company, limited public information, hard to assess trajectory. Treat current MAU as the best available signal but note the uncertainty. Examples: pre-seed startups, stealth-mode companies with no public footprint.\n- **Flat\u002Fdeclining**: No growth signals, layoffs, or signs of contraction. Current MAU may overstate future spend. Examples: companies with recent layoffs, shrinking teams.\n\n**The growth trajectory classification directly affects qualification.** See Step 3 for how it modifies the $20K threshold.\n\n### Detect multi-product signals\n\nWhile researching, watch for signals that the lead's company has (or is building) multiple products. This is a spend multiplier because each product typically becomes a separate PostHog project with its own event volume.\n\n**Signals in the lead's message:**\n- \"some of our products\" \u002F \"multiple products\" \u002F \"across our portfolio\"\n- \"several teams\" \u002F \"multiple teams\" \u002F \"different business units\"\n- \"our platform and our apps\" \u002F \"our web app and mobile app\"\n- \"integrate into our stack\" (implies breadth)\n\n**Signals from company research:**\n- Company has multiple product lines or brands\n- Company recently acquired other companies (each acquisition may have its own product)\n- Job postings reference multiple product teams\n- Company website shows multiple distinct products\n\nWhen multi-product signals are present, note the estimated product count (or range) and factor it into the MAU multiplier. A company with 5 products at 10K MAU each is a 50K MAU opportunity, not a 10K one.\n\n### Detect AI\u002FML company signals\n\nIf company research reveals the company is AI-native (building AI\u002FML products as their core business), flag AI\u002FLLM Observability as a probable secondary use case even if the lead's message doesn't mention AI, LLMs, model costs, or prompts.\n\n**AI-native signals:**\n- Company description mentions AI, ML, LLM, or \"artificial intelligence\" as core to what they build\n- Company is in an AI-adjacent industry (AI infrastructure, AI applications, AI research)\n- Team is heavily ML\u002FAI engineers\n- Recent AI-related acquisitions or product launches\n\nWhen detected, include AI\u002FLLM Observability in the use case assessment and mention it in the email as a relevant capability, even if the lead didn't ask about it. Frame it as: \"since you're building AI products, you might also find our LLM analytics useful for tracking model costs and performance.\"\n\n### What to surface to the TAE\n\nPresent the company research as a brief profile including:\n- What the company does (one sentence)\n- Funding and valuation (if available)\n- Employee count and engineering composition (if available)\n- Growth trajectory classification\n- Multi-product signals (if any)\n- AI-native flag (if applicable)\n- Any notable context (recent news, acquisitions, leadership)\n\nThis goes right after the Vitally findings and before the use case assessment.\n\n## Step 2: Identify the Use Case\n\nEvery lead maps to one or more of PostHog's six use cases. Identifying the use case determines how to frame the response, what products to highlight, and what resources to link. Evaluate the **person\u002Fpersona**, **company** (informed by your Step 1 research), and **message** to determine the match.\n\n### The Six Use Cases\n\n| Use Case | Job to Be Done | Core Buyer Persona | Key Signals in the Lead |\n|---|---|---|---|\n| **Product Intelligence** | \"Help me understand what users do, why they do it, and what to build next.\" | PMs, designers, product engineers, founders | Mentions analytics, funnels, retention, user behavior, \"why users drop off\", feature adoption, NPS, surveys, session replay for UX research |\n| **Release Engineering** | \"Help me ship faster without breaking things.\" | Engineering managers, platform teams, developers | Mentions feature flags, rollouts, A\u002FB testing releases, kill switches, progressive delivery, replacing LaunchDarkly |\n| **Observability** | \"Help me know when things break, understand why, and fix them fast.\" | SREs, platform engineers, DevOps | Mentions error tracking, bug reproduction, replacing Sentry\u002FDatadog, logging, incident response, stack traces |\n| **Growth & Marketing** | \"Help me understand what drives acquisition, conversion, and revenue.\" | Growth engineers, marketing leads, CRO, GTM engineers | Mentions attribution, ROAS, campaign performance, replacing GA4\u002FSegment, conversion optimization, onboarding automation, marketing stack consolidation |\n| **AI\u002FLLM Observability** | \"Help me understand how my AI features perform, what they cost, and how users interact with them.\" | AI\u002FML engineers, AI PMs, AI founders | Mentions LLM, AI features, model costs, prompt testing, AI quality, replacing Langfuse\u002FHelicone, token usage. **Also inferred from company research** — if the company is AI-native, this use case is relevant even if the lead didn't mention it. |\n| **Data Infrastructure** | \"Help me unify product data with business data and get it where it needs to go.\" | Data engineers, analytics engineers, product ops | Mentions data warehouse, Snowflake\u002FBigQuery, data pipelines, batch exports, combining PostHog data with Stripe\u002FCRM, replacing Segment\u002FFivetran |\n\n### Mapping Persona to Use Case\n\nThe **person's role** is one of the strongest signals:\n\n- **PM, Head of Product, UX Researcher, Designer** → Product Intelligence\n- **Engineering Manager, VP Eng, Platform Engineer, Developer** → Release Engineering (or Observability if they mention errors\u002Fincidents)\n- **SRE, DevOps, Infrastructure Engineer** → Observability\n- **Growth Engineer, Marketing Lead, CRO, GTM Engineer, Demand Gen** → Growth & Marketing\n- **AI\u002FML Engineer, AI PM, AI Founder** → AI\u002FLLM Observability\n- **Data Engineer, Analytics Engineer, Head of Data, RevOps** → Data Infrastructure\n- **Founder\u002FCTO (early stage)** → Usually Product Intelligence or AI\u002FLLM Obs depending on the product; may span multiple use cases\n\n### Mapping Company to Use Case\n\nThe **company type** (from your Step 1 research) helps narrow it:\n\n- **AI-native startup** → AI\u002FLLM Observability is almost always relevant, often alongside Product Intelligence\n- **PLG SaaS** → Product Intelligence + Growth & Marketing are the most common pair\n- **Enterprise with multiple teams** → Often starts as one use case but the expansion potential spans several\n- **E-commerce \u002F marketplace** → Growth & Marketing (conversion, attribution) + Product Intelligence (user behavior)\n- **Developer tools \u002F infrastructure** → Release Engineering + Observability\n\n### Mapping Message to Use Case\n\nThe **specific ask** confirms or overrides the persona\u002Fcompany signal:\n\n- \"We want to understand user behavior\" → Product Intelligence\n- \"We need feature flags\" or \"replacing LaunchDarkly\" → Release Engineering\n- \"We need error tracking\" or \"replacing Sentry\" → Observability\n- \"We want attribution\" or \"replacing GA4\" → Growth & Marketing\n- \"We're building AI features\" or \"LLM costs\" → AI\u002FLLM Observability\n- \"We need to get data into Snowflake\" → Data Infrastructure\n- Vague \"show me features\" \u002F \"want a demo\" → Can't determine use case from the message alone; **use company research to infer the most likely use case(s)**, then ask a targeted clarifying question to confirm\n\n**If the use case is ambiguous even after company research**, include a targeted clarifying question in the email to narrow it down. Frame the question around their problem, not PostHog products: \"What's the main problem you're trying to solve?\" is better than \"Which PostHog product are you interested in?\"\n\n### Multiple Use Cases\n\nMany leads map to more than one use case. When this happens:\n\n- **Lead with the primary use case** — the one most closely matching their stated pain\n- **Mention the secondary use case as a natural extension** — \"PostHog also handles X, which tends to come up once teams are doing Y\"\n- **Don't try to sell the entire platform** — focus on solving the problem they came in with\n\n## Step 3: Qualify the Lead\n\n### Growth Trajectory Override\n\n**The $20K annual spend threshold is the default qualification bar, but growth trajectory can override it.**\n\nWhen all of the following are true, qualify for a call even if current MAU alone wouldn't hit $20K:\n\n1. **Growth trajectory is \"Accelerating\"** — Recent large funding, aggressive hiring, early-stage with significant capital\n2. **High-value company signals** — At least two of: $10M+ in funding, 50+ employees, engineering-heavy team, multi-product, AI-native\n3. **Reasonable path to $20K within 12 months** — Based on growth trajectory and multi-product multiplier, it's plausible they'll reach the threshold as they scale\n\nWhen the override applies, note it explicitly in the disposition: \"Current MAU of 10K is below the $20K threshold, but growth trajectory is Accelerating ([$X funding, Y employees, etc.]) with multi-product potential. Qualifying for call based on trajectory.\"\n\n**When the override does NOT apply:**\n- Growth trajectory is Steady, Early\u002Funknown, or Flat — stick to the $20K threshold based on current signals\n- The company has funding but the lead's use case is narrow and unlikely to expand (e.g., a well-funded company asking about feature flags for one internal tool)\n- The lead is from a large company but the team using PostHog would be tiny with no expansion path\n\n### Multi-Product Spend Multiplier\n\nWhen multi-product signals are detected (from the lead's message or company research), adjust the MAU estimate:\n\n- **Stated MAU × estimated product count = adjusted MAU estimate**\n- Use the adjusted estimate for qualification, not the raw stated MAU\n- Note the multiplier in the disposition: \"10K MAU stated, but 'some of our products' + company research suggests 3-5 products → 30-50K adjusted MAU\"\n\nThis multiplier is an estimate, not a guarantee. It shifts the disposition from \"definitely below threshold\" to \"plausibly above threshold, worth a call to confirm.\"\n\n### Special Case: Competitor Displacement\n\nWhen a lead mentions they're currently using a competitor and looking to switch (e.g., \"using Heap looking to move\", \"replacing Amplitude\", \"evaluating alternatives to Sentry\", \"moving off LaunchDarkly\"), this is a high-signal inbound. They already have budget allocated to a tool in the category, they have a defined need, and they likely have some urgency.\n\n**However, the $20K floor still applies (unless the growth trajectory override kicks in).** A competitor displacement lead still needs to show potential for $20K+ annual spend to qualify for a call. Don't offer a call just because they're switching from a paid tool.\n\n**For competitor displacement leads, the initial response should surface BANT signals** before offering a call or routing to self-serve. Ask targeted discovery questions that uncover:\n\n- **Budget:** What's driving the switch? Cost, missing features, data ownership, or something else? (If cost, that implies existing budget.)\n- **Authority:** Who's involved in the decision? Is this an engineering-led eval or a top-down mandate?\n- **Need:** What are you hoping PostHog solves that [competitor] doesn't? Are you looking to replace just [product], or are you interested in consolidating with additional capabilities (replay, flags, experiments, etc.)?\n- **Timeline:** How soon are you looking to make a decision? (Don't ask this in the first email — let it emerge naturally or ask in a follow-up.)\n\n**You don't need all four BANT signals in the first email.** Ask 1–2 questions that surface the most important unknowns — typically Budget (why are you switching?) and Need (what do you want beyond what you have?). Let Authority and Timeline emerge in the reply.\n\n**After the lead replies with BANT context:**\n- If the answers confirm $20K+ potential and a real use case → Qualify for call, and offer your calendar\n- If the answers reveal a small team \u002F low spend \u002F simple replacement → Route to self-serve with specific migration resources\n- If the lead asks for a call before you have BANT context → It's OK to offer the calendar, but also point out that everything needed to evaluate PostHog is publicly available (pricing, docs, free signup), so they can start evaluating in parallel\n\n### Special Case: Vague Request from a High-Value Company\n\nWhen the lead's message is vague (e.g., \"want to start a review process\", \"looking to learn more\", \"interested in PostHog\") BUT company research reveals a high-value account, **do not default to self-serve routing.**\n\nInstead, treat vague requests from high-value companies as \"needs discovery\" rather than \"not serious enough for a call.\" The disposition should be \"qualify for call with discovery questions.\"\n\n**High-value company indicators** (any two or more qualifies):\n- $10M+ in total funding\n- 100+ employees\n- Engineering team >40% of headcount\n- Multi-product signals\n- AI-native company\n- Growth trajectory classified as \"Accelerating\"\n- Well-known brand or notable founders\u002Fleadership\n\nThe email for these leads should:\n- Acknowledge their interest without making assumptions about the use case\n- Ask 1-2 discovery questions to understand what they're trying to solve\n- Mention 1-2 PostHog capabilities most relevant to their company type (informed by research)\n- Offer a call to walk through how PostHog fits their stack\n\n### Disposition: Qualify for Call\n\nAll of these should be true:\n- Annual spend potential ≥ $20K (based on current MAU, OR adjusted MAU with multi-product multiplier, OR growth trajectory override)\n- Engineers are involved or will be on the call\n- Specific, defined use case (mapped to at least one of the six above) — OR vague request from a high-value company (see special case above)\n- Company size and product needs justify sales-assisted motion\n\nIf qualified, draft a response that:\n- Acknowledges their specific use case (or, for vague requests from high-value companies, their company context and likely use cases)\n- Asks 1–2 targeted discovery questions from the relevant use case playbook\n- Offers to schedule a call\n\n### Disposition: Route to Self-Serve\n\nAny of these are true:\n- Spend potential clearly below $20K based on company size, research, AND growth trajectory does not justify the override\n- Low volume explicitly stated (e.g., \"1,000 MAU\", \"small team\", \"just getting started\") AND company research confirms this is the ceiling (small company, flat trajectory)\n- Vague request with no specific use case AND company research does not reveal a high-value account\n- No engineer involvement mentioned or expected\n- Generic \"learn more\" or \"get a demo\" with no substance behind it AND company research doesn't change the picture\n\nDraft a helpful email that:\n- Answers their question with use-case-specific resources\n- Provides links to the most relevant product docs for their identified use case\n- Directs them to self-serve channels (in-app support, community)\n- Does NOT offer a call\n\n### Disposition: Route to Startup Plan\n\n- Company is early-stage and potentially eligible for the startup plan\n- Direct them to the [startup plan application](https:\u002F\u002Fposthog.com\u002Fstartups)\n- Disqualify as an immediate sales opportunity\n\n### Disposition: Disqualify\n\n- Clearly not ICP (wrong industry vertical, no product-engineering use case)\n- Spam or irrelevant inquiry\n- No response needed, or a brief polite decline\n\n### Disqualification Reasons & Notes\n\nWhen recommending any disposition other than \"Qualify for Call,\" you MUST provide a **disqualification reason** (from the list below) and **disqualification notes** (250 characters or fewer, specific and copy-pasteable into the Salesforce disqualification notes field).\n\n**Available disqualification reasons:**\n\n- BAA \u002F DPA Request\n- Below Sales Assist Threshold - Pass\n- Below Sales Assist Threshold - Prospect\n- Billing Support Request\n- Business Closed\n- Duplicate Lead\n- Event request\n- Existing customer inquiry\n- Feedback\n- Invalid Contact Info\n- No Budget\n- No Current Need\n- No Product Fit\n- No Response - Pass\n- No Response - Prospect\n- No Technical Resource\n- Non-Commercial\n- Not a Good Fit\n- Other\n- Partnership request\n- Resource Constraints\n- Self-Hosted Requirement\n- Spam\n- Stale - autoclosed\n- Startup Plan \u002F YC\n- Support Request\n- Using Competitor \u002F Unsolicited RFP\n\n**How to choose the right reason:**\n\n- **Below Sales Assist Threshold - Pass**: Below $20K potential, no growth trajectory override, and no realistic growth path to get there. Use for small companies routed to self-serve.\n- **Below Sales Assist Threshold - Prospect**: Below $20K now but company shows signals it could grow into threshold (e.g. recent funding, growing team). Worth revisiting later. Use when the growth trajectory is promising but doesn't meet the override criteria yet.\n- **BAA \u002F DPA Request**: Lead requires a BAA or DPA. Note: BAAs are available starting at the Boost add-on ($250\u002Fmonth + usage-based pricing) for standard (no redlines) BAAs, or Enterprise ($2K\u002Fmonth paid annually) for custom\u002Fredlined BAAs. Use this reason when the lead's primary need is HIPAA\u002FBAA and they've been given the relevant pricing info.\n- **No Technical Resource**: The contact is non-technical and no engineer is mentioned or expected to be involved.\n- **Startup Plan \u002F YC**: Early-stage company routed to the startup plan application.\n- **Support Request**: They're asking a support question, not evaluating PostHog for purchase.\n- **Existing customer inquiry**: Already a PostHog customer with a product\u002Fbilling question - not a new sales opportunity.\n- **No Product Fit**: What they need isn't something PostHog does well (e.g. self-hosted requirement, industry mismatch).\n\n**Disqualification notes must be specific and copy-pasteable.** Include the key data points that justify the disqualification, including relevant findings from company research.\n\nGood DQ notes:\n- \"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.\"\n- \"Bay Area nonprofit, 20K MAUs, ICP -5. Sr Dir Product, strong use case but well below $20K threshold. BAA available via Boost ($250\u002Fmo). Routed to self-serve with HIPAA + funnel guidance.\"\n- \"15-person seed startup. Developer asking about feature flags. Free tier covers their needs. Pointed to docs + in-app support.\"\n- \"5-person pre-revenue startup, no funding found. 2K MAU. Vague 'want to learn more.' Routed to self-serve, suggested startup plan application.\"\n\nBad DQ notes:\n- \"Not a good fit\" (too vague)\n- \"Small company\" (which signal matters?)\n- \"Routed to self-serve\" (why?)\n- \"Low MAU\" (did you check if the company is actually small, or is the product just early?)\n\n## Step 4: Write the Response Email\n\nRead `references\u002Fwriting-style.md` before drafting. Key rules:\n\n- **Get to the point.** No long intros, no fluff, no corporate jargon.\n- **Be helpful, not sales-y.** Solve their problem with specific guidance.\n- **Be opinionated.** Don't hedge with \"it depends\" — recommend a path.\n- **Frame around their use case, not PostHog products.** Talk about solving their problem, not about product names.\n- **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.\"\n- **Embed links in anchor text.** Never paste bare URLs or use \"click here.\"\n- **Minimal formatting.** Use bullet points only when listing resources or steps. Keep it conversational.\n- **One question max** per email to avoid overwhelming the recipient.\n\n### Email Structure\n\n1. Brief, friendly greeting\n2. Acknowledge their specific situation and use case (informed by company research)\n3. Provide the answer, guidance, or resources mapped to their use case\n4. Clear next step (self-serve action, schedule link, or \"reply if you have questions\")\n5. Simple sign-off\n\n## Step 5: Validate All URLs\n\n**This step is mandatory.** Before presenting the draft email, fetch every URL included in the email using `web_fetch` to verify:\n\n1. **The URL resolves** — It returns a 200 status, not a 404 or redirect to a generic page\n2. **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)\n\n**If a URL fails validation:**\n- Search posthog.com for the correct page using `web_search` (e.g., \"posthog docs feature flags getting started\")\n- Replace the broken link with the correct one\n- If no valid page exists for that resource, remove the link rather than send a broken one\n\n**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.\n\n## Use-Case-Specific Resources to Link\n\n### Product Intelligence\n- [Product analytics docs](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fproduct-analytics)\n- [Funnels](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fproduct-analytics\u002Ffunnels)\n- [Session Replay](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsession-replay)\n- [Surveys](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsurveys\u002Fcreating-surveys)\n- [Experiments](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fexperiments)\n\n### Release Engineering\n- [Feature Flags getting started](https:\u002F\u002Fposthog.com\u002Fdocs\u002Ffeature-flags\u002Fstart-here)\n- [Experiments](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fexperiments)\n- [Session Replay](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsession-replay) (for debugging rollouts)\n\n### Observability\n- [Error Tracking](https:\u002F\u002Fposthog.com\u002Fdocs\u002Ferror-tracking)\n- [Session Replay](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsession-replay) (for error context)\n\n### Growth & Marketing\n- [Web Analytics](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fweb-analytics\u002Fgetting-started)\n- [Marketing Analytics](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fweb-analytics\u002Fmarketing-analytics)\n- [Data Pipelines](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fcdp)\n- [Workflows](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fworkflows\u002Fstart-here)\n\n### AI\u002FLLM Observability\n- [AI Engineering \u002F LLM Observability](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fai-engineering)\n- [Experiments](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fexperiments) (for prompt\u002Fmodel testing)\n\n### Data Infrastructure\n- [Data Warehouse](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fdata-warehouse)\n- [Batch Exports](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fcdp\u002Fbatch-exports)\n- [Realtime Destinations](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fcdp\u002Fdestinations)\n\n### General (all use cases)\n- [Installation guide](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fgetting-started\u002Finstall)\n- [Pricing page](https:\u002F\u002Fposthog.com\u002Fpricing)\n- [Community questions](https:\u002F\u002Fposthog.com\u002Fquestions)\n- [HIPAA compliance guide](https:\u002F\u002Fposthog.com\u002Fdocs\u002Fprivacy\u002Fhipaa-compliance)\n- [BAA generator](https:\u002F\u002Fposthog.com\u002Fbaa)\n- In-app support button (always mention for product questions)\n- Free tier: 1M events\u002Fmonth, all core features included\n\n## BAA \u002F HIPAA Pricing Reference\n\nWhen a lead mentions HIPAA, BAA, or healthcare data, use this pricing info:\n\n**Standard BAA (no redlines):**\n- Available on the **Boost add-on** at **$250\u002Fmonth** + usage-based pricing\n- Also available on Scale and Enterprise add-ons\n- The BAA can be generated at posthog.com\u002Fbaa for PostHog to countersign\n\n**Custom\u002Fredlined BAA:**\n- Requires the **Enterprise plan** at **$2K\u002Fmonth** (paid annually) + usage-based pricing\n- Only needed if the customer wants to modify the standard BAA terms\n\n**Key framing:** Lead with Boost as the standard path. $250\u002Fmonth 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.\n\n**Practical note for leads with mixed PHI\u002Fnon-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.\n\n## Non-Profit Discount Reference\n\nPostHog offers non-profit discounts on credit purchases:\n\n- **Credit purchases below $25K:** 15% discount\n- **Credit purchases $25K-$100K:** additional 5% on top of standard volume discount\n- **Credit purchases above $100K:** standard volume discounts apply (no additional non-profit discount)\n\nTo qualify, the customer needs to provide proof they fit their country's definition of a non-profit entity (tax law in country of origin).\n\n**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.\n\n## Output Format\n\nWhen responding to the TAE, always provide:\n\n1. **Vitally findings** — Whether the lead or their company was found in Vitally, and what that means\n2. **Company research** — Brief profile from web research: what they do, funding, headcount, growth trajectory, multi-product signals, AI-native flag\n3. **Use case assessment** — Which of the six use cases this lead maps to, and why (based on persona, company research, and message)\n4. **Disposition recommendation** — Qualify \u002F Self-serve \u002F Startup plan \u002F Disqualify\n5. **Disqualification reason** — From the available list (required for all dispositions except Qualify for Call)\n6. **Disqualification notes** — 250 characters or fewer, specific and copy-pasteable (required for all dispositions except Qualify for Call)\n7. **Draft email** — The response to send, framed around the identified use case and informed by company research\n\n## Reference Files\n\nRead these before drafting responses:\n- `references\u002Femail-examples.md` — Example emails for common inbound scenarios\n- `references\u002Fsales-context.md` — Sales process, thresholds, qualification criteria\n- `references\u002Fwriting-style.md` — PostHog tone, formatting, and style rules\n\n## Critical Reminders\n\n1. **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.\n2. **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.\n3. **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.\n4. **Multi-product signals are spend multipliers** — \"Some of our products\" means the stated MAU is a floor, not a ceiling. Adjust your estimate.\n5. **AI-native companies get AI\u002FLLM Obs as a secondary use case** — Even if they didn't mention it. It's almost always relevant.\n6. **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.\n7. **$20K threshold is firm for non-override cases** — Do not offer calls below this for companies with steady\u002Fflat trajectories and no high-value signals.\n8. **Always identify the use case** — This is the foundation for everything: the disposition, the framing, and the resources you link.\n9. **Always recommend a disposition** — Don't just write an email; state the qualification decision explicitly so the TAE can update Salesforce.\n10. **Always mention in-app support** for product questions — it's the fastest path to help.\n11. **PostHog is built for product engineers** — If no engineer is involved, that's a red flag for qualification.\n12. **Frame around problems, not products** — \"Here's how to understand why users drop off\" not \"Here's our Product Analytics feature.\"\n13. **Use company research to personalize the email** — Reference what they build, not just what they asked. It shows you did your homework.\n14. **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.\n15. **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.\n16. **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.\n",{"data":38,"body":39},{"name":4,"description":6},{"type":40,"children":41},"root",[42,51,57,64,150,156,161,168,173,242,271,277,285,299,307,325,333,341,347,352,385,391,401,407,412,470,476,481,661,667,672,715,725,731,736,744,767,775,798,803,809,814,822,845,850,855,860,898,903,909,935,941,1136,1142,1154,1227,1233,1244,1297,1303,1314,1359,1369,1375,1380,1413,1419,1425,1433,1438,1471,1484,1492,1510,1516,1521,1542,1547,1553,1558,1568,1578,1635,1645,1653,1671,1677,1687,1692,1702,1740,1745,1768,1774,1779,1802,1807,1825,1831,1836,1864,1869,1892,1898,1925,1931,1949,1955,1974,1982,2120,2128,2203,2213,2218,2241,2246,2269,2275,2288,2371,2377,2405,2411,2429,2452,2460,2485,2495,2501,2506,2559,2564,2595,2600,2623,2628,2671,2676,2699,2704,2737,2743,2806,2812,2817,2825,2857,2865,2891,2901,2911,2917,2922,2955,2960,2970,2976,2981,3054,3060,3065,3100,3106],{"type":43,"tag":44,"props":45,"children":47},"element","h1",{"id":46},"posthog-inbound-lead-disposition",[48],{"type":49,"value":50},"text","PostHog Inbound Lead Disposition",{"type":43,"tag":52,"props":53,"children":54},"p",{},[55],{"type":49,"value":56},"Evaluate inbound leads from Salesforce and either draft a response email or recommend a disposition. This skill is for any PostHog TAE handling inbound sales inquiries.",{"type":43,"tag":58,"props":59,"children":61},"h2",{"id":60},"core-workflow",[62],{"type":49,"value":63},"Core Workflow",{"type":43,"tag":65,"props":66,"children":67},"ol",{},[68,80,90,100,110,120,130,140],{"type":43,"tag":69,"props":70,"children":71},"li",{},[72,78],{"type":43,"tag":73,"props":74,"children":75},"strong",{},[76],{"type":49,"value":77},"Ingest lead context",{"type":49,"value":79}," — Read whatever the TAE provides (Salesforce fields, email body, notes)",{"type":43,"tag":69,"props":81,"children":82},{},[83,88],{"type":43,"tag":73,"props":84,"children":85},{},[86],{"type":49,"value":87},"Check Vitally for existing account context",{"type":49,"value":89}," — Search for the lead's email and email domain (see Step 0 below)",{"type":43,"tag":69,"props":91,"children":92},{},[93,98],{"type":43,"tag":73,"props":94,"children":95},{},[96],{"type":49,"value":97},"Research the company",{"type":49,"value":99}," — Web search to understand who they are, their funding, size, and growth trajectory (see Step 1 below)",{"type":43,"tag":69,"props":101,"children":102},{},[103,108],{"type":43,"tag":73,"props":104,"children":105},{},[106],{"type":49,"value":107},"Identify the use case",{"type":49,"value":109}," — Map the lead to one or more of PostHog's six use cases, informed by company research (see Step 2 below)",{"type":43,"tag":69,"props":111,"children":112},{},[113,118],{"type":43,"tag":73,"props":114,"children":115},{},[116],{"type":49,"value":117},"Qualify the lead",{"type":49,"value":119}," — Apply the disposition framework, informed by company research and growth trajectory (see Step 3 below)",{"type":43,"tag":69,"props":121,"children":122},{},[123,128],{"type":43,"tag":73,"props":124,"children":125},{},[126],{"type":49,"value":127},"Recommend a disposition",{"type":49,"value":129}," — State the recommended action and identified use case(s) clearly",{"type":43,"tag":69,"props":131,"children":132},{},[133,138],{"type":43,"tag":73,"props":134,"children":135},{},[136],{"type":49,"value":137},"Draft a response",{"type":49,"value":139}," — Write the appropriate email, framed around their use case (see Step 4 below)",{"type":43,"tag":69,"props":141,"children":142},{},[143,148],{"type":43,"tag":73,"props":144,"children":145},{},[146],{"type":49,"value":147},"Validate all URLs",{"type":49,"value":149}," — Fetch every link in the draft email to confirm it resolves and points to the intended content (see Step 5 below)",{"type":43,"tag":58,"props":151,"children":153},{"id":152},"step-0-check-vitally-for-existing-account-context",[154],{"type":49,"value":155},"Step 0: Check Vitally for Existing Account Context",{"type":43,"tag":52,"props":157,"children":158},{},[159],{"type":49,"value":160},"Before qualifying or drafting anything, check Vitally to see if this lead (or their company) is already a PostHog user. This changes the disposition and email framing significantly — an existing customer asking for help is different from a cold inbound.",{"type":43,"tag":162,"props":163,"children":165},"h3",{"id":164},"what-to-check",[166],{"type":49,"value":167},"What to check",{"type":43,"tag":52,"props":169,"children":170},{},[171],{"type":49,"value":172},"Run two Vitally lookups using the lead's email address:",{"type":43,"tag":65,"props":174,"children":175},{},[176,203],{"type":43,"tag":69,"props":177,"children":178},{},[179,184,186,193,195,201],{"type":43,"tag":73,"props":180,"children":181},{},[182],{"type":49,"value":183},"Search by exact email",{"type":49,"value":185}," — ",{"type":43,"tag":187,"props":188,"children":190},"code",{"className":189},[],[191],{"type":49,"value":192},"vitally:search_users",{"type":49,"value":194}," with ",{"type":43,"tag":187,"props":196,"children":198},{"className":197},[],[199],{"type":49,"value":200},"email",{"type":49,"value":202}," set to the lead's email address. This tells you if this specific person already has a PostHog account.",{"type":43,"tag":69,"props":204,"children":205},{},[206,211,212,217,218,224,226,232,234,240],{"type":43,"tag":73,"props":207,"children":208},{},[209],{"type":49,"value":210},"Search by email domain",{"type":49,"value":185},{"type":43,"tag":187,"props":213,"children":215},{"className":214},[],[216],{"type":49,"value":192},{"type":49,"value":194},{"type":43,"tag":187,"props":219,"children":221},{"className":220},[],[222],{"type":49,"value":223},"emailSubdomain",{"type":49,"value":225}," set to the domain portion of the lead's email (e.g., ",{"type":43,"tag":187,"props":227,"children":229},{"className":228},[],[230],{"type":49,"value":231},"acme.com",{"type":49,"value":233}," from ",{"type":43,"tag":187,"props":235,"children":237},{"className":236},[],[238],{"type":49,"value":239},"jane@acme.com",{"type":49,"value":241},"). This tells you if anyone at their company is already using PostHog.",{"type":43,"tag":52,"props":243,"children":244},{},[245,247,253,255,261,263,269],{"type":49,"value":246},"If either search returns results, pull up the associated account with ",{"type":43,"tag":187,"props":248,"children":250},{"className":249},[],[251],{"type":49,"value":252},"vitally:get_account_full",{"type":49,"value":254}," using the ",{"type":43,"tag":187,"props":256,"children":258},{"className":257},[],[259],{"type":49,"value":260},"accountId",{"type":49,"value":262}," from the user record(s). Use ",{"type":43,"tag":187,"props":264,"children":266},{"className":265},[],[267],{"type":49,"value":268},"detailLevel: \"summary\"",{"type":49,"value":270}," for a quick overview.",{"type":43,"tag":162,"props":272,"children":274},{"id":273},"how-to-use-what-you-find",[275],{"type":49,"value":276},"How to use what you find",{"type":43,"tag":52,"props":278,"children":279},{},[280],{"type":43,"tag":73,"props":281,"children":282},{},[283],{"type":49,"value":284},"Lead's email is an existing user:",{"type":43,"tag":286,"props":287,"children":288},"ul",{},[289,294],{"type":43,"tag":69,"props":290,"children":291},{},[292],{"type":49,"value":293},"They're already in PostHog. The email should acknowledge this (\"I can see you're already using PostHog\") and focus on their specific ask rather than onboarding-style resources.",{"type":43,"tag":69,"props":295,"children":296},{},[297],{"type":49,"value":298},"Check their account's MRR and health score — this informs whether they're a self-serve user reaching out to grow, or an existing account with an expansion opportunity.",{"type":43,"tag":52,"props":300,"children":301},{},[302],{"type":43,"tag":73,"props":303,"children":304},{},[305],{"type":49,"value":306},"Different person at the same company is already a user:",{"type":43,"tag":286,"props":308,"children":309},{},[310,315,320],{"type":43,"tag":69,"props":311,"children":312},{},[313],{"type":49,"value":314},"Their company is already on PostHog. Reference this in the email (\"I see your team is already using PostHog\") and ask how their request relates to the existing usage.",{"type":43,"tag":69,"props":316,"children":317},{},[318],{"type":49,"value":319},"Check who else is on the account — the lead may need to connect with the internal champion rather than start a separate evaluation.",{"type":43,"tag":69,"props":321,"children":322},{},[323],{"type":49,"value":324},"If the account already has a TAE assigned, flag this to avoid stepping on someone's book of business.",{"type":43,"tag":52,"props":326,"children":327},{},[328],{"type":43,"tag":73,"props":329,"children":330},{},[331],{"type":49,"value":332},"No results in Vitally:",{"type":43,"tag":286,"props":334,"children":335},{},[336],{"type":43,"tag":69,"props":337,"children":338},{},[339],{"type":49,"value":340},"Net new lead. Proceed with the standard qualification workflow below.",{"type":43,"tag":162,"props":342,"children":344},{"id":343},"what-to-surface-to-the-tae",[345],{"type":49,"value":346},"What to surface to the TAE",{"type":43,"tag":52,"props":348,"children":349},{},[350],{"type":49,"value":351},"When presenting the Vitally findings, include:",{"type":43,"tag":286,"props":353,"children":354},{},[355,360,365,370,375,380],{"type":43,"tag":69,"props":356,"children":357},{},[358],{"type":49,"value":359},"Whether the person or company was found",{"type":43,"tag":69,"props":361,"children":362},{},[363],{"type":49,"value":364},"Account name and current MRR (if applicable)",{"type":43,"tag":69,"props":366,"children":367},{},[368],{"type":49,"value":369},"Health score (if applicable)",{"type":43,"tag":69,"props":371,"children":372},{},[373],{"type":49,"value":374},"Assigned TAE (if any — important for routing)",{"type":43,"tag":69,"props":376,"children":377},{},[378],{"type":49,"value":379},"Number of users on the account",{"type":43,"tag":69,"props":381,"children":382},{},[383],{"type":49,"value":384},"A one-line recommendation on how this changes the response (e.g., \"Existing $3K\u002Fmo account, no TAE assigned — this is an expansion opportunity, not a new lead\")",{"type":43,"tag":58,"props":386,"children":388},{"id":387},"step-1-research-the-company",[389],{"type":49,"value":390},"Step 1: Research the Company",{"type":43,"tag":52,"props":392,"children":393},{},[394,399],{"type":43,"tag":73,"props":395,"children":396},{},[397],{"type":49,"value":398},"This step is mandatory for every lead.",{"type":49,"value":400}," The lead's form submission alone is not enough information to qualify or disqualify. A 10K MAU lead from a $6B startup and a 10K MAU lead from a 5-person agency require completely different dispositions.",{"type":43,"tag":162,"props":402,"children":404},{"id":403},"what-to-research",[405],{"type":49,"value":406},"What to research",{"type":43,"tag":52,"props":408,"children":409},{},[410],{"type":49,"value":411},"Run 1-3 web searches to understand the company. Start with the company name and domain:",{"type":43,"tag":286,"props":413,"children":414},{},[415,434,451],{"type":43,"tag":69,"props":416,"children":417},{},[418,424,426,432],{"type":43,"tag":187,"props":419,"children":421},{"className":420},[],[422],{"type":49,"value":423},"web_search",{"type":49,"value":425}," for ",{"type":43,"tag":187,"props":427,"children":429},{"className":428},[],[430],{"type":49,"value":431},"[Company Name] [domain]",{"type":49,"value":433}," — Get the basics: what they do, who they are",{"type":43,"tag":69,"props":435,"children":436},{},[437,442,443,449],{"type":43,"tag":187,"props":438,"children":440},{"className":439},[],[441],{"type":49,"value":423},{"type":49,"value":425},{"type":43,"tag":187,"props":444,"children":446},{"className":445},[],[447],{"type":49,"value":448},"[Company Name] funding employees",{"type":49,"value":450}," — Get firmographics: funding stage, headcount, growth signals",{"type":43,"tag":69,"props":452,"children":453},{},[454,456,462,464],{"type":49,"value":455},"If the company appears to be notable or well-funded, search for recent news: ",{"type":43,"tag":187,"props":457,"children":459},{"className":458},[],[460],{"type":49,"value":461},"[Company Name] 2026",{"type":49,"value":463}," or ",{"type":43,"tag":187,"props":465,"children":467},{"className":466},[],[468],{"type":49,"value":469},"[Company Name] news",{"type":43,"tag":162,"props":471,"children":473},{"id":472},"what-to-extract",[474],{"type":49,"value":475},"What to extract",{"type":43,"tag":52,"props":477,"children":478},{},[479],{"type":49,"value":480},"From the research, identify and record:",{"type":43,"tag":482,"props":483,"children":484},"table",{},[485,509],{"type":43,"tag":486,"props":487,"children":488},"thead",{},[489],{"type":43,"tag":490,"props":491,"children":492},"tr",{},[493,499,504],{"type":43,"tag":494,"props":495,"children":496},"th",{},[497],{"type":49,"value":498},"Signal",{"type":43,"tag":494,"props":500,"children":501},{},[502],{"type":49,"value":503},"Why It Matters",{"type":43,"tag":494,"props":505,"children":506},{},[507],{"type":49,"value":508},"Example",{"type":43,"tag":510,"props":511,"children":512},"tbody",{},[513,535,556,577,598,619,640],{"type":43,"tag":490,"props":514,"children":515},{},[516,525,530],{"type":43,"tag":517,"props":518,"children":519},"td",{},[520],{"type":43,"tag":73,"props":521,"children":522},{},[523],{"type":49,"value":524},"What they build",{"type":43,"tag":517,"props":526,"children":527},{},[528],{"type":49,"value":529},"Determines use case mapping and whether they're ICP",{"type":43,"tag":517,"props":531,"children":532},{},[533],{"type":49,"value":534},"\"AI tools for manufacturing\" → AI\u002FLLM Obs is relevant",{"type":43,"tag":490,"props":536,"children":537},{},[538,546,551],{"type":43,"tag":517,"props":539,"children":540},{},[541],{"type":43,"tag":73,"props":542,"children":543},{},[544],{"type":49,"value":545},"Funding stage and amount",{"type":43,"tag":517,"props":547,"children":548},{},[549],{"type":49,"value":550},"Proxy for budget and growth trajectory",{"type":43,"tag":517,"props":552,"children":553},{},[554],{"type":49,"value":555},"Series B, $50M → likely has budget for tooling",{"type":43,"tag":490,"props":557,"children":558},{},[559,567,572],{"type":43,"tag":517,"props":560,"children":561},{},[562],{"type":43,"tag":73,"props":563,"children":564},{},[565],{"type":49,"value":566},"Employee count",{"type":43,"tag":517,"props":568,"children":569},{},[570],{"type":49,"value":571},"Proxy for spend potential and team complexity",{"type":43,"tag":517,"props":573,"children":574},{},[575],{"type":49,"value":576},"200 employees → multiple teams, multi-project potential",{"type":43,"tag":490,"props":578,"children":579},{},[580,588,593],{"type":43,"tag":517,"props":581,"children":582},{},[583],{"type":43,"tag":73,"props":584,"children":585},{},[586],{"type":49,"value":587},"Engineering team size or ratio",{"type":43,"tag":517,"props":589,"children":590},{},[591],{"type":49,"value":592},"PostHog's buyer is engineers; more engineers = better fit",{"type":43,"tag":517,"props":594,"children":595},{},[596],{"type":49,"value":597},"\"80% of team is engineering\" → strong ICP signal",{"type":43,"tag":490,"props":599,"children":600},{},[601,609,614],{"type":43,"tag":517,"props":602,"children":603},{},[604],{"type":43,"tag":73,"props":605,"children":606},{},[607],{"type":49,"value":608},"Growth trajectory",{"type":43,"tag":517,"props":610,"children":611},{},[612],{"type":49,"value":613},"Determines whether current MAU is the ceiling or the floor",{"type":43,"tag":517,"props":615,"children":616},{},[617],{"type":49,"value":618},"Founded 6 months ago, hiring aggressively → MAU will grow fast",{"type":43,"tag":490,"props":620,"children":621},{},[622,630,635],{"type":43,"tag":517,"props":623,"children":624},{},[625],{"type":43,"tag":73,"props":626,"children":627},{},[628],{"type":49,"value":629},"Recent news",{"type":43,"tag":517,"props":631,"children":632},{},[633],{"type":49,"value":634},"Acquisitions, launches, pivots that change context",{"type":43,"tag":517,"props":636,"children":637},{},[638],{"type":49,"value":639},"Just acquired an AI startup → expanding product surface",{"type":43,"tag":490,"props":641,"children":642},{},[643,651,656],{"type":43,"tag":517,"props":644,"children":645},{},[646],{"type":43,"tag":73,"props":647,"children":648},{},[649],{"type":49,"value":650},"Business model",{"type":43,"tag":517,"props":652,"children":653},{},[654],{"type":49,"value":655},"SaaS, marketplace, dev tools, agency, etc.",{"type":43,"tag":517,"props":657,"children":658},{},[659],{"type":49,"value":660},"B2B SaaS → classic PostHog ICP",{"type":43,"tag":162,"props":662,"children":664},{"id":663},"classify-the-growth-trajectory",[665],{"type":49,"value":666},"Classify the growth trajectory",{"type":43,"tag":52,"props":668,"children":669},{},[670],{"type":49,"value":671},"Based on the research, classify the company into one of four growth trajectories:",{"type":43,"tag":286,"props":673,"children":674},{},[675,685,695,705],{"type":43,"tag":69,"props":676,"children":677},{},[678,683],{"type":43,"tag":73,"props":679,"children":680},{},[681],{"type":49,"value":682},"Accelerating",{"type":49,"value":684},": Recent large funding round (especially if raised in last 12 months), aggressive hiring, early-stage with significant capital, or clear signs of rapid expansion. Current MAU is almost certainly not the ceiling. Examples: well-funded Series A+ startups, companies that just raised mega-rounds, companies with \"hundreds of open roles.\"",{"type":43,"tag":69,"props":686,"children":687},{},[688,693],{"type":43,"tag":73,"props":689,"children":690},{},[691],{"type":49,"value":692},"Steady",{"type":49,"value":694},": Established company, moderate and predictable growth. Current MAU is a reasonable proxy for near-term spend. Examples: mid-market SaaS with stable revenue, mature PLG companies.",{"type":43,"tag":69,"props":696,"children":697},{},[698,703],{"type":43,"tag":73,"props":699,"children":700},{},[701],{"type":49,"value":702},"Early\u002Funknown",{"type":49,"value":704},": New company, limited public information, hard to assess trajectory. Treat current MAU as the best available signal but note the uncertainty. Examples: pre-seed startups, stealth-mode companies with no public footprint.",{"type":43,"tag":69,"props":706,"children":707},{},[708,713],{"type":43,"tag":73,"props":709,"children":710},{},[711],{"type":49,"value":712},"Flat\u002Fdeclining",{"type":49,"value":714},": No growth signals, layoffs, or signs of contraction. Current MAU may overstate future spend. Examples: companies with recent layoffs, shrinking teams.",{"type":43,"tag":52,"props":716,"children":717},{},[718,723],{"type":43,"tag":73,"props":719,"children":720},{},[721],{"type":49,"value":722},"The growth trajectory classification directly affects qualification.",{"type":49,"value":724}," See Step 3 for how it modifies the $20K threshold.",{"type":43,"tag":162,"props":726,"children":728},{"id":727},"detect-multi-product-signals",[729],{"type":49,"value":730},"Detect multi-product signals",{"type":43,"tag":52,"props":732,"children":733},{},[734],{"type":49,"value":735},"While researching, watch for signals that the lead's company has (or is building) multiple products. This is a spend multiplier because each product typically becomes a separate PostHog project with its own event volume.",{"type":43,"tag":52,"props":737,"children":738},{},[739],{"type":43,"tag":73,"props":740,"children":741},{},[742],{"type":49,"value":743},"Signals in the lead's message:",{"type":43,"tag":286,"props":745,"children":746},{},[747,752,757,762],{"type":43,"tag":69,"props":748,"children":749},{},[750],{"type":49,"value":751},"\"some of our products\" \u002F \"multiple products\" \u002F \"across our portfolio\"",{"type":43,"tag":69,"props":753,"children":754},{},[755],{"type":49,"value":756},"\"several teams\" \u002F \"multiple teams\" \u002F \"different business units\"",{"type":43,"tag":69,"props":758,"children":759},{},[760],{"type":49,"value":761},"\"our platform and our apps\" \u002F \"our web app and mobile app\"",{"type":43,"tag":69,"props":763,"children":764},{},[765],{"type":49,"value":766},"\"integrate into our stack\" (implies breadth)",{"type":43,"tag":52,"props":768,"children":769},{},[770],{"type":43,"tag":73,"props":771,"children":772},{},[773],{"type":49,"value":774},"Signals from company research:",{"type":43,"tag":286,"props":776,"children":777},{},[778,783,788,793],{"type":43,"tag":69,"props":779,"children":780},{},[781],{"type":49,"value":782},"Company has multiple product lines or brands",{"type":43,"tag":69,"props":784,"children":785},{},[786],{"type":49,"value":787},"Company recently acquired other companies (each acquisition may have its own product)",{"type":43,"tag":69,"props":789,"children":790},{},[791],{"type":49,"value":792},"Job postings reference multiple product teams",{"type":43,"tag":69,"props":794,"children":795},{},[796],{"type":49,"value":797},"Company website shows multiple distinct products",{"type":43,"tag":52,"props":799,"children":800},{},[801],{"type":49,"value":802},"When multi-product signals are present, note the estimated product count (or range) and factor it into the MAU multiplier. A company with 5 products at 10K MAU each is a 50K MAU opportunity, not a 10K one.",{"type":43,"tag":162,"props":804,"children":806},{"id":805},"detect-aiml-company-signals",[807],{"type":49,"value":808},"Detect AI\u002FML company signals",{"type":43,"tag":52,"props":810,"children":811},{},[812],{"type":49,"value":813},"If company research reveals the company is AI-native (building AI\u002FML products as their core business), flag AI\u002FLLM Observability as a probable secondary use case even if the lead's message doesn't mention AI, LLMs, model costs, or prompts.",{"type":43,"tag":52,"props":815,"children":816},{},[817],{"type":43,"tag":73,"props":818,"children":819},{},[820],{"type":49,"value":821},"AI-native signals:",{"type":43,"tag":286,"props":823,"children":824},{},[825,830,835,840],{"type":43,"tag":69,"props":826,"children":827},{},[828],{"type":49,"value":829},"Company description mentions AI, ML, LLM, or \"artificial intelligence\" as core to what they build",{"type":43,"tag":69,"props":831,"children":832},{},[833],{"type":49,"value":834},"Company is in an AI-adjacent industry (AI infrastructure, AI applications, AI research)",{"type":43,"tag":69,"props":836,"children":837},{},[838],{"type":49,"value":839},"Team is heavily ML\u002FAI engineers",{"type":43,"tag":69,"props":841,"children":842},{},[843],{"type":49,"value":844},"Recent AI-related acquisitions or product launches",{"type":43,"tag":52,"props":846,"children":847},{},[848],{"type":49,"value":849},"When detected, include AI\u002FLLM Observability in the use case assessment and mention it in the email as a relevant capability, even if the lead didn't ask about it. Frame it as: \"since you're building AI products, you might also find our LLM analytics useful for tracking model costs and performance.\"",{"type":43,"tag":162,"props":851,"children":853},{"id":852},"what-to-surface-to-the-tae-1",[854],{"type":49,"value":346},{"type":43,"tag":52,"props":856,"children":857},{},[858],{"type":49,"value":859},"Present the company research as a brief profile including:",{"type":43,"tag":286,"props":861,"children":862},{},[863,868,873,878,883,888,893],{"type":43,"tag":69,"props":864,"children":865},{},[866],{"type":49,"value":867},"What the company does (one sentence)",{"type":43,"tag":69,"props":869,"children":870},{},[871],{"type":49,"value":872},"Funding and valuation (if available)",{"type":43,"tag":69,"props":874,"children":875},{},[876],{"type":49,"value":877},"Employee count and engineering composition (if available)",{"type":43,"tag":69,"props":879,"children":880},{},[881],{"type":49,"value":882},"Growth trajectory classification",{"type":43,"tag":69,"props":884,"children":885},{},[886],{"type":49,"value":887},"Multi-product signals (if any)",{"type":43,"tag":69,"props":889,"children":890},{},[891],{"type":49,"value":892},"AI-native flag (if applicable)",{"type":43,"tag":69,"props":894,"children":895},{},[896],{"type":49,"value":897},"Any notable context (recent news, acquisitions, leadership)",{"type":43,"tag":52,"props":899,"children":900},{},[901],{"type":49,"value":902},"This goes right after the Vitally findings and before the use case assessment.",{"type":43,"tag":58,"props":904,"children":906},{"id":905},"step-2-identify-the-use-case",[907],{"type":49,"value":908},"Step 2: Identify the Use Case",{"type":43,"tag":52,"props":910,"children":911},{},[912,914,919,921,926,928,933],{"type":49,"value":913},"Every lead maps to one or more of PostHog's six use cases. Identifying the use case determines how to frame the response, what products to highlight, and what resources to link. Evaluate the ",{"type":43,"tag":73,"props":915,"children":916},{},[917],{"type":49,"value":918},"person\u002Fpersona",{"type":49,"value":920},", ",{"type":43,"tag":73,"props":922,"children":923},{},[924],{"type":49,"value":925},"company",{"type":49,"value":927}," (informed by your Step 1 research), and ",{"type":43,"tag":73,"props":929,"children":930},{},[931],{"type":49,"value":932},"message",{"type":49,"value":934}," to determine the match.",{"type":43,"tag":162,"props":936,"children":938},{"id":937},"the-six-use-cases",[939],{"type":49,"value":940},"The Six Use Cases",{"type":43,"tag":482,"props":942,"children":943},{},[944,970],{"type":43,"tag":486,"props":945,"children":946},{},[947],{"type":43,"tag":490,"props":948,"children":949},{},[950,955,960,965],{"type":43,"tag":494,"props":951,"children":952},{},[953],{"type":49,"value":954},"Use Case",{"type":43,"tag":494,"props":956,"children":957},{},[958],{"type":49,"value":959},"Job to Be Done",{"type":43,"tag":494,"props":961,"children":962},{},[963],{"type":49,"value":964},"Core Buyer Persona",{"type":43,"tag":494,"props":966,"children":967},{},[968],{"type":49,"value":969},"Key Signals in the Lead",{"type":43,"tag":510,"props":971,"children":972},{},[973,999,1025,1051,1077,1110],{"type":43,"tag":490,"props":974,"children":975},{},[976,984,989,994],{"type":43,"tag":517,"props":977,"children":978},{},[979],{"type":43,"tag":73,"props":980,"children":981},{},[982],{"type":49,"value":983},"Product Intelligence",{"type":43,"tag":517,"props":985,"children":986},{},[987],{"type":49,"value":988},"\"Help me understand what users do, why they do it, and what to build next.\"",{"type":43,"tag":517,"props":990,"children":991},{},[992],{"type":49,"value":993},"PMs, designers, product engineers, founders",{"type":43,"tag":517,"props":995,"children":996},{},[997],{"type":49,"value":998},"Mentions analytics, funnels, retention, user behavior, \"why users drop off\", feature adoption, NPS, surveys, session replay for UX research",{"type":43,"tag":490,"props":1000,"children":1001},{},[1002,1010,1015,1020],{"type":43,"tag":517,"props":1003,"children":1004},{},[1005],{"type":43,"tag":73,"props":1006,"children":1007},{},[1008],{"type":49,"value":1009},"Release Engineering",{"type":43,"tag":517,"props":1011,"children":1012},{},[1013],{"type":49,"value":1014},"\"Help me ship faster without breaking things.\"",{"type":43,"tag":517,"props":1016,"children":1017},{},[1018],{"type":49,"value":1019},"Engineering managers, platform teams, developers",{"type":43,"tag":517,"props":1021,"children":1022},{},[1023],{"type":49,"value":1024},"Mentions feature flags, rollouts, A\u002FB testing releases, kill switches, progressive delivery, replacing LaunchDarkly",{"type":43,"tag":490,"props":1026,"children":1027},{},[1028,1036,1041,1046],{"type":43,"tag":517,"props":1029,"children":1030},{},[1031],{"type":43,"tag":73,"props":1032,"children":1033},{},[1034],{"type":49,"value":1035},"Observability",{"type":43,"tag":517,"props":1037,"children":1038},{},[1039],{"type":49,"value":1040},"\"Help me know when things break, understand why, and fix them fast.\"",{"type":43,"tag":517,"props":1042,"children":1043},{},[1044],{"type":49,"value":1045},"SREs, platform engineers, DevOps",{"type":43,"tag":517,"props":1047,"children":1048},{},[1049],{"type":49,"value":1050},"Mentions error tracking, bug reproduction, replacing Sentry\u002FDatadog, logging, incident response, stack traces",{"type":43,"tag":490,"props":1052,"children":1053},{},[1054,1062,1067,1072],{"type":43,"tag":517,"props":1055,"children":1056},{},[1057],{"type":43,"tag":73,"props":1058,"children":1059},{},[1060],{"type":49,"value":1061},"Growth & Marketing",{"type":43,"tag":517,"props":1063,"children":1064},{},[1065],{"type":49,"value":1066},"\"Help me understand what drives acquisition, conversion, and revenue.\"",{"type":43,"tag":517,"props":1068,"children":1069},{},[1070],{"type":49,"value":1071},"Growth engineers, marketing leads, CRO, GTM engineers",{"type":43,"tag":517,"props":1073,"children":1074},{},[1075],{"type":49,"value":1076},"Mentions attribution, ROAS, campaign performance, replacing GA4\u002FSegment, conversion optimization, onboarding automation, marketing stack consolidation",{"type":43,"tag":490,"props":1078,"children":1079},{},[1080,1088,1093,1098],{"type":43,"tag":517,"props":1081,"children":1082},{},[1083],{"type":43,"tag":73,"props":1084,"children":1085},{},[1086],{"type":49,"value":1087},"AI\u002FLLM Observability",{"type":43,"tag":517,"props":1089,"children":1090},{},[1091],{"type":49,"value":1092},"\"Help me understand how my AI features perform, what they cost, and how users interact with them.\"",{"type":43,"tag":517,"props":1094,"children":1095},{},[1096],{"type":49,"value":1097},"AI\u002FML engineers, AI PMs, AI founders",{"type":43,"tag":517,"props":1099,"children":1100},{},[1101,1103,1108],{"type":49,"value":1102},"Mentions LLM, AI features, model costs, prompt testing, AI quality, replacing Langfuse\u002FHelicone, token usage. ",{"type":43,"tag":73,"props":1104,"children":1105},{},[1106],{"type":49,"value":1107},"Also inferred from company research",{"type":49,"value":1109}," — if the company is AI-native, this use case is relevant even if the lead didn't mention it.",{"type":43,"tag":490,"props":1111,"children":1112},{},[1113,1121,1126,1131],{"type":43,"tag":517,"props":1114,"children":1115},{},[1116],{"type":43,"tag":73,"props":1117,"children":1118},{},[1119],{"type":49,"value":1120},"Data Infrastructure",{"type":43,"tag":517,"props":1122,"children":1123},{},[1124],{"type":49,"value":1125},"\"Help me unify product data with business data and get it where it needs to go.\"",{"type":43,"tag":517,"props":1127,"children":1128},{},[1129],{"type":49,"value":1130},"Data engineers, analytics engineers, product ops",{"type":43,"tag":517,"props":1132,"children":1133},{},[1134],{"type":49,"value":1135},"Mentions data warehouse, Snowflake\u002FBigQuery, data pipelines, batch exports, combining PostHog data with Stripe\u002FCRM, replacing Segment\u002FFivetran",{"type":43,"tag":162,"props":1137,"children":1139},{"id":1138},"mapping-persona-to-use-case",[1140],{"type":49,"value":1141},"Mapping Persona to Use Case",{"type":43,"tag":52,"props":1143,"children":1144},{},[1145,1147,1152],{"type":49,"value":1146},"The ",{"type":43,"tag":73,"props":1148,"children":1149},{},[1150],{"type":49,"value":1151},"person's role",{"type":49,"value":1153}," is one of the strongest signals:",{"type":43,"tag":286,"props":1155,"children":1156},{},[1157,1167,1177,1187,1197,1207,1217],{"type":43,"tag":69,"props":1158,"children":1159},{},[1160,1165],{"type":43,"tag":73,"props":1161,"children":1162},{},[1163],{"type":49,"value":1164},"PM, Head of Product, UX Researcher, Designer",{"type":49,"value":1166}," → Product Intelligence",{"type":43,"tag":69,"props":1168,"children":1169},{},[1170,1175],{"type":43,"tag":73,"props":1171,"children":1172},{},[1173],{"type":49,"value":1174},"Engineering Manager, VP Eng, Platform Engineer, Developer",{"type":49,"value":1176}," → Release Engineering (or Observability if they mention errors\u002Fincidents)",{"type":43,"tag":69,"props":1178,"children":1179},{},[1180,1185],{"type":43,"tag":73,"props":1181,"children":1182},{},[1183],{"type":49,"value":1184},"SRE, DevOps, Infrastructure Engineer",{"type":49,"value":1186}," → Observability",{"type":43,"tag":69,"props":1188,"children":1189},{},[1190,1195],{"type":43,"tag":73,"props":1191,"children":1192},{},[1193],{"type":49,"value":1194},"Growth Engineer, Marketing Lead, CRO, GTM Engineer, Demand Gen",{"type":49,"value":1196}," → Growth & Marketing",{"type":43,"tag":69,"props":1198,"children":1199},{},[1200,1205],{"type":43,"tag":73,"props":1201,"children":1202},{},[1203],{"type":49,"value":1204},"AI\u002FML Engineer, AI PM, AI Founder",{"type":49,"value":1206}," → AI\u002FLLM Observability",{"type":43,"tag":69,"props":1208,"children":1209},{},[1210,1215],{"type":43,"tag":73,"props":1211,"children":1212},{},[1213],{"type":49,"value":1214},"Data Engineer, Analytics Engineer, Head of Data, RevOps",{"type":49,"value":1216}," → Data Infrastructure",{"type":43,"tag":69,"props":1218,"children":1219},{},[1220,1225],{"type":43,"tag":73,"props":1221,"children":1222},{},[1223],{"type":49,"value":1224},"Founder\u002FCTO (early stage)",{"type":49,"value":1226}," → Usually Product Intelligence or AI\u002FLLM Obs depending on the product; may span multiple use cases",{"type":43,"tag":162,"props":1228,"children":1230},{"id":1229},"mapping-company-to-use-case",[1231],{"type":49,"value":1232},"Mapping Company to Use Case",{"type":43,"tag":52,"props":1234,"children":1235},{},[1236,1237,1242],{"type":49,"value":1146},{"type":43,"tag":73,"props":1238,"children":1239},{},[1240],{"type":49,"value":1241},"company type",{"type":49,"value":1243}," (from your Step 1 research) helps narrow it:",{"type":43,"tag":286,"props":1245,"children":1246},{},[1247,1257,1267,1277,1287],{"type":43,"tag":69,"props":1248,"children":1249},{},[1250,1255],{"type":43,"tag":73,"props":1251,"children":1252},{},[1253],{"type":49,"value":1254},"AI-native startup",{"type":49,"value":1256}," → AI\u002FLLM Observability is almost always relevant, often alongside Product Intelligence",{"type":43,"tag":69,"props":1258,"children":1259},{},[1260,1265],{"type":43,"tag":73,"props":1261,"children":1262},{},[1263],{"type":49,"value":1264},"PLG SaaS",{"type":49,"value":1266}," → Product Intelligence + Growth & Marketing are the most common pair",{"type":43,"tag":69,"props":1268,"children":1269},{},[1270,1275],{"type":43,"tag":73,"props":1271,"children":1272},{},[1273],{"type":49,"value":1274},"Enterprise with multiple teams",{"type":49,"value":1276}," → Often starts as one use case but the expansion potential spans several",{"type":43,"tag":69,"props":1278,"children":1279},{},[1280,1285],{"type":43,"tag":73,"props":1281,"children":1282},{},[1283],{"type":49,"value":1284},"E-commerce \u002F marketplace",{"type":49,"value":1286}," → Growth & Marketing (conversion, attribution) + Product Intelligence (user behavior)",{"type":43,"tag":69,"props":1288,"children":1289},{},[1290,1295],{"type":43,"tag":73,"props":1291,"children":1292},{},[1293],{"type":49,"value":1294},"Developer tools \u002F infrastructure",{"type":49,"value":1296}," → Release Engineering + Observability",{"type":43,"tag":162,"props":1298,"children":1300},{"id":1299},"mapping-message-to-use-case",[1301],{"type":49,"value":1302},"Mapping Message to Use Case",{"type":43,"tag":52,"props":1304,"children":1305},{},[1306,1307,1312],{"type":49,"value":1146},{"type":43,"tag":73,"props":1308,"children":1309},{},[1310],{"type":49,"value":1311},"specific ask",{"type":49,"value":1313}," confirms or overrides the persona\u002Fcompany signal:",{"type":43,"tag":286,"props":1315,"children":1316},{},[1317,1322,1327,1332,1337,1342,1347],{"type":43,"tag":69,"props":1318,"children":1319},{},[1320],{"type":49,"value":1321},"\"We want to understand user behavior\" → Product Intelligence",{"type":43,"tag":69,"props":1323,"children":1324},{},[1325],{"type":49,"value":1326},"\"We need feature flags\" or \"replacing LaunchDarkly\" → Release Engineering",{"type":43,"tag":69,"props":1328,"children":1329},{},[1330],{"type":49,"value":1331},"\"We need error tracking\" or \"replacing Sentry\" → Observability",{"type":43,"tag":69,"props":1333,"children":1334},{},[1335],{"type":49,"value":1336},"\"We want attribution\" or \"replacing GA4\" → Growth & Marketing",{"type":43,"tag":69,"props":1338,"children":1339},{},[1340],{"type":49,"value":1341},"\"We're building AI features\" or \"LLM costs\" → AI\u002FLLM Observability",{"type":43,"tag":69,"props":1343,"children":1344},{},[1345],{"type":49,"value":1346},"\"We need to get data into Snowflake\" → Data Infrastructure",{"type":43,"tag":69,"props":1348,"children":1349},{},[1350,1352,1357],{"type":49,"value":1351},"Vague \"show me features\" \u002F \"want a demo\" → Can't determine use case from the message alone; ",{"type":43,"tag":73,"props":1353,"children":1354},{},[1355],{"type":49,"value":1356},"use company research to infer the most likely use case(s)",{"type":49,"value":1358},", then ask a targeted clarifying question to confirm",{"type":43,"tag":52,"props":1360,"children":1361},{},[1362,1367],{"type":43,"tag":73,"props":1363,"children":1364},{},[1365],{"type":49,"value":1366},"If the use case is ambiguous even after company research",{"type":49,"value":1368},", include a targeted clarifying question in the email to narrow it down. Frame the question around their problem, not PostHog products: \"What's the main problem you're trying to solve?\" is better than \"Which PostHog product are you interested in?\"",{"type":43,"tag":162,"props":1370,"children":1372},{"id":1371},"multiple-use-cases",[1373],{"type":49,"value":1374},"Multiple Use Cases",{"type":43,"tag":52,"props":1376,"children":1377},{},[1378],{"type":49,"value":1379},"Many leads map to more than one use case. When this happens:",{"type":43,"tag":286,"props":1381,"children":1382},{},[1383,1393,1403],{"type":43,"tag":69,"props":1384,"children":1385},{},[1386,1391],{"type":43,"tag":73,"props":1387,"children":1388},{},[1389],{"type":49,"value":1390},"Lead with the primary use case",{"type":49,"value":1392}," — the one most closely matching their stated pain",{"type":43,"tag":69,"props":1394,"children":1395},{},[1396,1401],{"type":43,"tag":73,"props":1397,"children":1398},{},[1399],{"type":49,"value":1400},"Mention the secondary use case as a natural extension",{"type":49,"value":1402}," — \"PostHog also handles X, which tends to come up once teams are doing Y\"",{"type":43,"tag":69,"props":1404,"children":1405},{},[1406,1411],{"type":43,"tag":73,"props":1407,"children":1408},{},[1409],{"type":49,"value":1410},"Don't try to sell the entire platform",{"type":49,"value":1412}," — focus on solving the problem they came in with",{"type":43,"tag":58,"props":1414,"children":1416},{"id":1415},"step-3-qualify-the-lead",[1417],{"type":49,"value":1418},"Step 3: Qualify the Lead",{"type":43,"tag":162,"props":1420,"children":1422},{"id":1421},"growth-trajectory-override",[1423],{"type":49,"value":1424},"Growth Trajectory Override",{"type":43,"tag":52,"props":1426,"children":1427},{},[1428],{"type":43,"tag":73,"props":1429,"children":1430},{},[1431],{"type":49,"value":1432},"The $20K annual spend threshold is the default qualification bar, but growth trajectory can override it.",{"type":43,"tag":52,"props":1434,"children":1435},{},[1436],{"type":49,"value":1437},"When all of the following are true, qualify for a call even if current MAU alone wouldn't hit $20K:",{"type":43,"tag":65,"props":1439,"children":1440},{},[1441,1451,1461],{"type":43,"tag":69,"props":1442,"children":1443},{},[1444,1449],{"type":43,"tag":73,"props":1445,"children":1446},{},[1447],{"type":49,"value":1448},"Growth trajectory is \"Accelerating\"",{"type":49,"value":1450}," — Recent large funding, aggressive hiring, early-stage with significant capital",{"type":43,"tag":69,"props":1452,"children":1453},{},[1454,1459],{"type":43,"tag":73,"props":1455,"children":1456},{},[1457],{"type":49,"value":1458},"High-value company signals",{"type":49,"value":1460}," — At least two of: $10M+ in funding, 50+ employees, engineering-heavy team, multi-product, AI-native",{"type":43,"tag":69,"props":1462,"children":1463},{},[1464,1469],{"type":43,"tag":73,"props":1465,"children":1466},{},[1467],{"type":49,"value":1468},"Reasonable path to $20K within 12 months",{"type":49,"value":1470}," — Based on growth trajectory and multi-product multiplier, it's plausible they'll reach the threshold as they scale",{"type":43,"tag":52,"props":1472,"children":1473},{},[1474,1476,1482],{"type":49,"value":1475},"When the override applies, note it explicitly in the disposition: \"Current MAU of 10K is below the $20K threshold, but growth trajectory is Accelerating (",{"type":43,"tag":1477,"props":1478,"children":1479},"span",{},[1480],{"type":49,"value":1481},"$X funding, Y employees, etc.",{"type":49,"value":1483},") with multi-product potential. Qualifying for call based on trajectory.\"",{"type":43,"tag":52,"props":1485,"children":1486},{},[1487],{"type":43,"tag":73,"props":1488,"children":1489},{},[1490],{"type":49,"value":1491},"When the override does NOT apply:",{"type":43,"tag":286,"props":1493,"children":1494},{},[1495,1500,1505],{"type":43,"tag":69,"props":1496,"children":1497},{},[1498],{"type":49,"value":1499},"Growth trajectory is Steady, Early\u002Funknown, or Flat — stick to the $20K threshold based on current signals",{"type":43,"tag":69,"props":1501,"children":1502},{},[1503],{"type":49,"value":1504},"The company has funding but the lead's use case is narrow and unlikely to expand (e.g., a well-funded company asking about feature flags for one internal tool)",{"type":43,"tag":69,"props":1506,"children":1507},{},[1508],{"type":49,"value":1509},"The lead is from a large company but the team using PostHog would be tiny with no expansion path",{"type":43,"tag":162,"props":1511,"children":1513},{"id":1512},"multi-product-spend-multiplier",[1514],{"type":49,"value":1515},"Multi-Product Spend Multiplier",{"type":43,"tag":52,"props":1517,"children":1518},{},[1519],{"type":49,"value":1520},"When multi-product signals are detected (from the lead's message or company research), adjust the MAU estimate:",{"type":43,"tag":286,"props":1522,"children":1523},{},[1524,1532,1537],{"type":43,"tag":69,"props":1525,"children":1526},{},[1527],{"type":43,"tag":73,"props":1528,"children":1529},{},[1530],{"type":49,"value":1531},"Stated MAU × estimated product count = adjusted MAU estimate",{"type":43,"tag":69,"props":1533,"children":1534},{},[1535],{"type":49,"value":1536},"Use the adjusted estimate for qualification, not the raw stated MAU",{"type":43,"tag":69,"props":1538,"children":1539},{},[1540],{"type":49,"value":1541},"Note the multiplier in the disposition: \"10K MAU stated, but 'some of our products' + company research suggests 3-5 products → 30-50K adjusted MAU\"",{"type":43,"tag":52,"props":1543,"children":1544},{},[1545],{"type":49,"value":1546},"This multiplier is an estimate, not a guarantee. It shifts the disposition from \"definitely below threshold\" to \"plausibly above threshold, worth a call to confirm.\"",{"type":43,"tag":162,"props":1548,"children":1550},{"id":1549},"special-case-competitor-displacement",[1551],{"type":49,"value":1552},"Special Case: Competitor Displacement",{"type":43,"tag":52,"props":1554,"children":1555},{},[1556],{"type":49,"value":1557},"When a lead mentions they're currently using a competitor and looking to switch (e.g., \"using Heap looking to move\", \"replacing Amplitude\", \"evaluating alternatives to Sentry\", \"moving off LaunchDarkly\"), this is a high-signal inbound. They already have budget allocated to a tool in the category, they have a defined need, and they likely have some urgency.",{"type":43,"tag":52,"props":1559,"children":1560},{},[1561,1566],{"type":43,"tag":73,"props":1562,"children":1563},{},[1564],{"type":49,"value":1565},"However, the $20K floor still applies (unless the growth trajectory override kicks in).",{"type":49,"value":1567}," A competitor displacement lead still needs to show potential for $20K+ annual spend to qualify for a call. Don't offer a call just because they're switching from a paid tool.",{"type":43,"tag":52,"props":1569,"children":1570},{},[1571,1576],{"type":43,"tag":73,"props":1572,"children":1573},{},[1574],{"type":49,"value":1575},"For competitor displacement leads, the initial response should surface BANT signals",{"type":49,"value":1577}," before offering a call or routing to self-serve. Ask targeted discovery questions that uncover:",{"type":43,"tag":286,"props":1579,"children":1580},{},[1581,1591,1601,1625],{"type":43,"tag":69,"props":1582,"children":1583},{},[1584,1589],{"type":43,"tag":73,"props":1585,"children":1586},{},[1587],{"type":49,"value":1588},"Budget:",{"type":49,"value":1590}," What's driving the switch? Cost, missing features, data ownership, or something else? (If cost, that implies existing budget.)",{"type":43,"tag":69,"props":1592,"children":1593},{},[1594,1599],{"type":43,"tag":73,"props":1595,"children":1596},{},[1597],{"type":49,"value":1598},"Authority:",{"type":49,"value":1600}," Who's involved in the decision? Is this an engineering-led eval or a top-down mandate?",{"type":43,"tag":69,"props":1602,"children":1603},{},[1604,1609,1611,1616,1618,1623],{"type":43,"tag":73,"props":1605,"children":1606},{},[1607],{"type":49,"value":1608},"Need:",{"type":49,"value":1610}," What are you hoping PostHog solves that ",{"type":43,"tag":1477,"props":1612,"children":1613},{},[1614],{"type":49,"value":1615},"competitor",{"type":49,"value":1617}," doesn't? Are you looking to replace just ",{"type":43,"tag":1477,"props":1619,"children":1620},{},[1621],{"type":49,"value":1622},"product",{"type":49,"value":1624},", or are you interested in consolidating with additional capabilities (replay, flags, experiments, etc.)?",{"type":43,"tag":69,"props":1626,"children":1627},{},[1628,1633],{"type":43,"tag":73,"props":1629,"children":1630},{},[1631],{"type":49,"value":1632},"Timeline:",{"type":49,"value":1634}," How soon are you looking to make a decision? (Don't ask this in the first email — let it emerge naturally or ask in a follow-up.)",{"type":43,"tag":52,"props":1636,"children":1637},{},[1638,1643],{"type":43,"tag":73,"props":1639,"children":1640},{},[1641],{"type":49,"value":1642},"You don't need all four BANT signals in the first email.",{"type":49,"value":1644}," Ask 1–2 questions that surface the most important unknowns — typically Budget (why are you switching?) and Need (what do you want beyond what you have?). Let Authority and Timeline emerge in the reply.",{"type":43,"tag":52,"props":1646,"children":1647},{},[1648],{"type":43,"tag":73,"props":1649,"children":1650},{},[1651],{"type":49,"value":1652},"After the lead replies with BANT context:",{"type":43,"tag":286,"props":1654,"children":1655},{},[1656,1661,1666],{"type":43,"tag":69,"props":1657,"children":1658},{},[1659],{"type":49,"value":1660},"If the answers confirm $20K+ potential and a real use case → Qualify for call, and offer your calendar",{"type":43,"tag":69,"props":1662,"children":1663},{},[1664],{"type":49,"value":1665},"If the answers reveal a small team \u002F low spend \u002F simple replacement → Route to self-serve with specific migration resources",{"type":43,"tag":69,"props":1667,"children":1668},{},[1669],{"type":49,"value":1670},"If the lead asks for a call before you have BANT context → It's OK to offer the calendar, but also point out that everything needed to evaluate PostHog is publicly available (pricing, docs, free signup), so they can start evaluating in parallel",{"type":43,"tag":162,"props":1672,"children":1674},{"id":1673},"special-case-vague-request-from-a-high-value-company",[1675],{"type":49,"value":1676},"Special Case: Vague Request from a High-Value Company",{"type":43,"tag":52,"props":1678,"children":1679},{},[1680,1682],{"type":49,"value":1681},"When the lead's message is vague (e.g., \"want to start a review process\", \"looking to learn more\", \"interested in PostHog\") BUT company research reveals a high-value account, ",{"type":43,"tag":73,"props":1683,"children":1684},{},[1685],{"type":49,"value":1686},"do not default to self-serve routing.",{"type":43,"tag":52,"props":1688,"children":1689},{},[1690],{"type":49,"value":1691},"Instead, treat vague requests from high-value companies as \"needs discovery\" rather than \"not serious enough for a call.\" The disposition should be \"qualify for call with discovery questions.\"",{"type":43,"tag":52,"props":1693,"children":1694},{},[1695,1700],{"type":43,"tag":73,"props":1696,"children":1697},{},[1698],{"type":49,"value":1699},"High-value company indicators",{"type":49,"value":1701}," (any two or more qualifies):",{"type":43,"tag":286,"props":1703,"children":1704},{},[1705,1710,1715,1720,1725,1730,1735],{"type":43,"tag":69,"props":1706,"children":1707},{},[1708],{"type":49,"value":1709},"$10M+ in total funding",{"type":43,"tag":69,"props":1711,"children":1712},{},[1713],{"type":49,"value":1714},"100+ employees",{"type":43,"tag":69,"props":1716,"children":1717},{},[1718],{"type":49,"value":1719},"Engineering team >40% of headcount",{"type":43,"tag":69,"props":1721,"children":1722},{},[1723],{"type":49,"value":1724},"Multi-product signals",{"type":43,"tag":69,"props":1726,"children":1727},{},[1728],{"type":49,"value":1729},"AI-native company",{"type":43,"tag":69,"props":1731,"children":1732},{},[1733],{"type":49,"value":1734},"Growth trajectory classified as \"Accelerating\"",{"type":43,"tag":69,"props":1736,"children":1737},{},[1738],{"type":49,"value":1739},"Well-known brand or notable founders\u002Fleadership",{"type":43,"tag":52,"props":1741,"children":1742},{},[1743],{"type":49,"value":1744},"The email for these leads should:",{"type":43,"tag":286,"props":1746,"children":1747},{},[1748,1753,1758,1763],{"type":43,"tag":69,"props":1749,"children":1750},{},[1751],{"type":49,"value":1752},"Acknowledge their interest without making assumptions about the use case",{"type":43,"tag":69,"props":1754,"children":1755},{},[1756],{"type":49,"value":1757},"Ask 1-2 discovery questions to understand what they're trying to solve",{"type":43,"tag":69,"props":1759,"children":1760},{},[1761],{"type":49,"value":1762},"Mention 1-2 PostHog capabilities most relevant to their company type (informed by research)",{"type":43,"tag":69,"props":1764,"children":1765},{},[1766],{"type":49,"value":1767},"Offer a call to walk through how PostHog fits their stack",{"type":43,"tag":162,"props":1769,"children":1771},{"id":1770},"disposition-qualify-for-call",[1772],{"type":49,"value":1773},"Disposition: Qualify for Call",{"type":43,"tag":52,"props":1775,"children":1776},{},[1777],{"type":49,"value":1778},"All of these should be true:",{"type":43,"tag":286,"props":1780,"children":1781},{},[1782,1787,1792,1797],{"type":43,"tag":69,"props":1783,"children":1784},{},[1785],{"type":49,"value":1786},"Annual spend potential ≥ $20K (based on current MAU, OR adjusted MAU with multi-product multiplier, OR growth trajectory override)",{"type":43,"tag":69,"props":1788,"children":1789},{},[1790],{"type":49,"value":1791},"Engineers are involved or will be on the call",{"type":43,"tag":69,"props":1793,"children":1794},{},[1795],{"type":49,"value":1796},"Specific, defined use case (mapped to at least one of the six above) — OR vague request from a high-value company (see special case above)",{"type":43,"tag":69,"props":1798,"children":1799},{},[1800],{"type":49,"value":1801},"Company size and product needs justify sales-assisted motion",{"type":43,"tag":52,"props":1803,"children":1804},{},[1805],{"type":49,"value":1806},"If qualified, draft a response that:",{"type":43,"tag":286,"props":1808,"children":1809},{},[1810,1815,1820],{"type":43,"tag":69,"props":1811,"children":1812},{},[1813],{"type":49,"value":1814},"Acknowledges their specific use case (or, for vague requests from high-value companies, their company context and likely use cases)",{"type":43,"tag":69,"props":1816,"children":1817},{},[1818],{"type":49,"value":1819},"Asks 1–2 targeted discovery questions from the relevant use case playbook",{"type":43,"tag":69,"props":1821,"children":1822},{},[1823],{"type":49,"value":1824},"Offers to schedule a call",{"type":43,"tag":162,"props":1826,"children":1828},{"id":1827},"disposition-route-to-self-serve",[1829],{"type":49,"value":1830},"Disposition: Route to Self-Serve",{"type":43,"tag":52,"props":1832,"children":1833},{},[1834],{"type":49,"value":1835},"Any of these are true:",{"type":43,"tag":286,"props":1837,"children":1838},{},[1839,1844,1849,1854,1859],{"type":43,"tag":69,"props":1840,"children":1841},{},[1842],{"type":49,"value":1843},"Spend potential clearly below $20K based on company size, research, AND growth trajectory does not justify the override",{"type":43,"tag":69,"props":1845,"children":1846},{},[1847],{"type":49,"value":1848},"Low volume explicitly stated (e.g., \"1,000 MAU\", \"small team\", \"just getting started\") AND company research confirms this is the ceiling (small company, flat trajectory)",{"type":43,"tag":69,"props":1850,"children":1851},{},[1852],{"type":49,"value":1853},"Vague request with no specific use case AND company research does not reveal a high-value account",{"type":43,"tag":69,"props":1855,"children":1856},{},[1857],{"type":49,"value":1858},"No engineer involvement mentioned or expected",{"type":43,"tag":69,"props":1860,"children":1861},{},[1862],{"type":49,"value":1863},"Generic \"learn more\" or \"get a demo\" with no substance behind it AND company research doesn't change the picture",{"type":43,"tag":52,"props":1865,"children":1866},{},[1867],{"type":49,"value":1868},"Draft a helpful email that:",{"type":43,"tag":286,"props":1870,"children":1871},{},[1872,1877,1882,1887],{"type":43,"tag":69,"props":1873,"children":1874},{},[1875],{"type":49,"value":1876},"Answers their question with use-case-specific resources",{"type":43,"tag":69,"props":1878,"children":1879},{},[1880],{"type":49,"value":1881},"Provides links to the most relevant product docs for their identified use case",{"type":43,"tag":69,"props":1883,"children":1884},{},[1885],{"type":49,"value":1886},"Directs them to self-serve channels (in-app support, community)",{"type":43,"tag":69,"props":1888,"children":1889},{},[1890],{"type":49,"value":1891},"Does NOT offer a call",{"type":43,"tag":162,"props":1893,"children":1895},{"id":1894},"disposition-route-to-startup-plan",[1896],{"type":49,"value":1897},"Disposition: Route to Startup Plan",{"type":43,"tag":286,"props":1899,"children":1900},{},[1901,1906,1920],{"type":43,"tag":69,"props":1902,"children":1903},{},[1904],{"type":49,"value":1905},"Company is early-stage and potentially eligible for the startup plan",{"type":43,"tag":69,"props":1907,"children":1908},{},[1909,1911],{"type":49,"value":1910},"Direct them to the ",{"type":43,"tag":1912,"props":1913,"children":1917},"a",{"href":1914,"rel":1915},"https:\u002F\u002Fposthog.com\u002Fstartups",[1916],"nofollow",[1918],{"type":49,"value":1919},"startup plan application",{"type":43,"tag":69,"props":1921,"children":1922},{},[1923],{"type":49,"value":1924},"Disqualify as an immediate sales opportunity",{"type":43,"tag":162,"props":1926,"children":1928},{"id":1927},"disposition-disqualify",[1929],{"type":49,"value":1930},"Disposition: Disqualify",{"type":43,"tag":286,"props":1932,"children":1933},{},[1934,1939,1944],{"type":43,"tag":69,"props":1935,"children":1936},{},[1937],{"type":49,"value":1938},"Clearly not ICP (wrong industry vertical, no product-engineering use case)",{"type":43,"tag":69,"props":1940,"children":1941},{},[1942],{"type":49,"value":1943},"Spam or irrelevant inquiry",{"type":43,"tag":69,"props":1945,"children":1946},{},[1947],{"type":49,"value":1948},"No response needed, or a brief polite decline",{"type":43,"tag":162,"props":1950,"children":1952},{"id":1951},"disqualification-reasons-notes",[1953],{"type":49,"value":1954},"Disqualification Reasons & Notes",{"type":43,"tag":52,"props":1956,"children":1957},{},[1958,1960,1965,1967,1972],{"type":49,"value":1959},"When recommending any disposition other than \"Qualify for Call,\" you MUST provide a ",{"type":43,"tag":73,"props":1961,"children":1962},{},[1963],{"type":49,"value":1964},"disqualification reason",{"type":49,"value":1966}," (from the list below) and ",{"type":43,"tag":73,"props":1968,"children":1969},{},[1970],{"type":49,"value":1971},"disqualification notes",{"type":49,"value":1973}," (250 characters or fewer, specific and copy-pasteable into the Salesforce disqualification notes field).",{"type":43,"tag":52,"props":1975,"children":1976},{},[1977],{"type":43,"tag":73,"props":1978,"children":1979},{},[1980],{"type":49,"value":1981},"Available disqualification reasons:",{"type":43,"tag":286,"props":1983,"children":1984},{},[1985,1990,1995,2000,2005,2010,2015,2020,2025,2030,2035,2040,2045,2050,2055,2060,2065,2070,2075,2080,2085,2090,2095,2100,2105,2110,2115],{"type":43,"tag":69,"props":1986,"children":1987},{},[1988],{"type":49,"value":1989},"BAA \u002F DPA Request",{"type":43,"tag":69,"props":1991,"children":1992},{},[1993],{"type":49,"value":1994},"Below Sales Assist Threshold - Pass",{"type":43,"tag":69,"props":1996,"children":1997},{},[1998],{"type":49,"value":1999},"Below Sales Assist Threshold - Prospect",{"type":43,"tag":69,"props":2001,"children":2002},{},[2003],{"type":49,"value":2004},"Billing Support Request",{"type":43,"tag":69,"props":2006,"children":2007},{},[2008],{"type":49,"value":2009},"Business Closed",{"type":43,"tag":69,"props":2011,"children":2012},{},[2013],{"type":49,"value":2014},"Duplicate Lead",{"type":43,"tag":69,"props":2016,"children":2017},{},[2018],{"type":49,"value":2019},"Event request",{"type":43,"tag":69,"props":2021,"children":2022},{},[2023],{"type":49,"value":2024},"Existing customer inquiry",{"type":43,"tag":69,"props":2026,"children":2027},{},[2028],{"type":49,"value":2029},"Feedback",{"type":43,"tag":69,"props":2031,"children":2032},{},[2033],{"type":49,"value":2034},"Invalid Contact Info",{"type":43,"tag":69,"props":2036,"children":2037},{},[2038],{"type":49,"value":2039},"No Budget",{"type":43,"tag":69,"props":2041,"children":2042},{},[2043],{"type":49,"value":2044},"No Current Need",{"type":43,"tag":69,"props":2046,"children":2047},{},[2048],{"type":49,"value":2049},"No Product Fit",{"type":43,"tag":69,"props":2051,"children":2052},{},[2053],{"type":49,"value":2054},"No Response - Pass",{"type":43,"tag":69,"props":2056,"children":2057},{},[2058],{"type":49,"value":2059},"No Response - Prospect",{"type":43,"tag":69,"props":2061,"children":2062},{},[2063],{"type":49,"value":2064},"No Technical Resource",{"type":43,"tag":69,"props":2066,"children":2067},{},[2068],{"type":49,"value":2069},"Non-Commercial",{"type":43,"tag":69,"props":2071,"children":2072},{},[2073],{"type":49,"value":2074},"Not a Good Fit",{"type":43,"tag":69,"props":2076,"children":2077},{},[2078],{"type":49,"value":2079},"Other",{"type":43,"tag":69,"props":2081,"children":2082},{},[2083],{"type":49,"value":2084},"Partnership request",{"type":43,"tag":69,"props":2086,"children":2087},{},[2088],{"type":49,"value":2089},"Resource Constraints",{"type":43,"tag":69,"props":2091,"children":2092},{},[2093],{"type":49,"value":2094},"Self-Hosted Requirement",{"type":43,"tag":69,"props":2096,"children":2097},{},[2098],{"type":49,"value":2099},"Spam",{"type":43,"tag":69,"props":2101,"children":2102},{},[2103],{"type":49,"value":2104},"Stale - autoclosed",{"type":43,"tag":69,"props":2106,"children":2107},{},[2108],{"type":49,"value":2109},"Startup Plan \u002F YC",{"type":43,"tag":69,"props":2111,"children":2112},{},[2113],{"type":49,"value":2114},"Support Request",{"type":43,"tag":69,"props":2116,"children":2117},{},[2118],{"type":49,"value":2119},"Using Competitor \u002F Unsolicited RFP",{"type":43,"tag":52,"props":2121,"children":2122},{},[2123],{"type":43,"tag":73,"props":2124,"children":2125},{},[2126],{"type":49,"value":2127},"How to choose the right reason:",{"type":43,"tag":286,"props":2129,"children":2130},{},[2131,2140,2149,2158,2167,2176,2185,2194],{"type":43,"tag":69,"props":2132,"children":2133},{},[2134,2138],{"type":43,"tag":73,"props":2135,"children":2136},{},[2137],{"type":49,"value":1994},{"type":49,"value":2139},": Below $20K potential, no growth trajectory override, and no realistic growth path to get there. Use for small companies routed to self-serve.",{"type":43,"tag":69,"props":2141,"children":2142},{},[2143,2147],{"type":43,"tag":73,"props":2144,"children":2145},{},[2146],{"type":49,"value":1999},{"type":49,"value":2148},": Below $20K now but company shows signals it could grow into threshold (e.g. recent funding, growing team). Worth revisiting later. Use when the growth trajectory is promising but doesn't meet the override criteria yet.",{"type":43,"tag":69,"props":2150,"children":2151},{},[2152,2156],{"type":43,"tag":73,"props":2153,"children":2154},{},[2155],{"type":49,"value":1989},{"type":49,"value":2157},": Lead requires a BAA or DPA. Note: BAAs are available starting at the Boost add-on ($250\u002Fmonth + usage-based pricing) for standard (no redlines) BAAs, or Enterprise ($2K\u002Fmonth paid annually) for custom\u002Fredlined BAAs. Use this reason when the lead's primary need is HIPAA\u002FBAA and they've been given the relevant pricing info.",{"type":43,"tag":69,"props":2159,"children":2160},{},[2161,2165],{"type":43,"tag":73,"props":2162,"children":2163},{},[2164],{"type":49,"value":2064},{"type":49,"value":2166},": The contact is non-technical and no engineer is mentioned or expected to be involved.",{"type":43,"tag":69,"props":2168,"children":2169},{},[2170,2174],{"type":43,"tag":73,"props":2171,"children":2172},{},[2173],{"type":49,"value":2109},{"type":49,"value":2175},": Early-stage company routed to the startup plan application.",{"type":43,"tag":69,"props":2177,"children":2178},{},[2179,2183],{"type":43,"tag":73,"props":2180,"children":2181},{},[2182],{"type":49,"value":2114},{"type":49,"value":2184},": They're asking a support question, not evaluating PostHog for purchase.",{"type":43,"tag":69,"props":2186,"children":2187},{},[2188,2192],{"type":43,"tag":73,"props":2189,"children":2190},{},[2191],{"type":49,"value":2024},{"type":49,"value":2193},": Already a PostHog customer with a product\u002Fbilling question - not a new sales opportunity.",{"type":43,"tag":69,"props":2195,"children":2196},{},[2197,2201],{"type":43,"tag":73,"props":2198,"children":2199},{},[2200],{"type":49,"value":2049},{"type":49,"value":2202},": What they need isn't something PostHog does well (e.g. self-hosted requirement, industry mismatch).",{"type":43,"tag":52,"props":2204,"children":2205},{},[2206,2211],{"type":43,"tag":73,"props":2207,"children":2208},{},[2209],{"type":49,"value":2210},"Disqualification notes must be specific and copy-pasteable.",{"type":49,"value":2212}," Include the key data points that justify the disqualification, including relevant findings from company research.",{"type":43,"tag":52,"props":2214,"children":2215},{},[2216],{"type":49,"value":2217},"Good DQ notes:",{"type":43,"tag":286,"props":2219,"children":2220},{},[2221,2226,2231,2236],{"type":43,"tag":69,"props":2222,"children":2223},{},[2224],{"type":49,"value":2225},"\"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.\"",{"type":43,"tag":69,"props":2227,"children":2228},{},[2229],{"type":49,"value":2230},"\"Bay Area nonprofit, 20K MAUs, ICP -5. Sr Dir Product, strong use case but well below $20K threshold. BAA available via Boost ($250\u002Fmo). Routed to self-serve with HIPAA + funnel guidance.\"",{"type":43,"tag":69,"props":2232,"children":2233},{},[2234],{"type":49,"value":2235},"\"15-person seed startup. Developer asking about feature flags. Free tier covers their needs. Pointed to docs + in-app support.\"",{"type":43,"tag":69,"props":2237,"children":2238},{},[2239],{"type":49,"value":2240},"\"5-person pre-revenue startup, no funding found. 2K MAU. Vague 'want to learn more.' Routed to self-serve, suggested startup plan application.\"",{"type":43,"tag":52,"props":2242,"children":2243},{},[2244],{"type":49,"value":2245},"Bad DQ notes:",{"type":43,"tag":286,"props":2247,"children":2248},{},[2249,2254,2259,2264],{"type":43,"tag":69,"props":2250,"children":2251},{},[2252],{"type":49,"value":2253},"\"Not a good fit\" (too vague)",{"type":43,"tag":69,"props":2255,"children":2256},{},[2257],{"type":49,"value":2258},"\"Small company\" (which signal matters?)",{"type":43,"tag":69,"props":2260,"children":2261},{},[2262],{"type":49,"value":2263},"\"Routed to self-serve\" (why?)",{"type":43,"tag":69,"props":2265,"children":2266},{},[2267],{"type":49,"value":2268},"\"Low MAU\" (did you check if the company is actually small, or is the product just early?)",{"type":43,"tag":58,"props":2270,"children":2272},{"id":2271},"step-4-write-the-response-email",[2273],{"type":49,"value":2274},"Step 4: Write the Response Email",{"type":43,"tag":52,"props":2276,"children":2277},{},[2278,2280,2286],{"type":49,"value":2279},"Read ",{"type":43,"tag":187,"props":2281,"children":2283},{"className":2282},[],[2284],{"type":49,"value":2285},"references\u002Fwriting-style.md",{"type":49,"value":2287}," before drafting. Key rules:",{"type":43,"tag":286,"props":2289,"children":2290},{},[2291,2301,2311,2321,2331,2341,2351,2361],{"type":43,"tag":69,"props":2292,"children":2293},{},[2294,2299],{"type":43,"tag":73,"props":2295,"children":2296},{},[2297],{"type":49,"value":2298},"Get to the point.",{"type":49,"value":2300}," No long intros, no fluff, no corporate jargon.",{"type":43,"tag":69,"props":2302,"children":2303},{},[2304,2309],{"type":43,"tag":73,"props":2305,"children":2306},{},[2307],{"type":49,"value":2308},"Be helpful, not sales-y.",{"type":49,"value":2310}," Solve their problem with specific guidance.",{"type":43,"tag":69,"props":2312,"children":2313},{},[2314,2319],{"type":43,"tag":73,"props":2315,"children":2316},{},[2317],{"type":49,"value":2318},"Be opinionated.",{"type":49,"value":2320}," Don't hedge with \"it depends\" — recommend a path.",{"type":43,"tag":69,"props":2322,"children":2323},{},[2324,2329],{"type":43,"tag":73,"props":2325,"children":2326},{},[2327],{"type":49,"value":2328},"Frame around their use case, not PostHog products.",{"type":49,"value":2330}," Talk about solving their problem, not about product names.",{"type":43,"tag":69,"props":2332,"children":2333},{},[2334,2339],{"type":43,"tag":73,"props":2335,"children":2336},{},[2337],{"type":49,"value":2338},"Use company research to personalize.",{"type":49,"value":2340}," If you know what they build, reference it. \"Since you're building AI tools for manufacturing\" is better than \"Since you're evaluating analytics.\"",{"type":43,"tag":69,"props":2342,"children":2343},{},[2344,2349],{"type":43,"tag":73,"props":2345,"children":2346},{},[2347],{"type":49,"value":2348},"Embed links in anchor text.",{"type":49,"value":2350}," Never paste bare URLs or use \"click here.\"",{"type":43,"tag":69,"props":2352,"children":2353},{},[2354,2359],{"type":43,"tag":73,"props":2355,"children":2356},{},[2357],{"type":49,"value":2358},"Minimal formatting.",{"type":49,"value":2360}," Use bullet points only when listing resources or steps. Keep it conversational.",{"type":43,"tag":69,"props":2362,"children":2363},{},[2364,2369],{"type":43,"tag":73,"props":2365,"children":2366},{},[2367],{"type":49,"value":2368},"One question max",{"type":49,"value":2370}," per email to avoid overwhelming the recipient.",{"type":43,"tag":162,"props":2372,"children":2374},{"id":2373},"email-structure",[2375],{"type":49,"value":2376},"Email Structure",{"type":43,"tag":65,"props":2378,"children":2379},{},[2380,2385,2390,2395,2400],{"type":43,"tag":69,"props":2381,"children":2382},{},[2383],{"type":49,"value":2384},"Brief, friendly greeting",{"type":43,"tag":69,"props":2386,"children":2387},{},[2388],{"type":49,"value":2389},"Acknowledge their specific situation and use case (informed by company research)",{"type":43,"tag":69,"props":2391,"children":2392},{},[2393],{"type":49,"value":2394},"Provide the answer, guidance, or resources mapped to their use case",{"type":43,"tag":69,"props":2396,"children":2397},{},[2398],{"type":49,"value":2399},"Clear next step (self-serve action, schedule link, or \"reply if you have questions\")",{"type":43,"tag":69,"props":2401,"children":2402},{},[2403],{"type":49,"value":2404},"Simple sign-off",{"type":43,"tag":58,"props":2406,"children":2408},{"id":2407},"step-5-validate-all-urls",[2409],{"type":49,"value":2410},"Step 5: Validate All URLs",{"type":43,"tag":52,"props":2412,"children":2413},{},[2414,2419,2421,2427],{"type":43,"tag":73,"props":2415,"children":2416},{},[2417],{"type":49,"value":2418},"This step is mandatory.",{"type":49,"value":2420}," Before presenting the draft email, fetch every URL included in the email using ",{"type":43,"tag":187,"props":2422,"children":2424},{"className":2423},[],[2425],{"type":49,"value":2426},"web_fetch",{"type":49,"value":2428}," to verify:",{"type":43,"tag":65,"props":2430,"children":2431},{},[2432,2442],{"type":43,"tag":69,"props":2433,"children":2434},{},[2435,2440],{"type":43,"tag":73,"props":2436,"children":2437},{},[2438],{"type":49,"value":2439},"The URL resolves",{"type":49,"value":2441}," — It returns a 200 status, not a 404 or redirect to a generic page",{"type":43,"tag":69,"props":2443,"children":2444},{},[2445,2450],{"type":43,"tag":73,"props":2446,"children":2447},{},[2448],{"type":49,"value":2449},"The content matches the intent",{"type":49,"value":2451}," — 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)",{"type":43,"tag":52,"props":2453,"children":2454},{},[2455],{"type":43,"tag":73,"props":2456,"children":2457},{},[2458],{"type":49,"value":2459},"If a URL fails validation:",{"type":43,"tag":286,"props":2461,"children":2462},{},[2463,2475,2480],{"type":43,"tag":69,"props":2464,"children":2465},{},[2466,2468,2473],{"type":49,"value":2467},"Search posthog.com for the correct page using ",{"type":43,"tag":187,"props":2469,"children":2471},{"className":2470},[],[2472],{"type":49,"value":423},{"type":49,"value":2474}," (e.g., \"posthog docs feature flags getting started\")",{"type":43,"tag":69,"props":2476,"children":2477},{},[2478],{"type":49,"value":2479},"Replace the broken link with the correct one",{"type":43,"tag":69,"props":2481,"children":2482},{},[2483],{"type":49,"value":2484},"If no valid page exists for that resource, remove the link rather than send a broken one",{"type":43,"tag":52,"props":2486,"children":2487},{},[2488,2493],{"type":43,"tag":73,"props":2489,"children":2490},{},[2491],{"type":49,"value":2492},"Why this matters:",{"type":49,"value":2494}," 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.",{"type":43,"tag":58,"props":2496,"children":2498},{"id":2497},"use-case-specific-resources-to-link",[2499],{"type":49,"value":2500},"Use-Case-Specific Resources to Link",{"type":43,"tag":162,"props":2502,"children":2504},{"id":2503},"product-intelligence",[2505],{"type":49,"value":983},{"type":43,"tag":286,"props":2507,"children":2508},{},[2509,2519,2529,2539,2549],{"type":43,"tag":69,"props":2510,"children":2511},{},[2512],{"type":43,"tag":1912,"props":2513,"children":2516},{"href":2514,"rel":2515},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fproduct-analytics",[1916],[2517],{"type":49,"value":2518},"Product analytics docs",{"type":43,"tag":69,"props":2520,"children":2521},{},[2522],{"type":43,"tag":1912,"props":2523,"children":2526},{"href":2524,"rel":2525},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fproduct-analytics\u002Ffunnels",[1916],[2527],{"type":49,"value":2528},"Funnels",{"type":43,"tag":69,"props":2530,"children":2531},{},[2532],{"type":43,"tag":1912,"props":2533,"children":2536},{"href":2534,"rel":2535},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsession-replay",[1916],[2537],{"type":49,"value":2538},"Session Replay",{"type":43,"tag":69,"props":2540,"children":2541},{},[2542],{"type":43,"tag":1912,"props":2543,"children":2546},{"href":2544,"rel":2545},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fsurveys\u002Fcreating-surveys",[1916],[2547],{"type":49,"value":2548},"Surveys",{"type":43,"tag":69,"props":2550,"children":2551},{},[2552],{"type":43,"tag":1912,"props":2553,"children":2556},{"href":2554,"rel":2555},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fexperiments",[1916],[2557],{"type":49,"value":2558},"Experiments",{"type":43,"tag":162,"props":2560,"children":2562},{"id":2561},"release-engineering",[2563],{"type":49,"value":1009},{"type":43,"tag":286,"props":2565,"children":2566},{},[2567,2577,2585],{"type":43,"tag":69,"props":2568,"children":2569},{},[2570],{"type":43,"tag":1912,"props":2571,"children":2574},{"href":2572,"rel":2573},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Ffeature-flags\u002Fstart-here",[1916],[2575],{"type":49,"value":2576},"Feature Flags getting started",{"type":43,"tag":69,"props":2578,"children":2579},{},[2580],{"type":43,"tag":1912,"props":2581,"children":2583},{"href":2554,"rel":2582},[1916],[2584],{"type":49,"value":2558},{"type":43,"tag":69,"props":2586,"children":2587},{},[2588,2593],{"type":43,"tag":1912,"props":2589,"children":2591},{"href":2534,"rel":2590},[1916],[2592],{"type":49,"value":2538},{"type":49,"value":2594}," (for debugging rollouts)",{"type":43,"tag":162,"props":2596,"children":2598},{"id":2597},"observability",[2599],{"type":49,"value":1035},{"type":43,"tag":286,"props":2601,"children":2602},{},[2603,2613],{"type":43,"tag":69,"props":2604,"children":2605},{},[2606],{"type":43,"tag":1912,"props":2607,"children":2610},{"href":2608,"rel":2609},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Ferror-tracking",[1916],[2611],{"type":49,"value":2612},"Error Tracking",{"type":43,"tag":69,"props":2614,"children":2615},{},[2616,2621],{"type":43,"tag":1912,"props":2617,"children":2619},{"href":2534,"rel":2618},[1916],[2620],{"type":49,"value":2538},{"type":49,"value":2622}," (for error context)",{"type":43,"tag":162,"props":2624,"children":2626},{"id":2625},"growth-marketing",[2627],{"type":49,"value":1061},{"type":43,"tag":286,"props":2629,"children":2630},{},[2631,2641,2651,2661],{"type":43,"tag":69,"props":2632,"children":2633},{},[2634],{"type":43,"tag":1912,"props":2635,"children":2638},{"href":2636,"rel":2637},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fweb-analytics\u002Fgetting-started",[1916],[2639],{"type":49,"value":2640},"Web Analytics",{"type":43,"tag":69,"props":2642,"children":2643},{},[2644],{"type":43,"tag":1912,"props":2645,"children":2648},{"href":2646,"rel":2647},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fweb-analytics\u002Fmarketing-analytics",[1916],[2649],{"type":49,"value":2650},"Marketing Analytics",{"type":43,"tag":69,"props":2652,"children":2653},{},[2654],{"type":43,"tag":1912,"props":2655,"children":2658},{"href":2656,"rel":2657},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fcdp",[1916],[2659],{"type":49,"value":2660},"Data Pipelines",{"type":43,"tag":69,"props":2662,"children":2663},{},[2664],{"type":43,"tag":1912,"props":2665,"children":2668},{"href":2666,"rel":2667},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fworkflows\u002Fstart-here",[1916],[2669],{"type":49,"value":2670},"Workflows",{"type":43,"tag":162,"props":2672,"children":2674},{"id":2673},"aillm-observability",[2675],{"type":49,"value":1087},{"type":43,"tag":286,"props":2677,"children":2678},{},[2679,2689],{"type":43,"tag":69,"props":2680,"children":2681},{},[2682],{"type":43,"tag":1912,"props":2683,"children":2686},{"href":2684,"rel":2685},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fai-engineering",[1916],[2687],{"type":49,"value":2688},"AI Engineering \u002F LLM Observability",{"type":43,"tag":69,"props":2690,"children":2691},{},[2692,2697],{"type":43,"tag":1912,"props":2693,"children":2695},{"href":2554,"rel":2694},[1916],[2696],{"type":49,"value":2558},{"type":49,"value":2698}," (for prompt\u002Fmodel testing)",{"type":43,"tag":162,"props":2700,"children":2702},{"id":2701},"data-infrastructure",[2703],{"type":49,"value":1120},{"type":43,"tag":286,"props":2705,"children":2706},{},[2707,2717,2727],{"type":43,"tag":69,"props":2708,"children":2709},{},[2710],{"type":43,"tag":1912,"props":2711,"children":2714},{"href":2712,"rel":2713},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fdata-warehouse",[1916],[2715],{"type":49,"value":2716},"Data Warehouse",{"type":43,"tag":69,"props":2718,"children":2719},{},[2720],{"type":43,"tag":1912,"props":2721,"children":2724},{"href":2722,"rel":2723},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fcdp\u002Fbatch-exports",[1916],[2725],{"type":49,"value":2726},"Batch Exports",{"type":43,"tag":69,"props":2728,"children":2729},{},[2730],{"type":43,"tag":1912,"props":2731,"children":2734},{"href":2732,"rel":2733},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fcdp\u002Fdestinations",[1916],[2735],{"type":49,"value":2736},"Realtime Destinations",{"type":43,"tag":162,"props":2738,"children":2740},{"id":2739},"general-all-use-cases",[2741],{"type":49,"value":2742},"General (all use cases)",{"type":43,"tag":286,"props":2744,"children":2745},{},[2746,2756,2766,2776,2786,2796,2801],{"type":43,"tag":69,"props":2747,"children":2748},{},[2749],{"type":43,"tag":1912,"props":2750,"children":2753},{"href":2751,"rel":2752},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fgetting-started\u002Finstall",[1916],[2754],{"type":49,"value":2755},"Installation guide",{"type":43,"tag":69,"props":2757,"children":2758},{},[2759],{"type":43,"tag":1912,"props":2760,"children":2763},{"href":2761,"rel":2762},"https:\u002F\u002Fposthog.com\u002Fpricing",[1916],[2764],{"type":49,"value":2765},"Pricing page",{"type":43,"tag":69,"props":2767,"children":2768},{},[2769],{"type":43,"tag":1912,"props":2770,"children":2773},{"href":2771,"rel":2772},"https:\u002F\u002Fposthog.com\u002Fquestions",[1916],[2774],{"type":49,"value":2775},"Community questions",{"type":43,"tag":69,"props":2777,"children":2778},{},[2779],{"type":43,"tag":1912,"props":2780,"children":2783},{"href":2781,"rel":2782},"https:\u002F\u002Fposthog.com\u002Fdocs\u002Fprivacy\u002Fhipaa-compliance",[1916],[2784],{"type":49,"value":2785},"HIPAA compliance guide",{"type":43,"tag":69,"props":2787,"children":2788},{},[2789],{"type":43,"tag":1912,"props":2790,"children":2793},{"href":2791,"rel":2792},"https:\u002F\u002Fposthog.com\u002Fbaa",[1916],[2794],{"type":49,"value":2795},"BAA generator",{"type":43,"tag":69,"props":2797,"children":2798},{},[2799],{"type":49,"value":2800},"In-app support button (always mention for product questions)",{"type":43,"tag":69,"props":2802,"children":2803},{},[2804],{"type":49,"value":2805},"Free tier: 1M events\u002Fmonth, all core features included",{"type":43,"tag":58,"props":2807,"children":2809},{"id":2808},"baa-hipaa-pricing-reference",[2810],{"type":49,"value":2811},"BAA \u002F HIPAA Pricing Reference",{"type":43,"tag":52,"props":2813,"children":2814},{},[2815],{"type":49,"value":2816},"When a lead mentions HIPAA, BAA, or healthcare data, use this pricing info:",{"type":43,"tag":52,"props":2818,"children":2819},{},[2820],{"type":43,"tag":73,"props":2821,"children":2822},{},[2823],{"type":49,"value":2824},"Standard BAA (no redlines):",{"type":43,"tag":286,"props":2826,"children":2827},{},[2828,2847,2852],{"type":43,"tag":69,"props":2829,"children":2830},{},[2831,2833,2838,2840,2845],{"type":49,"value":2832},"Available on the ",{"type":43,"tag":73,"props":2834,"children":2835},{},[2836],{"type":49,"value":2837},"Boost add-on",{"type":49,"value":2839}," at ",{"type":43,"tag":73,"props":2841,"children":2842},{},[2843],{"type":49,"value":2844},"$250\u002Fmonth",{"type":49,"value":2846}," + usage-based pricing",{"type":43,"tag":69,"props":2848,"children":2849},{},[2850],{"type":49,"value":2851},"Also available on Scale and Enterprise add-ons",{"type":43,"tag":69,"props":2853,"children":2854},{},[2855],{"type":49,"value":2856},"The BAA can be generated at posthog.com\u002Fbaa for PostHog to countersign",{"type":43,"tag":52,"props":2858,"children":2859},{},[2860],{"type":43,"tag":73,"props":2861,"children":2862},{},[2863],{"type":49,"value":2864},"Custom\u002Fredlined BAA:",{"type":43,"tag":286,"props":2866,"children":2867},{},[2868,2886],{"type":43,"tag":69,"props":2869,"children":2870},{},[2871,2873,2878,2879,2884],{"type":49,"value":2872},"Requires the ",{"type":43,"tag":73,"props":2874,"children":2875},{},[2876],{"type":49,"value":2877},"Enterprise plan",{"type":49,"value":2839},{"type":43,"tag":73,"props":2880,"children":2881},{},[2882],{"type":49,"value":2883},"$2K\u002Fmonth",{"type":49,"value":2885}," (paid annually) + usage-based pricing",{"type":43,"tag":69,"props":2887,"children":2888},{},[2889],{"type":49,"value":2890},"Only needed if the customer wants to modify the standard BAA terms",{"type":43,"tag":52,"props":2892,"children":2893},{},[2894,2899],{"type":43,"tag":73,"props":2895,"children":2896},{},[2897],{"type":49,"value":2898},"Key framing:",{"type":49,"value":2900}," Lead with Boost as the standard path. $250\u002Fmonth 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.",{"type":43,"tag":52,"props":2902,"children":2903},{},[2904,2909],{"type":43,"tag":73,"props":2905,"children":2906},{},[2907],{"type":49,"value":2908},"Practical note for leads with mixed PHI\u002Fnon-PHI data:",{"type":49,"value":2910}," 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.",{"type":43,"tag":58,"props":2912,"children":2914},{"id":2913},"non-profit-discount-reference",[2915],{"type":49,"value":2916},"Non-Profit Discount Reference",{"type":43,"tag":52,"props":2918,"children":2919},{},[2920],{"type":49,"value":2921},"PostHog offers non-profit discounts on credit purchases:",{"type":43,"tag":286,"props":2923,"children":2924},{},[2925,2935,2945],{"type":43,"tag":69,"props":2926,"children":2927},{},[2928,2933],{"type":43,"tag":73,"props":2929,"children":2930},{},[2931],{"type":49,"value":2932},"Credit purchases below $25K:",{"type":49,"value":2934}," 15% discount",{"type":43,"tag":69,"props":2936,"children":2937},{},[2938,2943],{"type":43,"tag":73,"props":2939,"children":2940},{},[2941],{"type":49,"value":2942},"Credit purchases $25K-$100K:",{"type":49,"value":2944}," additional 5% on top of standard volume discount",{"type":43,"tag":69,"props":2946,"children":2947},{},[2948,2953],{"type":43,"tag":73,"props":2949,"children":2950},{},[2951],{"type":49,"value":2952},"Credit purchases above $100K:",{"type":49,"value":2954}," standard volume discounts apply (no additional non-profit discount)",{"type":43,"tag":52,"props":2956,"children":2957},{},[2958],{"type":49,"value":2959},"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).",{"type":43,"tag":52,"props":2961,"children":2962},{},[2963,2968],{"type":43,"tag":73,"props":2964,"children":2965},{},[2966],{"type":49,"value":2967},"Note:",{"type":49,"value":2969}," 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.",{"type":43,"tag":58,"props":2971,"children":2973},{"id":2972},"output-format",[2974],{"type":49,"value":2975},"Output Format",{"type":43,"tag":52,"props":2977,"children":2978},{},[2979],{"type":49,"value":2980},"When responding to the TAE, always provide:",{"type":43,"tag":65,"props":2982,"children":2983},{},[2984,2994,3004,3014,3024,3034,3044],{"type":43,"tag":69,"props":2985,"children":2986},{},[2987,2992],{"type":43,"tag":73,"props":2988,"children":2989},{},[2990],{"type":49,"value":2991},"Vitally findings",{"type":49,"value":2993}," — Whether the lead or their company was found in Vitally, and what that means",{"type":43,"tag":69,"props":2995,"children":2996},{},[2997,3002],{"type":43,"tag":73,"props":2998,"children":2999},{},[3000],{"type":49,"value":3001},"Company research",{"type":49,"value":3003}," — Brief profile from web research: what they do, funding, headcount, growth trajectory, multi-product signals, AI-native flag",{"type":43,"tag":69,"props":3005,"children":3006},{},[3007,3012],{"type":43,"tag":73,"props":3008,"children":3009},{},[3010],{"type":49,"value":3011},"Use case assessment",{"type":49,"value":3013}," — Which of the six use cases this lead maps to, and why (based on persona, company research, and message)",{"type":43,"tag":69,"props":3015,"children":3016},{},[3017,3022],{"type":43,"tag":73,"props":3018,"children":3019},{},[3020],{"type":49,"value":3021},"Disposition recommendation",{"type":49,"value":3023}," — Qualify \u002F Self-serve \u002F Startup plan \u002F Disqualify",{"type":43,"tag":69,"props":3025,"children":3026},{},[3027,3032],{"type":43,"tag":73,"props":3028,"children":3029},{},[3030],{"type":49,"value":3031},"Disqualification reason",{"type":49,"value":3033}," — From the available list (required for all dispositions except Qualify for Call)",{"type":43,"tag":69,"props":3035,"children":3036},{},[3037,3042],{"type":43,"tag":73,"props":3038,"children":3039},{},[3040],{"type":49,"value":3041},"Disqualification notes",{"type":49,"value":3043}," — 250 characters or fewer, specific and copy-pasteable (required for all dispositions except Qualify for Call)",{"type":43,"tag":69,"props":3045,"children":3046},{},[3047,3052],{"type":43,"tag":73,"props":3048,"children":3049},{},[3050],{"type":49,"value":3051},"Draft email",{"type":49,"value":3053}," — The response to send, framed around the identified use case and informed by company research",{"type":43,"tag":58,"props":3055,"children":3057},{"id":3056},"reference-files",[3058],{"type":49,"value":3059},"Reference Files",{"type":43,"tag":52,"props":3061,"children":3062},{},[3063],{"type":49,"value":3064},"Read these before drafting responses:",{"type":43,"tag":286,"props":3066,"children":3067},{},[3068,3079,3090],{"type":43,"tag":69,"props":3069,"children":3070},{},[3071,3077],{"type":43,"tag":187,"props":3072,"children":3074},{"className":3073},[],[3075],{"type":49,"value":3076},"references\u002Femail-examples.md",{"type":49,"value":3078}," — Example emails for common inbound scenarios",{"type":43,"tag":69,"props":3080,"children":3081},{},[3082,3088],{"type":43,"tag":187,"props":3083,"children":3085},{"className":3084},[],[3086],{"type":49,"value":3087},"references\u002Fsales-context.md",{"type":49,"value":3089}," — Sales process, thresholds, qualification criteria",{"type":43,"tag":69,"props":3091,"children":3092},{},[3093,3098],{"type":43,"tag":187,"props":3094,"children":3096},{"className":3095},[],[3097],{"type":49,"value":2285},{"type":49,"value":3099}," — PostHog tone, formatting, and style rules",{"type":43,"tag":58,"props":3101,"children":3103},{"id":3102},"critical-reminders",[3104],{"type":49,"value":3105},"Critical Reminders",{"type":43,"tag":65,"props":3107,"children":3108},{},[3109,3119,3129,3139,3149,3159,3169,3179,3189,3199,3209,3219,3229,3239,3249,3259],{"type":43,"tag":69,"props":3110,"children":3111},{},[3112,3117],{"type":43,"tag":73,"props":3113,"children":3114},{},[3115],{"type":49,"value":3116},"Always check Vitally first",{"type":49,"value":3118}," — Search for the lead's email and email domain before doing anything else. An existing customer changes everything about the response.",{"type":43,"tag":69,"props":3120,"children":3121},{},[3122,3127],{"type":43,"tag":73,"props":3123,"children":3124},{},[3125],{"type":49,"value":3126},"Always research the company",{"type":49,"value":3128}," — 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.",{"type":43,"tag":69,"props":3130,"children":3131},{},[3132,3137],{"type":43,"tag":73,"props":3133,"children":3134},{},[3135],{"type":49,"value":3136},"Growth trajectory can override the $20K threshold",{"type":49,"value":3138}," — An accelerating company with strong signals should be qualified even if current MAU is low. Document the override reasoning.",{"type":43,"tag":69,"props":3140,"children":3141},{},[3142,3147],{"type":43,"tag":73,"props":3143,"children":3144},{},[3145],{"type":49,"value":3146},"Multi-product signals are spend multipliers",{"type":49,"value":3148}," — \"Some of our products\" means the stated MAU is a floor, not a ceiling. Adjust your estimate.",{"type":43,"tag":69,"props":3150,"children":3151},{},[3152,3157],{"type":43,"tag":73,"props":3153,"children":3154},{},[3155],{"type":49,"value":3156},"AI-native companies get AI\u002FLLM Obs as a secondary use case",{"type":49,"value":3158}," — Even if they didn't mention it. It's almost always relevant.",{"type":43,"tag":69,"props":3160,"children":3161},{},[3162,3167],{"type":43,"tag":73,"props":3163,"children":3164},{},[3165],{"type":49,"value":3166},"Vague requests from high-value companies need discovery, not self-serve",{"type":49,"value":3168}," — Don't punt a $6B startup to the docs because they didn't write a detailed form submission.",{"type":43,"tag":69,"props":3170,"children":3171},{},[3172,3177],{"type":43,"tag":73,"props":3173,"children":3174},{},[3175],{"type":49,"value":3176},"$20K threshold is firm for non-override cases",{"type":49,"value":3178}," — Do not offer calls below this for companies with steady\u002Fflat trajectories and no high-value signals.",{"type":43,"tag":69,"props":3180,"children":3181},{},[3182,3187],{"type":43,"tag":73,"props":3183,"children":3184},{},[3185],{"type":49,"value":3186},"Always identify the use case",{"type":49,"value":3188}," — This is the foundation for everything: the disposition, the framing, and the resources you link.",{"type":43,"tag":69,"props":3190,"children":3191},{},[3192,3197],{"type":43,"tag":73,"props":3193,"children":3194},{},[3195],{"type":49,"value":3196},"Always recommend a disposition",{"type":49,"value":3198}," — Don't just write an email; state the qualification decision explicitly so the TAE can update Salesforce.",{"type":43,"tag":69,"props":3200,"children":3201},{},[3202,3207],{"type":43,"tag":73,"props":3203,"children":3204},{},[3205],{"type":49,"value":3206},"Always mention in-app support",{"type":49,"value":3208}," for product questions — it's the fastest path to help.",{"type":43,"tag":69,"props":3210,"children":3211},{},[3212,3217],{"type":43,"tag":73,"props":3213,"children":3214},{},[3215],{"type":49,"value":3216},"PostHog is built for product engineers",{"type":49,"value":3218}," — If no engineer is involved, that's a red flag for qualification.",{"type":43,"tag":69,"props":3220,"children":3221},{},[3222,3227],{"type":43,"tag":73,"props":3223,"children":3224},{},[3225],{"type":49,"value":3226},"Frame around problems, not products",{"type":49,"value":3228}," — \"Here's how to understand why users drop off\" not \"Here's our Product Analytics feature.\"",{"type":43,"tag":69,"props":3230,"children":3231},{},[3232,3237],{"type":43,"tag":73,"props":3233,"children":3234},{},[3235],{"type":49,"value":3236},"Use company research to personalize the email",{"type":49,"value":3238}," — Reference what they build, not just what they asked. It shows you did your homework.",{"type":43,"tag":69,"props":3240,"children":3241},{},[3242,3247],{"type":43,"tag":73,"props":3243,"children":3244},{},[3245],{"type":49,"value":3246},"Match specificity to specificity",{"type":49,"value":3248}," — Vague inbound gets pointed to resources with a clarifying question; specific technical questions get specific answers tied to their use case.",{"type":43,"tag":69,"props":3250,"children":3251},{},[3252,3257],{"type":43,"tag":73,"props":3253,"children":3254},{},[3255],{"type":49,"value":3256},"Always validate URLs before presenting the draft",{"type":49,"value":3258}," — Fetch every link to confirm it resolves and points to the right content. Never send a broken link.",{"type":43,"tag":69,"props":3260,"children":3261},{},[3262,3267],{"type":43,"tag":73,"props":3263,"children":3264},{},[3265],{"type":49,"value":3266},"Always provide a DQ reason and DQ notes",{"type":49,"value":3268}," — 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.",{"items":3270,"total":3439},[3271,3288,3300,3312,3325,3340,3356,3373,3387,3402,3412,3429],{"slug":3272,"name":3272,"fn":3273,"description":3274,"org":3275,"tags":3276,"stars":3285,"repoUrl":3286,"updatedAt":3287},"analyzing-expensive-users","analyze expensive users in AI observability","Analyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3277,3280,3283,3284],{"name":3278,"slug":3279,"type":13},"Analytics","analytics",{"name":3281,"slug":3282,"type":13},"Cost Optimization","cost-optimization",{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-28T05:34:11.117757",{"slug":3289,"name":3289,"fn":3290,"description":3291,"org":3292,"tags":3293,"stars":3285,"repoUrl":3286,"updatedAt":3299},"auditing-endpoints","audit PostHog project endpoints","Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks \"what endpoints can I clean up?\", \"are any of my endpoints broken?\", \"which materialised versions are still being called?\", or wants a one-shot cleanup pass over the Endpoints product. Produces a prioritised report grouped by issue type, with recommended actions but does not modify anything without explicit confirmation.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3294,3295,3298],{"name":3278,"slug":3279,"type":13},{"name":3296,"slug":3297,"type":13},"Audit","audit",{"name":9,"slug":8,"type":13},"2026-06-08T08:08:33.693989",{"slug":3301,"name":3301,"fn":3302,"description":3303,"org":3304,"tags":3305,"stars":3285,"repoUrl":3286,"updatedAt":3311},"auditing-warehouse-source-health","audit PostHog data warehouse source health","Audit the health of a PostHog project's data warehouse sources and syncs — find every broken or degraded source connection, sync schema, and webhook channel. Use when the user asks \"why are my imports failing?\", \"what's broken with my sources?\", \"why is my warehouse data stale?\", or wants a one-shot triage of source\u002Fsync health before deciding where to dig in. Produces a prioritized report grouped by severity, with recommended next steps. For materialized-view health use `auditing-warehouse-view-health`; for a single failing sync use `diagnosing-failed-warehouse-syncs`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3306,3307,3309,3310],{"name":3296,"slug":3297,"type":13},{"name":2716,"slug":3308,"type":13},"data-warehouse",{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:22:57.67984",{"slug":3313,"name":3313,"fn":3314,"description":3315,"org":3316,"tags":3317,"stars":3285,"repoUrl":3286,"updatedAt":3324},"auditing-warehouse-view-health","audit PostHog materialized view health","Audit the health of a PostHog project's materialized views (saved queries) — find every failed materialization and flag unused or stale materialized views that cost storage and compute. Use when the user asks \"which of my views are broken?\", \"why is this materialized view failing?\", \"are any of my views wasting compute?\", or wants a one-shot triage of view health. For source\u002Fsync health use `auditing-warehouse-source-health`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3318,3319,3320,3323],{"name":3296,"slug":3297,"type":13},{"name":2716,"slug":3308,"type":13},{"name":3321,"slug":3322,"type":13},"Performance","performance",{"name":9,"slug":8,"type":13},"2026-06-18T08:25:10.936787",{"slug":3326,"name":3326,"fn":3327,"description":3328,"org":3329,"tags":3330,"stars":3285,"repoUrl":3286,"updatedAt":3339},"authoring-error-tracking-alerts","author PostHog error tracking alerts","Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack\u002Fwebhook\u002FLinear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing alerts, and shipping with the canonical message body shape.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3331,3334,3337,3338],{"name":3332,"slug":3333,"type":13},"Alerting","alerting",{"name":3335,"slug":3336,"type":13},"Debugging","debugging",{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:24:40.318583",{"slug":3341,"name":3341,"fn":3342,"description":3343,"org":3344,"tags":3345,"stars":3285,"repoUrl":3286,"updatedAt":3355},"authoring-log-alerts","author log alerts in PostHog","Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3346,3347,3350,3351,3354],{"name":3278,"slug":3279,"type":13},{"name":3348,"slug":3349,"type":13},"Monitoring","monitoring",{"name":1035,"slug":2597,"type":13},{"name":3352,"slug":3353,"type":13},"Operations","operations",{"name":9,"slug":8,"type":13},"2026-07-18T05:10:54.430898",{"slug":3357,"name":3357,"fn":3358,"description":3359,"org":3360,"tags":3361,"stars":3285,"repoUrl":3286,"updatedAt":3372},"building-workflows","build and edit PostHog workflows","Build, edit, test, enable, and monitor PostHog workflows over MCP. Author the action\u002Fedge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow, campaign, broadcast, drip sequence, or event-triggered automation in the workflows product.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3362,3365,3368,3369],{"name":3363,"slug":3364,"type":13},"Automation","automation",{"name":3366,"slug":3367,"type":13},"MCP","mcp",{"name":9,"slug":8,"type":13},{"name":3370,"slug":3371,"type":13},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":3374,"name":3374,"fn":3375,"description":3376,"org":3377,"tags":3378,"stars":3285,"repoUrl":3286,"updatedAt":3386},"check-posthog-loading","inspect PostHog SDK loading across URLs","Inspect how the PostHog JavaScript SDK is loaded across a list of URLs. Use to confirm consistent installation across pages, find pages missing the snippet, detect mismatched API keys or hosts between pages, and verify the load method (head snippet vs deferred vs array.js).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3379,3380,3381,3384,3385],{"name":3278,"slug":3279,"type":13},{"name":3335,"slug":3336,"type":13},{"name":3382,"slug":3383,"type":13},"Frontend","frontend",{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},"2026-05-07T05:56:19.828048",{"slug":3388,"name":3388,"fn":3389,"description":3390,"org":3391,"tags":3392,"stars":3285,"repoUrl":3286,"updatedAt":3401},"consuming-endpoints-from-client-code","integrate PostHog endpoints into client applications","Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api\u002Fopenapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says \"how do I call my endpoint\", \"generate a client for this\", or \"what auth header do I use\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3393,3396,3397,3398],{"name":3394,"slug":3395,"type":13},"API Development","api-development",{"name":3382,"slug":3383,"type":13},{"name":9,"slug":8,"type":13},{"name":3399,"slug":3400,"type":13},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":3403,"name":3403,"fn":3404,"description":3405,"org":3406,"tags":3407,"stars":3285,"repoUrl":3286,"updatedAt":3411},"copying-endpoints-across-projects","copy PostHog endpoints across projects","Copy a PostHog endpoint (a saved HogQL\u002Finsight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production, replicate an endpoint's query\u002Fvariables\u002Ffreshness config in another workspace, or clone an endpoint to iterate on it. Unlike feature flags and experiments, endpoints have NO native cross-project copy tool — this skill covers the read-then-recreate flow (endpoint-get then endpoint-create), the active-project switching it requires, name-collision checks, and the safe defaults (land unmaterialised in the target, verify with endpoint-run). Does not cover editing endpoint versions (see managing-endpoint-versions) or authoring a brand-new endpoint from scratch (see creating-an-endpoint).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3408,3409,3410],{"name":3394,"slug":3395,"type":13},{"name":3352,"slug":3353,"type":13},{"name":9,"slug":8,"type":13},"2026-07-15T05:29:58.442727",{"slug":3413,"name":3413,"fn":3414,"description":3415,"org":3416,"tags":3417,"stars":3285,"repoUrl":3286,"updatedAt":3428},"creating-ai-subscription","schedule recurring AI-generated PostHog reports","Create a recurring AI-generated PostHog report — schedule a free-text prompt to run on a cron, with the LLM-synthesized markdown delivered to email or Slack on each tick. Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly) rather than a one-off report. (To attach an AI summary to an existing insight\u002Fdashboard subscription instead of a free-text prompt, see `managing-subscriptions` and its `summary_enabled` option.)\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3418,3419,3421,3422,3425],{"name":3363,"slug":3364,"type":13},{"name":3420,"slug":200,"type":13},"Email",{"name":9,"slug":8,"type":13},{"name":3423,"slug":3424,"type":13},"Reporting","reporting",{"name":3426,"slug":3427,"type":13},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":3430,"name":3430,"fn":3431,"description":3432,"org":3433,"tags":3434,"stars":3285,"repoUrl":3286,"updatedAt":3438},"creating-an-endpoint","create PostHog API endpoints","Create a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says \"create an endpoint\", \"expose this query as an API\", \"turn this insight into an endpoint\", or asks for help structuring a new endpoint. Steers away from common mistakes: materialising a query with cohort breakdowns or compare mode, inline-only variables on a materialised endpoint, unbounded date ranges, ambiguous names.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3435,3436,3437],{"name":3278,"slug":3279,"type":13},{"name":3394,"slug":3395,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:29.624498",231,{"items":3441,"total":3540},[3442,3455,3471,3485,3501,3513,3524],{"slug":3443,"name":3443,"fn":3444,"description":3445,"org":3446,"tags":3447,"stars":26,"repoUrl":27,"updatedAt":3454},"account-handover","draft sales account handover notes","Draft structured handover notes for transitioning a PostHog account from one TAM or CSM to another. Use this skill when a TAM needs to hand over an account, prepare a transition briefing, write handover notes, create an account summary for a new owner, or any request involving account transitions between TAMs or CSMs. Triggers on \"hand over this account\", \"transition account to\", \"draft handover notes\", \"account briefing for new TAM\", \"prepare account transition\", or when a TAM names an account and says they're leaving or reassigning it.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3448,3451,3452,3453],{"name":3449,"slug":3450,"type":13},"Communications","communications",{"name":18,"slug":19,"type":13},{"name":9,"slug":8,"type":13},{"name":21,"slug":22,"type":13},"2026-04-16T05:13:00.172732",{"slug":3456,"name":3456,"fn":3457,"description":3458,"org":3459,"tags":3460,"stars":26,"repoUrl":27,"updatedAt":3470},"auditing-warehouse-data-health","audit PostHog data warehouse health","Audit the health of a PostHog project's data warehouse — find every broken or degraded pipeline item across sources, sync schemas, materialized views, batch exports, and transformations. Use when the user asks \"what's broken in my warehouse?\", \"give me a health check\", \"audit my data pipeline\", \"why are some dashboards stale?\", or wants a one-shot triage summary before deciding where to spend time. Produces a prioritized report of issues grouped by severity and type, with recommended next steps.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3461,3462,3465,3468,3469],{"name":3296,"slug":3297,"type":13},{"name":3463,"slug":3464,"type":13},"Data Engineering","data-engineering",{"name":3466,"slug":3467,"type":13},"Data Quality","data-quality",{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},"2026-06-21T08:19:05.85849",{"slug":3472,"name":3472,"fn":3473,"description":3474,"org":3475,"tags":3476,"stars":26,"repoUrl":27,"updatedAt":3484},"copying-flags-across-projects","copy feature flags across PostHog projects","Copy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace. Covers cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3477,3480,3483],{"name":3478,"slug":3479,"type":13},"Deployment","deployment",{"name":3481,"slug":3482,"type":13},"Feature Flags","feature-flags",{"name":9,"slug":8,"type":13},"2026-05-04T05:56:44.484909",{"slug":3486,"name":3486,"fn":3487,"description":3488,"org":3489,"tags":3490,"stars":26,"repoUrl":27,"updatedAt":3500},"diagnosing-experiment-results","diagnose PostHog experiment results and anomalies","Diagnoses bias, anomalies, and strange-looking results on a specific PostHog experiment. Covers empty \u002F 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A\u002FA, Bayesian vs Frequentist), PostHog-vs-SQL discrepancies, and surprises after mid-run edits. Symptom-driven dispatch to the right diagnostic.\nTRIGGER when: user asks 'is my experiment biased?' or 'why 0 exposures?', references the bias banner, says a variant looks strange \u002F wrong \u002F off, sees significance flipping, notices PostHog numbers disagreeing with their SQL, sees an A\u002FA test showing significance, or reports surprises after mid-run edits.\nDO NOT TRIGGER when: creating a new experiment (use creating-experiments), only configuring rollout (use configuring-experiment-rollout) or metrics (use configuring-experiment-analytics), or only asking lifecycle questions (use managing-experiment-lifecycle).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3491,3494,3495,3498,3499],{"name":3492,"slug":3493,"type":13},"A\u002FB Testing","a-b-testing",{"name":3278,"slug":3279,"type":13},{"name":3496,"slug":3497,"type":13},"Data Analysis","data-analysis",{"name":3335,"slug":3336,"type":13},{"name":9,"slug":8,"type":13},"2026-05-22T06:59:58.103867",{"slug":3502,"name":3502,"fn":3503,"description":3504,"org":3505,"tags":3506,"stars":26,"repoUrl":27,"updatedAt":3512},"diagnosing-missing-recordings","diagnose missing PostHog session recordings","Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota\u002Fbilling scenarios.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3507,3508,3509,3510,3511],{"name":3278,"slug":3279,"type":13},{"name":3335,"slug":3336,"type":13},{"name":3382,"slug":3383,"type":13},{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},"2026-04-22T05:06:51.989772",{"slug":3514,"name":3514,"fn":3515,"description":3516,"org":3517,"tags":3518,"stars":26,"repoUrl":27,"updatedAt":3523},"diagnosing-sdk-health","diagnose PostHog SDK health","Diagnoses the health of a project's PostHog SDK integrations — which SDKs are out of date and how to fix them. Use when a user asks about PostHog SDK versions, outdated SDKs, upgrade recommendations, \"SDK health\", \"SDK doctor\" (the former name), or when events or features seem off and it might be due to an old SDK.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3519,3520,3521,3522],{"name":3278,"slug":3279,"type":13},{"name":3335,"slug":3336,"type":13},{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},"2026-04-27T05:46:14.554016",{"slug":3525,"name":3525,"fn":3526,"description":3527,"org":3528,"tags":3529,"stars":26,"repoUrl":27,"updatedAt":3539},"error-tracking-android","track Android errors with PostHog","PostHog error tracking for Android",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[3530,3533,3534,3537,3538],{"name":3531,"slug":3532,"type":13},"Android","android",{"name":3335,"slug":3336,"type":13},{"name":3535,"slug":3536,"type":13},"Mobile","mobile",{"name":1035,"slug":2597,"type":13},{"name":9,"slug":8,"type":13},"2026-04-06T18:46:26.982494",110]