• Company name (required)
• Any context from the referral - e.g. a Slack message or email from the onboarding team (optional but helpful)
• Contact name if known (optional)

[company name] what does it do
[company name] crunchbase funding employees
[company name] series funding 2024 2025
[company name] engineering team hiring
[company name] product launch growth

• One-sentence description of what the company does
• Industry / vertical
• Company size (employees, engineering headcount if available)
• Funding stage and recency (series, amount, date)
• Revenue estimate if available
• HQ location
• Product type — is this a software product company? SaaS? Marketplace? E-commerce?
• Recent news — launches, expansions, partnerships, hiring sprees
• Growth signals — new product lines, international expansion, increasing headcount

references/scoring-model.md

• Positive signals: growth trajectory, multi-product usage, engineering team size, funding recency, industry fit, active user count, event volume trends
• Negative signals: flat/declining usage, no engineering growth, non-ICP industry, single product user, low user count

• 80-100: High confidence — Strong growth signals, multi-product, expanding team. Will likely hit $2K+ organically.
• 60-79: Moderate confidence — Good signals but some uncertainty. May need a nudge (e.g. new product adoption, config optimization).
• 40-59: Low confidence — Mixed signals. Could go either way. Worth engaging but temper expectations.
• 0-39: Unlikely — Flat usage, small team, no growth signals. May stay at current spend.

1. search_accounts_advanced

   with the company name
2. If that fails, ask the TAE for a contact email and use it to look up via user details

1. get_account_full

   (with

   detailLevel: "full"

   ) — Gets everything: MRR, health scores, traits, product usage, billing data, team assignments

2. get_account_health

   — Detailed health score breakdown

• organization_id

  (in traits) → Vitally URL:

  https://posthog.vitally-eu.io/customers/{organization_id}

• sfdc.Id

  (in traits) → Salesforce URL:

  https://posthog.my.salesforce.com/{sfdc.Id}

• usage_dashboard_link

  (in traits) → direct Metabase usage dashboard link

• Current MRR / monthly spend
• Which products are driving the spend (Analytics, Session Replay, Feature Flags, etc.)
• Billing plan (pay-as-you-go vs. annual)

• Event volume (current and trend)
• Session replay volume
• Feature flag evaluations
• Active users count and trend
• Products enabled vs. products actively used

• Is event volume increasing month over month?
• Are new products being adopted?
• Are new users being added to the org?
• Is there a gap between products enabled and products used? (expansion opportunity)

• Current monthly spend: $X
• Projected monthly spend (3 months): $X
• Key driver of growth: [product/volume/new users]
• Risk factors: [anything that could stall growth]

get_account_notes

• Initial outreach attempts and responses
• Call notes from onboarding sessions
• Configuration changes made
• Product recommendations given
• Customer pain points and goals
• Reasons for the handoff to sales

• Did the customer engage with the onboarding team? (calls, email replies, or silence)
• What did the onboarding team help with?
• What products/features were discussed?
• What pain points or goals did the customer mention?
• Why is the onboarding team handing off now?
• Any open issues or unfinished business?

get_account_conversations

• Email exchanges between the onboarding rep and the customer
• Details the customer shared about their use case
• Commitments or follow-ups that were promised

• Who was the primary contact on the customer side?
• What was the tone of engagement? (enthusiastic, transactional, unresponsive)
• Any specific asks or blockers the customer raised?
• Were there any promises or follow-ups left open?

[company name] Inc 5000 revenue growth
[company name] new customers partnerships 2025 2026
[company name] product launches announcements
[company name] hiring engineering jobs

• sfdc.harmonic_headcount__c

  vs

  sfdc.harmonic_headcount_180d__c

  — headcount delta

• sfdc.harmonic_headcountEngineering__c

  vs

  sfdc.harmonic_headcountEngineering_180d__c

  — eng headcount delta

• sfdc.harmonic_web_traffic__c

  vs

  sfdc.harmonic_web_traffic_90d__c

  /

  sfdc.harmonic_web_traffic_180d__c

  — traffic trends

