Replace catalog-style language with a brand story that named what the buyer was actually procuring — reliability, partnership, risk reduction — not a list of features. Give the sales team something to lead with that didn't reduce every conversation to a price negotiation.
Buyer research with procurement decision-makers and end-users. Messaging framework from category positioning down to feature-level talk tracks. Pitch deck rebuild, capabilities one-pagers, trade-show materials. Internal language alignment so the team described itself the same way in every room.
Sales now leads with a story instead of a spec list. Procurement understands the value before the price negotiation starts. The company has language that reflects the seriousness of what they actually do for the customer — and the team uses it.
The challenge
A growing industrial manufacturer with a respected product was selling on price and spec lists in a market where buyers cared about reliability, partnership, and the cost of the wrong choice. The internal language had become a catalog — bullet points of features, dimensions, certifications — in a buyer environment where procurement was actually weighing relationship, risk, and what happens when something goes wrong on a Friday at 2 AM.
The sales team had built workarounds. Each rep had their own deck. Each deck told a different story. Customers who bought from two different reps got two different versions of the company. Trade-show materials looked like the website which looked like the catalog — and none of them sounded like the conversation that actually closed deals.
What I did
Industrial buyers don't buy on hype. They buy on confidence. The work was about giving the company a way to demonstrate confidence in language — without faking softness on a product that's genuinely technical.
Buyer research with procurement and operators
- Interviewed procurement decision-makers about what they actually weigh when picking suppliers in this category — the criteria that go in the spreadsheet and the ones that don't
- Interviewed operators — the people who use the product after procurement signs — to understand what reliability actually means at the workbench
- Mapped the points in the buying cycle where the company's current language was costing it — usually before procurement's call even happened
Messaging framework from category to feature
- Category positioning that named what the buyer was actually procuring (a partner, not just a part)
- Three pillars beneath the category claim, each defensible against a competitor's own pitch
- Feature-level talk tracks that reinforced the pillars rather than competing with them — the spec sheet didn't go away, it stopped being the lead
Selling on spec when the buyer is buying on trust? Book your free 30-min slot →
Sales materials the team would actually use
- Pitch deck rebuild — opens with the buyer's problem, ends with the company's answer, doesn't spend slide six on the founding story
- Capabilities one-pagers per buyer segment, written in the language the buyers used in interviews
- Trade-show materials and conversation guides for the booth team so the live conversation matched the printed materials
- Internal language alignment workshop with the leadership team to lock in how the company describes itself in every room
The outcome
Sales now leads with a story instead of a spec list. Procurement understands the value of the relationship before the price negotiation starts — and the negotiations that do happen are about scope rather than discount. The company finally has language that reflects the seriousness of what it actually does for the customer, and the team uses it because the language came out of their conversations, not out of an agency conference room.
We sold on spec for years because that's how engineers talk to engineers. She showed us that procurement isn't engineering and that the buyer was waiting for us to name the thing we actually do. The team uses the new language because it's ours — she didn't hand us an agency deck.