B2B Go-To-Market Motion Selection Procedures

How to Select a B2B Go-to-Market Motion for Predictable Pipeline

To execute B2B go-to-market motion selection that produces predictable pipeline, run these five sequenced procedures. You will need four quarters of pipeline data, ACV benchmarks, segment definitions, and partner economics. The full process takes 4 to 6 weeks. The Starr Conspiracy recommends starting with the ACV-fit diagnostic against your demand states before committing to any motion or blend.

A note before you start: all thresholds in this piece are starting points we commonly see. Calibrate them to your own baseline before you lock anything in.

Step Summary

1. Run an ACV-fit diagnostic to identify viable motions.
2. Design a hybrid PLG plus sales-assist motion with PQL thresholds.
3. Build an outbound ABM motion for high-ACV segments.
4. Design a partner GTM motion with channel-conflict guardrails.
5. Resolve channel conflict using a deal-routing matrix.

Most GTM motion posts stop at labels. This one gives you prerequisites, gating thresholds, artifacts (ACV-Motion Fit Matrix, PQL specification, named-account play library, partner guardrails and scorecard, deal-routing matrix), and routing rules you can run in RevOps. Run it before annual planning, before comp changes, or before adding a new channel. Skip a prerequisite and the downstream step produces noise. Run them in order and you get a board-defensible GTM blend grounded in your economics, not vendor taxonomy.

Prerequisites / What You Need Before Starting

Assemble the following before Step 1. Each item is verifiable. If you cannot produce it, stop and source it first.

• Pipeline data, last four quarters. Closed-won ACV by segment, sales cycle length, and win rate by source. Pulled from your CRM with finance sign-off. If your CRM data is unreliable, fix attribution and stage definitions first.
• Segment definitions. ICP tiers (Tier 1, Tier 2, Tier 3) with named accounts in each, totaling at least 80% of TAM coverage. If you have never formalized ICP tiers, work through our ICP definition guide before continuing.
• Product self-serve readiness audit. A binary answer to whether a buyer can sign up, activate, and reach first value without sales contact.
• Partner economics, if applicable. Margin share, deal registration history, services capacity, territory coverage, and resale versus referral split for the last 12 months.
• Executive sponsor. A CRO or CEO who will arbitrate channel-conflict decisions in Step 5, and a marketing leader who co-owns the motion stack.

If you think you do not have time for this, compare it to the cost of one quarter of misrouted pipeline.

Step 1, Run a GTM Motion Fit Diagnostic

Run an ACV-fit diagnostic to map each segment to a viable primary and supplementary motion. RevOps owns the analysis. The CRO signs off. Output is the ACV-Motion Fit Matrix, a one-page artifact mapping each segment to a primary and supplementary motion. Time required is roughly 5 business days. Economics gates design here: if you cannot audit it monthly, it is not a motion.

1. Pull blended ACV by segment for the last four quarters from your CRM. Confirm finance has signed off on the calculation before moving on.
2. Map each segment to a starting band. ACV under $5K with high self-serve readiness points to PLG as primary; $5K to $25K typically requires hybrid PLG plus sales-assist; $25K to $150K is the sales-led range with ABM on Tier 1; above $150K demands outbound ABM and often partners for coverage. Confirm each band reflects your last four quarters of closed-won, not a competitor's playbook.
3. Verify each band against CAC payback and sales cycle length. CAC payback should come in under 18 months in every band before you lock the motion; if it exceeds that window, the motion is not economically viable as stated.
4. Document exceptions. Land-and-expand with modular pricing can justify PLG at higher ACV. Trivial implementation with sales cycles under 30 days can justify sales-light motions at lower ACV. Strategic accounts, M&A targets, and existing partner-of-record relationships also get carve-outs and route through the executive sponsor, not the matrix. Write the exceptions into the matrix, not into tribal knowledge.
5. Produce the one-page ACV-Motion Fit Matrix with columns for segment, ACV band, primary motion, supplementary motion, and verification metric. Confirm CRO and finance sign-off before proceeding.

Verification checklist. Finance signed off on ACV; bands reflect your own closed-won; CAC payback under 18 months per band; exceptions documented; CRO and finance sign-off captured.

If win rate varies more than 15 points across sources inside a single segment, your attribution is lying and the matrix will be too.

Gating decision. If the matrix surfaces any segment in the $5K to $25K band, proceed to Step 2. If any segment lands above $25K, also run Step 3. If partners appear in any band, also run Step 4. Every team runs Step 5.

