Most revenue enablement strategies are built out of the same three blocks: content, training, and tools. A new VP of Revenue Enablement inherits a messy content library, a stale onboarding program, and a stack nobody fully uses, and the first ninety days go to cleaning all three. That work is real. It is also aimed at the wrong constraint for a large share of the team, because the rep staring at a list of four hundred accounts does not lack a deck or a talk track. They lack a reason to call any one of those accounts this week.
That gap hides well. It does not show up in content usage dashboards, and it does not show up in certification completion rates. It shows up as reps working the list in alphabetical order, as first calls that open with a generic value proposition, and as pipeline that looks healthy by activity count and thin by conversation quality. The numbers look like a skills problem, so the fix that gets funded is more training.
This article is for someone in their first ninety days owning enablement across sales, customer success, and account management. It sequences the work by what compounds, and it makes one argument along the way: your list is not the problem, the missing reason is, and no amount of content or training fixes a research bottleneck.
What the standard playbook covers, and what it skips
Read any of the category definitions and the shape is consistent. The Sales Enablement Collective describes revenue enablement as a function supporting every revenue-generating team, built from content and messaging, training and coaching, technology, process improvement, and cross-team alignment. Highspot's guide organizes it as people, processes, and tools. Both are sound. Neither says much about the question every seller answers dozens of times a day before any of that material gets used: which account, and why now?
That question sits upstream of everything enablement usually owns. Content assumes the rep already knows which story fits the account. Talk tracks assume the rep knows which problem to open on. Coaching reviews the call after it happened. If the rep picked the wrong account, or the right account with no reason, every downstream asset performs worse, and the dashboards attribute the miss to the asset.
The cost of skipping it is visible in the research on how sellers spend their week. Salesforce surveyed 7,775 sales professionals for its State of Sales report and found reps spend 28% of their week actually selling. The same research found 66% of reps feel overwhelmed by the number of tools they are expected to use. Gartner, reported by CX Today, found 77% of sellers struggle to complete their assigned tasks efficiently, and 82% of sales leaders believe enablement content delivery needs meaningful change to hit revenue goals. More content and another tool are the two responses those numbers argue against.
Sequence the first ninety days by what compounds
Enablement work falls into two kinds. Some work pays once: a refreshed battlecard, a new onboarding module, a cleaned-up content folder. Other work compounds: a shared definition, a method every rep applies every day, a data habit that makes next quarter's decisions easier. In the first ninety days, favour the compounding kind, because it raises the return on everything you ship after it.
Days 1 to 30: find where the day actually goes
Before building anything, watch the work. Sit with five reps across segments and roles for a full morning each. Do not ask them what slows them down, because they will tell you about the CRM. Watch what they do between opening their list and making the first call. Write down three things for each account they touch: how long it took to decide to contact it, where they looked, and what they said in the first thirty seconds.
You are looking for one pattern in particular. If the time between opening the list and dialling is long, and the opening line is the same across accounts, the constraint is research, not skill. The rep is either spending an hour building a reason, or skipping the reason and calling anyway. Both show up in your metrics as low conversion, and neither is fixed by a better deck.
Days 31 to 60: install one method before any new content
Pick a single research method and make it the team standard before you touch the content library. A standard gives managers something to inspect in pipeline reviews, gives new hires something concrete to learn, and gives you a baseline to measure. The method below is the one we recommend, because it is short enough to run by hand and strict enough to change behaviour.
Days 61 to 90: rebuild content around the reasons reps actually find
Once reps are recording why they called each account, you have something most enablement teams never get: a list of the real reasons conversations start. Group them. A new security leader. A regional expansion. A hiring push for a team your product serves. Each group becomes a talk track, an opener, and a short proof point. Content built this way gets used, because it answers the situation the rep is already in, not the one marketing imagined.
The reason test: a method any rep can run on their own list
A name is worth calling when the rep can answer three questions about it. If they cannot, the name waits.
- What changed? A specific event at the account that makes your product more relevant than it was last quarter. A leadership hire, a funding round, a product launch, a new regulation, a spike in job postings for a role your product supports.
- Where did you see it? A link a colleague could open: a press release, a job post, a filing, an earnings call transcript. "I think they are growing" fails. A link to twelve open roles on their careers page passes.
- When did it happen? A date. A signal from last month is a reason. The same signal from eighteen months ago is background.
No reason, no call. That rule sounds restrictive and in practice it frees reps up, because it replaces the guilt of an untouched list with a clear queue: these twelve accounts have a reason this week, the rest do not yet.
The test also gives managers a coaching tool that does not depend on call recordings. In a pipeline review, ask for the three answers on any new opportunity. Reps who can give them are running a method. Reps who cannot are working a list. The pre-call research checklist goes further on what to gather once an account passes, and trigger events in sales covers how to tie each event to a specific product line so two reps reading the same news reach different conclusions.
Why content and training cannot fix a research bottleneck
The instinct in a new enablement seat is to treat low conversion as a skills gap. Sometimes it is. But skills and research fail differently, and the diagnostic is quick.
| Symptom | Skills gap | Research gap |
|---|---|---|
| First call quality | Right account, weak discovery | Generic opener, no account-specific reason |
| Where reps lose time | After the meeting is booked | Before the first touch |
| Top performers differ by | How they run the conversation | Which accounts they choose and when |
| What more training changes | Conversion improves | Nothing, the rep still has no reason |
| What fixes it | Coaching, practice, talk tracks | A research method and the hours to run it |
The last row is the uncomfortable one. A research method is labour. If a rep owns three hundred accounts and the reason test takes fifteen minutes per account done properly, that is seventy-five hours to work the book once. Nobody has seventy-five spare hours, so the method gets run on a handful of named accounts and the rest of the list gets the generic sequence. That is the gap between accounts with a plan and accounts with a cadence, and it is where most pipeline quality is lost.
There are three honest ways to close it. Narrow the book so the hours fit. Add research capacity, usually an SDR or an analyst function. Or automate the research while keeping the standard: every reason still needs a change, a source, and a date. This is the problem PitchSmart was built for. It researches every lead on your list against what you sell and returns a plan per lead: who to contact, what to pitch, why now, and what to say, with a source on every claim. It can also say hold or skip when there is no reason yet, which is the reason test run at the size of the whole list.
Metrics that show the strategy working
Content views and course completions tell you the enablement program is being consumed. They do not tell you whether reps are calling the right accounts for the right reason. Add a small set of measures that do.
- Share of first touches with a recorded reason. Ask reps to log the change, source, and date on every new outbound touch. Track the percentage. This is the adoption number for the method.
- Reply and meeting rate, split by reason versus no reason. This is the proof. If touches with a recorded reason do not outperform, the reasons are too weak and the method needs tightening.
- Time from list to first touch. If research gets faster without the reason rate dropping, the method is being absorbed.
- Reason categories that turn into pipeline. Over a quarter, this tells you which signals matter for your product, and it feeds straight into the content rebuild from days 61 to 90.
These measures work across roles. An account manager working an installed base can log the same three answers for an expansion conversation. A customer success leader can run the test before a renewal. The customer expansion playbook applies the same thinking to accounts you already own.
What to leave for later
A first-ninety-days plan is also a list of things you deliberately do not do yet. Hold these until the method is running:
- A full content audit. You will rebuild content from real reasons in month three. Auditing the old library first means grading it against a standard you have not set.
- A new platform purchase. Salesforce's finding that two in three reps feel overwhelmed by their tools is a reason to remove a tool before adding one.
- A certification program. Certify reps on the reason test once it is proven to lift reply rates on your own data. Certifying them on a messaging framework before that tests recall, not results.
The common thread is order. Enablement teams get judged on output, so the pressure is to ship assets early. The assets land better when they are built on top of a habit that tells reps which account to work and why. Start with the reason, measure it, then build everything else around the reasons that turn into meetings. If you are still separating the enablement charter from the operations one, sales enablement vs sales operations draws that line, and onboarding new sales reps shows how to teach the method to someone in their first week.
