What's the framework for a CRO to decide whether to build two separate sales motions (organic vs M&A/upmarket) with distinct qualification rules, or force-fit both into a single process in 2027?

Two engines or one process with a fork

The choice a CRO actually faces is not binary in the way it gets framed in the boardroom. There are three distinct structures, and most companies that think they are choosing between two are ignoring the one they should pick.

Option A — one motion, one process, no fork. Every deal, organic or upmarket, runs the same stages, the same qualification framework, the same comp plan, the same forecast roll-up. This is correct at small scale and correct whenever the segments differ only in degree. Its virtue is that all enablement, coaching, and pipeline math compound into a single system. Its failure mode is terminal force-fitting: when the segments genuinely have different physics, the shared process fits neither. The velocity stages never model procurement or a security review, so upmarket deals sit in Commit and die at a gate nobody instrumented. The shared qualification rubric marks deals "qualified" that have a budget and a timeline but no champion and no economic-buyer access. Win rates on the misfit segment look inexplicably bad because the data is blended and nobody can isolate the cause.

Option B — one motion with a documented branch. Same reps, same manager, same CRM org, same top-of-funnel stages — but an explicit fork at the qualification stage. Deals matching the upmarket profile get a different record type, a heavier qualification checklist, additional required fields, a longer stage path, and their own forecast category. This is the structure almost every company between roughly $3M and $12M in ARR should be running, and it is the one most CROs skip because it produces no org-chart artifact. It costs almost nothing, it is fully reversible, and critically it generates the data that makes the eventual separation decision evidence-based rather than narrative-based.

Option C — two separate motions with separate orgs. Dedicated reps, a dedicated first-line manager who has actually run that motion, a separate comp plan with its own quota methodology and ramp curve, a separate enablement curriculum, its own SDR support, and formal written handoff rules at the seam. This is correct once the physics have diverged and the segment clears the funding floor — and it is expensive, slow to build, and politically very hard to reverse.

The asymmetry worth naming: Option C fails loudly and fast — within two or three quarters the sub-scale pod is visibly missing quota and the comp budget is visibly blown. Option A fails quietly over a year or more through second-order effects that each look like something else. That difference in tempo, not difference in cost, is why CROs systematically overweight the risk of force-fitting and underweight the risk of premature separation — or, just as often, the reverse, because a separate "Enterprise org" is a visible, narratable artifact of progress and a documented branch is not. Both failure modes are expensive. The framework exists to take the decision out of the realm of ambition and put it back into measurable physics and economics.

One vocabulary correction prevents most of the confusion in this debate. A motion is the end-to-end repeatable system by which a specific kind of revenue is generated — who you target, how demand is created, who works the deal, what the buying process looks like, how you qualify, how you price, what the cycle math is, and how reps are paid. A process is the documented stage-by-stage workflow inside a motion. A qualification framework is the rubric reps use to decide whether a deal is real. A segment is a slice of the addressable market. One motion can serve multiple segments; the entire question is whether a given segment has crossed the threshold where it now requires its own motion. And a motion is a go-to-market motion, not a product line — two products sold to the same buyer at the same size on the same cycle by the same kind of rep are one motion regardless of SKU count, while a single product can require two motions if it sells both as a small practitioner purchase and as a large platform commitment to a buying committee.

The six-factor separation test and the funding floor

Score the candidate second motion against the core motion on six factors. Each scores 0 (no meaningful divergence) or 1 (clear structural divergence). Four or higher means the physics have diverged enough to warrant separation — provided the funding floor is also cleared.

Factor 1 — buyer persona divergence. Is the economic buyer a different person with a different problem? Selling to a VP of Marketing organically and to a CMO with a procurement team upmarket is arguably the same persona at a different altitude — score 0. Selling to a Head of Support organically and to a CFO in the acquired base is a true persona divergence — score 1.