A signed ACV-Motion Fit Matrix tells you which motions to build, which to skip, and which segments get a hybrid. That reduces forecast volatility because every motion has an economic rationale tied to a measurable control point.

If your matrix puts any segment in the hybrid band, go to Step 2.

Step 2, Design a Hybrid PLG Plus Sales-Assist Motion

Design a hybrid PLG plus sales-assist motion with explicit PQL thresholds for any $5K to $25K ACV segment. Most PLG versus sales-led debates collapse a blending problem into a binary. Marketing Ops and RevOps co-own this. Output is the PQL specification. Time required is 7 to 10 business days. A sloppy hybrid creates CAC creep on deals that would have self-serve converted: the failure signature is sales-assist reps logging "qualified" touches on accounts that had already hit activation and would have upgraded on their own.

1. Define the PQL signal stack. Typical triggers include workspace creation with 3 or more invited users, completion of a core activation event within 7 days of signup, and usage above a defined threshold. Confirm each signal can be instrumented in product analytics before publishing the spec.
2. Set the usage threshold by analyzing your last 200 closed-won self-serve accounts and identifying the median usage pattern at conversion. The threshold has to reflect your own baseline, not an industry estimate.
3. Write the handoff rule in one sentence. Example for Company A, Segment Tier 2: "When a PQL fires on a Segment Tier 2 account, route to the named sales-assist rep within 4 hours." Codify the rule in CRM routing, not in a Slack channel.
4. Define the sales-assist role narrowly. They remove friction and surface expansion paths. They do not pitch. Tie comp to expansion ARR, not net-new logo credit.
5. Instrument tracking for PQL-to-opportunity conversion, sales-assist-touched ARR, and self-serve cannibalization. Tracking must be live before launch, not bolted on later.
6. Review 30 days of post-launch data. Cannibalization should stay under 30%; if higher, raise the threshold and re-test.

Verification checklist. Signals instrumented; threshold derived from your 200-account baseline; handoff rule in CRM; comp aligned to expansion; tracking live pre-launch; 30-day cannibalization under 30%.

What if you want PLG at $150K ACV? It can work when the entry SKU is modular, expansion is usage-driven, and implementation is trivial. Otherwise, do not force it.

Gating decision. If cannibalization stays under 30% and PQL-to-opportunity exceeds 15%, the motion is healthy and you proceed to Step 5. If either fails for 2 consecutive months, kill the motion or rework thresholds.

A documented PQL specification with thresholds, handoff rules, and tracking prevents CAC creep from sales-assist touching deals that would have closed self-serve.

Step 3, Build an Outbound ABM Motion for High-ACV Segments

Build an outbound ABM motion for any segment Step 1 placed above $25K ACV. The procedure starts with account selection, not message development. Marketing and Sales co-own the list. Output is the named-account play library. Time required is 10 to 15 business days. ABM is how you turn high-ACV theory into capacity-aligned coverage.

1. Build the Tier 1 target list by intersecting ICP fit score with intent signals and trigger events such as funding rounds, executive hires, or technology adoption changes. The intersection logic has to be reproducible, not curated by hand.
2. Cap Tier 1 at the number of accounts your sales team can credibly cover, typically 50 to 150 per rep per year. If the list is 5,000 accounts, it is not ABM, it is a spreadsheet.
3. For each Tier 1 account, document a buying committee map (roles and names for economic buyer, champion, blocker, end user). Attach the map to the CRM account record, not a shared drive.
4. Build a 90-day touchpoint sequence across at least 3 channels, with measurable plays, content assets, and orchestration owners per channel. Each play needs an engagement threshold that triggers SDR outreach.
5. Match message to where each committee member sits using the Ten Demand States framework, rather than treating the account as a single buyer. Map message variants to roles before launch.
6. Confirm marketing and sales co-own the list with shared pipeline targets before launching any outreach, and verify quarterly that account coverage rates exceed 80%.

Verification checklist. Reproducible list logic; cap matches rep capacity; committee maps in CRM; per-play engagement thresholds; role-mapped messaging; shared targets with marketing.

If Tier 1 engaged-account rate diverges from Tier 1 pipeline coverage by more than 20 points, the play is reaching the wrong roles.

Gating decision. If engaged-account rate exceeds 30% within 90 days, scale to Tier 2 with a lighter play. If under 15%, the list or the play is wrong. Stop and rebuild.

A named-account play library with committee maps, sequences, and engagement thresholds prevents rep capacity waste and CAC creep on accounts with no buying signal.

