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

推荐订阅源

L
LangChain Blog
N
News and Events Feed by Topic
T
Tor Project blog
AI
AI
S
Schneier on Security
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
Hacker News: Ask HN
Hacker News: Ask HN
Spread Privacy
Spread Privacy
The Last Watchdog
The Last Watchdog
B
Blog
G
GRAHAM CLULEY
Recent Commits to openclaw:main
Recent Commits to openclaw:main
W
WeLiveSecurity
GbyAI
GbyAI
Hacker News - Newest:
Hacker News - Newest: "LLM"
C
Check Point Blog
SecWiki News
SecWiki News
Y
Y Combinator Blog
I
Intezer
S
Securelist
WordPress大学
WordPress大学
小众软件
小众软件
Google DeepMind News
Google DeepMind News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
美团技术团队
Schneier on Security
Schneier on Security
F
Full Disclosure
D
Darknet – Hacking Tools, Hacker News & Cyber Security
P
Proofpoint News Feed
Jina AI
Jina AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Help Net Security
Help Net Security
P
Privacy International News Feed
N
News and Events Feed by Topic
人人都是产品经理
人人都是产品经理
The Register - Security
The Register - Security
Application and Cybersecurity Blog
Application and Cybersecurity Blog
MyScale Blog
MyScale Blog
Vercel News
Vercel News
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
Threatpost
H
Help Net Security
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
G
Google Developers Blog
T
Tailwind CSS Blog
L
Lohrmann on Cybersecurity
Forbes - Security
Forbes - Security
C
Cisco Blogs
The GitHub Blog
The GitHub Blog
博客园 - 司徒正美

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 The 7 best HIPAA-compliant analytics tools 8 best open source analytics tools you can self-host - PostHog The best product analytics tools for startups, compared PostHog vs FullStory in-depth tool comparison The best in-app survey tools for product teams, compared The 7 best mobile app analytics tools PostHog vs Hotjar in-depth tool comparison The 8 best free and open-source feature flag services - PostHog The 5 best free and open-source A/B testing tools - PostHog The best mobile app A/B testing tools, compared What is a feature flag? Feature Flags vs Remote Config vs A/B Testing PostHog is now available in Vercel’s v0 The best Heap alternatives & competitors, compared PostHog vs Heap in-depth tool comparison PostHog vs Pendo in-depth tool comparison PostHog × Vercel: feature flags, minus the plumbing Your logs' final destination is in GA. You always end up here anyway Behind the scenes of a PostHog hackathon - PostHog The most popular Mixpanel alternatives & competitors, compared PostHog vs Mixpanel in-depth tool comparison The 9 best GDPR-compliant analytics tools How we use Logs at PostHog The best web analytics tools for developers, compared Stop AI slop: Run evals with LLM-as-a-Judge - PostHog You product data just got a job: Workflows is now out App onboarding: How to fix drop-off points Meet Logs (beta) – logs with all the tools you’re already using Why small teams crush tiger teams How we built user behavior analysis with multi-modal LLMs (in 5 not-so-easy steps) - PostHog The best Contentsquare alternatives & competitors, compared 8 learnings from 1 year of agents – PostHog AI - PostHog Why we killed our AI product assistant Workflows graduate to beta! Product data, meet automation The best Rollbar alternatives & competitors, compared Workflows are now in Alpha and I already broke mine - PostHog I've consistently underestimated how important communication is as a CEO - PostHog How we made feature flags even faster and more reliable The best session replay tools for developers, compared What I learned attending my first ever hackathon - PostHog Did you know AI is answering our community questions? - PostHog How not to be boring - PostHog We built an internal tool to generate changelog images for social media - PostHog What we built at our windswept Mykonos hackathon - PostHog How we built our onboarding email flow (with actual performance data) - PostHog We're building a better PostHog community by closing our public Slack - PostHog Introducing Notebooks for PostHog - PostHog Why we've launched PostHog user surveys - PostHog How we made feature flags faster and more reliable - PostHog In-depth: ClickHouse vs Redshift - PostHog Introducing HouseWatch: An open-source toolkit for ClickHouse - PostHog Introducing HogQL: Direct SQL access for PostHog - PostHog What we built at our sun-kissed Aruba hackathon - PostHog In-depth: ClickHouse vs BigQuery - PostHog In-depth: ClickHouse vs Elasticsearch - PostHog HogMail #22: Why do companies over-hire?" - PostHog Our simpler goal: Help engineers to be better at product - PostHog In-depth: ClickHouse vs Snowflake - PostHog HogMail #21: Avoiding the "Product Death Cycle" - PostHog Sunsetting Kubernetes support for PostHog - PostHog Why 'Product Engineer' is the most fun role I've had in tech - PostHog HogMail #20: Why do startups fail? - PostHog The best Google Optimize alternatives for apps and websites - PostHog Array 1.43.0: Massive performance improvements! - PostHog In-depth: ClickHouse vs Druid - PostHog HogMail #19: Which meetings should you kill? - PostHog The essential tools used by product engineers - PostHog HogMail #18: What can SaaS learn from the New York Times? - PostHog What is a product engineer? - Product Engineer Handbook - PostHog Array 1.42.0: Get beta features via our roadmap! - PostHog HogMail #17: The personal traits that can't be taught - PostHog
CEO diary: The things I learned in 2022 - PostHog
James Hawkin · 2023-01-11 · via PostHog's RSS Feed

