I lost six months of growth by following industry standards.
We were rebuilding onboarding at a marketplace I helped scale, and I asked the team to research what competitors did. They did good work. We shipped a clean, well-structured, perfectly average signup flow. Conversion stayed flat. Retention did not move.
Our users were not the average user a benchmark describes. They were ours, confused by things our competitors never had to handle, and the flow we copied was built for somebody else's customer. Benchmarks did not cause that. I used them as a substitute for thinking about who was actually signing up.
Benchmarks tell you where other companies have been. They cannot tell you where the opportunity is.
Why benchmarking feels safe
Copying a market leader feels like a decision someone smarter already made. "They do it this way and they lead the category, so it must work." But the category leader does not know your customers. They made different tradeoffs for different problems, and you are seeing the result without the reasoning.
I see it most when a marketplace borrows SaaS onboarding patterns, or a subscription business copies a DTC retail playbook because the screenshots looked polished. I call it cargo cult strategy: you build the runway and the control tower, and no planes land.
Benchmarks are lagging indicators
Say your closest competitor announces it doubled retention with a new feature set. By the time you ship your version, they have moved on, and you have built for their customer instead of yours. Their growth drivers came from their data. Yours are in yours.
At TripAdvisor, Instant Booking went from $0 to $200M in ecommerce revenue in 18 months. We got there by running experiments, watching what moved, and turning the winners into the system. Copying Booking.com was never the plan.
Your advantage is knowing your customer
When did someone on your team last talk to a customer? A real conversation with a person who uses your product or tried to and gave up. Reading a report or a dashboard does not count.
Customer knowledge is slow to build and hard to copy, which is exactly why it beats a benchmark. The practice is plain. Product leaders take user calls every week, not only the research team. The whole team reviews session recordings and support chats. You track the surprising friction as closely as the funnel steps that work. And you ask "what was confusing or annoying?" instead of "how was your experience from 1 to 10?"
Look forward instead of sideways
Amazon did not build around what Borders was doing. Airbnb did not set its strategy from Marriott's average room rate. Both solved a problem the incumbents were not looking at, and both created demand that had not existed.
Staying in the comparison loop keeps your differentiation incremental by design. Breakout value comes from doing one job better than anyone, and finding that job is a product risk question: what customers want, what they struggle with, and what they cannot get anywhere else.
Use benchmarks to inform, never to lead
Data on what other companies do is useful as a starting point. For churn, look at the patterns in comparable models, then test them against your own engagement curve. For a pricing change, scan similar models, then ask ten power users what they would pay and why. The second step is the one that decides.
That is why I built a pirate metrics framework for teams: to stop guessing and measure what moves growth in their own business.
How I coach executives out of the industry echo chamber
When I work with product and marketing leaders stuck comparing themselves to the category, we reset in three steps. Put the slide decks away. Get in front of real customers, not friendly ones. Then write hypotheses about behavior, not features: what would a customer have to do to prove this is worth building?
Executives come to me saying "we need a TikTok strategy." My first question is whether their customers use TikTok. Most of the time nobody has checked.
A product team structure that keeps teams close to users makes this sustainable, because decisions get made by the people who hear from customers every week. It also takes a leader willing to say: we are not doing what everyone else is doing this quarter, because our read of our customers is better.
Benchmarks are a fine place to start and a bad place to finish. Let your own users and your own tests decide. That is how you break out of the local maxima a benchmark keeps you in.
Building a product strategy that goes beyond benchmarks?
A benchmark-driven product strategy keeps you permanently behind whoever you benchmark against. I work with product leaders on strategy built from their own customers. Let's talk.