Factor 2 — deal-size delta of 3x or more. Compare median ACV, never mean; means are distorted by whales. Under 3x, the pricing, packaging, discount governance, and approval mechanics are close enough to share. At 3x or more, deal-desk involvement and CPQ complexity diverge structurally.

Factor 3 — sales-cycle delta of 2x or more. Median days from opportunity-created to closed-won. A 2x delta changes pipeline coverage ratios, forecast cadence, rep capacity math, and the entire rhythm of the motion.

Factor 4 — rep skill non-transferability. Can a strong rep from the core motion drop into the candidate motion and succeed within one ramp cycle? If yes, it is one motion with coaching. A transactional closer cannot run a seven-stakeholder, procurement-gated pursuit, and a patient enterprise rep is unproductive and miserable in a high-volume seat.

Factor 5 — qualification-criteria conflict. Run the same rubric against deals in both segments. If a deal that is "qualified" under one reading is "unqualified" under the other, or the two need entirely different fields, score 1.

Factor 6 — the segment can fund a pod. This is simultaneously a scoring factor and a hard gate.

The funding floor deserves separate emphasis because skipping it is the most expensive common mistake in this decision. A healthy pod is at least three quota-carrying reps plus one first-line manager. Below three reps, the manager has nothing to manage, one rep ramping or churning is a 33%-plus capacity hit, and the pod cannot absorb normal variance. Translate that to pipeline: if a separated upmarket rep carries roughly $1.0M–$1.4M of annual quota, three reps must reliably close $3M–$4.2M, which at a 25–30% win rate and realistic ramp implies you need roughly $8M–$12M of addressable, workable annual pipeline in that segment before separation is sustainable.

This is why Factor 6 is a gate rather than just a point. A segment can score 5 of 5 on the physics factors and still be the wrong thing to separate because it only supports a rep and a half. Both statements are true at once — the physics say "different motion," the economics say "cannot afford a separate org yet" — and the resolution is an overlay, not a reorg.

A second funding consideration is management load. A separate motion needs its own first-line leader who genuinely understands its physics. A velocity manager cannot coach enterprise pursuits and will revert the team to velocity habits; an enterprise manager will over-engineer velocity deals and crush throughput. If you cannot fund or hire a motion-appropriate manager, you cannot truly separate — you can only create a sub-team that the wrong leader will slowly break.

The rubric is deliberately strict because the cost of premature separation is high and asymmetric. Most companies hit the physics-divergence threshold well before they hit the funding floor — and that gap, divergent physics with insufficient scale, is exactly the zone the overlay model was built for.

The numbers behind each structure

Abstract thresholds are easy to nod at and hard to apply, so here is what each option looks like when you attach real operating numbers to it.

A representative velocity motion. Median ACV in the $20K–$30K range, median cycle 35–45 days, one to two stakeholders, no procurement gate, no security review, demand sourced mostly from inbound and product-led signups, reps productive within one to two quarters, five pipeline stages, pipeline coverage healthy at roughly 3x, quota set bottoms-up from capacity math because the deal flow is high-volume and statistically stable.

A representative upmarket motion. Median ACV in the $90K–$180K range, median cycle 80–120 days, five or more stakeholders, procurement and legal as explicit stages, security review as a real gate, demand sourced from named-account outbound, account-based marketing across a buying committee, executive events, and partner introductions. Reps ramp over three to four quarters because the rep will not see a full cycle complete until quarter two. Seven pipeline stages. Coverage needs 4–5x because the win rate is lower and the cycle longer. Quota cannot be set purely from capacity math — the deal flow is lumpy and low-count, so a pure capacity number is either unreachable in a slow quarter or trivially beaten when two deals land together. Enterprise quota-setting blends capacity math with a top-down named-account potential view and tolerates more variance, often through rolling-four-quarter attainment rather than strict quarterly cliffs.

Blending these two produces numbers that are wrong for both. A blended coverage ratio makes you look over-covered on enterprise and under-covered on velocity, and you staff to the wrong number. A blended win rate hides which segment is actually decaying. A single ramp assumption either declares your enterprise reps failures at month four or lets your velocity reps coast for three quarters.