• sfdc.webtraffic_growth__c

  — percentage growth

• sfdc.lnkd_follower_change__c

  — LinkedIn momentum

• sfdc.eng_headcount_change__c

  and

  sfdc.headcount_eng_growth__c

  — engineering team growth

• Revenue estimates from funding announcements, Inc. 5000 rankings, press releases
• Any disclosed growth rates (e.g. "doubled ARR", "3x revenue")
• Evidence of pricing power or contract expansion (moving upmarket, bigger deals)

• Recent fundraise amount, date, lead investor, and what the funds are earmarked for
• Repeat investors (insiders participating again = confidence)
• Are they raising a growth round (go-to-market) or an R&D round? GTM rounds drive PostHog usage faster.

• New product launches or major features shipped in the last 12 months
• New product lines = new surfaces to instrument = more PostHog events and replays
• Platform plays (APIs, integrations, clearinghouses, marketplaces) create multiplicative event growth

• New customer segments being targeted (enterprise, SMB, new verticals, new geographies)
• Partnership announcements (channel partners, tech partnerships, integrations)
• Each new customer on their platform = more end-user sessions flowing through PostHog

• Total headcount delta (6-month and 12-month view using Harmonic data from Vitally)
• Engineering team growth specifically — more engineers = more features shipped = more things to instrument
• Go-to-market hiring (sales, CS, marketing) = more internal PostHog dashboard users
• Job postings on their careers page — what are they hiring for right now?

• Web traffic trends from Harmonic/SFDC data
• LinkedIn follower growth
• Industry recognition (awards, rankings, conference appearances)
• Content marketing velocity (blog posts, reports, webinars) — indicates go-to-market investment

• More customers on their platform → more end-user sessions → more events, replays, and flag evaluations
• New product launches → new surfaces to instrument → broader PostHog product adoption (analytics + replay + flags)
• Engineering team growth → more features shipped → more things tracked → higher event volume
• GTM team growth → more internal PostHog users → more dashboards and insights consumed
• Platform/marketplace plays → multiplicative event growth (each participant generates events)
• Geographic expansion → new user cohorts → step-function increases in volume

• Score >= 60 (High or Moderate confidence)
• 2+ active users in the account
• No one from PostHog is already actively engaged with this account

• Score 40-59 (Low confidence) but the account has interesting signals worth exploring
• Single active user but spend is meaningful (>= $1K/month)
• The account already has a relationship with PostHog (e.g. engaged with onboarding team)

• Score 0-39 (Unlikely)
• Non-ICP industry with no offsetting signals
• Usage declining with no business growth to suggest recovery
• Account shows churn risk (past due billing, declining spend)
• Customer explicitly declined engagement (said "no thanks" or similar) - unless their spend is high enough that hearing about discounts from a TAE would be genuinely useful to them

• "MRR declining $1,763->$696 forecast. Single product (analytics). 8 employees, 3 engineers. No growth signals despite $9.1M revenue. Group Analytics likely unnecessary."
• "Non-ICP: school bus routing company (founded 1977). Analytics-only, $1,369 flat MRR. 4.78 health. No expansion signals. Govt/education customer base."
• "Past due billing. MRR forecast drops 49% ($2,130->$1,086). 7-person seed startup. Likely cash-constrained despite Khosla backing."
• "Explicitly declined onboarding engagement. $380 MRR, single product, no growth trajectory. No value angle for TAE outreach."

