What we'd rebuild in Typeform's funnel

Same discipline as every ZIAVE teardown: the public funnel, mapped onto the eight stages of the Growth System, with the honest constraint stated up front. We can only see what any visitor can see: no conversion rates, no traffic mix, no in-app flows. The bottleneck ranking below is modeled leverage, not measured impact, and inside data could reorder it.

The template library is a genuine SEO machine: ungated browsing, clean structure, twenty-plus categories by role and goal. Social proof is specific, not decorative: named case studies with numbers, "48 million responses collected monthly". Pricing is transparent: every limit and the 30% annual discount are visible without a sales call. And the product is demonstrably alive: blog current to July 2026, an ISO/IEC 42001 certification announced in June 2026, a Winter 2026 feature drop. The leaks below are architecture choices, not neglect.

Typeform's value metric is responses: the thing customers want more of. The meter starts punishing early. The free plan allows 10 responses per month across all forms (verified in the help center on July 12, 2026). The $39 Basic plan allows 100 responses: $0.39 per response. The next step is a tenfold usage jump at double the price. Then Growth Flow, the flagship new product, costs $379 per month while its comparison row shows the same headline limits as the $129 Business plan; the difference lives in automations the pricing table doesn't express. On top of that sits a second meter: a "Contacts & Automations" add-on billed in "actions", so a buyer has to predict two independent counters before choosing a plan. And the commitment models are mixed: buy-now CTAs on core plans, a card-gated 14-day trial on the one product that most needs adoption proof.

This ranks first because it sits at the bottom of the funnel where every upstream improvement compounds, and every fix is a page-level change.

The hero says "Your favorite forms. Now with AI automation." The sub-headline sells three jobs in one breath: forms, in-depth research, and "the entire customer lifecycle". Two sections flagged NEW push Growth Flow and Research Flow while the primary CTA still says "Get started", it's free. A visitor is being asked to believe in a $379 growth platform by a page whose identity is still the free form builder. The category migration and the free tool compete for the same click.

The rebuild: one job per surface. The homepage keeps the thing they're famous for; Growth Flow and Research Flow get dedicated landers with their own proof and their own CTA logic, and traffic routes by intent. This is the same architecture leak we found at Teachable, wearing a different logo: the highest-traffic decision surface serving three audiences at once.

The template hub and the blog are excellent top-of-funnel assets, and on the surfaces we fetched they run almost entirely without capture. The blog index has no visible newsletter signup; some individual posts carry one, some don't. Template browsing jumps straight to signup with no intermediate step for the visitor who isn't ready. A company whose product is forms deploys almost none of them between "reading" and "registering". Whatever that content engine wins, very little of it becomes an owned audience.

The rebuild: a micro-conversion layer. Persistent capture on the blog index, a "send me this template" step in the library, segment-specific nurture behind both. The CRM and Automation stages of the Growth System doing their job: catching demand that isn't ready yet. (Fairness note: a JS popup our fetcher can't render may exist on some surfaces; the visible architecture still routes cold readers straight to signup.)

Parts of the help center returned 403 to our automated fetcher; the free-plan limit cited above was verified manually in a real browser session on July 12, 2026. We make no claims about signup form fields, in-app upgrade prompts, over-limit behavior, paid ads, or email sequences: none of that is observable from outside. Typeform is not a client and hasn't asked for this; it's our outside-in read, published because it shows how we think. If someone at Typeform spots an error, tell us and we'll correct it in public, per our publication standard.