This One Button Cost Them $300 Million
Your customers want to give you money.
They found you. They liked what they saw. They clicked "buy".
And then… they left.
Not because of the price. Not because of the product. Because of something small, something you probably never noticed.
One online store had exactly this problem. One button. Just one.
When they changed it, they made fifteen million dollars more in the first month.
And three hundred million dollars more in the first year.
Same products. Same prices. Same website. One button.
And this isn't a lucky accident. A presidential campaign raised an estimated sixty million dollars by testing a button and a photo. Microsoft found over a hundred million dollars a year in an idea that had been sitting ignored for six months.
All of them did the same thing. They stopped guessing and started testing.
Today I'll show you five simple rules to find the money your business is leaving on the table, whether you sell online, run a clinic, or work as a freelancer.
This is The Alpha Drive. Agile thinking for business and life.
[Watch this on youtube or listen on spotify podcast]
THE STORY
So let's start with the button.
The story was told by Jared Spool, a well-known user experience researcher. His team was hired by a big online retailer. He never said which one. It doesn't matter.
The checkout looked completely normal. You add products to the cart. You click "Checkout". And then you see a simple form: email, password, two buttons, "Login" and "Register", and a little link, "Forgot password?".
Nothing strange. You've seen that form a thousand times. The designers thought it was helpful: returning customers log in faster, new customers create an account and come back later.
But then the team did something nobody had done before. They watched real people try to buy.
And the people hated that form.
New shoppers didn't want to register. One of them said: "I'm not here to enter into a relationship. I just want to buy something."
Returning shoppers had a different problem. They couldn't remember which email they had used, or what their password was. So they guessed. They failed. They clicked "Forgot password". And many of them never came back.
Then the team looked at the database. And the numbers were shocking.
Forty-five percent of all customers had registered more than once. Some had ten accounts.
The site was getting about one hundred and sixty thousand password reset requests every day.
And seventy-five percent of the people who asked for a password reset never finished their purchase.
So what was the fix? Something big? A new website? A new payment system?
No.
They removed the "Register" button. In its place, they put a "Continue" button, and a short message: you don't need an account to buy. Just enter your details and pay. If you want an account, you can make one later.
That's it.
The number of customers who completed a purchase went up by forty-five percent.
Fifteen million dollars extra in the first month. Three hundred million in the first year.
Now, here's the part that matters for you. This company was not stupid. They had designers, developers, managers, budgets. That form had been there for a long time, and everybody thought it was fine.
Nobody saw the problem because nobody was looking at real people. They were looking at their own opinion of the website.
And that's exactly what agile thinking is about. You don't assume. You check. Small steps, real feedback, then adjust.
So let's turn this into five rules you can use.
RULE 1 — Watch real people use what you sell
Not your team. Not yourself. Real customers.
You know your business too well. You know where every button is. You know what every word means. So you are the worst possible person to test it.
Your customer is seeing it for the first time, maybe on a phone, maybe in a hurry, maybe with a child on their lap.
And here's good news: you don't need a big research budget. The usability expert Jakob Nielsen famously showed that testing with just five users finds most of the big problems. Five.
So here's how simple it can be. Ask a friend, or better, someone who doesn't know your business, to buy something from you or book an appointment while you watch. Don't help them. Don't explain. Just watch and take notes.
Where do they hesitate? Where do they scroll up and down, looking for something? Where do they say "hmm"?
Every "hmm" is money.
And it's not only for websites. If you run a clinic, call your own reception and try to book a visit. If you're a freelancer, read your own offer email as if you were the client. How many steps does it take before someone can say yes?
You'll be surprised. Most business owners have never gone through their own buying process the way a customer does.
One more thing: when you watch, don't defend. It's very tempting to say, "Oh, but the button is right there!" Yes, it is. And they didn't see it. That's the whole point. The customer is never wrong about where they got lost.
Write down every moment of confusion, without judging it. After five people, you'll see a pattern. The same place, the same hesitation, again and again. That's where you start.
RULE 2 — Remove one step
Every step between "I want this" and "I bought this" is a place where people leave.
An extra form field. A required account. A phone call instead of an online booking. A PDF price list you have to ask for by email. Each one feels small. Together, they kill sales.
The three hundred million dollar button wasn't about adding something clever. It was about taking something away.
And that's the agile mindset too. We often think improvement means adding: more features, more options, more information. But very often, the biggest improvement is subtraction.
So here's a simple exercise. Write down every single step your customer goes through, from the moment they find you to the moment they pay. Every click, every form, every email, every wait.
Then ask one question about each step: what happens if we delete this?
Sometimes the answer is "we can't, we need it for legal reasons". Fine, keep it. But very often, the answer is: "we've always done it this way."
That's your target.
Let me give you a few quick examples. Do you really need the phone number on the contact form, or just the email? Can a client book online instead of waiting for a call back? Can you show the price, instead of "contact us for a quote"? Can the invoice go out automatically, instead of someone remembering to send it?
And watch out for steps that exist only to make your life easier, not your customer's. A form that asks for ten details because it's convenient for your database. A mandatory account because marketing wants more emails. Remember the three hundred million dollar button: the account was there for the company, not for the customer. And it cost them a fortune.
If a step helps you but annoys the customer, find another way to get what you need. Ask for the extra details after the purchase, when they're already happy. Offer the account at the end, not at the start.
You don't need to fix all of it. Remove one step this week. Just one. Then see what happens.
RULE 3 — Test small, not big
When businesses want better results, they often plan a big project. A new website. A rebrand. Six months, a big budget, and at the end, everybody hopes it works.
The problem is, if it doesn't work, you don't know why. Too many things changed at once.
Let me tell you about the 2008 Obama presidential campaign.
Their website had a simple sign-up page: a big image or video on top, and a button below to join the email list. Simple.
The team decided to test it. Four different buttons. Six different images and videos. Twenty-four combinations in total, shown to over three hundred thousand visitors.
Now, the campaign team had a favorite. A video. Everybody in the office loved it. They were sure it would win.
It didn't. In fact, every video did worse than every image.
The winner was a simple family photo with a button that said "Learn more". It increased sign-ups by about forty percent.
The team later estimated that this one test brought in nearly three million extra email addresses, and roughly sixty million dollars in extra donations.
A photo and a button. Not a new strategy. Not a new website.
That's the power of small tests. They're cheap, they're fast, and when one works, you know exactly why.
And you can do this without any fancy tools. Try two versions of your email subject line and see which one gets more replies. Try two versions of your offer: one with the price, one without. Try a different first sentence on your website.
Change one thing. Measure. Keep the winner. Repeat.
And notice what happened to the team's favorite video. Everybody was sure. Everybody was wrong. If they had just launched what they liked, they would never have known how much they were losing. That's the hidden cost of not testing: you never see the money you didn't make.
RULE 4 — Let data beat opinions, including your own
This one is uncomfortable, because we all trust our gut. Especially experienced people. Especially bosses.
In 2012, an employee at Microsoft had a small idea for Bing, their search engine. A tiny change to how ad headlines were displayed. It would take only a few days to build.
The managers looked at it and said: low priority. So the idea sat in the backlog for more than six months. Nobody touched it.
Then one engineer decided to just test it. Within hours, revenue went up so much that the system raised an alarm. It looked too good to be true. They thought it was a bug.
It wasn't a bug. Revenue went up by twelve percent. That's more than one hundred million dollars a year, in the US alone.
From an idea that the experts had ignored for six months.
And here's the most important part. The people who run these experiments say that at Google and Bing, only about ten to twenty percent of experiments actually improve things.
Think about that. These are some of the smartest product teams in the world. And most of their ideas don't work. They only know which ones do because they test.
So if they can't trust their gut, neither can we.
This doesn't mean you need a data science team. It means you change the question you ask in meetings. Instead of "what do we think?", you ask "how can we find out?"
And sometimes, finding out takes one week and twenty customers. That's enough to stop arguing and start learning.
There's a nice side effect, too. When decisions are based on data, meetings get shorter. Nobody has to win the argument. Nobody's ego is on the line. The test decides, and everybody moves on.
But be honest with your measurement. Decide before the test what "better" means. More bookings? More replies? More completed payments? If you decide after you see the results, you'll always find a way to prove you were right.
RULE 5 — Make it a loop, not a project
Most businesses improve things once. They fix the website, they launch the new process, and then they forget about it for three years.
But your customers change. Your market changes. The phones in their hands change. What worked last year is slowly getting worse, and you won't notice unless you keep looking.
Booking.com understood this. According to Harvard Business Review, they run more than ten thousand controlled experiments every year. Ten thousand. Every button, every word, every photo is constantly being tested.
You don't need ten thousand. You need one at a time, regularly.
This is exactly how agile teams work. Short cycles. Try something, measure it, learn, adjust, and try again. Not one big launch, but a steady rhythm.
So here's a simple rhythm for a small business. Once a month, pick one thing to improve. Watch it, change it, measure it for a few weeks. Keep it or throw it away. Next month, pick the next one.
That's twelve improvements a year. Even if only a few of them work, they stack on top of each other.
Think about it with simple numbers. If you find just three changes in a year that each bring ten percent more customers, that's not thirty percent. Because they multiply, it's over thirty-three percent more customers. From the same traffic, the same ads, the same reputation.
And the loop also protects you. When something stops working, you notice in weeks, not years.
And this is honestly what we do with our clients at NodeHighway. Most of the money isn't in some big new idea. It's hiding in the process you already have: the extra steps, the manual follow-ups, the customer who gets no reply for two days. We find one thing, fix it, measure it, and move to the next.
It's not magic. It's a loop.
OBJECTIONS
Before we wrap up, let me answer the two objections I hear most.
The first one: "I don't have enough traffic to test anything."
That's fine. Then don't start with statistics. Start with rule number one. Watch five people. You don't need thousands of visitors to see someone get stuck on your booking form. And many of the biggest wins, like that three hundred million dollar button, came from watching, not from big data.
The second one: "I'm not an online business. This doesn't apply to me."
It applies even more. A dentist, a language school, a beauty clinic, a mechanic. Every one of them has a buying process: a phone call, a booking, a reminder, a payment, a follow-up. Every step can lose a customer. And because almost nobody in those industries tests anything, even small improvements can put you ahead of everyone around you.
Think of the last time you tried to book something and gave up. Maybe nobody answered the phone. Maybe the form didn't work on your mobile. You didn't complain. You just went somewhere else. And that business never found out why.
Your customers do exactly the same to you.
CLOSE
So let's put it all together.
Watch real people, because you know your business too well.
Remove one step, because every step costs you customers.
Test small, not big, so you know what actually works.
Let data beat opinions, including yours.
And make it a loop, so you keep improving, month after month.
Somewhere in your business, there's a button. Maybe it's a form. Maybe it's a phone call nobody returns. Maybe it's a price nobody can find.
Your customers already want to pay you. Stop making it hard.
I'm Alex. This is The Alpha Drive.
If this was useful, subscribe. It's one click, no registration required.
And if you want to go deeper on making better calls, my text on building a decision-making system is right here.