If your sales cycle is dragging and “good leads” keep stalling, the constraint usually isn’t outreach volume—it’s buying-group coverage and follow-through. And that’s why RDRs aren’t disappearing in 2026. They’re moving closer to the center of revenue execution.
Here’s the pattern interrupt: AI is getting real adoption in sales, and it’s associated with better outcomes—InsightMark Research reports 83% of sales teams using AI reported revenue growth, with claims of up to 40% productivity lift and up to 25% shorter sales cycles. But if AI is helping, why do deals still feel harder to move?
Because the hard part isn’t writing an email faster. It’s keeping a volatile buying group mapped, engaged, and coordinated while the cycle stretches. Capchase found B2B SaaS sales cycles became 3.8 weeks longer on average in 2023. Longer cycles create more time for stakeholders to change, priorities to shift, and internal champions to go quiet.
That’s the loop: AI speeds up tasks, but buying groups create drag. RDRs are the role that can close the gap—if the job is re-scoped from “meeting setter” to “buying-group operator.”
Why this matters now: efficiency GTM + expansion-heavy ARR
Revenue teams didn’t wake up in 2026 and randomly decide to rethink RDRs. The economics pushed them there. Benchmarkit’s 2025 SaaS benchmarks put Sales & Marketing spend at an average 47% of revenue for VC-backed SaaS. When that line item is that big, “more activity” stops being an acceptable strategy.
At the same time, the revenue mix has changed. ChartMogul reported expansion revenue rose from 28.8% of ARR in 2020 to 32.3% in 2023, while new business fell from 62.0% to 57.9%. Best-in-class net revenue retention sits around 110–125%. Translation: more companies are living or dying on retention and expansion motions, not just net-new logos.
So the question isn’t “do RDRs still matter?” It’s “who owns the operational work of buying-group engagement across new logo and expansion?” In practice, that’s revenue execution.
The real job shift: from lead follow-up to buying-group coverage
Forrester’s buying-group guidance is blunt about what changes when teams move away from MQLs: formalize multi-threading. That means outreach cadences for all buying-group member roles, not a single-threaded chase of whoever filled out a form. It also means tracking engagement at the person level by adding buying-group members to the opportunity object once agreed-upon signals are captured (manually or via automation), so sales engagement platforms can actually show who’s engaging and who’s missing.
That’s not “nice to have process.” It’s the only way multi-threading becomes measurable instead of a vibe.
And it gets worse (or better, depending on whether someone likes operational problems): buying-group composition is volatile. Demand Gen Report cites that 25–40% of buying-group members can change within six months, and data degrades 2–5% per month on average. That’s a refresh problem. Constantly.
AI helps here, but only if the workflow is designed. Otherwise, teams end up auto-generating messages to the wrong people at the wrong accounts with the wrong context—fast.
Kyle Coleman (Clari/Casted) describes what high-performing orgs actually do: RDRs work with AEs on account planning, researching strategic initiatives, understanding the buying group, and mapping hierarchies and reporting structures. That’s a far cry from “book 12 meetings this week.” It’s closer to: keep the system of record accurate, keep the stakeholder map current, and keep the account in motion.
One move that makes RDRs the execution center: opportunity-member management
If you only change one thing, change this: treat buying-group mapping as a first-class object in your CRM, not a spreadsheet and not a rep’s memory.
Concretely, the tactic is to operationalize opportunity-member management tied to signals. Forrester recommends adding buying-group members to the opportunity object once agreed-upon signals are captured, then tracking engagement by person through sales engagement platforms. That’s the spine. Everything else (AI research, personalization, sequencing) hangs off it.
Here’s the 5-minute version you can run this week:
- Step 1 (define the buying group): Pick 5–7 role “seats” that show up in your deals (economic buyer, champion, security, finance, IT, end-user leader, procurement—whatever is real for your motion). Keep it stable for one quarter. No endless debating.
- Step 2 (define the signals): Write down 3–5 signals that justify “this is an active opportunity,” and only then require buying-group member creation (examples depend on your stack, but the point is agreement). This is your guardrail against junk opps.
- Step 3 (make RDRs the owners): RDRs don’t “support” this—they run it. Their job is to ensure each opportunity has named people mapped to the seats, and to refresh it continuously as contacts churn (Demand Gen Report’s 2–5% monthly decay is the reason).
- Step 4 (multi-thread from the map): Build role-based cadences per seat. Not one cadence for “the account.” This is what Forrester means by formalized multi-threading.
The trade-off: this will reduce volume before it improves quality. Early on, the team will open fewer opportunities because the bar is higher and the admin work is visible. Good. That’s the point.
The hypothesis (make it falsifiable)
If we require buying-group members to be added to the opportunity object when agreed-upon signals are captured, then opportunity progression will improve because multi-threading becomes systematic and engagement gaps become visible early.
What to measure (and what not to over-interpret)
- Primary metric: stage-to-stage conversion rate for opportunities that meet your buying-group coverage threshold vs. those that don’t (directional attribution is fine; don’t pretend it’s causal proof).
- Secondary metrics: median sales cycle length; number of engaged buying-group members per opportunity (tracked via your sales engagement platform once members are on the opp).
- Guardrails: opportunity creation volume; AE time spent on non-selling admin.
- Stop-loss threshold: if opp creation drops more than 20% for two consecutive weeks without any improvement in progression, loosen the coverage requirement (fewer seats, later enforcement point, or narrower signal definition).
When this is wrong
This approach can be overkill for low-ACV, high-velocity motions where buying-group complexity is minimal and the sales cycle is short. If the deal is truly single-threaded and closes fast, forcing a full map can add friction with no payoff. But for longer cycles (Capchase’s +3.8 weeks is a warning sign), it’s hard to argue against visibility.
Run it this week: setup, launch, readout, next test
- Audience: pick 20–40 active opportunities in one segment (same ACV band, same motion) so the readout isn’t polluted.
- Timeline: 2 weeks to implement; 4–6 weeks for a directional progression readout (because cycle time won’t magically compress overnight).
- Owners: RDR manager (process), RevOps (CRM fields + automation), 1 AE lead (field feedback), Marketing Ops (data quality / enrichment workflow).
- Tools: CRM opportunity object + sales engagement platform. Add AI assistance only where it reduces low-value work (account research summaries, role-based personalization drafts), with human review to avoid hallucinated context.
- Baseline: document current stage conversion and average number of engaged stakeholders per opp before you change anything. No baseline, no learning.
Then do the boring part: weekly QA. Buying groups change. Demand Gen Report’s 25–40% churn within six months makes “set it once” a fantasy.
Circle back to the opening claim. AI can speed up tasks, and the data suggests it often does. But the constraint in 2026 revenue execution is still human: getting the right people, in the right account, aligned at the same time. That’s not a meeting-setting problem. It’s an orchestration problem—and RDRs are the role built to run it.
