---
title: 7 A/B tests for SaaS sign-up pages, with the prompt for each (PDF) · Duelpilot
url: https://duelpilot.com/get/saas-tests
updated: 2026-10-26
description: Seven A/B test setups for SaaS homepages, landing pages, sign-up and pricing pages, each with A vs B, the goal and the guardrail, whether autopilot may launch it, and a copy-paste prompt for your AI agent; plus the tests that belong in your code.
---

> Site search for AI agents: https://duelpilot.com/api/search?q=YOUR+QUESTION
> (returns Markdown with source links). All pages: https://duelpilot.com/llms.txt
> MCP server (Streamable HTTP): https://duelpilot.com/agent/mcp

# 7 A/B tests for SaaS sign-up pages. With the prompt for each.

Seven setups for the pages that turn SaaS visitors into sign-ups: the sign-up button, demo or trial, the headline, real proof, what happens after sign-up, the page around the form and the pricing page. All seven change only what visitors see, so your agent can prepare them in the browser, with the prompt for each.

Get the 7 tests

This creates your Duelpilot account. No payment needed for the 7 tests. Every plan is €0 until you launch your first test.

We email you a 6-digit code; no password. You get a few short setup emails, and every one has a one-click unsubscribe. [Privacy](/privacy)

![The first page of 7 A/B tests for SaaS sign-up pages: the cover and what a browser-side test can change](/site/giveaways/saas-tests-cover.webp)

Page 1 of 5.

What's inside

## What a browser-side test can change, seven setups with a prompt each, and what belongs in your code.

1. 1
### What you can test in the browser, and what not
Copy, styling, layout and images: yes. Trial length, form fields, sign-up flow and prices: code tests.
2. Test 1
### The sign-up button: say what happens next
"Start my trial" or "Create my workspace" instead of "Get started".
3. Test 2
### Demo or trial: which button leads
Both stay; one is primary. Decide on sign-ups and booked demos together.
4. Test 3
### The headline: who it is for and what they get
The outcome in your customers' words, and nothing you can't back up.
5. Test 4
### Real proof next to the sign-up button
Logos, ratings and quotes you already have, moved to where people decide.
6. Test 5
### Show the first steps after sign-up
A short "what happens next" block with your real onboarding steps.
7. Test 6
### The sign-up page: the words around the form
Heading, button and the promise under it; the fields stay.
8. Test 7
### The pricing page: which plan stands out
Highlight and describe plans differently; prices never change. A person approves it.
9. 9
### What belongs in your code
Trial length, fewer fields, Google sign-in, a new onboarding flow: code tests on the Code plan, always approved by a person.

Why an account

## Read it, then try it on your own site.

Every prompt in it runs against Duelpilot. With your account you can connect your AI agent right after reading and let it check the first test against your own sign-up numbers. Autopilot is on Pro and up.

There is no free plan, but there is nothing to pay for the 7 tests, and every plan is €0 until you launch your first test: setting up is free, and your plan (from €9/month) starts when you launch. No launch within 30 days? We cancel it and you pay nothing.

[Get the 7 tests](#get)

## More guides

* [The Agentic CRO Playbook How to run A/B tests on autopilot with your own AI agent, inside guardrails you set. PDF · 11 pages ](/playbook)
* [10 A/B tests worth running first With the prompt for each: ten setups for webshops and SaaS sites that your own AI agent can prepare. PDF · 8 pages ](/get/10-tests)
* [The autopilot guardrails checklist What to allow, what to forbid, and the guardrails checked before every automatic launch, with a prompt to prepare them. PDF · 4 pages ](/get/autopilot-guardrails)
* [Your first A/B test with Claude or ChatGPT in 10 minutes The setup, step by step: one prompt, one script, one first test you approve. PDF · 3 pages ](/get/first-10-minutes)
* [How to read A/B test results honestly Not conclusive is an answer: peeking, sample size, guardrails, and why many tests don't win. PDF · 3 pages ](/get/read-results)