Latest / Content Marketing with Fexingo: Blogs, Videos, and Long-Form Content That Converts / How an Unpublished Blog Post Generated 10 Million in Pipeline
Transcript
- Lucas: So there's a B2B software company — I'm not going to name them because the person who told me this asked me not to — but they had a blog post that generated over ten million dollars in pipeline over about eighteen months. And here's the kicker: they never actually published it. Luna: Wait — never published? So it just sat in a draft folder generating pipeline? How does that work? Lucas: Exactly what I asked. The head of content told me they'd spent weeks on this post. Deep research, interviews with customers, a really sharp argument about a shift in their industry. It was supposed to be their flagship piece for the quarter. But when it came time to publish, they hit a wall — legal had concerns about one data point, the CEO wanted to soften a claim, and the piece just stalled. Luna: Classic. So the draft gets stuck, and most teams either kill it or water it down until it's generic. Lucas: Right. But here's what happened instead. A sales rep was on a call with a big enterprise prospect, and the prospect asked a question that the draft answered perfectly. The rep remembered reading the draft in an internal Slack thread, so she shared her screen and walked through it live. The prospect loved it. Asked for a copy. The rep sent the Google Doc link with view-only access. Luna: So the draft became a sales asset by accident. Lucas: By accident, yes. But then the content team noticed a pattern. Every time that draft was shared during a sales conversation, the deal moved faster. Prospects felt like they were getting insider access — this wasn't the polished, sanitized version on the website. It was the raw, honest, 'we're still figuring this out' version. The content team started intentionally gatekeeping it. Luna: Interesting. So they made a conscious decision not to publish it, to preserve that sense of exclusivity. Lucas: Exactly. They locked the Google Doc, put it in a folder that only the sales team could access, and gave reps a script on when to share it. They tracked every view. Over eighteen months, the doc was viewed about four hundred times — almost entirely by prospects during active deal cycles. The content team attributed over ten million dollars in influenced pipeline to that one unpublished draft. Luna: Okay, so let me play devil's advocate. Couldn't they have just published it and gotten even more views? More pipeline? Luna: Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. If these marketing conversations have sparked something you've actually used, no pressure, but that's how we keep it ad-free and focused on stuff like this. Lucas: Yeah, and honestly, it's a small group that already keeps it going. Appreciate every one of them. Anyway — back to the unpublished post. Luna, you asked if publishing would have been better. Let's look at the psychology. Lucas: Published content is public. Anyone can read it, share it, critique it. It's permanent. But a draft? A draft is ephemeral. It feels like a peek behind the curtain. The prospect thinks, 'They're trusting me with something unfinished.' That creates reciprocity. The sales rep isn't just sending a link — they're inviting the prospect into the process. Luna: There's a scarcity element too. Only a few hundred people saw it. If it had been published, it might have gotten thousands of views but with lower conversion impact per view. Lucas: That's the key metric shift. The content team measured pipeline per view, not page views. Their published posts might drive traffic, but the unpublished draft drove deals. The average deal that touched the draft was about twenty-five thousand dollars. That's a high-value audience. Luna: So what did the actual draft contain that made it so effective? Was it the format, the tone, the specific data? Lucas: All three. The tone was unusually direct. Because it wasn't going through the final editorial pass, it had sharper language. It called out industry myths by name. It included a customer quote that legal later flagged — but in the draft, that quote was still there, and it was the most powerful part. The data was preliminary, but that actually made it more credible to sophisticated buyers. They could see the thinking. Luna: I can see that working for enterprise deals where buyers are analytical. But wouldn't it fall flat for smaller prospects or transactional sales? Lucas: Probably. This company's average deal size is north of fifty thousand, so the buyers are used to evaluating complex arguments. The draft was long — about three thousand words. It wasn't a quick read. But for the right prospect, it was exactly what they needed to feel confident. Luna: Let's talk about the operational side. How did they set this up without it getting leaked or causing confusion about which version was current? Lucas: They used a simple system. The draft lived in a Google Drive folder with a specific naming convention: 'FLAGSHIP DRAFT — DO NOT PUBLISH — SHARE ONLY WITH PROSPECTS.' They set the sharing setting to 'view only' and disabled downloading. The sales team had a dedicated Slack channel where they could request access. Every time a rep shared it, they logged it in their CRM as a touchpoint. Luna: So it was gated, but not behind a form or an email capture. It was gated by human judgment. Lucas: Exactly. The gate was the sales rep's discretion. That's what made it feel personal. The prospect wasn't filling out a form — they were having a conversation, and the rep decided, 'This person would value this.' That's a completely different dynamic. Luna: I'm thinking about the content team's role here. Most content marketers are measured on publishing frequency and traffic. How did they justify keeping this draft unpublished when their boss probably wanted it live? Lucas: That's the hard part. The content lead told me she had to argue for a new metric: pipeline influenced per content asset, not per published post. She showed the data after three months — the draft had already influenced about a million dollars in pipeline. Her VP saw the numbers and agreed to keep it unpublished. But it took that proof point. Luna: So the lesson isn't 'stop publishing.' It's 'don't be afraid to leave some things unpublished if they serve a higher-value purpose.' Lucas: Exactly. This company still publishes regularly. But they now have a formal 'draft as sales enablement' workflow. Any blog post that gets stuck in editorial can be evaluated for its sales potential. If it has a sharp point of view or proprietary data, they might keep it as a 'private' asset. Luna: Are they the only ones doing this? Or is there a broader trend of companies using unpublished content strategically? Lucas: It's still rare, but I've seen a few variations. Some SaaS companies do 'pre-release documentation' for beta customers — they share draft API docs before launch. That builds loyalty and gets feedback. Others do 'private briefings' where a draft whitepaper is shared only with top prospects. The common thread is that the content feels exclusive and honest. Luna: I wonder if there's a way to systematize this without relying on sales reps remembering to share a random draft. Could you build a content library that's only accessible during a demo? Lucas: You could. Some platforms let you create 'draft' content that's only visible to users with a specific URL parameter. So a rep could generate a unique link during a demo call that grants temporary access to a set of private assets. That would scale the model without losing the exclusivity. Luna: That's actually a really specific, actionable tactic. I can see a content team creating a whole 'vault' of unpublished pieces — each one tailored to a different buyer persona or stage of the funnel. Lucas: Right. And the key is that these pieces don't have to be perfect. In fact, 'unfinished' might be part of their appeal. One company I know shares a 'living document' — a Google Doc that gets updated every quarter with new data. Prospects can see the edit history. That transparency builds trust. Luna: What about the risk of a prospect sharing the draft publicly? If it goes viral, you lose control. Lucas: It's a real risk. The company I mentioned put a watermark on every page: 'Confidential — prepared for.' That way if it leaked, they'd know who shared it. They also set the doc to expire after thirty days. The prospect had to ask for a new link if they wanted to revisit it. Luna: That's smart. Makes it feel even more exclusive. Lucas: And it creates a natural reason for the rep to re-engage the prospect. 'Hey, I noticed your access expired — want me to send a fresh link? We've added a new section on X.' It becomes a conversation starter. Luna: So the draft isn't just an asset; it's part of the sales cadence. Lucas: Exactly. The content team told me that the draft generated more follow-up meetings than any other sales enablement material they had. Because when the prospect re-engaged, they had questions about the draft. It pulled them deeper into the buying process. Luna: I'm thinking about the resource allocation here. If a team invests weeks in a draft that never publishes, is that a good use of time? Or would they be better off publishing it and creating a separate sales deck? Lucas: That's a fair question. The content lead's answer was that the draft was going to be written anyway. They didn't spend extra time on it. The only difference was that they stopped before the final polish. They saved the editing, design, and legal review costs. So actually, keeping it unpublished was cheaper. Luna: So the cost is the opportunity cost of not publishing it for broad awareness. But if broad awareness doesn't convert as well, then it's a net positive. Lucas: Exactly. For this company, the unpublished draft outperformed every published post on a per-view basis by a factor of about twenty. That's a massive efficiency gain. Now they're exploring a whole series of 'draft-only' pieces — each one aimed at a specific industry vertical. Luna: I love that this flips the typical content playbook. Most advice says 'publish more, publish faster.' This says 'sometimes, hold back and share deliberately.' Lucas: It's not an either-or. It's about having a second path for content that doesn't fit the public feed. If you've got a piece that's too raw, too opinionated, or too niche for your general audience, don't dumb it down. Keep it sharp and use it as a secret weapon in sales conversations. Luna: I wonder what other types of content could work in that 'draft' format. Video? Audio? Internal memos? Lucas: I've seen a company do it with a recorded internal strategy meeting — they shared the transcript with prospects. It was messy, full of jargon, but it showed how they thought about the market. Prospects loved it. Another company shared a draft of their annual planning document. That level of transparency is rare and powerful. Luna: So the underlying principle is trust through vulnerability. You're showing your work before it's perfect. Lucas: Exactly. And that's something most marketing teams are trained not to do. We polish everything. But for the right buyer, the rough edges are what make it credible. Luna: Alright, I'm convinced. I'm going to look at our content backlog and see what drafts we've abandoned that could be repurposed this way. Lucas: That's the move. And if you find one that works, let us know. I'd love to hear a real example from a listener. Luna: Yeah, hit us up. In the meantime, maybe we all need to rethink what 'finished' means. Lucas: Maybe 'good enough for a prospect' is a higher bar than 'good enough for the public.' That's the takeaway I keep coming back to.