Step 4, Design a Partner GTM Motion With Channel-Conflict Guardrails

Design partner guardrails before recruiting partners. Partner GTM fails most often because the guardrails were written after the first conflict. RevOps and Channel leadership co-own this. Output is the partner guardrails document and scorecard. Time required is 10 to 15 business days. Documented rules turn partner pipeline into a forecastable line instead of a wildcard.

1. Define the partner motion type explicitly. Referral partners send leads and receive a fee. Resellers transact and own the client relationship. Co-sell partners run joint sales motions with shared pipeline. Each partner agreement names exactly one type.
2. Pick one type per partner tier. Mixing types inside a single tier guarantees conflict. Document the tier-to-type mapping in the partner program charter.
3. Write the deal registration policy before signing any partner agreement. Specify who owns an opportunity when a direct rep and a partner both engage the same account, the lookback window, and the escalation path. Set the window by analyzing your last 20 disputes and choosing the duration that would have prevented them, typically 60 to 90 days. Legal and the executive sponsor sign the policy.
4. Set margin and capacity guardrails. Cap partner-sourced deals by services capacity to prevent implementation backlogs. Enforce the cap in deal-desk approval, not in spreadsheets.
5. Build a partner scorecard tracking sourced pipeline, influenced pipeline, deal registration accuracy, and partner-led win rate versus direct. Auto-populate the scorecard from CRM, not by hand each month.
6. Review the scorecard quarterly with your executive sponsor. Deal registration disputes should stay under 5% of partner-touched deals.

Verification checklist. Single motion type per agreement; tier-to-type mapping in the charter; signed registration policy with lookback window; capacity cap enforced in deal desk; auto-populated scorecard; quarterly executive review on the calendar.

Track your own dispute rate as the proof, not a vendor's white paper. No registration rules, no partners.

Gating decision. If partner-sourced win rate trails direct by more than 15 points after 2 quarters, retrain or restructure the tier. If disputes exceed 5%, the registration policy has a gap.

Step 5, Resolve Channel Conflict Using a Deal-Routing Matrix

Build a deal-routing matrix to govern any GTM stack running 3 or more motions concurrently. Conflict at that point is structural, not behavioral. The Starr Conspiracy delivers the deal-routing matrix as a standard artifact in multi-motion GTM integration engagements. RevOps owns it. The CRO arbitrates. Time required is 5 to 7 business days for the build, plus monthly reviews. Routing without rules is just letting the loudest rep win, and the cost is disputed deals, slower speed-to-lead, and lower coverage.

1. Build a two-axis matrix. Rows are deal origin signals (self-serve signup, inbound demo request, outbound SDR meeting, partner-registered deal, ABM-account engagement). Columns are deal characteristics (ACV band, segment tier, geography, product line). Every active motion needs at least one row.
2. Populate each cell with a routing rule and a credit-split policy. Example: a self-serve signup from a Tier 1 ABM account routes to the named-account rep with full credit, not to sales-assist. For multi-product accounts, route to the rep owning the highest-ACV product line with split credit to secondary owners. Credit rules have to be reflected in the comp plan, not just the matrix.
3. Configure CRM routing to match the matrix exactly. Manual overrides require executive sign-off, and override volume should be auditable monthly. See our RevOps governance guide for routing configuration patterns.
4. Instrument two metrics: time-to-route (median hours between deal origin and rep assignment) and disputed deals as a percent of total. Both metrics should be visible in the weekly RevOps review.
5. Review monthly for the first quarter, then quarterly. Update rules when a new motion or product line ships. The review cadence belongs on the executive sponsor's calendar.
6. Audit 20 routed deals per month. Disputed deals should stay under 5%; if higher, the matrix has a gap and needs a new rule.

Verification checklist. Every motion mapped to a row; credit rules in the comp plan; CRM routing matches the matrix; override volume audited monthly; time-to-route and dispute rate in weekly review; 20-deal audit each month.

CRO versus CMO and partner leader versus direct sales are the two fights this artifact settles. If credit and comp do not align with the matrix, the matrix loses.

Gating decision. If disputes stay under 5% and time-to-route stays under 4 hours for 2 consecutive quarters, move to quarterly cadence. If either exceeds threshold, return to monthly until stable.

Once the five steps are live, the cadence is the operating system: rerun Step 1 annually, review Step 5 quarterly, and tune PQL thresholds in Step 2 monthly during the first two quarters of a hybrid launch. That cadence is what keeps pipeline predictable.

