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

推荐订阅源

S
Schneier on Security
B
Blog RSS Feed
V
V2EX
博客园 - 聂微东
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Apple Machine Learning Research
Apple Machine Learning Research
博客园 - 司徒正美
L
LINUX DO - 热门话题
WordPress大学
WordPress大学
腾讯CDC
酷 壳 – CoolShell
酷 壳 – CoolShell
Scott Helme
Scott Helme
T
Threatpost
P
Privacy International News Feed
博客园 - Franky
Spread Privacy
Spread Privacy
K
Kaspersky official blog
博客园_首页
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
爱范儿
爱范儿
L
Lohrmann on Cybersecurity
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
T
The Exploit Database - CXSecurity.com
GbyAI
GbyAI
T
Tenable Blog
C
Cisco Blogs
阮一峰的网络日志
阮一峰的网络日志
V
Visual Studio Blog
I
Intezer
J
Java Code Geeks
P
Proofpoint News Feed
C
Cybersecurity and Infrastructure Security Agency CISA
Y
Y Combinator Blog
月光博客
月光博客
有赞技术团队
有赞技术团队
T
Tailwind CSS Blog
H
Help Net Security
D
Docker
M
MIT News - Artificial intelligence
AWS News Blog
AWS News Blog
Security Latest
Security Latest
C
CERT Recently Published Vulnerability Notes
Blog — PlanetScale
Blog — PlanetScale
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
D
Darknet – Hacking Tools, Hacker News & Cyber Security
T
Threat Research - Cisco Blogs
T
Tor Project blog
The Cloudflare Blog
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Microsoft Azure Blog
Microsoft Azure 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 CEO diary: The things I learned in 2022 - 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
The time before YC - PostHog
James Hawkin · 2019-09-01 · via PostHog's RSS Feed

I'm James, and I work with Tim. We are the co-founders of PostHog - a current batch YC company.

This is us (I'm on the right), just after we got now-redundant, pre-pivot swag:

James and Tim

We quit our jobs around August 2019, and put the last $8K of salary into a business bank account. We had both saved enough money to live on for at least 12 months without any income.

I went travelling with my wife for 3 weeks around Europe whilst we worked on our first idea.

Our product was 'a sales territory management platform, that uses predictive analytics so you stop wasting time on deals that won't sell'. I used to run a sales team, and this was something I'd have wanted to help me manage territories. Tim ran R&D and was very quick at building things.

Tim built the product and I started doing customer calls from the cheapest Airbnbs I could find around Lake Geneva, cafés in Venice and a hut in an olive grove in Tuscany:

Olive groves in Tuscany

Not only did I have slow wifi, but the idea was complicated and people didn't get it. We had just two customers start using it, and that's only because they were already our friends. One of those two was happy paying $200 MRR for it, but then his company pivoted. We ended up bringing Aaron on board as our first employee the following January.

If we explained the complex modelling, we'd watch people's eyes glaze over. If we didn't, they wouldn't believe it worked.

We decided to simplify it. We turned our 1-liner into "a sales 1:1 tool that uses predictive analytics to make sure you talk about the deals that matter". When I ran sales, I struggled to find time to do this, yet I felt it was important, and I felt that salespeople would want to talk about good news but not bad news. Our predictive analytics could keep 1:1s well organised and balanced.

I drove back to the UK from Tuscany. Sidenote: my ac broke and it was the hottest day of the year. It was a 30 hour drive.

Tim and I managed to get cheap WeWork access. We spent $100/month each. If you're in the US, I would get a platinum AMEX card instead, it's an even better deal. It wasn't perfect, but working together and not in cafés helped our focus immeasurably.

Although I can code, I am too slow, but I have done a lot of sales and marketing before. We split our roles out clearly. Tim was to build the product, I was to book 2 meetings with heads of sales every day.

We did that for 3 weeks. We wrote lengthy notes and took quotes from every single meeting in a gigantic Google Doc. We hit our target. I got meetings by finding real life communities, making friends in those and asking around. I also used LinkedIn a lot, engaging in conversations and eventually asking to talk about our roadmap with people who might find it interesting. People are pretty helpful if you are just asking for advice and not trying to sell them. It was uncomfortable and hard work, but it helped us constantly "talk to users" - something YC preaches.

In the product, we focused heavily on the onboarding flow. We wanted each user to bring more than 1 extra user. Just like Facebook in the early days. When a user signed in, it would send them to a page that'd read their calendar to guess which meetings were 1:1s, and it'd ask them to invite those users. Once they were in the tool, it'd also integrate with Slack so it'd remind you to plan your 1:1s and it'd let you plan the whole thing through their UX.

The calls sounded like they were going really well. 15 people said they would use it for their team.

After the first week of building it, we started sending the link out to sign up after each call.

Almost no one even clicked the link in the email. Not a single person planned a 1:1 with it properly.

YC later told us, at the induction, that we should read The Mom Test. Now we know why. We think we failed because we didn't ask if sales leaders have ever planned their 1:1s in advance, and to show us what their agenda looked like. It turns out, they usually don't. If this really felt like a problem to them, they would.

It was around this time we thought about applying to YC. We had originally had visions of bootstrapping.

Sat in the bright lights and gentle noise of people cold calling from communal work areas, fuelled by a free oat cappuccino or four, Tim and I talked about what we would regret not doing when we were 80.

That turned out to be the most helpful way to clarify what we actually wanted. We decided that we could bootstrap and over 4 years get to the kind of job we already had with good pay and with financial stress along the way. That sounded slow, and dull.

We wanted to push for more. We wanted to go bigger. Getting fuel from VCs meant our success wouldn't come from owning a huge pie, we'd own a smaller chunk of a massive one, and we would get a lot more breadth of experience by doing this. Neither of us is particularly patient, and so we decided shooting for the stratosphere would be more fun.

We had a problem though. The YC deadline was looming, we had a product no-one cared about. That's not what the YC t-shirts say.

It was now a Thursday evening, the deadline was Tuesday.

We decided we wanted to focus on developers. They'd give a better signal:noise ratio when we asked them what they needed, and they'd be more willing to try new products out.

In our past, we both saw challenges with tech debt when organisations scale. It causes shipping to slow down and good engineers to get frustrated.

I did the website, Tim did the product. I started outreach to every developer I knew, interviewing them on pain points. The good news was that a bunch of our friends worked at big companies.

Tuesday swung around. We had an MVP working and we had developers at 10 companies saying they were interested.

We wrote the application form. We kept talking about benefits. My previous job was selling enterprise software to banks - that's how I write by default.

Each word had way too many letters, and it was boring. We chucked it away, at 8pm - the night it was due.

Everyone in the example application videos had thousands of users, revenue or had worked at impressive companies. We were intimidated by them.

The situation on paper was so bad, that it felt funny.

We relaxed, and wrote in natural language using very few, and very simple, words.

We put together a video of our MVP for the demo. We designed it to look so simple it felt tongue in cheek:

Neither of us has worked at a FANG company. Neither of us knew anyone at YC, and my only knowledge of the West Coast came from my wife making me watch the OC with her. We had no actual users, and we definitely had no revenue.

We got the interview email.

We just followed the instructions, and got in. They take people at any stage if they like the application.

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