It's always helpful to look back on the year just gone, and 2022 was an exceptionally good year for PostHog. Here's my personal perspective on how it went.

We grew very fast and are much more durable

Our 2022 revenue growth over time, which increases by 6 times

  • Revenue grew nearly 6x without any outbound sales team.

  • We hit a 2 month CAC payback period, salaries included. Around 12 months is seen as exceptional.

  • We are comfortably default alive and will likely be profitable in 2023.

We still have work to do. We're working on gross margin – we've done close to zero cost optimization on our hosting so far - and we want to hit a higher absolute level of revenue (around $10M ARR) without spending significantly more before we fundraise again.

We let people go when we needed to

We remained disciplined and let people go when we needed to. This helps us retain an ambitious and performance-oriented culture. While these moments are painful, we received positive feedback from our team when we explained why we made these decisions, transparently.

We are compassionate, but reasonable – we pay 4 months severance because our attitude is letting people go earlier is better for everyone and a big payout for them is kinder in return, so having the latter means the former condition is met.

Tim and I wound up in the wrong roles, but we spotted this and fixed them

Tim (my co-founder) and I realized we were managing the wrong teams because the game had changed. I was good at early sales, but we've moved on from that and now he's the right person to help us scale things there.

Likewise in product, we want to go from good to great and that'll take more design attention, which I can help with.

Tim and I therefore swapped a bunch of priorities around with each other, and (so far) it feels much better.

There are two reasons we spotted this: the combination of (1) feedback from our teams and (2) a love / tradition of going for "salt of the earth curries".

We regularly do 360 feedback dinners at offsites, but this feedback came from asking these questions about each other on the exec team in our 1:1s, randomly:

  • What do I do that you experience as world-class?

  • What do I do where I appear to be experiencing fun, peace or joy (if different from above)

  • What do I do that I am good at but that I don't appear to enjoy?

  • What do I do that I am not better at than others?

  • What do I do that I am actually worse than others?

