Why "what's working for everyone else" is the most expensive advice in eCommerce

 

Six months into running PromptBoox, an online bookstore built around unique and offbeat book gifts, I made a decision that cost me nearly a third of my monthly revenue for two straight months. I want to walk through exactly what happened, because the mistake wasn't obvious until it had already done damage — and I think most small eCommerce owners make some version of it at least once.

 

The trend everyone was chasing

 

Personalized products were having a moment. Every gift-shop competitor I tracked was rolling out custom engraving, name-stamped covers, "build your own gift box" tools. The data backing it looked real: personalization was showing up in every gifting-trend roundup that season, and a few direct competitors were visibly leaning into it hard.

So I did what felt like the obvious move. I paused development on a slower, less flashy project — expanding our curated "books for hard moments" collection, built around specific life situations like grief, divorce, and career loss — and redirected that budget toward a personalization feature: custom bookplates and gift-note printing.

 

What actually happened

 

The personalization feature launched on schedule. It looked good. It got a modest bump in social shares. And it did almost nothing for revenue.

Here's the part that stung: while I was building it, our best-performing existing product line — the curated "hard moments" collection — kept converting at nearly triple the site average, with zero marketing spend behind it, purely on repeat customers and word of mouth. I had taken time and budget away from the thing that was already working, to chase something that was working for other people.

It took about two months of flat growth before I pulled the actual numbers apart and saw it clearly. The personalization feature had cost roughly six weeks of development time and a meaningful chunk of ad spend to promote. In that same window, the "hard moments" collection — untouched, unpromoted — had quietly driven more revenue than the new feature ever would.

 

The mistake, named plainly

 

I hadn't validated that personalization solved a problem my specific customers had. I'd validated that it solved a problem the market had, in general, based on what competitors were doing. Those are not the same signal, and conflating them is an easy trap, because competitor activity feels like data. It has numbers attached. It looks like research. But a competitor moving into a feature tells you they believe it'll work for their customer base and their positioning — not that it will work for yours.

My actual customers weren't buying from PromptBoox because they wanted customization. They were buying because they wanted someone else to have already done the hard work of matching a book to a difficult moment in another person's life. The personalization feature added friction — an extra decision, an extra step — to a purchase process that worked because it removed decisions, not because it added them.

 

What I changed afterward

 

I killed the personalization feature's marketing push, kept it available quietly as an option rather than a headline, and redirected the budget back to the collection that was already proving itself. Within a month, growth returned to its previous trajectory.

More importantly, I changed how I evaluate a new feature or product line before committing real budget to it. Now, before building anything, I ask three questions:

  • Does this solve a problem my existing best customers have already told me about — in reviews, support emails, or repeat-purchase patterns — or am I inferring the problem from what competitors are doing?
  • Am I taking resources away from something that's already working, and if so, do I have real evidence the new thing will outperform it, or just a hunch that it should?
  • Would I still build this if no competitor had done it first?

That last question turned out to be the most useful filter. If the honest answer is "no, I only want this because everyone else has it," that's usually a sign the feature is solving my anxiety about falling behind, not a real problem for the customer in front of me.

 

The takeaway

 

Trend-chasing in eCommerce feels like diligence because it's backed by visible competitor activity and market reporting. But market-level signals and customer-level signals are different kinds of evidence, and only one of them tells you what your specific buyer actually wants. The fastest way to find out which is which is to look at what's already converting on your own site before you look at what everyone else is building — the answer is usually sitting in data you already have.

 

PromptBoox, an online bookstore for unique and gift-worthy books. More at promptboox.com.