What you'll understand by the end of this lesson
- Why pre-selected options get chosen far more than identical options left unselected
- How defaults shape plan selection, billing frequency, and consent choices
- Why designing defaults is an ethical act, not just a design decision
- How to audit whether your defaults are working for users or against them
The principle in plain English
When a choice is already made for you, you are far more likely to go with it than to change it.
This is Default Bias — the tendency to accept whatever comes pre-selected, pre-filled, or already active. It isn't laziness. It's a combination of cognitive efficiency (changing takes effort), loss aversion (what if the change is wrong?), and an implicit assumption that the default was chosen for a reason.
Defaults feel neutral. They're not. Every default is a design decision that nudges a large proportion of users toward a specific choice. The question is whether that choice serves the user or the business — and whether users would agree to it if they were asked explicitly.
A simple example
A streaming service shows three plan options: Basic, Standard, and Premium. Standard is pre-selected with a subtle blue highlight.
Users who land on this page are significantly more likely to choose Standard — not because they evaluated all three and concluded it was best for them, but because it was already selected. Changing it requires a decision. The default removes the need to decide.
Now imagine the same page with no pre-selection. Users distribute across plans more evenly, and many choose Basic. The product hasn't changed. The pricing hasn't changed. Only the default has changed. The business revenue changes substantially.
Billing frequency and plan tier defaults
The most commercially significant defaults in SaaS are billing frequency and plan tier.
Annual vs monthly billing
Showing monthly pricing by default and annual as an opt-in is the conservative approach. It removes friction for new users but costs the business annual commitment.
Showing annual pricing by default — with a visible saving vs monthly — increases annual plan take-up significantly. Users who would never have considered annual billing often don't switch away, because switching requires a decision and the annual option is already selected.
Neither default is wrong. But the choice of default has a measurable impact on revenue and churn — which is why it deserves a deliberate decision, not an accidental one.
Plan tier selection
Pre-selecting the middle or recommended tier converts more users to that tier than leaving all options equal. The "Recommended" badge and pre-selection together signal: this is the right choice for most people, and we've already made it for you.
Pre-selecting the most popular or most appropriate plan for a visitor segment is a legitimate and helpful default — if that plan genuinely suits most users. The test of a good default is: if every user saw this default and accepted it, would most of them be well served? If yes, the default is aligned with user interest. If no, it's aligned with revenue at users' expense.
The ethics of defaults
Defaults become ethically problematic when they serve the business by hiding something from the user that they would object to if they understood it clearly.
The most discussed example is consent checkboxes. Pre-ticking a consent checkbox — for marketing emails, data sharing, or terms agreement — exploits Default Bias to capture consent that users would not give if they had to actively choose.
In the UK and EU, pre-ticked consent checkboxes for marketing are illegal under GDPR. But beyond legality, they represent a class of dark pattern: using psychological friction to extract a choice the user wouldn't make freely.
There's a clear line between a helpful default (pre-selecting the plan tier that suits most users) and a manipulative one (pre-ticking a consent box users don't notice). The test is informed choice: does the user understand what they're agreeing to, and would they agree if they were asked clearly? If the answer is no, the default is manipulative — regardless of whether it's technically legal in your jurisdiction.
The CRO audit
Look at every pre-selection, pre-fill, and active state on your key pages and ask:
1. What is your pricing page defaulting to?
Is a plan pre-selected? Is annual or monthly billing the default? Are these defaults deliberate decisions with known impacts, or are they whatever the developer set up first? Measure the difference by testing the opposite.
2. Are your form defaults working for users or against them?
Pre-filled fields can reduce friction (saved addresses, remembered preferences) or create unwanted selections (a pre-ticked "send me weekly emails" box). Review every pre-filled or pre-checked field for whether users would choose it if starting from blank.
3. Are any of your defaults extracting consent?
Pre-ticked checkboxes for marketing opt-in, data sharing, or third-party communications are the most common instance of Default Bias crossing into dark pattern territory. Check every checkout and registration flow.
A SaaS pricing page pre-selects the annual billing option with a visible '2 months free' saving displayed. A product manager argues this is manipulative. A CRO specialist argues it's helpful. Who is more likely to be right, and why?
You've seen how defaults shape choices before users even start. Now — what happens after they start? The more users put into a product, the harder it becomes to leave. Why does investment create loyalty?