GT-M Mediation launch: from technical spec to cohesive market narrative

Last summer I sat down with our product and engineering leads to start pulling apart what they were building. Advanced mediation. The internal name was GT-M. The spec was thick and the language was technical, and my job — starting that week — was to figure out how to translate it into something four different audiences could rally around by end of year.

Then the launch date slipped from November to January. Then the January launch produced a lot of clicks and no conversions. Then in March we tore up the messaging and started over.

Then, in the last three months, four qualified opportunities landed in the pipeline as a direct result of that rework.

This is the story of how we got from the technical spec to the narrative that actually moved deals — and what I learned about the difference between a coherent launch and a converting one.

What mediation actually is (and why the old one was breaking)

If you don’t work in enterprise billing, mediation is one of those words that sounds like it should mean something else. In our world it means this: a customer generates raw usage events — API calls, seat activations, data transactions, streaming minutes, whatever they’re monetizing — and those events land in whatever format the source system emits. Mediation is the layer that ingests those events, transforms them, normalizes them, and turns them into something the rating and billing engines can actually work with. It is the difference between “we captured that customer’s usage” and “we can bill for that customer’s usage without a manual reconciliation call at end of quarter.”

Our old mediation tool was push-only. If your source system could format its events the way our tool expected, and could push them into our tool on our tool’s schedule, mediation worked fine. If your source system did anything else — which most enterprise source systems do — you were writing custom middleware or asking your finance team to close the gap. That was becoming a real problem. Customer feedback was consistent. Competitive pressure was building.

The new tool changed that. It pulls as well as pushes. It ingests a much broader set of formats. It handles transformation and normalization inline rather than requiring the source system to do the work upstream. If you’re an enterprise finance leader, that translates to fewer edge cases, less middleware, and cleaner data flowing into revenue recognition.

That is the technical value proposition. It is also, as I would learn six months later, not the story that closes deals.

The launch plan

We started planning the go-to-market in June. Engineering was targeting a November product release. That gave me five months to translate the spec into a launch narrative that would work across marketing, sales, and partners, then to sequence the promotional campaign around the release date.

I spent the summer in working sessions with the product managers and engineering leads, mapping every capability against buyer relevance. Not every technical improvement needed a marketing story. Some of them were platform hygiene — real work, but not something a CFO cares about. Others were buyer-facing but needed careful framing to avoid overpromising or getting lost in technical detail. The output of those sessions was a working narrative document that our sales and partner teams could adapt into their own conversations.

The promotional plan was standard launch sequencing. Teasers over social in the weeks leading up to the release. A supporting blog series. Updated website content on the mediation product page. Playbooks and solution briefs for the field. A launch-day landing page with the full narrative. Retargeting for anyone who engaged with the teaser content.

The product slipped from November to January. That was fine — arguably better. Late November and December are quiet months in enterprise finance. Buying committees are focused on close-of-year and holidays. Nobody was going to make a platform decision in that window. Pushing to January meant landing in Q1 planning cycles, which is where you want to be.

January launch, February impressions, March reckoning

We launched in January with everything aligned. Landing pages, ads, social promotion, playbooks, solution briefs — every surface told the same story. The narrative was coherent across every touchpoint. It was, honestly, one of the cleanest launches I’d been part of. From a marketing operations standpoint everything ran the way it was supposed to.

And the numbers came in. Impressions were strong. Click-throughs were strong. Landing page engagement was strong. The retargeting sequence was firing. By late February our attribution dashboards looked healthy at the top of the funnel.

The final conversion wasn’t happening.

Not “wasn’t happening enough.” Wasn’t happening at all. We had traffic. We had engagement. We had the same accounts coming back to the landing page again and again. We did not have anyone filling out the form or getting on a call.

By early March I had that specific feeling that PMMs get when the numbers look right and nothing is closing. Like being at Mile 13 of a marathon — you’re not done, but you’re not where you thought you’d be either, and something in the plan needs to change.

We took the launch back to the drawing board as a team. Product, engineering, sales, partners, demand gen. What we found, once we started actually talking to the accounts that were engaging without converting, was that our launch narrative was correct and useless at the same time.

