Features instead of outcome
The home page explains the product instead of naming the visitor’s problem.
SAFor SaaS
A variation that lowers the barrier brings more registrations and worse users. So in SaaS you measure further down the funnel, and protect the rest with guardrails.
The pattern
The home page explains the product instead of naming the visitor’s problem.
“Price on request” filters out not just bad leads, but good ones too.
Counting only registrations optimises for dead accounts.
Concretely
A concrete outcome instead of a category. Goal: registration started.
Starting price versus request. Goal: qualified enquiry, guardrail: total enquiries.
Four fields instead of nine. Goal: completed registration.
Two routes as a redirect test. Goal: whatever actually counts downstream.
Measuring
Take the latest step you still see often enough within the test window, usually the completed registration or the first real step of use. The bare click rate on the button belongs alongside as an additional goal, not in first place.
Sample size and runtimeMatching platforms
Other industries
Make your next change an informed one
One question is a good place to start.