What It Takes to Publish a Real Number

Writing a customer story takes a few days. Getting permission to publish it takes months, and that gap is most of the reason B2B fintech marketing teams tend to have one real case study on the site instead of six.

The approval path runs through the customer’s marketing lead, who’s usually glad to help, then their legal team, then whoever actually owns the number you want to quote. Any one of those people can stop it without much thought, because none of them get much out of saying yes. When one does stop it, what’s left is the anonymized version, and the anonymized version persuades few. Buyers in this category have learned to read “a leading payments platform” as a phrase that means the writer had nothing.

So calendars fill up with the pieces you can publish without needing another company’s permission. You can put a trends post on a January calendar and publish it in March and be reasonably confident nothing will interfere with it, which is a strange thing to want from a piece of content and a very appealing one when you have a cadence to protect.

I’d push on the cadence.

There’s far more capable, technically accurate content in this category than there was two years ago, and a growing share of it gets produced without anyone spending much real time on it. That’s the supply situation, and the practical consequence is that the pieces still doing work are the ones that were structurally hard to make. Hard in a specific sense: not costly to produce, but dependent on access that couldn’t be bought in a hurry.

A number from a named customer is one kind of that. There’s another kind sitting inside your own company that doesn’t need anyone’s approval to publish.

Take your compliance reviewer. She reads every draft before it goes out, and she flags the same handful of things over and over, and she could list them from memory if anybody asked her to. Nobody asks her to. That list would make a better article than most of what gets published in this category, and getting it costs an hour and a calendar invite.

Whoever runs your implementations is the same. They know which step of onboarding fails most often and why, and they’ve known for about a year.

But you have to actually go sit with them, and most content operations have no room in the week for an hour that doesn’t end in a draft. Frankly, that’s the part that needs fixing first, ahead of anything to do with topics or keywords, because it’s the input problem underneath all of it.

The practical effect on a calendar is that publishing has to bend around when proof is available rather than the other way around. If the customer story clears legal in October, it goes up in October, and September’s slot either sits open or takes something already in hand. I’d rather carry the open slot than fill it, though I’ll grant that’s easier to say than to defend in a meeting where somebody’s counting output.

You also have to open more permission conversations than you need, and start them earlier than feels reasonable, because a fair share of them die somewhere in the middle. Two published stories this year probably means five conversations started last quarter. The dead ones aren’t a complete loss anyway, since the conversation itself usually tells you how the customer describes the value in their own words, which is useful even when the case study never runs. Some of the best positioning language I’ve gotten came out of approvals that fell apart.

Still, the honest cost of all this is that you publish less. There’s no arrangement where the pieces get harder to make, and the output holds flat. You’ll have quarters where your calendar looks thin next to a competitor going three times a week, and somebody on your exec team will notice and ask you about it directly.

That’s a real conversation, and I don’t have a clever way around it. What I’d say in it is that the thin quarter tends to produce the piece a salesperson will actually send to a prospect, and in my experience that’s the one worth the argument.