Sell the story, not the specs.

During a discovery call last week, a marketing manager told me that despite months of work on their website, it still read like a "lab catalogue". Their words, not mine, but I would have been lying if I said I disagreed.

I spent four years of my PhD reading technical sheets so dense I could recite reagent concentrations in my sleep, so believe me when I say scientists can read a spec sheet, yet it doesn't mean we enjoy it (despite what many marketers think). What most companies forget is that reading one was never the point of visiting a homepage.

They're not alone in this. Walk through the site of almost any life science tools company and you'll find the same thing. Run time. Temperature range.

Dimensions. Throughput. All correct, all necessary somewhere, and none of it doing the one job a website actually has: making someone want to keep reading.

The market got too good to win on spec alone

Ten years ago, being the best product might have been enough. It isn't anymore.

Walk any exhibition hall in this sector and you'll find half a dozen instruments doing the same job to a comparable standard, built by companies who all genuinely know what they're doing. Bench space is more contested than it's ever been, and the products competing for it are remarkably close in performance.

That changes what wins; for better or for worse. When every option on the shortlist is good, the deciding factor stops being the specs and starts being how well the company communicated it. Not louder, or flashier, or solely on marketing spend. But how well it is understood, and most importantly - remembered. A spec sheet cannot do either of those things on its own.

Data proves the point. It doesn't make the point

There's a myth I hear constantly from marketing teams in this space: scientists love and make decisions on data, so the content has to be data first. Half true.

Scientists do want the numbers, eventually, right down to a level they could put in the methods section of their own paper. But that's the last step of a decision, not the opening argument.

Nobody gets curious about a product because of its run time alone. They get curious because something in the workflow annoys them, and a company shows up describing that exact annoyance back to them, then shows the fix. The data closes the sale. It was never going to open it.

Spec sheets are where marketing goes to avoid taking a position

Here's my hypothesis. Loading a homepage with specifications is often a communication decision, and usually not a conscious one. A number is safe.

Nobody can argue with the specs. A story requires the company to say something specific about the problem their buyer has, which means being willing to be wrong about it, or being seen to have an opinion at all.

That safety costs the entire storytelling. My client built a site that was thorough, accurate and instantly forgettable, because accuracy was the brief they gave themselves. If your product is genuinely comparable to three others on the market, and it almost certainly is, accuracy alone will never be the reason someone picks you.

Where the real estate actually belongs

The fix isn't complicated, even if it takes discipline to apply. Specs belong on the tech sheet, the brochure, the document a buyer downloads once they're already interested. Your website gets a fraction of a stranger's attention before they leave, and that attention is too valuable to spend restating what's already in the datasheet.

Use it instead to bring the product to life. Show the workflow it replaces, the moment it fixes, the specific researcher who was stuck before they found you.

Give them that "aha-moment" where they think, "this company understands the challenge better than I do". Build the data in, absolutely, but build it into an argument rather than a list. If your product can't win on features alone because the market has caught up, story is the only lever left that a competitor can't simply copy from your datasheet.

One test tells you where you stand. Read your own website as if you'd never worked there. Better still, hand it to a scientist who has nothing to do with your company and watch where they stop reading. If the answer is "the second paragraph," the fix isn't a rewrite of the copy. 

It's to develop the story.