PostHog
One platform for product engineering and analytics
Open one model's full scorecard.
Choose a model to read every category grade. The best grade in each category is marked.
The OS desktop metaphor and the self-driving angle are unique. No competitor page looks like this.
The retro OS system is intentional and consistent, but the window shows a large empty area below the hero copy.
The self-driving headline is not clear alone. You must read three paragraphs to know what PostHog does.
Product engineers are a named buyer. The 500,000+ teams claim and the 20+ tool list show a credible wedge.
The Trash icon, the Demo cartridge, and the joke social proof line give a stranger a reason to share the page.
The 500,000+ teams claim, docs, pricing, and a Talk to a human link build trust. Customer logos are not visible here.
A landing page dressed as an operating system: the joke lands, but the vague headline and the empty window soften the punch.
The OS metaphor works and makes the page memorable, and the joke social proof line shows a confident brand. The headline sells self-driving mode, but the filed pitch sells one platform, and a new visitor must read the full body text to connect the two. Fill the empty right half of the hero window with a live product view, and add one plain line that says what PostHog is.
The desktop workspace and automatic bug-to-pull-request promise make a distinct angle.
The icons, soft window, type, and colors use one clear system, but the panel has too much empty space.
The hero explains diagnosis, bug fixes, and pull requests, but the filed pitch is broad and less useful.
The page targets product teams with costly bug work, and the 500,000+ team claim supports demand.
The self-driving product phrase and desktop page are easy to remember, but no sharing loop is shown.
The page shows 500,000+ teams, pricing, docs, and human contact, but it gives no customer names or results.
PostHog makes automatic product repair memorable, but its largest claim needs proof inside the hero.
The desktop system and bug-to-pull-request message make a complex platform feel distinct. The 500,000+ claim cannot support the broad repair promise by itself. Add one named customer case with a real issue, generated pull request, and measured result below the hero.
The desktop interface design is highly unusual for business software.
The retro desktop theme operates as a deliberate and consistent visual system.
The text clearly states the product functions, but the layout requires brief adjustment.
Automated bug resolution solves a well-known problem for software engineers.
Developers will share the unconventional design and ambitious product claims.
The user count shows massive adoption, but the automated code changes require proof.
PostHog uses a memorable desktop interface to present an ambitious vision of automated product engineering.
The desktop interface is distinct and removes the brand from generic competitors. The main text makes a strong claim, but automatic code changes sound difficult to believe without evidence. A short video in the center must show how this automation works.
The grass desktop and the window give a product-OS angle that most analytics pages do not use.
The page uses one desktop system with icons and a window, but the window has too much empty space.
The headline states the self-driving claim, but the full product set is not clear at first look.
The text is for product teams that need bug fixes and pull requests, and it uses data PostHog already has.
A person can share the self-driving promise and the desktop website that looks like an operating system.
The page states 500,000+ teams and a free start, but it shows no named customers or humans.
The page shows a desktop and an auto-fix claim, but the empty window hides the product and the proof.
The desktop layout and the self-driving headline are easy to see. The founder pitch names one platform for product engineering and analytics, but the empty window does not show that platform, a demo, or named customers. Put one real fix or pull request in the window so users can see the work.
What works and what to improve next.
What the jury liked
- A brand system so distinct that the page itself demonstrates the company culture.
- A clear bug-to-pull-request story gives the broad platform a sharp focus.
- The retro desktop interface creates a highly memorable brand experience.
- The self-driving claim uses customer data that PostHog already has.
What to improve next
- The self-driving headline can confuse buyers who search for an analytics platform.
- The automatic repair claim can reduce trust when the page gives no named result.
- The claim of unprompted automatic bug fixing can cause skepticism in technical buyers.
- Users can think this is only an AI agent and miss the full platform.
What each model saw in every category.
Choose a category to compare all model scores and reasoning side by side.
The OS desktop metaphor and the self-driving angle are unique. No competitor page looks like this.
The desktop workspace and automatic bug-to-pull-request promise make a distinct angle.
The desktop interface design is highly unusual for business software.
The grass desktop and the window give a product-OS angle that most analytics pages do not use.
The retro OS system is intentional and consistent, but the window shows a large empty area below the hero copy.
The icons, soft window, type, and colors use one clear system, but the panel has too much empty space.
The retro desktop theme operates as a deliberate and consistent visual system.
The page uses one desktop system with icons and a window, but the window has too much empty space.
The self-driving headline is not clear alone. You must read three paragraphs to know what PostHog does.
The hero explains diagnosis, bug fixes, and pull requests, but the filed pitch is broad and less useful.
The text clearly states the product functions, but the layout requires brief adjustment.
The headline states the self-driving claim, but the full product set is not clear at first look.
Product engineers are a named buyer. The 500,000+ teams claim and the 20+ tool list show a credible wedge.
The page targets product teams with costly bug work, and the 500,000+ team claim supports demand.
Automated bug resolution solves a well-known problem for software engineers.
The text is for product teams that need bug fixes and pull requests, and it uses data PostHog already has.
The Trash icon, the Demo cartridge, and the joke social proof line give a stranger a reason to share the page.
The self-driving product phrase and desktop page are easy to remember, but no sharing loop is shown.
Developers will share the unconventional design and ambitious product claims.
A person can share the self-driving promise and the desktop website that looks like an operating system.
The 500,000+ teams claim, docs, pricing, and a Talk to a human link build trust. Customer logos are not visible here.
The page shows 500,000+ teams, pricing, docs, and human contact, but it gives no customer names or results.
The user count shows massive adoption, but the automated code changes require proof.
The page states 500,000+ teams and a free start, but it shows no named customers or humans.
How every model's score evolved.
How PostHog ranks.
Want another look? Owners can request a $9 re-review from their private Chambers link. Models used: claude-fable-5 · gpt-5.6-sol · gemini-3.1-pro-preview · grok-4.6.