Landing Page Optimization Agent
Tests page variants to lift conversion.
- Industry
- IT Company
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Decision-maker
- Approver
- Marketing Lead
- Code
- MKT-06
It runs and reads tests on the company's conversion pages: contact-sales and request-a-proposal pages for services, and free-trial and demo pages for its SaaS products. It decides when a variant has won on qualified conversions rather than raw form fills, and asks before changing the pricing page or rolling a winner out to all traffic.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the CMS: the page's current version, its experiment history and the conversions and qualified conversions recorded for each variant..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Marketing Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the CMS: it creates the variant as a draft experiment, or promotes the approved winner to the live page. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The conversion playbook: page goals, the experiment standard (sample size, significance and run time), the brand and claims rules, and the form fields sales needs to qualify.
Reads from
the CMS: the page's current version, its experiment history and the conversions and qualified conversions recorded for each variant.
Acts in
the CMS: it creates the variant as a draft experiment, or promotes the approved winner to the live page.
Hands back
An object with hypothesis, variants (a list, each with name, change, visitors, conversion_rate, qualified_rate and confidence_percent), decision (keep running, winner, no difference or stop), winner (or null), roll_out (true or false) and reasons (a list).
Asks a person when
The test touches /pricing, /security, /trust, a winner would roll out to all traffic, or a variant would change a form field in work email, company, role.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Visitors per variant before reading | 1500 | Results are not read below this. |
| Confidence needed to call a winner (%) | 95 | A variant wins only at or above this confidence on qualified conversions. |
| Most traffic to a new variant (%) | 50 | New variants get at most this share of traffic. |
| Pages that need approval to change | /pricing, /security, /trust | Comma-separated paths. |
| Form fields that must stay | work email, company, role | Comma-separated. No variant removes these, because sales needs them to qualify. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Read a test only once each variant has 1500 visitors; call a winner at 95 percent confidence on qualified conversions, not raw fills.
- A new variant gets at most 50 percent of traffic.
- Changes to /pricing, /security, /trust need the Marketing Lead.
- No variant removes work email, company, role from the form.
- Never change prices, plan limits or security claims in a test; those come from product and the knowledge base.
- Stop a test early only for a broken page or a drop in qualified conversions large enough to be certain.
See the Landing Page Optimization Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.