From scattered docs to one source of truth: How I transformed sales enablement at my company

One of the first things I noticed was that we had a lot of product information, but no single place to make sense of it.

Product messaging lived in one document. Product information was somewhere else. Sales enablement assets were spread across different folders. Competitive information had its own documents. If someone wanted to understand a product properly, they often had to know where to look, what to look for, or who to ask.

I got the same message from reps at least once a week, always some version of "do we have anything on this?" Sometimes it was a feature update. Sometimes it was an objection they didn't know how to answer. Sometimes it was just "what's our latest positioning again?"

The frustrating part wasn't the questions themselves. It was that the answers already existed. They were just scattered across five different places, half of them out of date, and nobody but me could tell which version was current.

The information existed. The system didn't.

And that created a bigger problem than messy documentation. It meant sales could technically have access to the same information and still not have a consistent understanding of what the product does, who it is for, why it matters, how we differentiate it, and how to talk about it with customers.

As a leader, I didn't want to solve that by creating another document. I wanted to create a system.

The problem wasn't a lack of content

It's easy to look at a sales enablement problem and think the answer is more content. Create another battlecard. Create another one-pager. Create another product deck. Create another FAQ.

But more content can actually make the problem worse when there is no clear structure for finding and using it.

The challenge wasn't that sales didn't have enough information. It was that the information was fragmented. And fragmentation creates friction.

A salesperson preparing for a customer conversation shouldn't have to search through multiple documents to answer basic questions about a product. They shouldn't have to remember which version of a message is the latest.

And they shouldn't have to rely on a product marketer being available to explain the same product repeatedly, especially not at 8 pm on a Sunday or from a train with patchy signal.

I started thinking about sales enablement differently. What if sales could access the product knowledge they needed themselves, whenever they needed it, from one place?

That became the starting point.

Why I decided to build rather than wait

The obvious next step would have been to request a proper enablement platform through procurement, get it scoped, wait for budget approval, wait for implementation, and hope adoption followed. That process can take months, and months of reps guessing at messaging is months of inconsistent narrative reaching customers.

I didn't have a developer sitting next to me, and I didn't need one. Using Replit, I built a lightweight internal system myself: one place that held our product narrative, messaging, competitive positioning, and enablement insight, structured so sales could navigate it without needing me to translate it for them first.

This wasn't about replacing a future investment in a dedicated platform. It was about closing the gap now, with something reps could use immediately, without a login process that took longer than the question they were trying to answer.

I stopped thinking about documents and started thinking about a system

The first shift was conceptual. Instead of asking "what sales asset do we need," I started asking "what information does sales need throughout the buying journey, and how should that information be organized?"

That changed what I built.

The system became a central source of truth for our product narrative and sales enablement information. It brought together:

• Product information
• Positioning and messaging
• Value propositions
• Key product features and benefits
• Competitive intelligence and battlecards
• Sales enablement insights
• Customer-facing narratives
• Supporting resources and assets

But simply putting everything in one place wasn't enough. A giant folder called "Sales Enablement" would technically solve the location problem while creating a usability problem of its own.

So I focused heavily on how the information was structured. The goal was for someone to enter the system and quickly understand: what is this product, who is it for, what problem does it solve, why should a customer care, how do we position it, how are we different from competitors, and what should I use when I'm speaking to a prospect.

That structure was the difference between creating a repository and creating an enablement system.

Making product marketing knowledge accessible to sales

One of the things I wanted to change was the dependency on product marketing as the gatekeeper of information.

As PMMs, we naturally become repositories of knowledge. We know the product. We know the positioning. We know the competitive landscape. We know which customer problems we're trying to solve. And because we know all of this, Sales can easily come to us whenever they need an answer.

But that's not scalable. If sales have to ask the PMM every time they need to understand a product, we've created a bottleneck.

My goal was to turn the knowledge that previously lived in my head, in conversations and across different documents, into something the wider team could access independently. The system became a way of productizing product marketing knowledge. Instead of "ask marketing," it became "here is where you can find it."

That sounds like a small change, but I think it is one of the most valuable things a PMM can do for a growing commercial team.

Building for how sales actually works

Another important consideration was accessibility.

Sales doesn't only need information when they're sitting in the office preparing for a meeting. They might be travelling. They might be preparing for a call five minutes before it starts. They might be speaking to a prospect and need to quickly refresh themselves on a product. They might want to understand a competitor before going into a meeting.

So I wanted the system to work as a self-service resource rather than something that only made sense to the marketing team. That meant thinking about the experience from the salesperson's perspective. 

• If I have five minutes before a customer call, can I find what I need?
• If I'm new to the product, can I understand it without needing someone to walk me through it? 
• If I'm speaking to a competitor's customer, can I quickly understand our differentiation? 
• If I want to use a particular narrative in a conversation, can I find it without searching through ten documents?

Those questions shaped how I structured the system.

What changed once sales actually adopted it

The shift wasn't instant. Reps had years of habit built around asking me directly or digging through old email threads, and habits like that don't disappear just because a better system exists.

Adoption took intentional effort: walking the team through it in a sales meeting, showing them exactly how to find what they needed in under a minute, and being visibly responsive when they flagged gaps.

Once it stuck, the change was noticeable. Reps stopped pinging me for information that already existed and started using the system on their own, including outside office hours when they were prepping for calls or travelling. The constant "do we have anything on this" messages dropped off almost entirely.

The biggest change wasn't that we suddenly had more information. We had less fragmentation. Previously, product knowledge was distributed across different documents and locations. Now, sales had one central system to access the product narrative, messaging, and enablement information, whether they were in London or working a deal in another market.

That created a much clearer relationship between product marketing and sales. Product marketing was no longer simply producing assets and sending them over. We were creating the infrastructure that helped sales understand and use the product, and Sales had somewhere they could return to whenever they needed to refresh their knowledge.

The system became more than a collection of documents. It became a living source of truth for our product narrative.

What I learned

Building this taught me something important about sales enablement. It isn't about how many assets you produce. It's about how effectively you help Sales access and use the right knowledge at the right moment.

It's very easy to measure enablement by output: how many battlecards did we create, how many one-pagers did we produce, how many decks did we update. But those numbers don't necessarily tell you whether you've enabled anyone.

The better questions are: can sales find what they need, can they understand it, can they use it confidently, does it help them have better customer conversations? And perhaps most importantly, have we made sales more self-sufficient?

That became my measure of success.

The role of the PMM is bigger than creating assets

This experience changed how I think about product marketing.

I don't see the PMM's role as simply translating product features into marketing messages or creating sales collateral. A strong PMM can create the system around the message.

We can bring together product knowledge, customer insight, positioning, competitive intelligence and commercial needs, and turn all of that into something the organisation can actually use.

In my case, that meant taking fragmented information and turning it into one accessible system. But the broader lesson is one I think applies to almost every PMM: don't just create content, create clarity.

Because when sales knows where to go, what to say, why it matters, and how to use it, product marketing stops being a library of documents and starts becoming a force multiplier for the commercial team.

And that, ultimately, is what I wanted the system to become. Not another place for sales to find documents, but one place where they could understand the story we were telling about our products, and confidently take that story to the market.