Add communications template for new feature adoption (TAMs)

[leonhardprinz]

Add TAM feature adoption communications template

Changes

What

• Adds a handbook page with a TAM template for driving first use of new features
• Includes cadence, goal-tied examples, and direct doc links

Why

• Marketing builds awareness; TAMs drive first use and proof of value for named accounts

Review asks

• Tone and clarity match the handbook
• Examples feel realistic and useful
• Links point to the right PostHog docs

Checklist

• Words are spelled using American English
• Titles are in sentence case
• Feature names are in sentence case too. It's "product analytics" not "Product Analytics" and so on.
• Use relative URLs for internal links
• If I moved a page, I added a redirect in vercel.json
• Remove this template if you're not going to fill it out!

Article checklist

• I've added (at least) 3-5 internal links to this new article
• I've added keywords for this page to the rank tracker in Ahrefs
• I've checked the preview build of the article
• The date on the article is today's date
• I've added this to the relevant "Tutorials and guides" docs page (if applicable)

[vercel]

@leonhardprinz is attempting to deploy a commit to the PostHog Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[landon-posthog]

Looks good, ship it

[landon-posthog]

@corywatilo or @ivanagas are we able to sort this?

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
posthog	Ready	Preview	Nov 12, 2025 0:10am