Common Mistakes to Avoid

• Skipping the ACV-fit diagnostic in Step 1. Teams pick a motion based on what competitors are doing or what the CRO ran at their last company. This produces motion-segment mismatches that show up as inflated CAC and stalled pipeline 9 to 12 months later. Always start with your own data.
• Setting PQL thresholds too low in Step 2. A low threshold floods sales-assist with accounts that would have self-serve converted, inflating CAC and cannibalizing margin. If you cannot point to median usage from 200 closed-won accounts, you do not have a threshold, you have a guess.
• Treating ABM as a list in Step 3. Buying a 5,000-account list and calling it ABM is the most common failure pattern. Real ABM caps accounts at rep coverage capacity, builds committee maps, and runs multi-touchpoint plays. Below that bar, it is volume marketing with extra steps.
• Signing partner agreements before writing the deal registration policy in Step 4. Once the first conflict happens, every subsequent policy change feels like a takeaway to the partner. Write the rules first, then recruit partners against them.
• Assuming CRM routing in Step 5 is enforceable without comp alignment. A routing matrix without aligned credit rules gets overridden the first time a rep escalates. Fix it by aligning credit splits to matrix outcomes and requiring executive sign-off on every override. Every month you run conflicting motions, you create disputed deals, slower speed-to-lead, and lower coverage.

What to Do Next

Run Step 1 this week, get CRO sign-off on the ACV-Motion Fit Matrix, then pick a build path from the gating decisions. Run it before you lock next quarter's targets or comp plan.

If you are seeing disputed deals, slow speed-to-lead, or channel fights, Step 5 is the fix. Talk to The Starr Conspiracy about a GTM motion selection and integration sprint. You leave with a signed ACV-Motion Fit Matrix, PQL specification, partner guardrails, and a deal-routing matrix your CRO will enforce.

Related Questions

How do I decide between outbound, ABM, and partnerships for high-ACV deals?

Use the ACV-fit diagnostic in Step 1. Above $150K ACV, outbound ABM is usually the primary motion because deal economics justify named-account coverage. Partnerships become the supplementary motion when you need geographic, vertical, or implementation coverage your direct team cannot provide. Outbound without ABM at this band wastes rep capacity on accounts with no buying signal.

Can a company run PLG and sales-led motions at the same time?

Yes, and most B2B SaaS firms we work with at scale run both. The blending mechanism is the PQL threshold and the sales-assist handoff rule in Step 2. The failure mode is running them as separate organizations with separate pipelines, which produces internal competition for the same accounts. Treat PLG and sales-assist as one motion with two entry points. See the Ten Demand States framework for matching motion entry points to buyer context.

What about sales-led without ABM for mid-ACV segments?

For $25K to $75K ACV segments with shorter cycles and single-threaded buying, sales-led without full ABM works. Run a lighter targeting model: tier accounts by ICP fit and intent, route inbound and outbound to AE pods with shared SDR coverage, and skip the committee-map artifact. Verify with engaged-account rate and AE capacity utilization. If win rate trails Tier 1 ABM segments by less than 10 points, the lighter model is holding.

When does community-led growth work as a primary GTM motion, and how do I evaluate it?

Community-led works as primary when your product has high peer-to-peer learning value (developer tools, design platforms, analyst-facing software) and buyers research inside community spaces before evaluating vendors. To evaluate viability as a mini-procedure: (1) confirm at least 30% of self-reported buyer journey touchpoints originate in community spaces; (2) identify an owned or earned community surface where your category is actively discussed; (3) instrument attribution from community touchpoint to pipeline; (4) run a 90-day pilot with one community surface and measure community-sourced pipeline as a percent of total. If under 10% after 90 days, demote to supplementary. For most B2B categories, community amplifies PLG or ABM rather than standing alone.

How do I handle multiple products with different ACVs?

Treat each product line as its own row in the Step 5 routing matrix with its own ACV band from Step 1. Define primary ownership by the highest-ACV product on the account, with split credit to secondary product owners based on attach rate. Comp must reflect the split or reps will route around the matrix. Re-run Step 1 per product line annually and reconcile motion assignments at the account level quarterly.

How often should I revisit my GTM motion selection?

Rerun the ACV-fit diagnostic annually and after any material change: a new product line, a pricing model shift, entry into a new segment, or 2 consecutive quarters of pipeline miss. The deal-routing matrix in Step 5 needs quarterly review. PQL thresholds in Step 2 need monthly review during the first 2 quarters of a hybrid launch, then quarterly.