Comp mechanics diverge just as sharply. A velocity motion supports a higher deal-count quota, a flatter accelerator, and a fast ramp. An enterprise motion needs a lower deal-count quota, a steeper accelerator to reward the rare large land, a longer ramp, and frequently a richer base-to-variable mix because the deal cadence is lumpy and a rep cannot live on eat-what-you-kill when deals close quarterly rather than weekly. The classic force-fit failures are symmetrical: put an enterprise rep on a velocity quota and they are structurally underwater for two quarters before their first large deal lands, they panic, they down-sell to hit activity metrics, and they churn; put a velocity rep on an enterprise quota and long ramp and they coast, because the per-deal quota is too easy and the ramp removes urgency.

The cost of separation is larger than headcount math suggests. A separated pod is three reps plus a manager, but it also needs dedicated or aligned development-rep support, a named solutions-engineering or deal-desk resource, a second enablement curriculum, and motion-appropriate demand generation. Separating the closing reps while leaving a single blended demand-gen engine produces an upmarket pod starved of motion-appropriate pipeline — the SDR team measured on a single blended "meetings booked" metric will rationally feed it velocity-shaped meetings, and the upmarket AEs will spend their days disqualifying them. Always ask the demand-gen leader: if I separate the closing motion, what does the top of the funnel have to look like, and can we afford to build it?

Four worked cases show the numbers deciding the answer.

A Series B infrastructure company at $7M ARR runs a $22K median ACV, 38-day, mostly-inbound motion. The board pushes upmarket, so the CRO hires a VP of Enterprise and three AEs on $1.2M quotas. The physics divergence was real — persona, deal size, cycle, skill, and qualification would all have scored 1, for a physics score of 5. But actual workable upmarket pipeline was roughly $4M against a floor of $8M–$12M. Eighteen months later all three AEs sit below 60% of quota, the VP manages a sub-scale team, and collapsing it back reads internally as a failed strategy and a demotion. The framework's verdict was overlay, not org.

A $40M vertical SaaS company acquires a competitor with a $9M ARR base. The acquirer sells to operations leaders at $30K ACV on 45-day cycles; the acquired product sells to finance leaders at $110K on 100-day cycles with procurement and security review. That is 3.6x on deal size, 2.2x on cycle, a different economic buyer, non-transferable skills, and conflicting qualification — a 6 of 6, with the funding floor already cleared on day one. The CRO folds everything into the existing velocity process "for a clean integration." Within two quarters the acquired-segment forecast is unreliable because the velocity stages never modeled procurement, the acquired enterprise sellers are demoralized by activity metrics built for a 45-day cycle, the best of them leave, and the acquired base starts to churn because nobody is running the relationship-heavy motion it needs.

A $14M martech company sees roughly 20% of bookings arriving as $90K, 80-day, multi-stakeholder deals against a $25K, 35-day core. Rather than reorganize, the CRO documents an upmarket branch, promotes two strong AEs into overlay specialist roles with a documented 60/40 credit split, and runs the upmarket forecast category separately for three quarters. Trailing-twelve-months upmarket bookings reach $11M, comfortably above the floor, and the overlays are beating quota. Only then does a four-rep pod get formalized, with one overlay promoted to manage it — a low-drama launch, because the bench was already built and the forecast was trustworthy from day one.

A $20M HR-software company is convinced it has an SMB motion and a mid-market motion. Run honestly, the test scores near zero: same People Ops persona at a slightly larger company, $34K versus $19K median ACV (1.8x, under the threshold), 52 versus 41 days (1.3x, under the threshold), strong SMB reps succeed in mid-market within one ramp cycle, and the same lightweight qualification framework works cleanly for both. That is one motion serving two segments that differ in degree, not physics. The CRO tiers territories so more experienced reps carry more mid-market accounts — no new manager, no new comp plan, no seam to manage.

