PostHog Insights for Solo Founders

You shipped your product. Users are coming. But you're flying blind on what they're actually doing.

Maybe they're churning at signup. Maybe they're hitting a wall at onboarding. Maybe they're not hitting the feature that justifies your pricing. You don't know because you haven't set up analytics properly—or you've set up something bloated that takes three hours to query.

This is where PostHog Insights comes in. It's the fastest way for solo founders to see user behavior without hiring a data analyst or wasting time in dashboards.

This guide walks you through the exact templates you can clone, the questions you can answer in minutes, and the specific setup that takes less than an hour. By the end, you'll have actionable insights into what your users are doing—and where they're dropping off.

Prerequisites: What You Need Before Starting

Before you dive into PostHog Insights, make sure you have these in place.

You need a PostHog account. If you don't have one, head to PostHog's homepage and sign up for free. PostHog offers a generous free tier that includes up to 1 million events per month, which is plenty for early-stage founders.

You need PostHog installed on your product. This means you've added the PostHog SDK to your frontend, backend, or both. If you haven't done this yet, PostHog's documentation has step-by-step guides for every framework—React, Next.js, Python, Node, you name it. Installation takes 10 minutes.

You need at least 48 hours of data. PostHog Insights works better with a sample of real user behavior. If you just launched, you might have limited data, but the templates in this guide work regardless of scale.

You should have Google Analytics 4 connected. While not strictly required for PostHog Insights, pairing PostHog with GA4 gives you the full picture. If you haven't set up GA4 yet, read our guide on setting up Google Analytics 4 for SEO tracking from day one and linking GA4 with Google Search Console.

You need to understand your core user journey. Know what "success" looks like for your product. Is it signing up? Completing onboarding? Making a payment? Using a specific feature? Write this down before you start building Insights.

If you're just starting with SEO and product analytics together, check out the free SEO tool stack every founder should set up today for a complete bootstrapper's foundation.

Step 1: Understand What PostHog Insights Actually Does

PostHog Insights is not a dashboard. It's a query builder for user behavior. You ask questions, and it answers them with data.

The key difference: traditional dashboards show you metrics over time. Insights shows you why those metrics moved. It's the difference between "we had 100 signups today" and "signups dropped 40% because users are bouncing after the onboarding video."

Insights lets you:

• Track user journeys. See the exact sequence of events users take before they convert (or churn).
• Segment by user properties. Compare behavior across cohorts—new users vs. returning users, paid vs. free, desktop vs. mobile.
• Funnel analysis. Identify exactly where users drop off in your core flow.
• Retention cohorts. See which user cohorts stick around and which ones ghost.
• Custom event tracking. Build queries around the specific events that matter to your business.

The brutal truth: most founders never set up Insights properly. They install PostHog, get distracted, and never actually use it. Then they make product decisions based on guesses instead of data.

Don't be that founder. The templates in this guide take 15 minutes each to set up and will answer the questions that matter.

Step 2: Set Up Your Core Events

Before you build any Insights, you need to define what events matter. An event is anything a user does in your product—a click, a page view, a form submission, a purchase.

PostHog captures page views and clicks automatically. But you need to manually track custom events for anything specific to your business.

Here's the minimal event stack every solo founder should track:

1. Signup. When a user creates an account.

posthog.capture('signup', {
  'source': 'organic',
  'plan': 'free'
})

2. Onboarding completed. When a user finishes your setup flow.

posthog.capture('onboarding_completed', {
  'time_to_complete_seconds': 240
})

3. Core feature used. When a user takes the action that justifies your product.

posthog.capture('feature_used', {
  'feature_name': 'export_data',
  'success': true
})

4. Payment. When a user upgrades or pays.

posthog.capture('payment_completed', {
  'amount': 9900,
  'plan': 'pro'
})

5. Churn signal. When a user does something that indicates they're leaving (unsubscribe, delete account, long inactivity).

