Sales and Marketing Blog | Todd Hockenberry

You're Not Bad at Marketing. You're Good at Information and Bad at Story - Part 2

Written by Todd Hockenberry | Nov 06, 2026

I told a client this year that their marketing problem wasn't what they thought it was. Their website was accurate. Their spec sheets were thorough. Their product pages would satisfy any engineer who already knew what they were looking for. And one of their most differentiated product lines pulled a whopping 137 organic visits in an entire month.

Quick Answer

Manufacturers with great products often stay invisible online because their websites describe products instead of the problems buyers need to solve. The fix is to lead with the buyer's problem, demonstrate results through real customer stories, and support those stories with the technical information engineers need to make decisions.

Table of Contents

  1. Why Do Manufacturers with Great Products Stay Invisible Online?
  2. What's the Difference Between Information and Story?
  3. How Do AI Search Tools Raise the Cost of Being Story-Blind?
  4. What Does Fixing the Story Problem Look Like?

They weren't bad at marketing. They were good at information and bad at story. Their pages described what the products are. Nothing on the site described the problem a buyer wakes up with, the cost of living with it, or what changes once it's solved. If that sounds familiar, keep reading, because this diagnosis fits most of the manufacturers I talk to.

Why Do Manufacturers with Great Products Stay Invisible Online?

Manufacturers stay invisible because their websites are written in product language while their buyers search in problem language. An engineer doesn't type your part number into ChatGPT. They type “how do I install my doohicky in molten lava without cracking the framistan.” Insert your product info in the appropriate places!

If your pages don't speak in those terms, you don't exist in that moment, no matter how good the product is.

This is the pattern I see over and over in industrial companies. The website works as a catalog. Specs, dimensions, materials, tolerances, all correct and all complete. What's missing is any content that meets a buyer at the start of their process, when they have a problem and no vendor list yet.

That timing matters more than most owners realize. 6sense’s B2B Buyer Experience Report found that buyers are nearly 70% of the way through their buying process before they contact a seller, and that around 80–81% of them choose a vendor that was already their preferred choice before first contact.

The research and elimination happen before you know the deal exists. If your site only serves people who already found you, you're competing for the small slice of buyers who put you on that list some other way.

What's the Difference Between Information and Story?

Information describes the product. Story describes the buyer's problem, what it costs them, and what their operation looks like after it's solved. Information answers “what is this?” Story answers “why should I care, and will this work for someone in my situation?”

Here's the test I run on client websites. Pick your most differentiated product line and read the page for it. Count how many sentences are about the product and how many are about the customer. On most manufacturing sites the score is something like 20 to zero.

Now think about what your best salesperson does on a call. They don't recite the spec sheet. They ask about the application, the failure the prospect is dealing with, the downtime it's causing, the customer breathing down their neck. Then they tell them about another company with the same problem and how it got fixed. That's story. Your best salespeople already do this every day. Your website just never learned it from them.

That gap is why “we make great products and our customers love us, but we can't find new ones” is the single most common thing I hear from owners. The knowledge that wins deals in conversation never made it into the content that wins attention online.

How Do AI Search Tools Raise the Cost of Being Story-Blind?

AI tools raise the cost because they answer problem questions, and they build those answers from content that explains problems. When a buyer asks Claude or Perplexity how to solve an application issue, the tool pulls from pages that walk through the problem, the options, and the tradeoffs. A spec table gives it nothing to work with.

This is where the old excuse dies. For years you could get away with a catalog website because a motivated buyer would dig, call, and ask around. Trade shows and reps filled the gap at the top of the funnel. Buyers now hand the digging to an AI tool, and that tool eliminates most vendors before a human ever looks at the shortlist. The companies that get cited are the ones whose content reads like a knowledgeable peer explaining a problem, because that's what these systems are built to extract and summarize.

So the client with 137 monthly visits on a flagship product line isn't losing to competitors with better products. They're losing to competitors whose content answers the questions buyers ask.

In an AI-mediated buying process, being technically excellent and digitally silent produces the same result as not existing.

What Does Fixing the Story Problem Look Like?

Fixing it means rewriting your most important pages around the buyer's problem first and the product second, then backing them with real customer stories that name the situation, the numbers, and the outcome. You don't need more content. You need your existing knowledge restructured around the questions buyers ask.

Start with three moves. Rewrite your top product pages to open with the problem the product solves, in the words a buyer would use, before a single spec appears. Interview your best salesperson and your service team about the five situations that most often lead someone to you, and turn each one into a page that walks through that situation honestly. Then build case studies with names, numbers, and timeframes, because a story with a real company and a real result does the trust-building work that no feature list can.

None of this requires abandoning the technical depth. Keep every spec. Engineers still need them at the evaluation stage. The fix is: problem first, proof second, product third. The specs close the deal. The story is what gets you into it.

I've spent 30 years in industrial markets, and the pattern holds across every one of them: the companies that grow are the ones whose expertise is visible where buyers look, framed around what buyers are trying to fix.

If you want to know how your own site scores on the information-versus-story test, read your top three pages the way a stranger with a problem would. If you can't get through them without already knowing what you're looking for, that's your answer, and it's fixable.