Examples of B2B sales motions, by segment. The pipeline shape, the cycle, and the CRM configuration that fits each.
B2B sales is not one motion. The SaaS SMB inbound funnel runs 20 days with a 25% close rate. Enterprise field sales runs 180 days at 7%. Services account development runs a different shape again. Strkr adapts to the motion instead of forcing yours into a template.
The phrase "B2B sales" covers at least five distinct motions: SMB inbound (20 to 45 day cycle, high volume), mid-market consultative (60 to 90 days), enterprise field (120 to 240 days), SaaS product-led upsell (lower-touch), and services account development (quarterly cycles, deep account depth). Each motion wants a different pipeline shape, different stage definitions, different forecasting cadence, and different coaching rhythm. Most CRMs assume one motion and bend awkwardly for the others. The six pain points below are the ones that come up on every B2B team evaluating a motion-aware CRM.
One pipeline for every motion
SMB and enterprise deals on the same stages make noise.
A team selling to SMB and enterprise simultaneously ends up with two very different cycles sharing one pipeline. The stage conversion rate blends 25% SMB win rates with 7% enterprise win rates into a meaningless 12% average. Forecasting is impossible because the two cohorts behave nothing alike. Strkr supports multiple deal paths per workspace with path-specific stages, exit criteria, and SLAs so each motion stays legible.
MEDDPICC on every deal including the $5k ones
The methodology bloat kills high-velocity motion.
A $5k SMB deal does not need Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition captured on the record. The qualification depth is overkill for the deal size and the AE spends more time on the methodology than on the deal. Strkr allows per-deal-path qualification methodology (BANT for SMB, MEDDPICC for enterprise, Challenger for services) so the discipline matches the deal.
Forecast cadence mismatched to cycle
Weekly forecasts on a 180-day cycle is noise.
Weekly forecast submissions make sense for a 30-day SMB cycle where deals genuinely change state week to week. On a 180-day enterprise cycle, the same deal says "committed" for 12 straight weeks and the forecast ritual loses meaning. Strkr allows per-motion forecast cadence (weekly for SMB, bi-weekly or monthly for enterprise) so the ritual matches how deals actually move.
Enterprise deals need deal rooms; SMB does not
Attaching a mutual action plan to a $3k deal is overkill.
Enterprise deals need deal rooms with mutual action plans, exec sponsors tracked, procurement workflows mapped. SMB inbound deals need an email reply and a demo book. Forcing deal-room primitives on SMB adds overhead without value; omitting them on enterprise loses deals. Strkr makes the deal-room feature set a per-deal-path configuration, visible when needed and hidden otherwise.
Comp plans mix across motions
The AE comping on SMB velocity is also chasing enterprise logos.
When one AE works both SMB inbound and enterprise outbound, the comp plan ends up pulling the AE in two directions: velocity on small deals, patience on large ones. The AE ends up over-indexing on whichever motion the comp plan rewards more clearly. Strkr tracks per-motion production so the comp plan can be structured deliberately per motion or the team can be segmented into motion-specific roles.
Services sales does not fit the SaaS mold
A services sell is relationship depth, not pipeline stages.
Services sales (consulting, agency, implementation) is less about discrete deal stages and more about account development: deepening a relationship, generating repeat engagements, cross-selling practice areas. Classic SaaS pipeline stages (Discovery, Proposal, Negotiation, Closed) feel awkward because engagements overlap and renew. Strkr supports an account-development view alongside the pipeline view for services teams, so the primary unit of work is the account relationship over quarters rather than the discrete deal.
B2B sales by segment
The five motions, their shapes, and the CRM configuration behind each.
The sections below cover the five most common B2B sales motions with concrete examples: pipeline stages, cycle length, win rate benchmarks, qualification methodology, forecast cadence, and the Strkr configuration that fits. The point is not to prescribe one motion as correct; it is to make the design choice conscious so the CRM matches the business instead of the other way around. The nine cards cover the operational pieces that distinguish each motion.
SMB inbound SaaS
30-day cycle, 25% win rate, product demo-driven.
SMB inbound SaaS deals come from form fills on the marketing site, often around pricing or demo pages. Cycle is 20 to 45 days. Win rate is 20 to 30% depending on fit. Qualification is BANT-complete at demo. Comp plan rewards velocity. Strkr configuration: inbound deal path with four stages (Lead, Qualified, Demo, Closed), BANT fields on the deal, weekly forecast cadence, deal-room primitives hidden.
Mid-market consultative SaaS
60-90 day cycle, 15% win rate, multi-threaded.
Mid-market SaaS deals need multi-stakeholder discovery, a proof of concept or pilot, and procurement engagement. Cycle is 60 to 90 days. Win rate is 12 to 18%. Qualification is MEDDPICC-light with the Economic Buyer and Decision Process emphasized. Strkr configuration: mid-market deal path with six stages including POC, MEDDPICC-light fields, bi-weekly forecast, mutual action plan optional, exec sponsor tracked.
Enterprise field sales targets named accounts with a dedicated team (AE, SE, AM, exec sponsor). Cycle is 120 to 240 days. Win rate is 5 to 10%. Qualification is full MEDDPICC with Paper Process and Competition tracked explicitly. Strkr configuration: enterprise deal path with eight stages, full MEDDPICC fields, monthly forecast, mandatory mutual action plan, deal-room with document assembly for proposal and SOW.
SaaS product-led upsell
14-day cycle, driven by usage signals.
Product-led SaaS teams run upsell motions triggered by usage signals (seat count hitting a threshold, feature use hitting a plan boundary, engagement score climbing). Cycle from signal to close is often 7 to 21 days. Qualification is "usage already fits" so the sales motion is more consultative than qualifying. Strkr configuration: upsell deal path triggered by product-event webhooks, two stages (Signal, Closed), tight automation on the signal-to-outreach workflow.
Services account development
Quarterly rhythm, account-depth-driven.
Consulting, agency, and implementation services teams sell engagements rather than products. A single account may generate three to six engagements per year across practice areas. Cycle per engagement is 30 to 90 days but the account relationship runs multi-year. Strkr configuration: account-centric view with engagement objects underneath, cross-practice-area tracking, QBR cadence, expansion-focused forecasting.
Mid-market services
Agency and consulting selling into $50-500k engagements.
Mid-market services firms (agencies, boutique consultancies) sell engagements between $50k and $500k. The buyer is a VP or Director; the sales cycle is 45 to 90 days. The deliverable scope is custom per engagement, so the proposal takes significant SE and partner time. Strkr configuration: services deal path with scope and SOW fields, PandaDoc integration for proposal delivery, resource-availability check on the deal.
SMB outbound
Cold-sourced small-dollar deals; sequence-driven.
SMB outbound teams source cold leads through SDR sequences into small-business targets. Cycle is 30 to 60 days (longer than SMB inbound because the lead is not self-identified). Win rate is 5 to 10%. The motion is high-volume per SDR but low revenue per deal. Strkr configuration: outbound deal path with sequencing stages, tight stage SLAs, meeting-booked webhook triggers.
Enterprise strategic
Few named accounts, long cycles, exec-led.
Enterprise strategic motions target 10 to 30 named accounts with CEO or GTM-leader involvement. Cycle can run 12 to 24 months. One deal represents significant revenue. The data captured on the account is deeper than the deal, because the relationship cycle outruns any single deal. Strkr configuration: strategic-account view with multi-year relationship tracking, exec engagement log, deal-room with full document assembly and procurement workflow.
Partner-sourced enterprise
Reseller or SI-sourced large deals.
Partner-sourced enterprise deals come through systems integrators (SIs) or resellers who have an existing relationship with the end buyer. Cycle is 90 to 180 days. Win rate is 2 to 3x direct enterprise because the partner is pre-qualified. Strkr configuration: partner deal path with partner org attached, deal registration lock, revenue share tracking, partner-visible deal room for collaboration.
The CRM configuration that makes each motion work
Pipeline design, qualification, forecast, and tooling.
A CRM configuration that fits an SMB inbound motion will break an enterprise field motion and vice versa. The cards below are the configuration pieces that distinguish a motion-aware CRM setup from a template-driven one. Strkr customers tend to run these configurations in parallel across deal paths so each motion has the right discipline without any single motion dictating the shape of the others.
Per-motion pipeline stages
4 stages for SMB inbound; 8 stages for enterprise.
Stage count should scale with cycle length. SMB inbound (4 stages: Lead, Qualified, Demo, Closed) because the cycle is too short for finer-grained tracking. Enterprise (8 stages: Lead, MQL, SQL, Discovery, POC, Proposal, Procurement, Closed) because the cycle warrants precision. Strkr's multi-path pipeline design makes this per-motion decision cleanly without forcing a compromise.
Per-motion qualification
BANT for SMB; MEDDPICC for enterprise.
Qualification methodology should match deal complexity. BANT (Budget, Authority, Need, Timing) for SMB inbound. MEDDPICC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition) for enterprise. Challenger-style for services sales. Strkr ships methodology as a per-deal-path field set so the AE sees the right prompts for the deal in front of them.
Per-motion forecast cadence
Weekly for SMB; monthly for enterprise.
Forecast cadence should match cycle. Weekly for SMB (deals genuinely change state week to week). Bi-weekly for mid-market. Monthly for enterprise (weekly is noise on a 180-day cycle). Services teams typically forecast quarterly on account development with monthly check-ins. Strkr allows per-motion forecast cadence with distinct submission locks and manager override layers.
Deal room on strategic deals
Mutual action plan + document assembly + procurement workflow.
Strategic deals above a configurable value threshold (typically $50k ARR) get a deal room: mutual action plan with buyer and seller tasks, document assembly for proposal and SOW, procurement workflow with security review and legal review stages tracked. Below the threshold, the deal uses the simpler flow. Strkr enables deal-room primitives per-deal-path and per-value-threshold.
Comp plan clarity
Per-motion production tracked separately.
When one AE works multiple motions, the comp plan should split the production tracking so the AE sees SMB velocity and enterprise logos as separate scorecards. Strkr tracks per-motion deal credit automatically and surfaces per-motion attainment on the AE scorecard. The comp plan can reward velocity on SMB and logo count on enterprise without the two motions crowding each other out.
Methodology templates per path
The CRM prompts the right discipline for the motion.
A BANT template on an SMB deal is three required fields with a quick-fill UX. A MEDDPICC template on an enterprise deal is eight required fields with a champion-strength scoring layer. Strkr renders the methodology template per deal path so the AE experience matches the motion. The template is a workspace setting, not a per-deal addition, so adoption does not depend on rep motivation.
Hybrid motions and segment transitions
Teams that run multiple motions and move deals between them.
Many B2B teams run more than one motion simultaneously, and some teams move deals between motions over the deal's life (an SMB deal that expands to mid-market, an inbound lead that moves to enterprise field, a product-led signup that becomes a strategic account). The cards below are the operational patterns Strkr supports for teams running hybrid motions or managing segment transitions over the account lifecycle.
Segment reassignment
An SMB account grows into mid-market; the deal path transitions.
A customer that started at 15 seats grows to 150 seats and moves from SMB inbound to mid-market consultative. Strkr supports deal-path transition with history retention: the original path transitions complete, the new path starts with pre-populated history, and the account scorecard reflects both lifetimes. The feature prevents the "SMB rep keeps a 150-seat account" problem that happens by default when CRMs do not model segment reassignment.
Product-led to sales-led handoff
A free-tier signup hits the trigger threshold.
Product-led signups accumulate in a product database. When a signup hits a trigger (seat count, feature use, engagement score, invoice attempt), Strkr creates a deal on the appropriate deal path and assigns to an AE with the usage signal attached. The handoff is deterministic rather than depending on an SDR scanning product data in a separate tool. The automation is a flow trigger that reads from product-event webhooks.
Account-to-opportunity split
One account with multiple active deal paths at once.
A mid-market account may have an active expansion deal on one path and a new-product-line deal on another at the same time. Strkr's account record carries the deals-across-paths view so the account team sees everything in play without flipping between pipelines. The account scorecard aggregates across paths for the exec-level account health view.
Partner-direct hybrid
A partner opens; the direct AE closes.
Partner-sourced deals sometimes transition to direct for close (the partner opens, the direct AE runs discovery through close with the partner engaged). Strkr's deal-path transition captures the partner credit at open and the direct AE credit at close with the revenue-share policy applied automatically. The adjudication rule is deterministic and the partner tier sees the correct credit without a weekly reconciliation meeting.
Services-plus-SaaS
The implementation engagement and the SaaS deal track together.
Teams selling SaaS with required services (implementation, training, custom build) run two parallel but related deals: the SaaS subscription and the services engagement. Strkr links the two with a parent-child relationship so the forecast reflects both revenue streams and the delivery team sees the services commitments as the SaaS deal closes.
Account development alongside opportunity
The account relationship outlives any single deal.
For services and enterprise strategic motions, the account relationship data (exec contacts, past engagements, open commitments, strategic context) outlives any single deal. Strkr's account record holds this data with its own cadence (QBRs, strategic planning docs, exec sponsor rotation) while the deals come and go. The account view is the primary unit of work for strategic motions, not the deal.
Head-to-head
Strkr vs Salesforce Sales Cloud for multi-motion B2B teams.
Salesforce Sales Cloud is the common incumbent for B2B teams running multiple sales motions. The surface can be configured for anything, but the configuration cost (admin headcount, time to deploy, change management) tends to grow faster than the business does.
How B2B teams actually run multiple motions on Strkr.
Teams that choose Strkr for multi-motion B2B tend to do it because the alternative is a Salesforce admin team they do not want to pay for. The playbooks below are motions live on customer accounts today.
B2B SaaS, $8M ARR, SMB + mid-market
Split one pipeline into two deal paths; forecast accuracy climbed 18 points.
An $8M ARR B2B SaaS team ran SMB inbound and mid-market consultative on one pipeline. Forecast accuracy sat around 61% because the two motions blended into one noisy funnel. The team split into two deal paths in Strkr with path-specific stages, SLAs, and forecast cadence (weekly for SMB, bi-weekly for mid-market). Within one quarter the SMB forecast accuracy climbed to 83% and the mid-market to 76%. The exec team stopped the Monday "why did we miss again" meeting that had been running for three quarters.
Enterprise field team, 14 reps, 2 managers
Deal-room assembly cut proposal cycle from 11 days to 4 days.
A 14-rep enterprise field team closed deals at $85k average ACV. The proposal and SOW assembly ran 8 to 11 business days per deal because the SE, legal, and finance back-and-forth happened across email, Google Docs, and DocuSign. Strkr's deal room with document assembly, PandaDoc integration, and procurement workflow dropped proposal cycle to 4 to 5 days. The 6-day acceleration per deal across 60 deals a year is roughly 360 reclaimed days of sales-cycle time, which the team used to work more deals rather than compress each one.
Services agency, 8 account directors
Account-development view replaced the engagement pipeline.
An 8-AD services agency sold engagements averaging $120k with 3 to 6 engagements per year per strategic account. The CRM pipeline felt wrong because engagements overlapped and renewed. Strkr's account-development view made the account record the primary unit with engagements as sub-objects. The ADs stopped forcing engagements into stage columns and started working account-depth plays. Account-level revenue climbed 23% in the following four quarters as the ADs got better at cross-practice-area selling.
Product-led SaaS, $4M ARR, 10 person team
Product-event webhooks drove the sales handoff automatically.
A $4M ARR product-led SaaS team had a 5-person sales team scanning product usage data manually to spot upsell signals. The team found roughly 60% of upsell-ready accounts; the rest aged out. Strkr's product-event webhook triggers created deals on the upsell path when a signup hit seat-count or usage thresholds. The sales team captured 95% of upsell-ready accounts and the upsell-sourced ARR grew roughly 2.1x year over year.
Hybrid team, SaaS + implementation services
Linked deals surfaced the services forecast correctly.
A hybrid SaaS-plus-implementation team sold the SaaS subscription and the implementation engagement as two deals. Before Strkr, the services forecast was always 60 to 90 days behind the SaaS forecast because the services deal only opened when the SaaS deal closed. On Strkr with parent-child linked deals, the services forecast opened at the same time as the SaaS deal and tracked through implementation delivery. The services team got 90 days of advance capacity planning that let the business accept two large deals in Q3 without rushing to hire mid-engagement.
A CRM that fits whichever B2B motion you actually run.
Start a 14-day trial with multi-path pipelines, per-motion qualification, per-motion forecast cadence, and deal-room primitives all live. Pilot the configuration against your actual pipeline and see the forecast accuracy climb.
Five common motions. SMB inbound (short cycle, high volume, product-demo-driven, BANT qualification). Mid-market consultative (60 to 90 day cycle, multi-stakeholder, MEDDPICC-light, pilot or POC phase). Enterprise field (120 to 240 day cycle, named-account team-based, full MEDDPICC, mandatory mutual action plan, deal room). Product-led upsell (triggered by usage signals, short cycle, usage-pre-qualified). Services account development (quarterly rhythm, account-depth-driven, engagements overlap and renew). Each motion has distinct pipeline shape, qualification depth, forecast cadence, and tooling needs. A B2B team of any size typically runs two to four of these in parallel, which is why multi-path CRM design matters more than any single motion's features.
Can one AE run multiple motions, or should each AE be motion-specific?
The pragmatic answer depends on deal volume and complexity. An AE running pure SMB inbound can handle 40 to 80 deals a quarter because the cycle is short and the qualification depth is shallow. An AE running pure enterprise field handles 4 to 8 strategic deals a quarter because the cycle is long and the account depth is deep. The two profiles want different skills, different pacing, and different comp plans. When one AE does both, they tend to over-index on whichever motion is lower-friction (usually SMB) and let strategic deals drift. Most teams past $5M ARR split into motion-specific roles. Below $5M ARR, hybrid roles can work if the comp plan explicitly tracks per-motion production and the manager coaches each motion separately. Strkr's per-motion scorecard surfaces the split production so the hybrid pattern is observable.
How does enterprise B2B differ structurally from SMB B2B beyond cycle length?
Four structural differences. Buyer committee size: enterprise averages 6 to 10 decision influencers versus 1 to 2 for SMB. Risk aversion: enterprise buyers escalate security and legal reviews that SMB buyers rarely run. Procurement process: enterprise deals go through a formal procurement workflow (vendor registration, security questionnaires, redlined contracts) that adds 30 to 90 days. Internal champion requirement: enterprise deals rarely close without a strong internal champion who navigates the committee; SMB deals often close with the direct contact. The structural implications for the CRM are that enterprise deals need mutual action plans, champion-strength scoring, exec sponsor tracking, document assembly for proposals and SOWs, and a procurement workflow. SMB deals need almost none of those; forcing them on produces friction without upside.
Should a services firm use a sales CRM at all?
Services firms benefit from a CRM but a classic SaaS-centric pipeline often fits awkwardly. Services sales is less about discrete deal stages and more about account development: deepening relationships, generating repeat engagements, cross-selling practice areas. Strkr supports an account-development view alongside the pipeline view, where the account record is the primary unit of work with engagements as sub-objects. The view supports QBR cadence, exec-sponsor tracking, cross-practice-area engagement patterns, and multi-year relationship health. For services firms that have been resisting classic CRMs because the pipeline model felt wrong, the account-development framing usually fits what the business actually needs. The pipeline view stays available for discrete new-engagement deals, so both lenses are present.
How many deal paths should a growing B2B team run?
The right number tracks business stage and segment coverage. One path is almost always too few past $2M ARR because inbound and outbound mix badly on the same pipeline. Two paths work for a team running one scaled motion plus founder-led. Three to four paths fit a team running SMB inbound, mid-market consultative, enterprise field, and expansion. Five or more paths usually indicates either a true multi-motion business (justified) or over-fragmentation of what should be one or two paths (not justified). The design test is whether each candidate path has meaningfully different stage conversion rates, cycle times, and qualification depth; if two candidates behave similarly on all three dimensions, they are one path. Strkr can support an arbitrary number of paths technically, but admin cognitive load caps the useful ceiling around five to six.
How does Strkr handle a B2B team running on Salesforce today?
Migration from Salesforce to Strkr is a common pattern for teams that have outgrown the admin overhead or want multi-motion configuration without the specialist headcount. Strkr ships a Salesforce migration tooling package that preserves account and contact history, deal data with stage transitions, custom fields, user roles, and audit trail. The tooling runs in sandbox mode first so the team can preview the migration before committing. Teams migrating off Salesforce typically run both systems in parallel for 2 to 4 weeks while the new motion-aware configuration is validated. Strkr is HIPAA compliant with BAA available, SOC 2 Type II in progress through 2026-Q4, and GDPR plus CCPA compliant, so the compliance posture required for a Salesforce replacement is in place. The open REST API with webhooks covers the integration surface for Marketo, Pardot, or any other adjacent system the Salesforce stack included.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
