REVENUE MOTION FRAMEWORK™ · PHASE 3 OF 5

From buying signal to one coordinated play across marketing and sales

When a buying signal fires, the buyer should experience one coherent conversation across channels — not twelve disconnected touches.

What you get
A play library that maps buying signals to coordinated, multi-channel motions, with clear ownership at every step.

The problem this phase solves

Why one signal becomes twelve touches

A target account starts comparing your product on G2 and visiting your pricing page. The Account Interest Rating spikes (see Phase 2 — Sense). Then five things happen in the same 72 hours, none of them aware of each other:

  • Marketing automation drops the account into a nurture sequence triggered off the pricing visit.
  • Paid retargeting starts serving banner ads to every cookie at that domain.
  • The SDR working the territory pulls the account into a 14-touch outbound cadence.
  • The Account Manager fires off a “saw you were looking — happy to chat” LinkedIn message.
  • An exec at the selling company, alerted by an internal dashboard, sends a peer-to-peer note to their counterpart.

The buyer experiences this as twelve disconnected touches from one vendor in one week. They pattern-match to “we’ve been targeted” and either disengage or — worse — quietly route the evaluation around you. The signal was real. The orchestration failed.

Orchestrate is the phase that turns a spike into one coherent conversation, sequenced across channels and roles, with explicit handoffs between functions. Without it, every prior investment — alignment, signal infrastructure, account scoring — leaks at the moment of action.

Visual_Revenue_Motion_Framework_OnePager_orchestrate

What "good" looks like

What Orchestrate actually produces

Orchestrate produces four artefacts. None of them are tooling decisions; they are operating-model decisions that the tooling then executes.

  1. A four-stage account model with explicit transition criteria.
    Every account in the universe sits in exactly one of four marketing-owned stages:
      • Target Account — in the ICP, on the list, no qualifying intent yet.
      • Spotted Opportunity — the Account Interest Rating has crossed the threshold or other intent signals have fired. Worth investigating, not yet worth interrupting sales for.
      • Qualified Opportunity — the Marketing Account Developer has developed the account and confirmed three things from signals and research: fit (still inside ICP after a closer look), buying-group activity (multiple roles engaged, not a single curious user), and credible timing (the evaluation appears to be real and current). The account is ready for the BDR to contact.
      • Accepted Opportunity — the BDR has built the qualification through direct conversations, and the AM, in agreement with the BDR, has accepted it as a sales opportunity and taken ownership of the deal.
  1. A Marketing Account Developer role + queue.
    A named marketing role, distinct from the BDR and from campaign managers, whose job is to work Spotted Opportunities into Qualified Opportunities. The MAD does not contact the buyer. They run the marketing side of the development plays (research, buying-group mapping, role-specific ads and content), document what they learn on each account, and prepare the qualification packet the BDR picks up. Without this role, intent signals sit in a dashboard nobody develops, and “alignment” defaults to whoever shouts loudest.
  2. A play library + role-by-role messaging matrix.
    For each recognisable spike pattern (e.g. pricing + competitor comparison, technical-evaluation cluster, renewal-window expansion signal), one defined play. Each play has a name, a trigger, a set of moves, an owner per move (the MAD for marketing moves before Qualified, the BDR for outreach, the AM after Accepted), an exit condition, and a per-role messaging angle. The CFO, the VP Engineering, and the practitioner don’t get the same opening line — the matrix is where that discipline lives. Six to twelve plays cover the vast majority of patterns.
  3. A handoff + acceptance protocol, with a clear “not yet” path. When the MAD marks an account Qualified, the BDR picks it up, reaches out and builds the qualification. The AM then decides, in agreement with the BDR and within an agreed SLA. Accept: the stage moves to Accepted Opportunity, a sales opportunity. The AM takes ownership of the deal, pipeline and reporting, and marketing automation suspends. Not accepted: the account stays a marketing opportunity to develop further, or is disqualified to stop all effort. The reasons are discussed in the weekly joint call. The handoff is not triggered by an intent score. The intent score is an insight for sales (context, not a task) and a signal for the MAD (a queue item, not a hand-raise). Qualified-to-Accepted is the only stage transition sales touches.

