There is an old line in enterprise sales, "nobody ever got fired for buying IBM", and it stuck around for decades. The line was about the buyer's real worry, the meeting after the purchase where somebody senior asked why. That meeting has not gone anywhere. The person on a B2B sales call is rarely the one who signs. Finance usually has to sign off, IT often does too, and someone more senior who never joined the call almost always does.
So the champion who liked the demo walked out of it with a second job. They had to repeat the pitch, in their own words, to a person who never heard the founder speak, who had a budget to protect and a pile of other vendors in the inbox. Nobody gave them slides for that meeting. They improvised.
The questions turn after the first demo
Listen back to a first call and the questions are about the product. What it does, what it connects to, how long setup takes. By the second or third call they turn. The prospect asked how to explain the price to finance, what IT would want to see, whether there was something short to send the boss. Those questions sound like admin, and founders tend to answer them in a sentence and move on to the next slide.
We think those questions carried more weight than anything else on the call. When a prospect asked how to explain a product to their CFO, the deal had already left the room. It had moved into a conversation the founder would never attend, run by someone with a fraction of the founder's conviction and none of the founder's answers.
Write the late questions down first
A spoken answer survives one retelling, maybe two. By the time a champion has summarized the pricing logic to finance from memory, the part that made it reasonable has usually fallen off. They need it in writing, in a form they can forward without looking like they joined the vendor's sales team. A deck addressed to them looks like a pitch. A blog post built around the exact question their CFO is about to ask looks like homework somebody else already did.
The usual B2B content plan opens with thought leadership about the future of the industry, a genre no CFO has ever forwarded to anyone. That is why a founder doing B2B content marketing should write the late-stage posts first. A post about features competes with the homepage, the demo and every rival's feature page. A post about justifying the purchase travels from the person who wanted the product to the people who sign, and that is where the deal lives or dies.
The late questions are already in your call transcripts
If you record your calls, the raw material is already sitting there. Search the transcripts for the moments a prospect talked about someone who was absent. The same phrases show up across deals, things like "how do I explain", "my boss will ask", "finance is going to want", "IT will need" and "can you send me something". Copy each question in the prospect's own words, note what you said back, and note whether the deal moved afterwards.
Once you have read through enough later-stage calls, the same three or four questions tend to come back. Those are the first posts. We built Listen, which is in beta, to read Granola transcripts and Slack and pull out ideas like these. A search box and a quiet afternoon will get a founder most of the way.
One question turned into a post
A common version of the late question sounds like this: "How do I explain this cost to finance?" The post it becomes keeps that wording as the title, since the CFO will recognize it in a forwarded link and the champion would likely phrase a search the same way. The plain answer goes in the first paragraph. That paragraph lists what the product replaces, what it costs over a year, and what the company stops paying for or doing once it is in place.
The next section takes the two follow-ups finance tends to raise. One is what happens if the thing fails, and the other is how hard it is to leave. Then comes the cost of saying yes, stated plainly. That order matters. It mirrors the meeting the champion is about to walk into.
Write for the person who missed the call
The reader of that post missed the call and has no interest in how charming the founder was on it. Write as if they have never seen the product. Use the question in the prospect's words, give the answer in the first paragraph, and define every term the champion picked up in the demo. Then say what yes costs the buyer in price, in hours of setup, in people who have to be involved, and in the tool or habit that gets switched off.
Founders tend to leave that last paragraph out, since it feels like arguing against their own deal. We think it is the paragraph finance reads twice. A post that hides the cost looks like marketing the moment it lands in a CFO's inbox, and the champion who forwarded it ends up looking naive in front of their boss.
Start once deals get past the first demo
This advice has a floor. If every call so far has been a discovery call, there are no late questions to write from. Discovery questions are about the buyer's problem, and plenty of people already write about problems. Those posts can still be worth doing, but they make weaker first posts than the ones a champion forwards. Get a few deals past the first demo, read what changed in the questions, and start there.
A colleague forwarded it
The sign it works is small and specific. It shows up on a later call, when the prospect has already read one of these posts because a colleague sent it. Sometimes that colleague is the person you never met, the one who skipped the demo, the deck and the follow-up email and still arrived knowing the answer to the question that usually stalls the deal. We would trade a month of traffic for one call like that.