Secondly, Tim and I love going for a curry every couple of weeks when we work together in person (we're all remote, but we do make an effort to hang out). This means specifically an unpretentious but tasty curry somewhere.

My wife isn't a huge fan of them so, nearly every time we meet, I jump at the chance and I think I've converted Tim. During one of these, we talked through the feedback we'd received. It's a good reminder to hang out and not make every interaction 'zoomformulaic'.

I was prioritizing badly, but Tim held me accountable and we fixed that too

At one point, I was getting the individual contributor (IC) work done, but not prioritizing things like company vision/OKRs. Knowing when to do this is a real skill. Too much of it and you're setting a silly culture of planning over trying stuff out; too little, and you don't have a clear direction.

Tim suggested I hire Kendal (Exec Assistant) to help solve this. I felt really silly hiring someone to manage my time and to keep me organized, but the reality is that I can now give more value to the company, which helps everyone. Having a nudge from someone else was what I needed to commit.

A crappy family situation got much better

My (then) one-year-old daughter got diagnosed with bilateral retinoblastoma (a type of cancer) in 2021. She lost an eye as a result, has her vision permanently damaged in the other, and had to go through chemo. We were delighted to wrap up treatment in the Spring 2022. We were lucky that it went perfectly... she was "cured" (as far as you can be of cancer), and now we're in regular monitoring mode. When she got diagnosed, I chose to focus on revenue over fundraising (instead of trying to do both while taking care of her), and now a year and a half on, I'm very glad that's what we picked.

We are shipping stuff

We made too many improvements to list on user-facing functionality, and infra / ingestion-based functionality. It feels like we can make new things appear, although Q1 will be a big test – it'll be one of our most ambitious quarters.

Other teams also get their work out the door quickly, unimpeded by bureaucracy / excessive planning. We've had a ton of marketing content appearing, a smooth time with our

People & Ops mini crest

People & Ops Team

People & Ops mini crest
People & Ops Team, and a
Growth mini crest
Growth Team
Growth mini crest
Growth Team
that can't stop producing winning variants!

I'm really glad we're not doing outbound / went for a growth team instead

It is always tempting to hire an outbound sales team. After all, we can sell the product and retain users, to a tightly defined audience.

However, it just feels like it'd be very hard to do outbound sales to developers. I can't think of a worse group to target this way (this is coming from a place of experience as I've run outbound sales teams before).

Instead, we set up a growth team. We've had dramatic results from doing this – such as 25% improvements in our activation flow from single experiments. Yep, one experiment has led to a 25% increase in our monthly growth, forever. That's why we have such a low CAC payback period...

If we had hired a sales team, I guarantee we'd be focusing on how to send more cold emails more effectively versus the more leveraged work of improving our onboarding, activation and billing flows.

We can take pride in not focusing on number of staff / investors

Lots of companies raised very hyped funding rounds in 2021 – we had demand, but ultimately chose not to move forward. We are confident we made the right call not to do this, but we felt at the time that we were going against the grain. It was really cool to talk about this stuff openly with our team, and to see how quickly we started taking pride in building a real company.

Doing more of what works in many parts of the company has been great

In go-to-market, it's always tempting to explore new channels. However, in 2022, we really benefited from understanding where our growth was actually coming from, and doing more of those things. This meant content marketing and word of mouth growth.

Our free support quality has been a bit variable

We get around twice as many community support questions now as we did last year. We've not tracked it, but it feels like we're a lot more rushed as a result when trying to get to everything.

We've implemented multiple things to try to improve this – Squeak!, a backup infra hero, generally prioritizing cloud (since it's a better experience if possible), launching Cloud EU to help with GDPR compliance, and hiring Paul Hultgren to work on our docs full time.

These improvements caused a 75% drop in the likelihood of each user to need support, but that was outweighed by how much growth we had. There are therefore more things to come here as this is an ongoing challenge as we keep scaling.

Staying on top of IC work as a cofounder with 40 people is hard

Tim and I have both felt this at different times. We think it's very important we both do individual work – simply, it's more fun to work alongside someone, and that's only the case if we do some actual work. Longer term, we want a culture that values individual contribution, so we should do this ourselves.

However, it is tough pulling this off while making sure the entire company runs in a manner that we're proud of – we've both felt frustrated when we see our individual work slip as a result. That's no reason not to do it, though.

  • Looking after hobbyist users as our revenue is accelerating. Most users of PostHog pay us nothing, and they're often the ones talking about us as part of our word of mouth growth. This can conflict with short-run revenue goals at times, but is fundamentally in line with long term targets (if we have a big fanbase, then that'll bring more fans both free and paid) - and that's ultimately more important, since we're default alive.

  • Our margins! It'll be the first year we put real effort into hosting costs specifically. Alongside increasing our overall revenue figure, which will happen naturally with time, this is the other metric that'll make a series C easier to raise if we improve it (all the others we need are already in a great place).

  • Scaling execution. We want to build a real machine around certain things that are working (like content and customer success), so we can get more done and/or to a higher standard without more people.

  • New UI. We've a PostHog 3000 project to pull off. It'll affect multiple teams, so managing to do that without a coordination mess happening will prevent us from being slow at shipping features.

  • Keeping on top of our infra/ingestion. We have a ridiculous number of events coming in - we must stay up and reliable. We've hired a lot here so far, but we've a huge surface area to manage.

  • New feature buzz. We should get more marketing benefit from all the cool stuff we ship. Lots of ideas about doing more with our public roadmap here.

Enjoyed this? Subscribe to our newsletter to hear more from us twice a month!