Win Wires: The Customer Win Story Enterprise Tech Sellers Never See
If you're a technology partner, your customer wins are probably showing up in your case studies and marketing materials. But they may not be reaching the sellers at the enterprise brand you partner with, unless you're taking advantage of an underappreciated format: win wires.
When I was a copywriter at a B2B agency, I wrote win wires for Microsoft internal sales teams. I was handed a format, given deal details from the sales team, and had short calls with reps to understand how they'd closed a sale or landed an upsell. The finished win wires went into internal sales newsletters to help other sellers replicate the success.
What I didn’t understand at the time was how that same format is valuable to partner marketing.
What a Win Wire Is
A win wire is a short summary of a customer win, written to help someone else sell. The original use case that I learned was an internal one, distilling one sales team's success into a format other sellers could learn from and reference in their own conversations.
The format works because it answers the questions a seller needs answered: What was the customer's situation? What solution did they choose? What changed as a result? And why does this matter to the next customer I'm going to talk to?
Those are the same questions a good case study can answer. But a win wire answers them in seller language, without requiring the reader to draw their own parallels. They also have the advantages of being much shorter, faster to produce, and written for a sales audience.
How the Format Translates to Partner Marketing
Microsoft partners, for example, have a sales audience that most of their content never reaches: Microsoft sellers.
A Microsoft seller responsible for a solution area can't be an expert on every partner solution in their ecosystem. When a partner produces a win wire written in seller language that’s focused on how the solution drives Microsoft technology adoption, advances a co-sell motion, or helps a seller land a deal, it gives that seller something concrete to work with.
What Makes a Win Wire Effective
A win wire should be short enough to read in two minutes. And if a Microsoft seller has to work to get through it, it won't get read. One page is a good target length.
Marketing language won't land with a seller. Shift away from customer benefits and toward seller relevance. What does this win mean for the seller's pipeline? How does it demonstrate that the partner's solution drives Microsoft technology adoption? How does it help the seller make the case to their next customer?
Example: Demonstrating Microsoft technology adoption means connecting the customer win to its downstream effect on Microsoft. That could include more licenses deployed, deeper Azure usage, or a co-sell motion advanced. That connection isn't always obvious from the customer's perspective, but it makes the win wire useful to a Microsoft seller.
That's a different approach than a case study. And writing for Microsoft sellers requires knowing what they care about, which isn't the same as what your customers care about.
Distribution matters too. Win wires don't belong in automated marketing campaigns. Microsoft's systems are set up to block that kind of outreach anyway. The most effective approach is direct: identifying the right sellers, equipping someone on the partner's team to distribute them personally, and building relationships one conversation at a time. It takes more effort than a campaign, and it's also more likely to work.
When to Produce a Win Wire
A win wire doesn't require a completed case study. You can write it as soon as a customer win is confirmed, and sometimes before the customer has agreed to a full case study. You can also write a win wire instead of a case study. The bar for production is lower because the format is simpler and the audience is internal to the sales ecosystem.
That's a nice benefit of a win wire. Partners who wait for a full case study are missing a window to build seller awareness while the win is still fresh.