If these four artefacts don’t exist, you don’t have orchestration. You have busy departments.

Three roles, not two.
The Revenue Motion Framework™ distinguishes three operational roles across the marketing-to-sales handoff:
1 – the Marketing Account Developer (MAD), in marketing, develops Spotted accounts into Qualified Opportunities through research and marketing, without contacting the buyer;
2 – the Business Developer (BDR) reaches out, builds the qualification and prepares the opportunity for acceptance;
3 – the Account Manager (AM) accepts it as a sales opportunity, in agreement with the BDR, and works the deal through to Won.

Collapsing any two of these into one role is the most common reason the operating model breaks in practice.

Sub-capabilities

The five capabilities that make Orchestrate work

Capability 1 — Stage discipline.
Moving accounts cleanly through Target → Spotted → Qualified → Accepted requires written transition criteria and a single source of truth. Without written criteria, Qualified drifts to mean “marketing wants this to be a deal” and sales (correctly) ignores it. Stage discipline is the unglamorous foundation everything else rests on.

Capability 2 — The weekly joint rhythm. 
A well-running orchestration system has a weekly rhythm that keeps marketing and sales operating from the same picture. At the start of each week, account intelligence is reviewed jointly — which accounts have increased in signal strength, which have plateaued, which new accounts have entered the target tier, which Spotted Opportunities are progressing toward Qualified, which Qualified Opportunities the BDR is working, and which are ready for the AM to accept. This is where the joint gate-keeping decision lives: before the MAD is activated on a new Spotted Opportunity, both functions agree that the account is worth developing. Sales brings essential context — existing relationships at the account, open opportunities that might create conflict, capacity constraints. Activating the MAD on an account that sales cannot or will not eventually accept is wasted effort — and erodes the trust between the two functions that the entire system depends on.

Capability 3 — Account development.
The work the Marketing Account Developer does between Spotted and Qualified: research, buying-group mapping and role-specific marketing, designed to confirm fit, map the buying group on this specific account, validate the timing of the evaluation, and document what was learned, without contacting the buyer directly. The direct conversations start with the BDR. This is the hardest capability to build because it requires marketing people who can think like sellers without being sellers, and who can comfortably mark an account de-qualified when the development work tells them it isn’t real.

Capability 4 — Play design and choreography. 
A play is a repeatable answer to a recognisable spike pattern. Designing one means: identifying the pattern (which signals, which threshold, which roles active), sequencing the moves (which touches in what order across channels), assigning the owner of each move, building the per-role messaging matrix so the CFO and the VP Engineering each hear the right angle, and setting an exit condition (Qualified, de-qualified, explicit “not now,” or hard timeout). The choreography — three well-timed touches over 14 days, not twelve in five — is what makes a multi-role motion feel like one conversation rather than vendor harassment.

Capability 5 — Handoff and feedback discipline.
Most “alignment” work breaks at the qualified-to-accepted handoff. The MAD believes the account is ready; sales finds five reasons it isn’t. Without a protocol, the handoff becomes politics. With one, it becomes a contract: the MAD produces a qualification packet, the BDR builds the qualification through direct conversations, and the AM accepts or not within an agreed SLA, in agreement with the BDR. Accounts that are not accepted stay with marketing for further development or are disqualified, and the reasons are discussed in the weekly call. Sales owns opportunity reporting after Accept. Success rate from Qualified → Accepted → Won is a recurring joint conversation between marketing and sales — not a marketing slide, not a sales report.

What changes for Orchestrate in the AI era

Buyers reach you later, often with a shortlist already formed, so plays get shorter and focus on validation rather than education. AI also changes how your team works: an AI-supported Marketing Account Developer can prepare account research and briefings in minutes, so people spend their time on the conversations that need judgement.

