// teardown · supabase.com
Automated conversion teardown · visit supabase.com
Sells Postgres development platform with auth, APIs, functions, realtime, storage, vectors
// scorecard
"Build in a weekend, scale to millions" + Postgres platform + feature list answers what/for whom/outcome clearly.
Two competing CTAs at top: "Start your project" and "Request a demo" — no clear primary; labels lack specificity.
Heavy on Twitter testimonials (real names/handles) but no company logos, metrics, or outcome numbers; proof is sentiment-heavy, not outcome-heavy.
"Start your project" likely leads to signup; no visible form fields in static HTML; low friction path assumed.
Clean, organized feature sections with clear hierarchy; no obvious AI-slop; distinctive Supabase branding and layout.
Benefit-led headers ("Build multiplayer experiences", "Easy as a spreadsheet"); mostly plain language; some buzzwords ("best of breed").
// 8 leaks + fixes
"Start your project" and "Request a demo" appear at the same prominence in the hero. For self-serve SaaS, this creates decision friction — a visitor unsure whether to try free or talk to sales will often do neither.
Make "Start your project" the primary CTA (larger, bolder, higher contrast); move "Request a demo" to a secondary position or reserve it for enterprise-intent signals later on the page.
Twitter quotes like "I love everything about Supabase" and "It's fun" are authentic but don't prove business impact. No mention of speed gains, cost savings, or scale achieved — the exact outcomes your hero promises.
Weave in 2–3 outcome-specific testimonials: e.g., "Scaled to 1M users in 7 months" (you have this buried in a story title — promote it) or "Reduced auth setup time from 3 weeks to 2 hours."
"Trusted by fast-growing companies worldwide" is a claim with zero visual proof. No logos of known companies (Chatbase, Maergo, etc.) appear in the hero or early sections to anchor credibility.
Add a 3–4 logo row below the hero or in the "Customer Stories" section header: Chatbase, Maergo, and 2–3 other recognizable names. Logos are a trust multiplier for developer tools.
No indication of what happens after clicking — will a sales rep email? Will a calendar open? This ambiguity creates friction for enterprise buyers who expect a clear booking flow.
Rewrite to "Book a demo" or "Schedule a call with sales" to set expectation; ideally link to a Calendly or Chili Piper embed so the action is instant.
"Postgres Database", "Authentication", "Edge Functions" etc. are described but have no associated CTA or link to docs/examples. A developer reading these may want to explore but has no clear next step.
Add a small "Explore" or "View docs" link under each feature, or a unified "Explore all features" CTA after the feature grid to guide curious visitors deeper.
The templates/examples section uses "View all examples" — a weak, generic label that doesn't convey the benefit (e.g., "Kickstart with pre-built templates").
Rewrite CTA to "Browse starter templates" or "Get started with a template" to make the action and outcome clearer.
Nav shows "Pricing" link, but no pricing tiers, free tier details, or cost comparison appear in the static HTML. For self-serve SaaS, transparency on cost is a trust signal and reduces friction.
Ensure pricing section is visible on the live page (may be JS-rendered). If not, add a brief "Free tier + paid plans" callout in the hero or a dedicated pricing section below features.
After 15+ testimonials, the only action is "Join us on Discord" — a secondary engagement, not a conversion. No CTA to sign up or start building after the social proof.
Add a final CTA section after testimonials: "Ready to build?" with a prominent "Start your project" button to recapture intent before the footer.
// more teardowns
Same rubric, ~20 seconds. Full report and an AI-rebuilt version for $2.90.
Audit my page ›
