Don't Be Like Rolls-Royce: Customers Don't Pay for Your Effort
Don't be like Rolls-Royce. Or that one product manager.
Whenever someone tries to explain why Rolls-Royce cars are so expensive, the answer is often: "We're expensive because we're hand-built." Even ChatGPT starts with this point as the USP.
Honestly, that's a pointless argument.
As a customer, I don't care if it's hand-built or robot-built. What really matters is: does it look stunning? Does it drive like a dream? Does it make me feel something when I sit in it?
It's the outcome that matters, not the effort.
TL;DR: Customers don't pay for your hustle, late nights, or heroic stories. They pay for outcomes: problems solved, intuitive experiences, lives made better. If you didn't deliver, apologize and learn. If you did deliver, talk about the value you created, not the struggle behind it. Effort is invisible to customers. Impact isn't.
The Rolls-Royce fallacy
"We're expensive because we're hand-built."
Think about what this argument actually says. It says: "Our process is labor-intensive, therefore our product is valuable."
But that's backwards. Value comes from what the product does for the customer. Not from how hard it was to make.
A hand-built car that drives poorly is still a bad car. A robot-built car that delivers a flawless experience is still a great car. The customer sitting in the driver's seat doesn't see or feel the manufacturing process. They see and feel the outcome.
The process is the company's concern. The outcome is the customer's concern. Never confuse the two.
The PM version of this fallacy
Same energy when product managers tell customers:
"We worked nights and weekends on this... but still missed the release date."
"This was really complex to build. The engineering team pulled heroic hours."
"We put so much effort into this feature."
I've heard these too many times. In customer calls. In release notes. In stakeholder updates. And here's the thing: customers don't pay for your hustle, late nights, or heroic stories.
All they care about:
- Did you solve my problem?
- Is it intuitive and easy to use?
- Does it actually make my life better?
- Did it arrive when you said it would?
That's it. The hours behind it? The architectural debates? The three refactors? The weekend deployments? Invisible. Completely irrelevant to their experience.
Why PMs fall into this trap
Three reasons:
1. We're emotionally invested. When you've poured months into something, it's natural to want recognition for the effort. But recognition should come from your team and manager, not from customers. Customers owe you nothing except payment for value.
2. We use effort as a defense mechanism. When something ships late or ships poorly, leading with "but we worked so hard" feels like it softens the blow. It doesn't. It just signals that you prioritize your narrative over their problem.
3. We confuse internal metrics with external value. Story points completed, sprints delivered, bugs fixed. These matter internally. They mean nothing to the customer who just wants their workflow to work.
The hard truth: if you spent 6 months building something and it doesn't solve the customer's problem, those 6 months are worthless to them. And if someone else solves their problem in 2 weeks with a simpler approach, that 2-week solution is worth more.
What customers actually remember
Think about the products you love. Do you know how they were built? Do you care?
- When you use Google Maps, do you think about the complexity of real-time traffic algorithms?
- When you use Notion, do you care how many engineers worked on the block editor?
- When you order on Amazon, do you appreciate the warehouse logistics that make 1-day delivery possible?
No. You just know: it works. It solves your problem. It saves you time.
That's what customers remember: the outcome. Not the effort.
| What PMs want customers to appreciate | What customers actually care about |
|---|---|
| "We worked 80-hour weeks" | "Does it work?" |
| "This was technically complex" | "Is it reliable?" |
| "We had to refactor the entire backend" | "Is it fast?" |
| "Three teams collaborated on this" | "Does it solve my problem?" |
| "We did extensive research" | "Does it feel intuitive?" |
What to do when you miss a deadline
It happens. Deadlines get missed. Features ship late. That's reality.
What not to do: explain how hard the team worked. Lead with effort. Make the customer feel like they should be grateful for whatever they get because people sacrificed weekends.
What to do: apologize simply. Explain what happened (briefly). Give a new realistic timeline. And then deliver.
"We're running two weeks behind on this. I apologize for the delay. We hit unexpected complexity in [area]. The updated delivery date is [date], and we're confident in that timeline."
That's it. No heroic narrative. No plea for sympathy. Just accountability and a clear path forward.
Customers respect accountability far more than effort stories.
What to do when you DO deliver
When you ship something great, the temptation is to tell customers about the journey. The struggle. The pivots. The late nights.
Resist it.
Instead, talk about the value you created:
- "This feature saves you 2 hours per week on report generation."
- "You can now do X without leaving the platform."
- "Based on your feedback about Y, here's how we addressed it."
Notice: all of these are about the customer's world. Their time saved. Their workflow improved. Their feedback heard.
Not: "We worked really hard on this." Not: "This was technically challenging." Not: "We're proud of what the team accomplished."
Save the pride for internal retros. For customer communication, it's outcomes only.
The internal vs. external lens
This doesn't mean effort doesn't matter. It does, internally.
Internally, celebrate effort: recognize the team. Acknowledge the complexity. Give credit for the hard work. Engineers and designers deserve to feel proud of what they built.
Externally, communicate impact: customers care about what changed for them. Frame every release, every update, every communication through the lens of customer value.
The same feature gets communicated two ways:
- Internal: "The team delivered a complete refactor of the payment flow in 6 weeks, handling 14 edge cases and reducing technical debt by 40%."
- External: "Checkout is now 3 clicks instead of 7. Your transactions are also 2x faster."
Both are true. Both are appropriate for their audience.
The bottom line
Effort is invisible to customers. Impact isn't.
If you didn't deliver, just apologize and learn. No excuses dressed as effort stories.
If you did deliver, talk about the value you created, not the struggle behind it.
That's what customers remember. That's what earns their loyalty. And that's what truly matters.
Build like Rolls-Royce if you want. Craft every detail by hand. Obsess over quality. But when you talk to customers, talk about the ride, not the factory.
How ProductResume helps
Your PM resume should follow the same principle: outcomes over effort. "Worked with 5 teams on a complex integration" is effort. "Launched integration that reduced customer onboarding time from 3 weeks to 3 days" is impact. Score your PM resume to see whether your bullets communicate value or just describe activity.