SKILL.md · 24000
servability) 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]
Output Format
Present the research brief as a structured report with clear sections. Use the Visualizer for the growth trajectory chart if the data supports it.
## [Company Name] - Onboarding Lead Research Brief
### Quick Links
- **Vitally:** [https://posthog.vitally-eu.io/customers/{organization_id}](https://posthog.vitally-eu.io/customers/{organization_id})
- **Salesforce:** [https://posthog.my.salesforce.com/{sfdc.Id}](https://posthog.my.salesforce.com/{sfdc.Id})
- **Usage Dashboard:** [{usage_dashboard_link}]({usage_dashboard_link}) *(or "Not available" if trait is blank)*
### Company Overview
- **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]
### $2K+ Spend Likelihood
**Score: [X]/100 - [High / Moderate / Low / Unlikely]**
Key factors:
- [Factor]: [+/- impact]
- [Factor]: [+/- impact]
- [Factor]: [+/- impact]
Projection: Currently at $[X]/month - projected $[X]/month in 3 months
### Vitally Usage & Billing
- **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
**Billing trajectory:**
[Chart or description of the trend - is spend growing, flat, or declining?]
**Expansion opportunities:**
- [Product they're not using that fits their use case]
- [Volume tier they're approaching]
- [Config optimization that could increase value]
### Onboarding Team Context
**Engagement level:** [Engaged / Partially engaged / Unengaged]
**Onboarding rep:** [Name]
**What happened:**
[Narrative summary of the onboarding engagement - what was discussed, what was done, what's left open]
**Key quotes or insights from the customer:**
- [Any notable things the customer said or asked about]
**Open items / unfinished business:**
- [Anything the onboarding team started but didn't finish]
- [Any promises made to the customer]
### Business Growth Trajectory
**Rating:** [Strong accelerating / Steady upward / Flat/stable / Contracting]
**Key growth signals:**
- **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]
**How this maps to PostHog spend:**
[Explicit analysis connecting each business growth vector to expected PostHog usage growth. e.g. "More customers on their platform - more end-user sessions - event volume will grow faster than current billing suggests." This is the most actionable part - it tells the TAE whether the Vitally billing trajectory understates or accurately reflects the real growth potential.]
**Score adjustment:** [If the business growth signals are strong enough to warrant adjusting the $2K+ likelihood score from Step 2, note the adjustment and reasoning here. e.g. "Business growth trajectory bumps the score from 72 to ~80 - billing data lags customer growth."]
### Recommended Play
**[Outreach / Light Touch / Skip / Wait and Watch]**
[Reasoning for the recommendation - 1-2 sentences.]
[If Skip: include DQ Reason below]
**DQ Reason (for Salesforce):**
`[250 characters or fewer - specific, concrete, copy-pasteable]`
### Draft Outreach
[If the play is Outreach or Light Touch, include the draft email in blockquoted format. If Outreach with Slack channel, also include the Slack welcome message.]
> **To:** [full email address]
> **Subject:** [subject line]
>
> [email body]
>
> [TAE name]
[If multi-user Outreach, also include:]
**Slack channel welcome message:**
> [Slack message body]
>
> [TAE name]
**Suggested angle:** [One sentence explaining why this hook was chosen and what it's designed to accomplish.]
When Processing Multiple Leads
After completing all individual research briefs, output a Summary & Priority Stack Rank table at the top of the combined output (or as a final summary section). Rank accounts by score descending.
## Summary & Priority Stack Rank
| Rank | Account | Score | Tier | MRR | Trend | Action |
|------|---------|-------|------|-----|-------|--------|
| 1 | [Company] | [X]/100 | High confidence | $[X] | Growing | Outreach |
| 2 | [Company] | [X]/100 | Moderate confidence | $[X] | Flat | Light Touch |
| 3 | [Company] | [X]/100 | Unlikely | $[X] | Declining | Skip |
Column guidance:
- Score: The final $2K+ likelihood score (0-100) with the adjusted figure if business trajectory warranted an adjustment
- Tier: High confidence (80-100) / Moderate confidence (60-79) / Low confidence (40-59) / Unlikely (0-39)
- MRR: Current MRR from Vitally billing data
- Trend: Growing / Flat / Declining - based on billing trajectory, not just business signals
- Action: Outreach / Light Touch / Skip / Wait and Watch
Reference Files
references/scoring-model.md- Full $2K+ spend likelihood scoring model with weights and criteriareferences/writing-style.md- PostHog writing style guidelines for email drafting
Critical Reminders
- 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.
- Vitally data is the source of truth for usage and billing. Don't guess at usage - pull it.
- Read every onboarding note. The onboarding team's context is gold. Skipping it means the TAE walks into the conversation blind.
- Project the trajectory. The TAE doesn't just need to know where the account is - they need to know where it's going.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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. - Use full email addresses. When listing contacts or drafting outreach, always use the full email address (e.g. [email protected]) for easy copy-paste.
- 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.