A rep has forty names on today's list. For the seventh one, a mid-market logistics company, they open the content library to find something worth sending. The library is tidy. There is a folder per product, a sub-folder per persona, and inside each a set of assets tagged by funnel stage: awareness, consideration, decision. The rep picks the logistics customer story because the company is in logistics, attaches it, and moves on to name eight. The prospect does not open it.
Nothing in that library was wrong. The customer story was current, the deck was on brand, the one-pager was approved by legal. The asset failed because the rep picked it by the only facts the library knew how to sort on: product, industry, role, stage. None of those facts says why this company should hear from you this month. The library answers "what do we have?" The rep needed an answer to "what just happened at this account, and which asset speaks to it?"
That gap is the reason most enablement content strategy work produces libraries reps do not use. The fix is not more content or a better search bar. It is organising content around the moment a rep needs it, and defining the moment by what changed at the account.
Why most enablement content goes unused
The waste is measured. In the 2025 Impact of Enablement research from Spekit and the Sales Enablement Collective, a survey of more than 100 enablement professionals, 24.2% reported that over 80% of the content they create goes unused. Almost half, 48.8%, said at least 40% of their collateral is out of date. Those are the people who build the library describing their own library.
The time pressure on the other side is just as well documented. Salesforce's State of Sales research found reps spend 28% of their week actually selling, with the rest going to deal management, data entry and other work. A rep with that little selling time does not browse a library. They grab the first asset that matches a filter, or they skip the asset and write from memory.
Now look at what the guides that rank for this topic tell you to build. Seismic's explainer on enablement content strategy describes a central library where sellers can browse, search and filter by product, industry, persona, stage or language. That is a sound way to store content. It is a poor way to choose it, because every one of those filters describes either your catalogue or your pipeline. None describes the account's situation today.
Funnel stage is the clearest example. "Consideration" is where the deal sits in your CRM. It tells you nothing about whether the prospect just hired a new CRO, closed an acquisition, or posted twelve SDR roles last week. Two accounts at the same stage can need completely different conversations, and a library sorted by stage hands both of them the same PDF.
The moment a rep needs content is set by the account
Enablement teams already talk about "the moment of need." The usual definition is internal: the rep is preparing for a discovery call, handling a pricing objection, or writing a first email. Those are real moments, but they are moments in the rep's workflow. They do not tell the rep what to say, only that they need to say something.
The moment that decides which asset fits is external. It is the change at the account that gives you a reason to show up. A few of the common ones:
- A new leader in the buying seat. New executives review their inherited tools and vendors early, and they want proof from peers who made the same change.
- An acquisition, either side. The acquirer has to integrate two teams and two stacks. The acquired company is about to have its tools questioned.
- A hiring wave in the function you sell to. Twelve open SDR roles is a ramp problem before it is a headcount number.
- Expansion into a new region or segment. New territory means new coverage, new compliance and new process.
- A public commitment. An earnings call, a press release or a strategy post that names a goal your product serves.
- A tool change. A job post that names the platform they are moving to, or a review that names the one they are leaving.
These are trigger events, and every one of them suggests a different asset from the same library. The new CRO wants a short peer story about the first ninety days. The acquirer wants an integration plan. The team hiring twelve SDRs wants something about ramp time. A library sorted by product and stage cannot route any of these, because it does not know any of them happened.
The reason test, applied to content
Before a rep sends an asset, it should pass the same test the outreach itself has to pass. A name is worth contacting when the rep can answer three questions:
- What changed? Name the event: the hire, the deal, the job posts, the announcement.
- Where did you see it? A link the rep could paste into the email if asked. A recollection does not count.
- When did it happen? A date. A leadership change from two years ago is history, and a hiring wave from last week is news.
If the rep can answer all three, the asset choice follows almost automatically: send the piece that speaks to that change, and say why in one sentence. If the rep cannot answer them, no asset will rescue the touch. The right move is to hold the name, not to attach the industry customer story and hope.
This is the part of enablement content strategy that the library model leaves out. Content does not create the reason to talk. It supports a reason the rep already has. When reps have no reason, they reach for content to fill the gap, and the content goes unopened because it was never about the buyer's situation in the first place. We made the same argument about the expansion slide in a QBR: the slide fails when the reason is missing, not when the design is weak.
Reorganise the library around moments
You do not need to rebuild your content. You need a second index on top of it, keyed to account moments rather than to products and stages. Here is what the top of that index looks like for a team selling sales software into mid-market companies:
| Moment | Evidence the rep should have | Asset that fits | Asset that does not |
|---|---|---|---|
| New VP of Sales or CRO | Announcement post or press release, with a start date | Short peer story on the first ninety days in the seat | Full product overview deck |
| Acquisition closed | Press release naming both companies and the close date | Integration checklist for two sales teams | Industry customer story |
| Hiring wave in sales or SDR roles | Careers page or job board listings, counted and dated | Ramp time guide with one worked example | ROI calculator |
| New region or segment | Office announcement or regional job posts | Territory design worksheet | Generic brand video |
| Stated growth goal | Earnings call quote or strategy post | One-pager tying your product to that goal | Feature comparison grid |
| Moving off a competitor | Job post or review naming the tool | Migration plan and switching timeline | Awareness-stage blog roundup |
The right-hand column matters as much as the third. Most of the assets in it are good assets. They are just answers to questions this buyer is not asking this month.
Building the index in a month
- Pull the last ninety days of first meetings that happened. For each, find the touch that got the reply and write down what had changed at the account. If nobody can say, mark it unknown. The unknown share is a finding in itself.
- Group the changes into six to eight moments. More than eight and reps stop remembering them. Use the buyer's language for each moment, not your internal campaign names.
- Map existing assets to each moment. Most libraries already hold something usable for four or five of them. Note the gaps rather than filling them all at once.
- Write one opening paragraph per moment. Two or three sentences a rep can adapt: name the change, say what it usually means, offer the asset. This is the piece reps use most, and it is the one most libraries do not have.
- Retire what no moment needs. If an asset maps to no moment and drew no engagement in the last two quarters, archive it. That shrinks the out-of-date share the Spekit research points at.
- Put the moment index where reps work. A pinned page in the sales channel or a field in the CRM beats a new tab in the library.
This fits inside a broader revenue enablement strategy without replacing it. Your product, persona and stage tags stay. The moment index sits on top and decides which tagged asset gets used for which name.
What to measure once the library is reorganised
Content views and downloads tell you whether reps opened the library. They do not tell you whether the asset fit the account. Four numbers do a better job:
- Share of first touches with a named moment. If reps cannot say what changed for most of the names they contact, the content problem is upstream of content.
- Reply rate by moment. Some moments will outperform others by a wide margin. Fund the assets for those first.
- Asset use by moment. An asset used across every moment is probably being used as filler.
- Out-of-date share. Track the share of the library past its review date, the same measure the 2025 research used, so you can see it fall.
The first number is the one most teams find uncomfortable. It usually shows that the library was never the bottleneck.
Where the bottleneck moves next
Once the library is organised by moment, the hard part is knowing the moment for each name. That is research: reading the announcements, the job posts, the earnings commentary and the news for every account on the list, and writing down what changed, where, and when. Done by hand, it is the work that a rep with 28% of the week for selling does not have time for, and it is why the industry customer story gets attached by default. Our pre-call research checklist walks the manual version for a single account.
PitchSmart does that research across the whole list. It reads every lead against what you sell and returns a plan for each one: who to contact, what to pitch, why now, and what to say, with a source on every claim. The "why now" is the moment, with the link and the date attached, which is exactly the input a moment-indexed library needs to route the right asset. When the research finds no change worth raising, the plan says hold rather than inventing a reason.
The library is not the problem
Enablement teams respond to low content usage by producing better content, tagging it more carefully, or buying a better platform. Those all improve the library. None of them gives the rep a reason to contact the seventh name on the list, and without a reason, the best asset in the library is just an attachment.
Run the test on your own list this week. Take ten names a rep plans to contact and ask the three questions for each: what changed, where did you see it, when. Count how many pass. Then look at what was going to be attached to the ones that did not. That count tells you more about your enablement content strategy than any usage dashboard.
