Procurement officers are not engineers. Program managers are not engineers either. The CFO’s chief of staff who actually decides whether the deal moves is definitely not an engineer. And yet the standard B2B technical sell — defense, industrial, aerospace, any sector with a spec sheet — treats every member of the buying committee as if they spent their weekends reading materials science papers.
I spent a stretch translating Henkel’s structural adhesives portfolio into language a defense UAS program manager would actually read past the first paragraph. The deck was the easy part. The harder part was getting the technical team to accept that a slide a procurement officer reads twice is more valuable than a slide an engineer admires once.
§ 01 — The setup
Henkel Adhesive Technologies is the largest adhesives business on Earth — annual revenues in the eleven-billion-euro range, with industrial applications spanning automotive, aerospace, electronics, and defense. The defense and UAS (unmanned aerial systems) portfolio sits in the high-value, high-specification end of the lineup: aircraft-grade epoxies, structural bonding films, thermal interface materials, conductive adhesives, anything that needs to survive in conditions where a fastener would be heavier, slower, or unfit for the job.
The product portfolio is, technically, excellent. The technical data sheets are dense. The application engineering team is brilliant. The challenge was never the product. The challenge was the gap between how the product is described and how the buying committee actually decides.
§ 02 — The B2B comms problem nobody admits
Most industrial B2B marketing reads like a manual translated from German into English by a chemist who has never met a buyer. Specs first, then more specs, then a paragraph that says the product is “innovative” and “reliable,” then a contact form. Somewhere in there is a number that matters — bond shear strength, operating temperature range, cure schedule — but nothing tells the reader why they should care.
The trade press will tell you B2B buyers are different from B2C buyers. They are. But they are not different in the way most marketers assume. They’re not less emotional. They’re not more rational. They are more risk-aware, because the consequence of a bad purchase is professional embarrassment in front of an audit committee, not a return label.
Gartner’s published research on B2B buying behavior has put the typical purchase committee for a considered industrial product at six to ten people, with the buying journey spending 17% of its time talking to suppliers and the remaining 83% doing independent research, internal coordination, and stakeholder management. McKinsey’s industrial buying surveys consistently land in the same neighborhood. The implication is brutal: most of the buying decision happens when you, the supplier, are not in the room. Your marketing has to do the work in your absence.
§ 03 — Mapping the room
The first thing we did was stop pretending the buying committee was one person. We mapped it. For a typical defense UAS bonding application, the room looks something like this:
- The structural engineer. Reads the data sheet first. Cares about bond shear MPa, peel strength, temperature performance, cure profile, hygrothermal aging. Speaks numbers.
- The manufacturing engineer. Cares about throughput. How long does it cure? Does it work on the existing line? Will it survive the autoclave cycle that’s already programmed?
- The materials qualification lead. Cares about specifications, certifications, test reports, AS9100, ITAR. Wants to know which other defense programs have already qualified this material.
- The program manager. Cares about schedule. What’s the lead time? What’s the second source? What happens if a single-source supplier goes down mid-program?
- Procurement. Cares about cost-per-part and total cost of ownership. Wants apples-to-apples comparisons against the incumbent. Wants volume pricing tiers.
- The finance partner. Cares about how the line item rolls up into the program P&L and what the working-capital implications are.
One product. Six different anxieties. Telling all of them the same story is how you lose deals to a competitor whose materials might be objectively worse but whose marketing is targeted.
§ 04 — What we built
The redesign was structural, not cosmetic. We built a tiered communications system, with the same underlying technical truth expressed in language and depth calibrated to each role:
- The one-page executive brief. Aimed at PMs, finance, and procurement. Lead with the program-level impact: weight saved, parts consolidated, cycle time reduced, second-source available, ITAR-compliant. The structural-bond-shear MPa number is on the page, but it lives in a sidebar, not the headline. Headlines are written in the language of business outcomes.
- The PM brief. Two-to-three pages. Includes the lifecycle picture: qualification timeline, supply continuity, support model, where this material is already flying. Designed to give the PM enough ammunition to defend the choice in a program review without having to consult an engineer.
- The engineer’s spec pack. The full technical depth. Bond performance curves, environmental exposure data, application notes, side-by-side with relevant competitive datasheets. This is the document where the chemistry geeks finally get to read what they came for. Crucially, it doesn’t try to also be the procurement document.
- The procurement appendix. Volume tiers, lead times, MOQ, packaging options, terms. Boring. Necessary. The deal closes here.
Same product. Same numbers. Four different documents, each written for the reader whose job it has to make easier.
§ 05 — The fight with engineering
The hardest internal conversation was with the application engineers, who had — fairly — spent careers being the only people who properly understood what the product did. Their instinct, when handed a one-page exec brief that omitted half the spec values, was to ask why we were “dumbing it down.”
We weren’t. Translating is not dumbing down. A one-page brief that lands a meeting with a program director is more technically useful, in the procurement-cycle sense, than a fifteen-page datasheet that the same program director closes after the third page.
The argument that finally worked: the engineer’s spec pack still exists. It hasn’t gone anywhere. The engineer who wants the full depth gets the full depth. We just stopped sending the spec pack to the program manager and expecting it to do the program manager’s job.
This is the framing every B2B technical organization needs to adopt: marketing exists to route people to the right document, not to flatten every document into the same generic register. The technical content survives. The presentation layer in front of it gets segmented.
§ 06 — The receipts
What changed once the tiered comms went out:
- Meeting acceptance rate from cold outreach to program managers and procurement leads went up significantly. A brief that respects the reader’s role gets opened. A datasheet does not.
- “Send me more info” loops shortened. Buyers had what they needed at the level they needed it. The follow-up questions were sharper and faster.
- Sales cycle length compressed on the relevant accounts. The committee had less to align on internally because each member had been pre-armed with the right artifact.
- Win rate against incumbent materials moved in the right direction, especially on accounts where the incumbent had a tenure advantage but a worse story.
None of this required a better product. The product was already the best. It required the discipline to recognize that “best product” doesn’t sell itself in a B2B environment where six people each need a different reason to say yes.
§ 07 — The artifact ladder, in practice
The tiered approach sounds clean in a blog post. In practice, it requires real discipline about which document does which job, and an internal commitment to not collapse them back into one mega-PDF the next time the team is in a hurry. The pattern that survived contact with the field looked like this.
Tier zero: the email subject line. Before any of the artifacts gets opened, an outreach email gets sent. This is the most-read document we produce. Six words, maximum. Concrete benefit, not capability. “Bond replaces 14 fasteners on UAS wing” beats “Henkel adhesive solutions for aerospace” by an order of magnitude on open rate. We A/B’d this. The boring subject line is the silent killer.
Tier one: the executive one-pager. Aimed at decision authority. Single page, eight to twelve lines of text, one diagram. The diagram is not a chemistry diagram. It is a before-and-after of the bill of materials or the production line. Decision-makers see structure, not molecules. The one number we always include is whatever rolls up into the program metric they own — weight saved, parts consolidated, cycle time, cost-per-aircraft. The bond shear MPa is a footnote.
Tier two: the PM brief. Two to three pages. Reads like a Wikipedia article about the application, not a sales document. Lifecycle, qualification status, supply continuity, where else this material is currently flying. The implicit promise of this document is “you will not be embarrassed in your program review if you choose this.” The PM is making a career bet every time they specify a new material. The brief has to defuse that risk before it sells the product.
Tier three: the engineer’s spec pack. Full technical depth. Bond strength curves at temperature. Environmental exposure data. Application notes. Side-by-side competitive comparisons where they exist. This is the document the application engineer will read in detail, mark up, and route internally to the structural team. The discipline here is the opposite of tier one — do not soften the numbers. Engineers smell hedging instantly and assume the worst.
Tier four: the procurement appendix. Pricing tiers, lead times, MOQ, packaging options, terms, second-source language. Boring. Necessary. The artifact where the deal actually closes. The procurement team will skip every other document and read this one twice.
The error mode most B2B marketing teams fall into is producing tier three only — the engineer’s spec pack — and assuming the other roles will just “find what they need” inside it. They won’t. They will close the document on page two and conclude that you are too hard to buy from. The cost of producing four documents instead of one is real but small. The cost of forcing every reader to be their own translator is enormous and invisible.
§ 08 — The take
B2B copywriting is not “make it boring.” It’s “make it land for everyone in the room.” The error mode most industrial marketing teams fall into is treating the technical reader as the only reader. That reader is usually a recommender. Recommenders need ammunition; they don’t need to be sold. The people who need to be sold — the ones with budget authority, schedule authority, risk authority — are reading something else, and you are losing them every time you confuse a datasheet for a sales tool.
If you run B2B marketing for a technical product right now, do this:
- List every role on a typical buying committee for your product.
- For each role, write down — in plain English — what they are afraid of.
- Look at your current marketing collateral. Which fears are addressed? Which aren’t?
The gap between “we have a data sheet” and “we have a piece of paper for every fear in the room” is where your win rate lives. Close that gap. The chemistry doesn’t have to change. The packaging does.
Structural bond shear MPa, on a slide a procurement officer reads twice. That’s the deliverable.