Solo founders do not lack data - they lack time to interpret it. GA4 and Search Console hold everything you need to know whether a launch worked, which landing page drives signups, and when tracking broke after a refactor. The trap is spending Friday night in Explorations instead of shipping. This guide is the minimum viable analytics stack for one-person companies: four metrics, one weekly habit, and tools that answer ad-hoc questions without SQL.
The four metrics that matter when you are the whole team
Ignore vanity dashboards. Watch organic sessions to pages that can convert (homepage, pricing, signup), your primary conversion event count week over week, Search Console clicks on queries you are actively targeting, and tracking health on form_submit or signup_completed. If those four are stable or improving, you have enough signal to decide what to build or write next. Everything else is optional until you hire. Adding more metrics does not make decisions easier - it makes them harder by adding noise that needs interpretation.
Setting up GA4 correctly as a solo founder
A default GA4 setup measures pageviews but misses what actually matters for a product. The first thing to fix is marking your conversion events as key events. Go to Admin, then Events, find your signup or trial_started event, and toggle it as a key event. If the event does not exist yet, you need to fire it from your application code (using gtag or the GA4 Measurement Protocol) or via a Google Tag Manager trigger. Without a marked key event, GA4 has no conversion column to track and you cannot answer the most important question: which sessions turned into users?
Second, extend data retention. GA4 defaults to 2 months of data retention for exploration reports. Go to Admin, Data Settings, Data Retention, and change it to 14 months. This is free and takes 30 seconds. Without it, you lose the ability to compare this quarter to the same quarter last year once you are beyond the 60-day window. Third, exclude your own traffic. Add your IP address or VPN range under Admin, Data Streams, Configure Tag Settings, Define Internal Traffic. Otherwise your own testing sessions inflate your metrics and make A/B test reads unreliable.
Ask questions instead of building reports
Founders think in questions: "Did Product Hunt traffic stick?" "Which blog post drove trials last month?" "Did rankings drop after the redesign?" You do not need a permanent Looker Studio tab for each one. Connect GA4 and Search Console to a conversational analytics tool - see /pricing - and type the question when it comes up. Save the twenty minutes you would have spent clicking through GA4 menus for questions that come up once and do not need a reusable report.
Catch broken tracking before you optimize the wrong page
A solo founder who A/B tests headlines while form_submit is broken wastes weeks on a test that produces no real signal. After every deploy, check conversions in GA4 Realtime by submitting a real test form and verifying the event appears within a few seconds. Or run /blog/how-to-audit-conversion-tracking for a more systematic check. ClimbPast /docs/mcp automates that scan so you are not learning about a tagging failure from a zero on the dashboard three weeks after it broke.
Reading Search Console as a solo founder
Search Console tells you what searches are surfacing your site - before anyone clicks. Open the Performance report and set the date range to the last 28 days. Sort by clicks descending to find your actual traffic drivers. Then sort by impressions descending to find pages Google is showing but no one is clicking - these are your title tag optimization opportunities. A page ranking at position 8 with 500 impressions and zero clicks has a title problem worth a 15-minute fix. A page ranking at position 3 with steady clicks is working; leave it alone and focus your energy on the underperformers.
Investor updates without screenshot archaeology
Weekly automated summaries from GA4 and Search Console give you organic trend lines and conversion counts you can forward to angels or advisors with one sentence of context. That is enough for check-in emails until you have a finance team asking for cohort models. The goal is to make analytics a communication asset, not a reporting burden. If you spend more than 30 minutes per week on analytics as a solo founder, something is wrong - either your setup is not automated enough, or you are looking at metrics that do not change what you build or write this week.