Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(SuperDay) Plugging the Teams-Add on in the existing startup-flow #10050

Open
SaraTribecastle opened this issue Dec 3, 2024 · 0 comments
Open
Assignees

Comments

@SaraTribecastle
Copy link
Contributor

@joethreepwood As we want to increase adoption of the Teams Add-on for our startup program, an easy place to start could be to just plug it in the existing

Considering many of the startups that sign up for the Teams Add-on do so early on after becoming Posthog customers, the first

  1. Welcome email
    Screenshot 2024-12-03 at 16 04 01
    Add a 4th "security" hedgehog, promoting the add-on

H1: Start-ups need security & rights management, too (and other things)
Get Posthog Teams Add-on for advanced security compliance, SSO enforcement, 2FA and features for collaboration with team members.

  1. Alerting of 50% use of credits
    Screenshot 2024-12-03 at 16 04 22
    Add a “PS.”-section after CTA

“P.S: Heard of our Teams Add-on? It’s brimful of useful security & collaboration features. You should check it out.”

  1. Alerting of 75% of credits
    Screenshot 2024-12-03 at 16 04 37
    Add a fourth hedgehog, somehow about teams or security?

H1: Check out our Teams Add-on

If you need advanced security like SSO, 2FA and other fun – but useful – Enterprise-level features, our Teams Add-on might be what you need.

My hunch is that the last email doesn't make sense to include this plug as it's no longer about adoption/upsell at that point, but rather if they stay with us overall.

@joethreepwood joethreepwood self-assigned this Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants