惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MyScale Blog
MyScale Blog
博客园 - 司徒正美
A
About on SuperTechFans
Vercel News
Vercel News
H
Hackread – Cybersecurity News, Data Breaches, AI and More
爱范儿
爱范儿
I
InfoQ
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园_首页
Google DeepMind News
Google DeepMind News
T
Tailwind CSS Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
F
Fortinet All Blogs
S
SegmentFault 最新的问题
阮一峰的网络日志
阮一峰的网络日志
D
Docker
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
G
Google Developers Blog
Stack Overflow Blog
Stack Overflow Blog
M
MIT News - Artificial intelligence
Jina AI
Jina AI
H
Help Net Security
量子位
IT之家
IT之家

PostHog's RSS Feed

Training our own AI models - PostHog From 270GB RAM to 5GB: Moving local flag evaluation from Django to Rust The best analytics stack for vibe-coded apps The do's and don'ts of minimum viable product marketing - PostHog The best MCP servers for startups, by workflow 4,063 errors closed without a human opening PostHog – here's what we learned - PostHog PostHog Code and the self-driving product - PostHog Why attacking your competitors online is dumb - PostHog The best real-time analytics platforms for developers, compared DuckDB vs ClickHouse: Why we use both at PostHog - PostHog PostHog's next chapter - PostHog Making Claude Cowork actually useful - PostHog PostHog vs Matomo in-depth tool comparison You're doing lifecycle emails wrong Untangling Tokio and Rayon in production: From 2s latency spikes to 94ms flat The best HIPAA-compliant A/B testing tools - PostHog A beginner's guide to testing AI agents - PostHog I hate the standup bot (so I built an agent to do it for me) - PostHog The best CDPs for developers, compared The best error tracking tools for developers, compared The best feature flag software for developers, compared 7 best session replay tools for mobile apps 7 best free open source business intelligence tools right now 7 best free and open source LLM observability tools PostHog vs LogRocket in-depth tool comparison The most popular PostHog alternatives, compared Open source (and self-hosted) session replay tools - PostHog The 9 best GA4 alternatives for apps and websites - PostHog PostHog vs Google Analytics 4 in-depth tool comparison How we built automatic clustering for LLM traces - PostHog
Our new objective: Nail Self Serve - PostHog
James Hawkin · 2022-06-10 · via PostHog's RSS Feed

The longer your strategy gets, the more useless it becomes.

That's why, at PostHog, we communicate strategy as 'Nail X', where X is the thing we need to nail. It's simple and effective.

We recently switched from Nail Enterprise to Nail Self Serve. This walks you through the previous context, and why we made that change.

James Hawkins is PostHog's Co-Founder & CEO. He launched PostHog with Tim Glaser in February 2020 as part the Y Combinator W20 batch. He lives in Cambridge, England with his wife Fran, daughter Ruby, and Wally (a cat).

The best products are generally built for end users.

The game we're playing isn't to please C-level executives or procurement - we want an engineer in any size organization on Earth to be able to use our software in production without getting up from their desk. If they work at a larger company, and if we provide them with a great experience, they'll share the platform with their peers, and will probably want to upgrade to one of our paid offerings. Our open source and free user base is our sales team.

Our original go to market plan was therefore a little like this:

  1. get our open source project to product market fit
  2. get a paid mid-size (at the time, ~$20K-$40K a year) product to product market fit
  3. get a paid large-size ($200K+ a year) product to product market fit

It took us until last Summer to get the open source product to feel successful. It became less buggy, easier to deploy, better featured and more scalable. As a result, we saw our inbound growth increasing and our retention improving.

We then focused on getting five reference customers. It turned out, we had to Nail Funnels to do this.

Things went much better than we thought. For the last six months, our paid products have averaged 20% month over month revenue growth - that's an 8.9x increase per year (for context - 3x is considered great, and Lenny's Newsletter breaks this out in more detail).

Three things combined caused this:

  • we were able to get larger (generally, up to $70k) deals than we expected
  • we made it easier to pay for our paid product, which led to more deals that we expected
  • we had more existing customer growth than we expected

Then we noticed something else.

Some customers are very fast (a couple of weeks, or less) to sell to, with minimal interaction, whereas others take months and are very intense. In fact, almost none of the customers that have put us through a big buying process have converted to revenue yet.

So we should do more of what's working.

For product, this means:

  • Quality: Our core features (insights, recordings, feature-flags / experimentation) work like a Swiss watch
  • Self-Service Subscription: Customers of every size sign-up, start using and subscribe to PostHog without asking us for help
  • Deployments: PostHog is the easiest self-hosted product to deploy and scale in the world

For go to market, this means:

  • Customer Success: Focus on time to revenue (for example, one of our Customer Success team's key results is volume of deals in our target range per week - rather than trying to hit an overall revenue figure)
  • Marketing: Accelerate word of mouth growth
  • Website and Docs: Make community self serve (for example, make our docs rather than Slack the main support channel)

Today, we're very good at serving large mid-market B2B companies who can buy quickly (through self serving).

I suspect we'll focus on B2C after the above is completed. From customer calls, it feels like this is how we'll go from landing $20k-$70k customers in a couple of weeks to $100k to $300k customers in the same, short time frame. It's much more appealing to do this, than to sell to B2B Enterprises that'll take months or years to purchase from us.

We already have plenty of (paying) customers in B2C, but to focus on it would require stronger mobile support, greater scalability still, and a suitable pricing model so we capture the right amount of value.

Long term, we think the future of our revenue will come from large enterprise. We're a natural fit - data control, consolidating multiple vendors, and complete extensibility. However, we want to avoid needing to go through complex purchasing decisions whilst there are easier ways to increase our numbers.