How much money a clunky cart and checkout steal every month

Usability and money
An awkward cart, a confusing checkout, or clunky navigation don't just annoy visitors, they pull a specific sum out of your revenue every month. Baymard's researchers figured out how to calculate that sum, and business owners should see it with their own eyes.
Table of contents
You look at a website and see a neat design, a clear menu, nice product photos. The metrics look fine too, traffic is coming in, orders are coming through. And yet every month a sum quietly leaks out of your account that you never see, because it's hidden not in an expense report but in carts that were never paid for.
What the Baymard methodology actually showed
Baymard, a research company that has spent over 200,000 hours testing the usability of online stores across 40-plus industries, noticed a simple management problem. UX specialists see points of friction in the cart, checkout, and navigation, but when it comes time to defend the budget in front of leadership, these observations sound like a designer's opinion rather than a financial argument. So the Baymard team built a calculator that translates specific usability issues into a range of money the site could recover each year.
The logic is simple. Every known interface problem has two dimensions: how often users run into it, and how strongly it hurt conversion during testing. Combine these two numbers with traffic, average order value, or revenue per visitor, and you get an estimate of how much money the site is losing because of a specific flaw, say, an awkward address form or a confusing mobile navigation.
Why this is a money question, not a taste question
When a conversation about design sounds like "this looks more modern," a business owner has every right to say "not now, there are more important things." When that same conversation sounds like "this form is costing you a percentage of your annual revenue," priorities shift on their own. Baymard states outright that without a monetary equivalent, usability fixes regularly lose the fight for a spot in the backlog to other tasks that simply know how to speak the language of finance.
This is also where the question of customer trust hides. A person who can't easily find a product's size, understand the shipping cost, or get through checkout without confusion doesn't write you a complaint. They just close the tab and go somewhere easier. Lost revenue and lost trust are, in this sense, the same hole in your conversion, just measured in different units.

Important: the calculator doesn't promise to double your conversion
It's worth noting how conservative this model is by design. Baymard deliberately doesn't let the forecast grow endlessly even if you fix absolutely everything. The methodology sets a ceiling: in the conservative scenario, total revenue growth is capped at 15 percent, in the base scenario at 25 percent, and in the aggressive scenario at 35 percent. On top of that, the effect of multiple fixes doesn't add up mechanically: if you fix the cart and then the checkout, the second improvement is calculated from the new, already-raised baseline, not from the original one, with diminishing returns built in. That's the kind of caution that separates a serious financial argument from marketing exaggeration.
What a site owner should do with this
- Calculate your revenue per visitor or average order value together with your conversion rate, these are the baseline numbers without which any estimate of lost revenue stays abstract.
- Walk through the buyer's journey yourself, from the first click to payment confirmation, and write down every spot where you yourself hesitated or didn't understand something.
- Prioritize not by how it looks, but by how many people pass through that point and how strongly it stops them.
- Fix things one at a time, not all at once, and check the effect after each step, keeping the diminishing returns in mind.
- Talk to leadership or investors in the language of an annual dollar figure, not the language of "it's more convenient now."
On my projects I take the same pragmatic approach. Before changing even one menu item or form field, it's worth understanding exactly where the customer is leaving the site and how much that costs each month. Design that doesn't count money easily turns into an argument about taste, while design tied to a specific amount of lost revenue stops being up for debate.
Original source: Baymard Institute


