Here is a mistake almost every founder makes, including me.
We build something, and then we describe it by listing what it can do. Ten integrations. AI-powered. Real-time dashboards. Fifty templates. Custom reports. We line the features up like trophies and wait for customers to be impressed.
Usually, they aren’t.
Not because the features are bad. Because the customer was never shopping for features. They were shopping for less work.
The job behind the purchase
Clayton Christensen, the Harvard professor behind the idea of “disruptive innovation,” liked to say that customers don’t buy products. They hire them to do a job.
The question is never “What does this product do?” The question is “What job was the customer trying to get done, and what was annoying them about the old way?”
When you look at business this way, a pattern shows up again and again. The job is very often the same one:
“Please take this off my plate.”
A restaurant owner doesn’t want accounting software. She wants to stop doing the books at midnight. A landlord doesn’t want a booking dashboard. He wants to stop copying guest names from three apps into one notebook. A teacher running a small tutoring center doesn’t want a database. She wants to know who hasn’t paid this month without checking every row.
The product is the means. The removed work is the thing they pay for.
Why founders miss this
If removing work is so valuable, why do so many products end up adding it?
1. Features are easy to see. Saved time is not.
A feature shows up in a demo. You can screenshot it, write a launch post about it, and put it on the pricing page. Saved time is invisible. Nobody takes a photo of the hour they didn’t spend on spreadsheets.
So founders build what they can show, not what the customer can feel.
2. Builders love building
Engineers (I am one) enjoy hard problems. A clever new feature is fun to make. Deleting a step from the user’s day is less fun, because the best version of it looks like nothing happened.
But “nothing happened” is exactly what a busy customer wants.
3. Every feature is a little bit of new work
This is the part people forget. Each new button is a new thing to learn. Each setting is a new decision. Each integration is a new account to connect. A product with fifty features can easily create more work than it removes.
The customer doesn’t add up your features. They add up their effort: how much of their day your product takes, versus how much it gives back.
The “less work” test
Before building anything, I now try to answer one question:
After this ships, what will the customer stop doing?
Not “what can they now do.” What will they stop doing.
If the honest answer is “nothing,” the feature probably isn’t worth building yet. If the answer is “they’ll stop copying bookings between three apps every morning,” now we’re talking. You can measure that. The customer can feel it. And you can explain it in one sentence on your homepage.
A few versions of the same test:
- Count the steps. How many clicks, tabs, copy-pastes or phone calls does the job take today? How many after? If the number didn’t go down, you didn’t help.
- Watch for the notebook. If customers still keep a paper notebook or a side spreadsheet “just in case,” your product hasn’t earned their trust. That notebook is your real competitor.
- Listen for the sigh. When customers describe their day, they sigh at certain points. “And then I have to…” That sigh is your roadmap.
Small businesses feel this the most
Big companies can hire someone to handle the boring work. Small businesses can’t. In a shop, a rental business or a tutoring center, the owner is the operations team, the finance team and customer support, often all before lunch.
That is why the most useful products for small businesses are often not the most impressive ones. A ready-made spreadsheet where every formula is already written can be worth more to a shop owner than a powerful platform they’ll never finish setting up. A short daily summary that says “these three guests arrive today, this room needs cleaning, this message needs a reply” can be worth more to a host than ten dashboards.
The winning product for a small business usually isn’t the one that does the most. It’s the one that asks the least.
Selling “less”
If customers buy less work, then your marketing should talk about less work too.
Compare:
- “AI-powered multi-channel booking aggregation platform.”
- “Stop copying bookings between Airbnb, Booking.com and WhatsApp. Get one summary every morning.”
The first one describes the product. The second one describes the customer’s day getting easier. Only one of them makes a tired host stop scrolling.
A simple rewrite rule: take every feature on your website and finish this sentence for it — “…so you no longer have to ___.” If you can’t fill in the blank, the feature doesn’t belong on the homepage.
Less work is also a business model
There is one more reason I like this idea: it lines up what’s good for the customer with what’s good for the business.
When your product removes real work, customers stay, because going back would mean doing that work again. They tell other people, because “this saved me an hour a day” is a story people love to share. And they are willing to pay, because they can compare your price directly to the value of their own time.
Features can be copied by a competitor in a few months. A habit of making your customer’s day lighter is much harder to copy, because it comes from paying attention, not just from writing code.
The takeaway
If you’re building a business, try this for one week: stop asking “What should we add?” and start asking “What can our customers stop doing?”
Then build that. Then say it out loud, in plain words, on your homepage.
People don’t pay for features.
They pay to do less.
Next: Your Real Competitor Is a Spreadsheet, on why so much software loses to Excel and a notebook, and how to win anyway.
