A common conversion optimisation problem
Your buttons describe the system, not the payoff
The short answer: say what they get instead. Here is how to recognise this problem in your funnel, why it happens, and how the best consumer apps design it away.
How to recognise it
- CTAs reading Submit, Continue, Next everywhere
- Button copy identical across completely different steps
- Users pausing at buttons, unsure what happens after the tap
Why does button copy matter for conversion?
Every button is a small decision under uncertainty: what happens if I tap this? “Submit” answers with bureaucracy. “Continue” answers with nothing.
System words make the user carry the meaning: they must remember why they are here and what this step wins them. At every carry, a few give up.
A button is the most-read copy in the funnel and usually the least-written: designed once as a component label and never touched by anyone thinking about persuasion.
How do you write CTAs that convert? Name the outcome, not the mechanism
Rewrite every CTA to name the payoff of tapping it: “See my results”. “Start my plan”. “Claim the discount”. The user's outcome, in the user's words, at the user's moment.
Run the test on each one: does it make sense after “Now you can...”? “Now you can submit” fails. “Now you can see your plan” passes.
Match the verb's energy to the step's stakes: playful early, precise at payment. A whimsical button on a card form undermines exactly the confidence it needs.
And surround the decisive buttons with answers to the silent fears: what it costs, whether it can be undone, what happens next. Clarity converts more than cleverness.
The building blocks that solve it
- JTBD Copywriting: The button names the outcome of pressing it.
- Personalisation: “Start my 5k plan” beats “Get started” every time.
Who does this well
Duolingo: Buttons restate the reason you're here: starting, continuing, keeping the streak. Never administering.
Airbnb: “Reserve” says exactly what happens and what you get: the weight of the word matches the weight of the step.
Questions founders ask
How long can button text be?
Two to four words is the working range. But clarity outranks brevity: a five-word button that removes doubt beats a one-word button that creates it.
Should every button be outcome-phrased?
No. Navigation and utility actions should stay conventional: Back means back, Cancel means cancel.
Spend outcome language on the decision points, and let the furniture stay furniture.