posthog.capture('account_deleted', {
  'reason': 'too_expensive'
})

Don't overthink this. Start with these five. You can add more later. The goal is to have enough data to answer: "Where do users drop off, and why?"

Once your events are live, wait 24 hours for data to accumulate. Then move to Step 3.

Step 3: Clone Template 1 — The Signup-to-Onboarding Funnel

This is the most important funnel for early-stage products. It answers: "How many users who sign up actually complete onboarding?"

Here's how to build it in PostHog Insights:

1. Go to Insights in the left sidebar.
2. Click New Insight.
3. Select Funnel.
4. Add your first step: Event equals 'signup'.
5. Add your second step: Event equals 'onboarding_completed'.
6. Add a third step (optional): Event equals 'core_feature_used' (or whatever your primary action is).
7. Click Save.

Now you'll see a visualization showing what percentage of users make it through each step.

If your funnel looks like this:

• 100 signups
• 60 complete onboarding (60% conversion)
• 25 use core feature (25% of signups)

You now know where to focus. If only 60% complete onboarding, your onboarding is broken. Ship a fix there before anything else.

This single Insight will tell you more than a week of guessing.

Pro tip: Add a breakdown by traffic source. Click Breakdown and select utm_source. Now you'll see if users from organic traffic have different onboarding completion rates than users from paid ads. This matters for SEO founders optimizing for organic visibility.

Step 4: Clone Template 2 — The Retention Cohort

Retention tells you if users are actually getting value. If they sign up but never come back, your product isn't solving their problem.

Here's the template:

1. Go to Insights and click New Insight.
2. Select Retention.
3. Set Returning user cohort to Event equals 'signup' (these are your cohorts).
4. Set Returning user action to Any event (or pick a specific action like 'core_feature_used').
5. Choose your retention window: Weekly or Monthly.
6. Click Save.

Now you'll see a cohort table. Each row is a cohort of users who signed up in a specific week. Each column shows what percentage came back in week 1, week 2, week 3, etc.

If your Day 7 retention is below 20%, users aren't finding value. If it's above 40%, you're doing something right.

This tells you:

• Which cohorts stick around (maybe organic traffic has better retention than paid).
• When users churn (most churn happens in week 1, some products see a second drop in week 3).
• Whether your product changes actually improve retention (run this monthly and compare).

Step 5: Clone Template 3 — The Feature Adoption Funnel

You have a feature you think is critical. But are users actually using it?

This template shows the path from signup to feature adoption:

1. Go to Insights and click New Insight.
2. Select Funnel.
3. Step 1: Event equals 'signup'.
4. Step 2: Event equals 'feature_viewed' (the user saw the feature).
5. Step 3: Event equals 'feature_used' (the user actually tried it).
6. Step 4: Event equals 'feature_used' AND Property 'success' equals true (the user completed it successfully).
7. Click Save.

Now you can see the drop-off at each stage. Are users not seeing the feature? Are they seeing it but not trying it? Are they trying it but failing?

Each answer points to a different fix:

• Not seeing it → visibility problem (redesign UI, add onboarding tutorial).
• Seeing but not trying → motivation problem (clearer copy, better CTA).
• Trying but failing → usability problem (simplify the flow, reduce friction).

This is how you debug product adoption without guessing.

Step 6: Clone Template 4 — The Cohort Comparison

Some users convert. Some don't. What's different about them?

This template compares behavior between two user segments:

1. Go to Insights and click New Insight.
2. Select Trends.
3. Choose your metric: Event equals 'core_feature_used' (or any event that matters).
4. Click Breakdown and select a property: plan (free vs. paid), traffic_source (organic vs. paid), device (mobile vs. desktop), or country.
5. Click Save.