For the full picture, read How AI Is Changing the B2B Demand Funnel.

A short example

What this looked like in practice

A B2B SaaS team had alignment (Phase 1) and a working AIR with a unified dashboard (Phase 2). When an account hit AIR 70+, it surfaced as “spiking” — visible to both sales and the Marketing Account Developer. What happened next was undefined. Sometimes the MAD developed it, sometimes an AM called it directly, sometimes marketing dropped it into a nurture, sometimes nothing happened at all. Of the accounts that crossed into the spiking band in Q1, 71% never received any coordinated development work. The signal infrastructure was doing its job. Orchestration wasn’t there to catch what it produced.

We rebuilt the operating model around the four stages and one play. Walk a single account through it: TechCo 

Day 0: Target → Spotted.
TechCo is a named Target Account on the AM’s list. The AIR has been background-level for months. Today it spikes to 78 — driven by pricing-page repeat visits and competitor comparison reads from the VP Engineering (3 sessions) and CFO (2 sessions) over the last 6 days. The unified dashboard shows the new status — Spotted Opportunity — to both the AM (as insight: “your account is heating up; marketing is developing it”) and the MAD (as a queue item: “develop this one this week”). The ABM ads layer for TechCo activates with two creative variants: procurement-angle to CFO/Procurement personas, technical-fit-angle to Engineering personas. No sales outreach yet. Sales sees the spike; sales does not act on the spike.

Day 1–10: the MAD runs the marketing side of the play. The Pricing + Competitor Comparison development play kicks in. The MAD does not contact TechCo; the work is research and marketing.

  • Day 1 — The MAD maps the buying group in the CRM: VP Engineering, CFO and a likely Director of Platform, with each person’s role in the decision and the topics they have engaged with.
  • Day 3 — The ABM ads switch to role-specific messages from the messaging matrix: a buy-vs-build comparison for the CFO, and for Engineering the integration concerns the named competitor typically misses.
  • Day 7 — The MAD adds a case study matched to the named competitor to the ads and the account’s web personalisation.
  • Day 10 — The MAD reviews the engagement: the CFO and VP Engineering both engaged with the new content, and a third person from platform engineering appeared.

Throughout, the MAD documents in the account record what the AIR did each day and which roles engaged with what. The goal is not to book a meeting. The goal is to confirm three things: fit, buying-group activity, and credible timing.

Day 11: Spotted → Qualified. The MAD’s notes show that TechCo is still firmly in ICP (fit ✓), three roles across engineering and finance are active (buying-group activity ✓), and engagement is concentrated on pricing and comparison (credible timing ✓). The MAD marks the account Qualified Opportunity and hands the BDR the qualification packet: the spike pattern, the buying-group map, which content each role engaged with, and a recommended entry point.

Day 11–14: the BDR builds the qualification. The BDR reaches out: a LinkedIn message to the CFO with a peer-style opener on buy-vs-build, and an email to the VP Engineering with a 90-second technical demo. The VP Engineering replies and brings in the Director of Platform; the CFO mentions a Q3 budget cycle. The BDR adds this to the packet and takes it to the AM.

Day 15: the AM decides, with the BDR. Two paths.

  • Accept — the AM and BDR agree the timing and fit are real. The stage moves to Accepted Opportunity, the AM takes ownership of the deal and the pipeline reporting, marketing automation suspends for this account, and the AM books the first conversation.
  • Not accepted — the AM explains why: “Wrong product fit — this looks like a hybrid-cloud play, we’re an on-prem story”, or “this buyer has no authority, and we’ve seen this pattern stall three times before.” The account stays a marketing opportunity, and the reasons are discussed in the weekly call. Marketing either develops it further with the corrected angle or disqualifies it to stop all effort.

In TechCo’s case, the AM accepts.