Correct because the technical value proposition was accurate. The tool did the things we said it did. It was demonstrably better than the old version. Useless because we had built a launch around a mediation tool, and no CFO in the market for enterprise billing wakes up thinking “I need a better mediation tool.” They wake up thinking about revenue leakage. About audit exposure. About the ninety-day close cycle they can’t seem to shorten. About the reconciliation calls their team runs every month to figure out what got captured wrong. Mediation, framed as mediation, is invisible to that audience. Mediation, framed as the layer that lets you trust the number your platform tells you every quarter, is very visible.

We had done a technically accurate launch of a technically superior product. And we had, at the message layer, forgotten to translate.

The rebuild

The rebuild took about six weeks. The core reframe was the piece that mattered — we stopped selling GT-M as a standalone tool and started positioning it as the piece that made the entire revenue lifecycle more reliable. Same product, different center of gravity.

Then everything downstream cascaded. Landing page copy got rewritten around business outcomes. Solution briefs led with the audit and revenue-recognition impact rather than the technical improvements. Sales playbooks got a new discovery script that started from finance pain points and worked backward into the mediation conversation. Partner messaging aligned. Ads got new creative that talked about revenue readiness instead of format support.

The other thing we changed was demand-side follow-up. Our NDR built out an eighteen-step sequence for the accounts that had been engaging without converting. Lead IQ pushed engagement data into HubSpot so we could tie return visits to specific people at specific accounts. 6sense intent signals told us who else at those accounts was researching us. The three of us — me, the NDR, our demand gen manager — sat down with the list of most-engaged accounts and built account-specific outreach: a call, an email referencing the specific content they’d engaged with, a retargeted ad tuned to their vertical, a personalized note referencing something from their public LinkedIn activity.

I want to be honest that this part was a lot of manual work. It was also the work that closed the loop.

What shifted

Four qualified opportunities in the pipeline that trace directly to the rework. Three of them had been engaging silently since January or February — creeping and lurking through the top of the funnel, coming back to the landing page repeatedly, never filling out a form. The rebuilt narrative gave them a story they could take internally to their finance and RevOps teams. The sequenced follow-up gave them a person to talk to when they were ready. The combination is what moved them.

Beyond pipeline, a few things I did not expect. Sales conversations at the top of the funnel are now starting from finance-outcome language rather than product-feature language. Engineering picked up some of the rebuilt narrative and started using it in their own customer-facing calls. Our partner team took the reframed positioning into two co-marketing conversations that we wouldn’t have won with the original launch story.

What did not shift

I want to name a few things honestly.

Traffic did not translate one-to-one. Not every account that engaged with the launch content converted after the rework, and I don’t want to pretend the rebuild was a magic reversal. It moved the accounts that were closest to ready. The others will move on their own timeline, or not at all.

I cost us three months. If I had tested the narrative with a few actual prospects before we launched — even ten discovery calls to pressure-test the framing — I would have caught the mediation-vs-lifecycle gap in October, not March. That is a real lesson and I don’t want to soften it. The most experienced PMM in the world can build a launch that looks perfectly coherent and still be pointed at the wrong audience frame. Testing is not optional.

The rebuild took real time and energy from people who had other jobs. Product and engineering had already shipped the product. Sales was already selling it. Asking them to sit through the rework, take new playbooks, adopt new discovery scripts — that was a cost I owed them. I’ve tried to pay it back by making the new materials as easy to adopt as possible, but the friction was real.

What I would do differently

Test the narrative before the launch, not after. Ten discovery calls with real accounts, in the target buyer role, listening to how they describe the problem before I write a single piece of launch content.

Bring demand-side follow-up into the launch plan from day one. Not month three. The follow-up sequence we ran in April should have been designed alongside the launch narrative in July, ready to fire in January. Every launch should ship with a plan for the accounts that engage without converting.

Talk to the NDR first, not last. Our NDR knows more about how prospects actually respond to messaging than anyone in the marketing meeting. He is the person receiving the objections in real time. I should have started with his intake, not ended with it.

Full arc, from technical spec to converted pipeline: about eleven months. I’ll take it. If you’re a PMM who has run into the same “everything is coherent, nothing is closing” moment, I would genuinely like to compare notes — send me a note.