• "Not a good fit" (too vague)
• "Low score" (doesn't explain why)
• "Small company" (which signal matters?)
• "No engagement with onboarding" (non-response is not a signal - they may have been busy)
• "Unresponsive" (same problem - silence is not rejection)

• Early-stage company with high variance - could go either way
• Score 40-59 with strong business growth signals but weak current billing
• Check back in 4-6 weeks to reassess

1. Lead with the Slack channel. For multi-user accounts, the shared Slack channel is the most valuable thing you're offering - a direct line to someone technical at PostHog. Open with it. Explain why it's useful for their specific situation based on your research. Don't bury it.
2. Write like a fellow engineer, not a salesperson. These are competent developers. The TAEs are deeply technical. Write the way you'd message a colleague - direct, concise. No praise or cheerleading about their setup. "Your team's ramped up fast!" reads as patronizing to engineers who know exactly what they've done.
3. Start with an observation about them, not about you. The first real sentence should reference something specific from Vitally or your research - which products they're using, what their team is building, a specific usage pattern. Never open with "I'm [name], your PostHog contact."
4. Keep it short. The initial email should be 3-5 sentences. Slack channel + why it's useful + one specific observation or optimization + a question. Save the details for Slack.
5. One question per email. More than one question overwhelms and reduces response rate. Pick the most interesting one.
6. Be direct about billing when relevant. Unlike big fish outreach, onboarding handoff leads already have meaningful spend. It's OK to reference costs - pair every cost mention with an actionable way to reduce it.
7. Only reference what you can verify. Safe: Vitally usage data, public website, confirmed funding rounds. Never cite enrichment data (Clearbit/Harmonic tech stack fields) as fact. If you state something about their setup and it's wrong, you lose credibility.

references/writing-style.md

• Get to the point. No "I'm reaching out because...", "I just wanted to...", "Saw you just signed up."
• American English. Oxford comma. Straight quotes.
• Hyphens only (-) for breaks in thought. Never em dashes or en dashes. Em/en dashes read as AI-generated.
• Links in anchor text. Never bare URLs. Never "click here." Always describe the destination: "here's a guide on connecting replay to funnels."
• Capitalize product names. "Session Replay", "Feature Flags", "Product Analytics."
• Abbreviate numbers. 10M, 100B (capital letter, no space).
• No emojis in emails.

• "I'm [name], your dedicated PostHog contact" - your name is in the signature.
• "Saw you just signed up" / "Just checking in" - they know. This adds nothing.
• "I'm here if you need anything" - too passive. Say something specific or don't say it.
• "Your team's ramped up fast!" / "That's impressive adoption" - patronizing. State facts.
• Feature laundry lists - reference the 1-2 products they're actually using, not all of PostHog.
• Multiple optimization suggestions in one email - save it for Slack.
• Bare URLs - always embed in anchor text.
• Citing enrichment data as fact - "I noticed you're using [competitor]" from an unverified SFDC field.
• Referencing exact event counts - "you sent 4.2M events last month" feels surveillance-y. Reference products and patterns, not precise numbers.
• More than one question per email.

To: team@acmecorp.com Subject: Slack channel for Acme <> PostHog

Hey Acme team,

Setting up a shared Slack channel for you - with 57 people in the account across analytics, replay, and error tracking, a direct line for questions will be useful as you scale.

One thing that might be worth exploring: Feature Flags for safe rollouts. With your new product line launching as a platform, gradual rollouts and instant kill switches are the kind of thing that keeps deploys boring. Happy to walk through the setup in Slack.

What's the main thing your team is trying to learn from the analytics right now?

[TAE name]

To: eng@example-payments.com Subject: Slack channel for Example Payments <> PostHog

Hey Example Payments team,

Sending over a Slack channel invite - with 42 people using analytics, flags, and replay, it'll be the fastest way to get answers on implementation or billing as things come up.

One quick win: if your team is running A/B tests on checkout flows, Experiments layers directly on top of your existing Feature Flags setup. For a payments product, measuring conversion impact per variant is where the real signal is.

What's the team trying to optimize right now?

[TAE name]

To: dev@example-ai.com Subject: Your PostHog setup

Hey,

Noticed you're using LLM Analytics alongside product analytics - that's a sharp setup for monitoring AI-generated content quality alongside user behavior.

If you're tracking prompt-to-output quality, this guide on LLM observability covers how to connect traces to user outcomes so you can see which prompts actually help students learn vs. just generate text.

Happy to help if questions come up.

[TAE name]

• Vitally: https://posthog.vitally-eu.io/customers/{organization_id}
• Salesforce: https://posthog.my.salesforce.com/{sfdc.Id}
• Usage Dashboard: {usage_dashboard_link} (or "Not available" if trait is blank)

• What they do: [one sentence]
• Industry: [vertical]
• Size: [employees] ([engineering count] engineers)
• Funding: [stage], [amount] ([date])
• HQ: [location]
• Growth trajectory: [Accelerating / Steady / Flat / Early stage]

• [Factor]: [+/- impact]
• [Factor]: [+/- impact]
• [Factor]: [+/- impact]

• Current MRR: $[X]
• Products in use: [list]
• Products NOT in use: [list - these are expansion opportunities]
• Event volume: [current] ([trend])
• Active users: [count] ([trend])
• Health score: [X]/10

• [Product they're not using that fits their use case]
• [Volume tier they're approaching]
• [Config optimization that could increase value]

• [Any notable things the customer said or asked about]

• [Anything the onboarding team started but didn't finish]
• [Any promises made to the customer]

• Revenue: [what's known about ARR growth, Inc. 5000 ranking, etc.]
• Funding: [recent round, amount, investors, what it's earmarked for]
• Product velocity: [new launches, features, platform plays in last 12 months]
• Customer expansion: [new segments, partnerships, geographic expansion]
• Headcount: [total delta, eng delta, GTM hiring signals]
• Web/brand momentum: [traffic trends, LinkedIn growth, awards/recognition]

To: [full email address] Subject: [subject line]

[email body]

[TAE name]

[Slack message body]

[TAE name]

undefined

• references/scoring-model.md

  - Full $2K+ spend likelihood scoring model with weights and criteria

• references/writing-style.md

  - PostHog writing style guidelines for email drafting

1. Research first, then draft. Complete all five research workstreams before recommending a play or drafting outreach. The research informs the outreach hook - without it, the email will be generic.
2. Vitally data is the source of truth for usage and billing. Don't guess at usage - pull it.
3. Read every onboarding note. The onboarding team's context is gold. Skipping it means the TAE walks into the conversation blind.
4. Project the trajectory. The TAE doesn't just need to know where the account is - they need to know where it's going.
5. Flag discrepancies. If the web research and Vitally data tell different stories (e.g. company seems to be growing but PostHog usage is flat), call that out explicitly. This is especially important in Step 5 - if the business is accelerating but PostHog billing is flat, the billing is lagging and there's upside.
6. If Vitally data is thin, say so. Don't invent data. If there are only 2 notes and no conversations, report that - it's useful context in itself (means the customer may not have engaged much).
7. Business growth is the leading indicator; billing is the lagging one. The Step 5 business growth trajectory analysis is what differentiates a good research brief from just reading Vitally numbers. A company that just raised $43M and doubled ARR is going to grow their PostHog spend - even if the current billing doesn't show it yet. Conversely, a company with declining headcount and no recent funding may be at peak spend already. Always connect the business trajectory to the expected PostHog spend trajectory.
8. Use Harmonic data from Vitally traits. The SFDC/Harmonic fields in the account traits contain headcount deltas, web traffic trends, LinkedIn growth, and funding details. Cross-reference these with your web research - they often tell a richer story than the web alone.
9. Industry context matters for the growth mapping. How a company grows affects how PostHog usage grows. A platform/marketplace company gets multiplicative event growth per customer. A SaaS company gets linear growth per customer. An infrastructure company may generate heavy backend events but few replays. Map the business model to the right PostHog products.
10. DQ reasons must be copy-pasteable. When recommending Skip, the DQ reason goes directly into Salesforce. Keep it under 250 characters, make it specific, and include the key data points that justify the disqualification.
11. Draft outreach follows the writing style guide. Read

    references/writing-style.md

    . Hyphens only (never em/en dashes). No bare URLs. No feature laundry lists. One question per email. Lead with the Slack channel for multi-user accounts.
12. Use full email addresses. When listing contacts or drafting outreach, always use the full email address (e.g. contact@acmecorp.com) for easy copy-paste.
13. Validate all URLs before presenting the draft. Fetch every link in the email to confirm it resolves. If broken, search for the correct page or remove the link.