Day 16+: Sales leads. 
TechCo is now an Accepted Opportunity. Sales runs the validation play (a post-acceptance play, different from the development play), owns the opportunity reporting, and pulls in marketing for tailored assets on request. The unified dashboard still shows TechCo’s stage, the AIR trend, and the active roles — but the action layer for this account has moved from the MAD’s queue to the AM’s pipeline.

The result. 
Across two quarters, the operating model produced four shifts that mattered. The Spotted-to-Qualified rate (development work resulting in genuinely-qualified accounts within 21 days) moved from informal-and-unmeasured to a steady 60–70%. The Qualified-to-Accepted rate (sales actually taking the handoff) moved to roughly 75%, with the rejected 25% giving the MAD specific, actionable feedback rather than silent ignoring. Win rate on Accepted Opportunities ran materially above win rate on cold-outbound deals — the qualification work was filtering for real evaluations, not just curious users. And the recurring conversation between marketing and sales — held monthly, looking at Spotted → Qualified → Accepted → Won as one funnel rather than two silos — became the place where qualification criteria, play design, and messaging matrix all got recalibrated based on what actually closed.

Three things to notice. First: the AIR is not a hand-raise to sales. It’s a signal to the MAD and an insight to sales. The handoff is the moment the Qualified packet is reviewed, not the moment the score crosses a threshold. Second: the “not accepted” path is what makes alignment real. If sales can’t say no without consequence, qualification quality erodes. Third: success rate is a joint conversation, not a marketing report. Sales owns opportunity reporting; both teams jointly own the question of whether the qualification engine is producing accounts that close.

Where to go from here

Once Orchestrate is working

A working Orchestrate capability is what makes Phase 4 (Convert) possible. Conversion is downstream of well-timed, well-sequenced, well-handed-off motions — not better closing technique.

Two ways to take this further:

  1. Read it. The complete Revenue Motion Framework™, second edition, with the 90-Day Action Plan deck. Free, no form. → Download free

  2. Work through it together. Want to apply this to your own demand engine? Let’s talk. →

Previous phase: ← Phase 2 — Sense. Next phase: Phase 4 — Convert →

FAQ

Isn't the AIR what triggers sales to act?

No. The AIR is an insight for sales (context on what’s heating up upstream) and a signal for the Marketing Account Developer (a queue item to develop). Sales gets involved once the MAD has developed the account into a Qualified Opportunity: the BDR then reaches out and builds the qualification, and the AM accepts it as a sales opportunity. Skipping the development stage and sending raw intent spikes straight to sales is the single most common reason “intent data” gets ignored.

What does the Marketing Account Developer actually do?

They work Spotted Opportunities into Qualified Opportunities, without contacting the buyer. That means running the marketing side of the development play (research, buying-group mapping, role-specific ads and content), documenting what they learn, and producing the qualification packet the BDR picks up. It’s a marketing role with a sales mindset, measured on Spotted-to-Qualified conversion and on how many Accepted Opportunities later win.

How many plays do we need?

Six to twelve covers most B2B SaaS environments. Most of those will be development plays (Spotted → Qualified). A smaller number are validation/expansion plays for Accepted Opportunities. More than fifteen becomes unmaintainable — nobody remembers which applies when, so people improvise, which is what you were trying to escape from.

What happens when the AM doesn't accept an account?

It stays a marketing opportunity. Marketing either develops it further with the angle the AM and BDR suggested, or disqualifies it to stop all effort. The reasons are discussed in the weekly joint call, so sales can say no without politics, marketing gets actionable feedback, and the next account with the same pattern gets developed better.

Who owns success-rate reporting?

Sales owns opportunity reporting once an account is Accepted — pipeline, forecast, win/loss. The success-rate question — what fraction of Qualified opportunities become Accepted, and what fraction of Accepted opportunities become Won — is a recurring joint conversation between marketing and sales, typically monthly. That conversation is where the qualification criteria, the play library, and the messaging matrix get recalibrated. If success rate isn’t being reviewed jointly, the operating model has reverted to two silos.