Outcome template · Landing page conversion

Grow the signup rate on your landing page.

An AI agent ships one change at a time, reads the result in your analytics, and keeps only what moved the signup rate.

macOS · Runs on your ChatGPT Plus sign-in

exampleNorth star

Signup completions as a share of unique landing page visitors

7.2%
signup rate / 7 days · +2.4pts over 6 runs
Measured in
PostHog, GA4, or Mixpanel
Also reads
CTA click rate · form completion rate · bounce rate
Guardrails

Bounce rate must not rise on the page it edited

Page load time must not regress after a change ships

01The loop

Two runs. Two verdicts.

Every run states a hypothesis before it acts, and the real number settles it afterwards. Here are two of them side by side. One held. The other did not, and that is the half that stops the next run spending another month on the wrong thing.

example
Run 01

Social proof

Hypothesis

Adding a specific proof point beside the CTA lifts the signup rate from 4.7% to 6% or better within 7 days, without bounce rate rising.

Action

Added one proof line naming a real number next to the signup button.

Measured
Landing page visitors, 7d
3,0003,120
Signups completed
141206
Bounce rate
58%57%
Signup rate
4.7%6.6%
Verdict
supported
Next

Signup rate cleared the bar and bounce rate held, so trust was the constraint, not clarity. Social proof moves toward proven and stays live for the next test.

Run 02

Hero clarity

Hypothesis

Rewriting the hero headline to name the signup outcome directly lifts the signup rate from 6.6% to 8% or better within 7 days, without CTA click rate falling.

Action

Rewrote the hero headline and the button copy to name the outcome directly.

Measured
Landing page visitors, 7d
3,0003,000
CTA click rate
22.0%31.0%
Form completion rate
30.0%21.6%
Signup rate
6.6%6.7%
Verdict
refuted
Next

Clicks rose but the extra visitors stalled in the form, so the headline was never the constraint. Signup friction moves to the front of the queue next.

02Lever bank

What it can try on your signup page.

A lever is a class of change the agent believes moves the signup rate. These four ship with the template.

Hero clarity

Rewrite the headline and button text so the first few seconds tell a visitor what they get, not which category the product sits in.

Signup friction

Cut the fields, steps, and decisions between landing and a finished signup. Every extra one is somewhere a visitor can quit.

Social proof

Put a specific proof point next to the button: a real number, a named customer, a before and after. Specific beats "trusted by thousands."

Traffic-message match

Build a version of the page whose headline echoes the exact words of the ad that sent the visitor. Wording that does not match is work you are asking them to do, and some will not.

And whatever your data points to next

Four is where the bank starts, not where it stops. As verdicts come in, the agent tests levers your own funnel data suggests and drops the ones that keep missing, so what it tries next is earned by your results, not fixed by a template.

Point it at your signup page.

What you connect

  • Your analytics tool, whichever one already tracks the landing page. The north star and every rate on this page is read from there.
  • The repo or page builder your landing page lives in. The agent edits where you already work and ships on the path you already use.
  • Stripe or an equivalent billing tool, optional. It confirms which signups turn into paying customers, so a rate that rose by cheapening the signup does not count as a win.

When you will see something

This one is bound by traffic, not the calendar. A rate difference means nothing until enough visitors have been through the page, so a busy page can settle a run in days while a quiet one takes weeks on the same test. Big changes clear that bar sooner than small ones.

macOS · Apple silicon and Intel · No credit card