Now you see the metric broken down by your chosen property. Maybe free users use the core feature 2x more than paid users (they're exploring). Maybe organic traffic converts 30% better than paid (quality difference). Maybe mobile users have 50% lower adoption (UX problem).

Each insight points to a specific action.

Step 7: Clone Template 5 — The User Journey Path

Sometimes you need to see the actual sequence of events, not just aggregates.

This template shows you the exact paths users take:

1. Go to Insights and click New Insight.
2. Select User Paths.
3. Set Starting point to Event equals 'signup'.
4. Set Ending point to Event equals 'payment_completed' (or any conversion event).
5. Click Save.

Now you see a Sankey diagram showing all the paths users take from signup to payment. You'll immediately see:

• Which events most users hit before converting (those are important).
• Which events are dead ends (users hit them and never convert).
• How many different paths lead to conversion (if there's one clear path, your product is clear; if there are 20 paths, it's confusing).

This is invaluable for understanding your actual user journey vs. what you think the journey is.

Step 8: Clone Template 6 — The Churn Analysis

Users are leaving. Why?

This template identifies users who churned and what they did (or didn't do) before leaving:

1. Go to Insights and click New Insight.
2. Select Funnel.
3. Step 1: Event equals 'signup'.
4. Step 2: Event equals 'core_feature_used' (users who found value).
5. Step 3: Event equals 'core_feature_used' AND Days since last event > 30 (users who used it but then ghosted).
6. Click Save.

This shows you the "dormant user" funnel. Users who started, engaged, then disappeared. Now ask: What's different about these users? Did they hit a paywall? Did they run out of use cases? Did they get stuck on a specific feature?

Add a breakdown by traffic_source to see if organic users churn differently than paid users. Add a breakdown by plan to see if free users churn faster than paid users.

Once you know why users churn, you can ship a fix.

Step 9: Set Up Alerts for Key Metrics

You don't want to check Insights manually every day. Set up alerts so PostHog tells you when something breaks.

1. In any Insight, click the bell icon (Alerts).
2. Set a threshold: "Alert me if signup completion drops below 50%" or "Alert me if retention week 1 drops below 30%."
3. Choose how to be notified: email, Slack, or webhook.
4. Click Save.

Now if your funnel breaks, you'll know immediately. This is critical for catching product regressions before they cascade.

For solo founders, set alerts on:

• Signup completion rate (if it drops 20%, something broke).
• Day 1 retention (if it drops below your baseline, users aren't finding value).
• Core feature adoption (if it drops, your feature might be broken or hidden).
• Payment completion (if it drops, your billing is broken).

Step 10: Connect PostHog to Your SEO Tracking

If you're using Seoable for AI-generated content and keyword roadmaps, you want to know: Does organic traffic convert better than other sources?

PostHog tracks traffic source automatically if you're using UTM parameters. Make sure your organic traffic is tagged correctly:

• Organic search: utm_source=google&utm_medium=organic
• Direct: utm_source=direct
• Paid ads: utm_source=google&utm_medium=cpc

Once tagged, create a Cohort Comparison Insight (Template 4) and break down by utm_source. You'll see:

• Conversion rate by source
• Feature adoption by source
• Retention by source

Organic traffic often has higher quality (they're searching for your exact problem). If your organic users convert 2x better than paid users, double down on SEO. If you're following the 100-day SEO roadmap for founders, you can measure the impact of each content piece by tracking which landing pages drive the highest-converting traffic.

Step 11: Build a Repeatable Weekly Review

Insights are only useful if you actually look at them. Set up a 15-minute weekly review:

Monday morning, 9 AM:

1. Open Signup-to-Onboarding Funnel (Template 1). Did completion rate stay above your baseline? If not, why?
2. Open Retention Cohort (Template 2). Did this week's cohort start strong? Any concerning drops in day 1 retention?
3. Open Feature Adoption (Template 3). Did adoption increase after your last product change?
4. Check alerts. Did any alerts fire? If yes, investigate.

That's it. 15 minutes. You now know if your product is healthy.

If you see a problem, ship a fix. If you see something working, double down. This is the difference between data-driven founders and founders who guess.

For a deeper dive on metrics that actually matter, read SEO reporting basics: the 5 metrics that tell you if it's working. The same principle applies to product metrics—focus on what matters, ignore vanity metrics.

Step 12: Advanced — Custom Properties and Segments

Once you're comfortable with the basics, level up with custom properties.

PostHog lets you attach properties to events. Instead of just tracking "signup," you can track:

posthog.capture('signup', {
  'source': 'organic',
  'utm_source': 'google',
  'utm_medium': 'organic',
  'utm_campaign': 'seo_blog',
  'plan_viewed': 'pro',
  'signup_time_seconds': 45
})

Now you can segment by any of these properties. You can see: "Users who viewed the Pro plan before signing up have 3x higher conversion rate." Or: "Users from organic search who come from the 'seo_blog' campaign have 60% week 1 retention."

This is how you optimize your funnel at scale. You're not guessing. You're measuring.

For solo founders using the busy founder's AI stack for SEO, you can even track which AI-generated blog post drove the signup, then measure its conversion rate and retention.

Step 13: Export Data and Build Your Own Dashboard

PostHog Insights are powerful, but sometimes you need to share data with your team (if you have one) or build a custom dashboard.

Every Insight can be exported:

1. Click the three dots (menu) in the top right of any Insight.
2. Select Export.
3. Choose format: CSV, JSON, or embed.

You can then import this into Looker Studio, Metabase, or any BI tool. For a quick setup, read our guide on connecting Google Search Console to Looker Studio. The same principles apply to PostHog data.

For most solo founders, you don't need a custom dashboard. PostHog Insights are enough. But if you want to combine PostHog data with Google Analytics data, SEO data, and revenue data in one place, export to Looker Studio.

Common Mistakes to Avoid

Mistake 1: Tracking too many events. You don't need 50 events. You need 5-10 that matter. Start small, add as you grow.

Mistake 2: Not setting user properties. Events without context are useless. Always tag events with user properties (plan, source, cohort, etc.). This is what lets you segment and understand why behavior changes.

Mistake 3: Ignoring low-traffic data. If you have 10 signups, your funnel metrics are noise. Wait until you have at least 100 signups before drawing conclusions.

Mistake 4: Building Insights but not acting on them. This is the killer. Founders set up PostHog, build beautiful Insights, then never look at them again. Set a calendar reminder. Review weekly. Act on what you learn.

Mistake 5: Comparing across different time periods without context. If you ran a launch campaign last week, your metrics will be different. Track context. Tag events with campaign names. Then compare apples to apples.

Key Takeaways

PostHog Insights is the fastest way for solo founders to understand user behavior without hiring analysts or wasting time in dashboards.

Here's what you now know how to do:

1. Set up core events that matter to your business (signup, onboarding, feature use, payment, churn).
2. Clone six templates that answer the questions that matter: funnels, retention, adoption, comparisons, journeys, and churn.
3. Set up alerts so you know immediately when something breaks.
4. Run a 15-minute weekly review to stay on top of your product health.
5. Connect to your SEO strategy by tagging organic traffic and measuring its conversion rate.
6. Export and share data when you need to.

The founders who win in 2026 are the ones who make fast, data-driven decisions. PostHog Insights gives you the data. Now you need to act on it.

Start with the signup-to-onboarding funnel this week. See what it tells you. Then ship a fix. That's the difference between founders who ship and founders who stay invisible.

For a complete playbook on building organic visibility alongside product analytics, check out the quarterly SEO review: a founder's repeatable process. The same discipline you apply to product metrics applies to SEO metrics.

If you need to accelerate your SEO while you're optimizing product metrics, Seoable delivers a domain audit, brand positioning, keyword roadmap, and 100 AI-generated blog posts in under 60 seconds for a one-time $99 fee. Many solo founders use Seoable to get the organic traffic flowing while they use PostHog Insights to optimize the funnel. Ship both, and you've got a moat.

Now go set up your first Insight. You'll have answers in 15 minutes.