A fifth case matters because it runs backward. A $60M security company separated an enterprise motion three years ago, correctly. The product matured, the brand strengthened, and inbound enterprise demand surged; cycles compressed from 110 days to 65, stakeholder counts fell as buying committees got more educated, and the skill gap narrowed. Re-scored, the physics score had fallen to 2 — the physics had converged. The correct call was to re-merge into a segment-tiered single motion. Being willing to undo a separation is as important as being disciplined about making one.

Sequencing, qualification design, and enforcing it in the stack

The highest-leverage insight in this entire decision is that "separate motion" and "separate org" are not the same step and should almost never happen simultaneously. Run them in sequence.

Stage 1 — documented branch. Before anything structural, fork the process on paper and in the CRM: deals matching the upmarket profile follow a different qualification checklist, a different stage path, and a different forecast category. Same reps, same manager, same org — but the data now lets you see the second motion as a distinct object. Nearly free, fully reversible.

Stage 2 — overlay specialists. Designate or hire one or two specialists who ride alongside the core team and get pulled into deals matching the second motion's profile. The overlay owns a motion-shaped slice of deals across the whole team's accounts rather than a territory. The core rep stays on the deal and keeps partial credit; the overlay brings the specialized skill. This proves the physics and economics with minimal disruption and full reversibility, and it builds the bench — your future pod manager almost always comes from this pool. Define the credit split in writing before the first deal, or reps will either hoard deals away from the overlay (killing the second motion's development) or dump everything on the overlay to offload risk (overloading the specialist and corrupting the data).

Stage 3 — instrumented separate forecast. Run the second motion as its own forecast category for two to three quarters: separate coverage targets, win-rate tracking, cycle-time tracking, and attainment for the overlays. You are testing two things — does the segment independently clear the funding floor on a trailing-twelve-months basis, and is the separation score stable rather than a one-quarter artifact of a single large deal?

Stage 4 — formalize the org. Only after Stages 1 through 3 produce two to three quarters of evidence do you stand up a pod with dedicated reps, a motion-appropriate manager, a dedicated comp plan, a dedicated enablement track, and written handoff rules.

Qualification design is where the fork becomes real. A velocity motion — short cycle, one or two stakeholders, deal sizes that never trigger procurement — is best served by a lightweight, speed-preserving framework such as SPICED or a tight BANT variant, because the rep must qualify in one or two calls and the cost of a heavy rubric is lost velocity plus reps gaming CRM fields. An upmarket or acquisition-driven cross-sell motion needs a heavyweight, multi-threading framework: MEDDICC or MEDDPICC earns its weight by forcing reps to find the economic buyer, build a champion, map the decision process, and understand the paper process — precisely the things that kill large deals when missed and precisely the things a lightweight rubric never asks about.

The force-fit runs both directions. Impose MEDDICC on a velocity motion and reps either ignore it, making the data fiction, or comply with it, making the motion slow. Impose BANT on an enterprise motion and reps mark deals qualified on a budget and a timeline with no champion and no mapped procurement path — and those deals slip, slip, and die at a gate nobody investigated. In the branch phase, the efficient middle is one base framework plus a heavier gate on the upmarket path: SPICED for everyone, plus three additional required fields — economic buyer, decision process, champion — that unlock only on the upmarket record type. You get the multi-threading discipline where you need it without maintaining two full frameworks before you have committed.

Enforce all of it in the stack, or it is just a slide. Salesforce record types and sales paths are the primary mechanism: each motion's reps see only their own stages, required fields, and exit criteria, which is what makes a branch a real thing rather than an aspiration. Validation rules make the qualification difference structural rather than cultural — the upmarket record type blocks stage advancement until the economic buyer, decision process, and champion fields are populated, while the velocity record type stays light. Forecast categories must roll the second motion up as its own line; this is non-negotiable from day one because it is what makes localized forecast rot visible before it spreads. CPQ product rules and price-book gating should make it structurally impossible for an organic rep to quote the enterprise bundle at enterprise discounting, which also enforces the two motions' different approval thresholds. Routing and assignment rules encode the handoff seam — a trigger such as "ACV above a defined threshold and stakeholder count above a defined number routes to the upmarket pod" belongs in automation, not rep judgment, so the seam is consistent and auditable. And revenue-intelligence tooling should segment its analysis by motion so win rate, cycle time, and slippage are never reported blended.

The seam is the most contentious operational surface in a two-motion org. You need written rules for three things: the trigger definition that routes a deal across the seam, the credit-sharing rule when it moves, and an SLA on response time so handed-off deals do not rot. Without written rules the seam becomes a political battlefield and good deals fall through it. Set up the pod as self-contained — three-plus reps, one motion-appropriate manager, aligned development-rep support, a named solutions or deal-desk resource — and avoid the matrixed alternative where reps report to one manager, are coached by another, and forecast into a third structure. Matrix org charts are where motion clarity goes to die.

Development-rep structure should lag the AE layer by one stage. While you run one AE motion with a branch, keep a single shared SDR pool with routing rules. When you formalize a separate AE pod, that is the trigger to dedicate SDRs to it — because the prospecting skill diverges too. An SDR optimizing speed-to-lead and volume is doing a different job than one researching a named account, mapping a buying committee, and running a multi-touch sequence to a CFO. Dedicated upmarket SDRs need their own activity model, their own comp (typically higher base, lower volume target, credited on pipeline quality rather than raw count), and their own enablement.

Enablement follows the org decision with a one-quarter lag. During the branch phase, run one core curriculum plus a branch module covering the heavier qualification fields, multi-threading, procurement and security stages, and larger-deal pricing mechanics — efficient, and it keeps every rep cross-trained so re-merging stays possible. Build the second full curriculum only after Stage 4 formalization. Building two curricula before separating doubles enablement cost during exactly the phase you should be staying cheap and reversible.

Acquisitions are the one case that can legitimately compress the sequence. An acquisition can drop a fully-formed revenue base — its own reps, pipeline, qualification habits, and CRM — on day one, which changes three things. The funding floor may already be cleared, which is the rare case justifying a jump straight to Stage 4 while retaining the acquired team's motion-appropriate leadership. The integration timeline is externally imposed by a board-promised date, so a leisurely three-quarter overlay experiment is not available. And acquisitions add failure modes the organic case lacks: account collision when reps from both legacy orgs call the same logo, incompatible comp mechanics, and CRM data debt from deduplication, field mapping, and stage reconciliation. Many acquisition "motion" failures are actually data-hygiene failures wearing a motion costume, and that RevOps work should be scoped and resourced before the acquired revenue is folded into any motion. The discipline: run the separation test on the acquired revenue before the integration plan is finalized, because the integration plan should be downstream of the motion decision, not the reverse.

Finally, revisit the decision every two quarters. The correct answer migrates with scale. Below roughly $3M ARR it is almost always one motion, founder-assisted on the big deals. From roughly $3M to $10M is the branch-and-overlay zone, where physics divergence typically becomes real before the funding floor is reachable. From roughly $10M to $30M genuine separation usually becomes both warranted and affordable, and seam management becomes essential because cross-seam volume is now material. Above $30M motions tend to multiply rather than merely split — velocity, mid-market, enterprise, partner, and customer-base expansion — and the CRO's question shifts from "should I separate" to "how many motions can I run well, and which should I deliberately not run." The transition quarters are the most dangerous: a company one quarter from clearing the floor faces the strongest pull to separate now, and separating one quarter early still strands a sub-scale pod for two or three quarters while it grows into the number. Let the rubric and the funding floor decide, and accept that the structure should lag the metric, never lead it.

Related questions

When should a CRO use overlay specialists instead of a dedicated team?

When the physics score says the segments have genuinely diverged but the segment cannot yet fund three reps plus a manager. Overlays prove the motion's economics with minimal disruption, keep the decision reversible, and build the bench that staffs the eventual pod.

Can two motions share one qualification framework?

During the branch phase, yes — run one lightweight base rubric plus three additional required fields (economic buyer, decision process, champion) that unlock only on the upmarket record type. After full separation, each motion should own its framework, required fields, and stage-exit criteria.

How do you prevent account collisions after an acquisition?

Resolve ownership before folding revenue into any motion: acquired-base renewals and simple expansions stay with the existing relationship owner, cross-sell of the acquirer's products becomes a defined upmarket motion, and net-new follows whatever motion fits its physics. Encode it in routing rules.

Is it ever correct to re-merge two separated motions?

Yes. Physics converge as well as diverge — product maturity, brand strength, and buyer education can compress cycles and shrink stakeholder counts until the separation score falls below the threshold. Re-scoring every two quarters is what catches it.

What is the single most expensive mistake in this decision?

Separating on physics alone while ignoring the funding floor. A segment can score high on every divergence factor and still strand three reps below quota because the workable pipeline supports one and a half. Physics is necessary; funding is the gate.

FAQ

How much pipeline does an upmarket segment need before separation makes sense?

Roughly $8M–$12M of addressable, workable annual pipeline. The math runs backward from the pod: three reps at $1.0M–$1.4M quota must reliably close $3M–$4.2M, which at a 25–30% win rate plus realistic ramp requires that pipeline volume. Below it you are building a sub-scale team, not a motion.

What if we cannot hire a manager who has actually run the upmarket motion?

Then you cannot truly separate yet. A velocity manager will revert an enterprise pod to velocity habits; an enterprise manager will over-engineer velocity deals and crush throughput. Absent a motion-appropriate leader, stay in the overlay phase — and treat the overlay pool as the place your future manager gets grown.

Does an acquisition automatically mean a second motion?

No. Run the same six-factor test on the acquired revenue. If the acquired base sells to the same buyer at similar size on a similar cycle, it is an integration project and a data-hygiene exercise, not a second motion. The legacy-company boundary is a coincidence, not a motion boundary.

How do we split credit when an overlay specialist joins a core rep's deal?

Define a documented split before the first deal — the core rep keeps territory credit and partial commission, the overlay earns a specialist commission. Without a written rule, reps either hoard deals away from the overlay or dump everything on them, and both outcomes corrupt the evidence you are trying to gather.

Should pipeline coverage targets differ between the two motions?

Yes. A higher-win-rate velocity motion is often healthy near 3x; a longer-cycle, lower-win-rate upmarket motion typically needs 4–5x. A blended number is wrong for both and will have you staffing to a coverage figure that describes neither motion accurately.

How often should the separation decision be revisited?

Every two quarters. Segments too small to fund a pod grow into one, and separated motions sometimes converge back toward the core as product and brand mature. Treat the structure as a living decision, and re-score the rubric on current trailing data rather than the numbers that justified the original call.

Sources

• https://hbr.org/2006/07/match-your-sales-force-structure-to-your-business-life-cycle
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.bain.com/insights/topics/mergers-and-acquisitions/
• https://www.saastr.com/
• https://openviewpartners.com/blog/
• https://www.gartner.com/en/sales
• https://sloanreview.mit.edu/topic/marketing-and-sales/
• https://www.salesforce.com/resources/articles/sales-process/
• https://www.pavilion.com/
• https://www.forrester.com/blogs/category/b2b-sales/

Related on PULSE

• How to design a sales compensation plan when deal sizes vary by 5x across segments
• What pipeline coverage ratio should a CRO target by segment and cycle length
• MEDDICC vs SPICED: choosing a qualification framework that matches your sales motion
• How to structure the SDR-to-AE handoff across velocity and enterprise motions
• RevOps integration checklist for the first 90 days after an acquisition
• When to re-merge a separated enterprise sales team back into the core org