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

Do more to show how PostHog helps massive companies at scale #8360

Open
charlescook-ph opened this issue Apr 25, 2024 · 6 comments
Open

Do more to show how PostHog helps massive companies at scale #8360

charlescook-ph opened this issue Apr 25, 2024 · 6 comments
Assignees

Comments

@charlescook-ph
Copy link
Collaborator

charlescook-ph commented Apr 25, 2024

We've heard on the grapevine that some leader in the analytics space is telling people that PostHog isn't enterprise-ready, doesn't scale etc. While this stuff is pretty subjective and sales-y, the reality is we are successfully serving large enterprises at scale today, and we could make a slightly bigger deal of this.

I have some ideas, maybe some are good, maybe some are bad:

  • Create content with credible proof points that we can serve large customers - some ideas:
    • Customer story with a giant company, ideally one doing massive scale
    • Customer story with a company doing something at huge scale where we can talk about performance specifically
    • Engineering content that shows how we've built PostHog to scale to XXbn events/month or whatever (this kind of thing maybe?)
  • Add to the enterprise page a little bit - still keep it tongue in cheek, but:
    • Add a handful of logos from the giant companies already using us (e.g. 'PostHog successfully navigated the procurement process of...' or 'Procurement teams at these giant companies love PostHog...'). We could do Airbus, DHL, Landmark and RG.
    • Add CCPA flair
    • Link those flair logos to the relevant bits of our docs/handbook
    • Maybe add links to this page somewhere in the contact us flow and in the footer
  • Contact us page - small thing: swap out Phantom, add in DHL, RG
@charlescook-ph
Copy link
Collaborator Author

(people 'assigned' is an FYI for feedback, not 'do the work please'!)

@joethreepwood
Copy link
Contributor

joethreepwood commented Apr 25, 2024

We can probably include more to emphasize our scale on the Product OS, and pricing page too. At the moment we don't mention scale at all on pricing, for example - that seems a prime place to emphasize our ability to scale or drop the name of a large team on the Enterprise plan.

I'll be looking at the decks and assets used by CS, as well as post-demo flows soon. I can also add things about scale in there.

@simfish85
Copy link
Contributor

I think RG would be up for this - are they Enterprise enough? They are definitely high scale.

@jtemperton
Copy link
Contributor

We're looking to do some company interviews in the newsletter, about how company X solved problem Y. Not explicitly focused on their use of PostHog, but we could totally make this work and tell an interesting story about a big company solving a thorny problem and using PostHog as an essential part of that.

@andyvan-ph
Copy link
Contributor

andyvan-ph commented Apr 26, 2024

A couple of thoughts:

  • We should have this messaging on the homepage and the product pages, not just the enterprise page. Afaik, atm it's mostly a meme-page atm and it's only had 64 page views in the last 30 days. Homepage and product pages are where the action is at.

  • RE: homepage, I'd like to see a component that shows how many events we ingest each month, day, year (pick your poison), users tracked, active users, experiments launched, flags, etc. (you get the idea). I'd suggest having this right after the animation – i.e. before the code examples.

  • Should we have a dedicated section in the Docs around how we scale PostHog etc.

@charlescook-ph
Copy link
Collaborator Author

We should have this messaging on the homepage and the product pages

The reason why I didn't suggest this is that I think it goes against our overall brand/is the first step towards being too enterprise salesy (I agree with your second bullet as that's of general interest).

Hence suggesting we link to the Enterprise page in a couple of places instead. I think that the Enterprise page, personally, can still be pretty tongue-in-cheek - on customer calls with these large companies, the person we're talking is usually fully self-aware/tongue in cheek themselves ('oh you know what big enterprises are like', 'yeah we've got a classic procurement process here, bear with us').

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

7 participants