Monetisation
2024
Why customers didn't purchase the Suite, and what we shipped instead
Sage wanted to sell a new small business proposition with Accounting, Payroll and HR as one Suite while keeping the pricing structure same. I led the e-commerce flow and a 3-round research and A/B testing programme that put the proposition in front of live traffic.
Problem area
A commercial test with no pricing change
Sage sell Accounting, Payroll and HR software to UK and Ireland small businesses. Each product had its own buying journey, its own page, its own plans. The business decided to move to a single promise,โOne solution for all your business needsโ.
The commercial architecture underneath was not up for discussion. Same tiers, same prices, same plan structure continued as they were. So the entire proposition was relying on if the design alone could change what people bought.
Design goals
Suite to run a business rather than a stack of products
We created a hypothesis to test:
Small businesses are looking for a solution to run their businesses, not just a software. If the journey leads with the solution and lets people configure what they need, they'll see the value and buy with confidence.
A personalised solution
Make it feel like configuring depending on needs instead of adding on extras.
How we tested
Three rounds of experimentation to understand comprehension using moderated research and live A/B test to see impact on metrics.
Design decision 01
Reframe a product page as a business plan
The default page sold Accounting plans and showed Payroll as an add-on. I reframed it as one Small Business plan and added a step-flow, so choosing Accounting reads as step 1 of a configuration, not the whole purchase.
1
Suite: one plan for the business
2
Step flow to show configuration
3
CTA label: choose and "add"
What we learned
Research proved the suites proposition landed well
People read the page as one solution
Behaviour said otherwise
Single-product buyers wanted a clear path out. More on this in Decision 03.
Design decision 02
Move the second product to step two
In the old journey, Payroll arrived as an add-on modal just before checkout. I moved it into the flow as step 2, carrying the Accounting choice forward, and made skipping it as visible as choosing it.

1
Step flow and summary: Accounting tier is selected and editable.
What we learned
Opting out was easier
Users saw and skipped the step when needed
Step flow wasn't seen
Only 20% noticed it, so it was removed in the next round
Design decision 03
Show the whole plan on one page
Previous round showed users treated Accounting as the whole product. Once they'd chosen a plan, they felt flow was done, and Payroll in step 2 came as a surprise. So I put all choices including the standalone product cards in a section before configuration.
1
Suite-first with standalone products
Suite is recommended, but Accounting and Payroll only are also available for users who came for one product.
3
All plans on one page
Accounting and Payroll sit together, and checkboxes make adding or skipping a product visually easy.
4
Plan total
Pricing and savings update with every choice, so the cost is visible before checkout.
What we learned
What it showed
Giving users the choice wasn't enough. Even with a single-product path on the first screen, single-product sales still dropped.
Retrospective
What we learned after losing the bet
Before
No hierarchy: features and price compete Opting out was hard to find Complex plan definitions and interface
After
Value-first simplified content Radio buttons to choose Pricing visible at a glance







