Marketing & Growth Systems
Conversion optimization: find the reason before you change the page
Evidence, and what it can't tell you
Three hypotheses from one page
Price range
- Observation
- 68% of visitors leave before the price range
- Change
- show the range in the first screen
- Expect
- more quote requests per visitor
- Measured by
- requests ÷ visitors, 4 weeks, split 50/50
- Guardrail
- average job value doesn't fall
Same day
- Observation
- 4 in 10 calls ask whether we can come the same day
- Change
- answer it under the heading: “same day if booked by 2 pm”
- Expect
- more requests, fewer calls just to ask
- Measured by
- requests and calls per visitor
- Guardrail
- same-day bookings the schedule can keep
Photo step
- Observation
- mobile visitors abandon the form at the photo upload
- Change
- ask for the photo after the request is sent
- Expect
- more mobile requests
- Measured by
- mobile finishes ÷ starts
- Guardrail
- quotes still have enough to price
- Status
- already being tested on the quote form
What we won't build
01
False urgency
“Only 2 slots left!”
No countdowns or scarcity that isn't true. If slots really are short, say so plainly.
02
Hidden costs
Fees at the last step
The price range shown is the price range. Anything extra appears beside it.
03
Pre-ticked boxes
Consent by default
Permission to send messages is asked for, never assumed.
04
Guilt buttons
“No, I like cold showers”
Saying no is a plain choice in plain words.
05
Hard exits
Easy in, impossible out
Unsubscribing or cancelling takes no more steps than signing up.
What conversion optimization hands off
In
Out
Worth doing when visits don't become requests
Good fit
- Pages get visits but few requests.
- You can see form steps and record calls.
- Enough people visit to test a change in weeks, not years.
Not the right fit
- A page gets a few dozen visits a month. Fix the obvious and move on.
- Nothing is measured yet. Start with instrumentation.
Questions about conversion optimization
Isn't this just A/B testing?
Testing is the last step. Most of the work is finding a good reason to change something, so the test is worth running.
How much traffic do we need?
Enough that a test finishes in weeks. With less, fix clear problems directly and save tests for the big questions.
Will you redesign the page?
Only if the evidence says the structure is the problem. Usually a few specific changes come first.
What if the test loses?
That's a result. The hypothesis was wrong, it's written down, and nobody suggests the same change next year.