Sales model is one of the most consequential operational choices a revenue team makes, and it is often picked implicitly rather than deliberately. This page defines the six common B2B sales models, shows when each fits, lays out how to pick between them, and shows how the CRM has to support each one. Written for operators making the call.
Teams running without an explicit sales model choice hit six consistent problems. Team structure gets inconsistent, metrics do not match the motion, and comp plans produce weird incentives. Six patterns show up on every sales-model intake conversation we run with revenue leaders.
Many teams run on an implicit sales model that nobody wrote down. The implicit model drifts over time as reps join and leave. Different team members think different models are in play. The implicit nature produces friction at every quarterly review.
Teams running mismatched metrics (PLG conversion metrics on an outbound team, enterprise cycle-length metrics on a transactional team) produce misleading dashboards. The metric mismatch leads to bad decisions about hiring, quota, and process. Explicit model picks drive the right metric set.
When comp plans do not match the sales model, incentives work against the motion. An AE paid on outbound sourced revenue on a PLG motion will refuse to help with trial conversions. Comp has to match the model. The mismatch creates team friction that erodes culture.
Team structure (SDR, AE, CS, specialist ratios) depends heavily on sales model. Transactional teams need different structure than enterprise teams. Teams with the wrong structure for their model carry excess cost or miss productivity. Model clarity drives structure.
CRM pipeline stages, forecast categories, and workflow automation all depend on sales model. Enterprise teams need different stage definitions than velocity teams. CRM configuration that does not match the model produces data quality problems that compound over quarters.
Scaling a sales team without model clarity amplifies drift. New reps join with assumptions from their last role, which may be a different model. Without explicit model documentation, each hire introduces variance. By 50 reps the team is running three implicit models in parallel.
Six sales models cover most B2B revenue teams in 2026. Each has clear fit criteria (deal size, cycle length, ICP, motion). Starting with explicit model selection is the first step toward operational clarity.
Transactional sales: deals typically under $25K ACV, cycle under 30 days, inside-sales rep handles end-to-end from lead to close. Common in SMB SaaS, services under $5K/mo retainer, and some mid-market point tools. Volume-heavy, process-automation-heavy.
SMB velocity sales: deals typically $5K-$50K ACV, cycle 2-6 weeks, 2-3 meeting close typical. Common in horizontal SMB SaaS, point tools, and transactional services. Inside-sales model with light SDR support. Depends on strong inbound and self-serve trial.
Mid-market consultative: deals typically $30K-$150K ACV, cycle 60-120 days, 4-7 meeting close with multi-threaded buying committee. AE-led with SDR support. Common in vertical SaaS, integrated platforms, and higher-ACV services. Discovery and demo quality drive win rate.
Enterprise strategic: deals typically $150K-$1M ACV, cycle 6-18 months, 10+ meeting close with 7+ stakeholder buying committee. AE plus SE plus CS plus specialist team. Common in enterprise SaaS, integrated platforms, strategic consulting. Account-based with named accounts.
Product-led growth: self-serve trial converts most users; sales team assists on larger teams and expansion. ACV ranges from $10K to $100K+ depending on segment. Cycle varies. Sales assist model with usage-triggered outbound. Common in developer tools, horizontal SaaS, modern productivity.
Enterprise ABM: strict named-account list, orchestrated outbound across marketing, SDR, AE, and executive sponsorship. Deal size typically $250K-$5M ACV. Cycle 9-24 months. Common in enterprise software, strategic infrastructure, and large consulting. Highest cost-to-serve.
The sales model choice follows from five business decisions. Making each decision explicitly produces a clear model pick. Trying to pick a model without the five decisions produces drift.
The median deal size in your ICP largely determines the model band. Under $25K ACV points at transactional. $25K-$50K at SMB velocity. $30K-$150K at mid-market consultative. $150K+ at enterprise strategic. The deal-size band is the first filter.
The typical buying committee size on your deals determines whether an AE-led or multi-role team is right. Under 3 stakeholders: AE-led. 3-7 stakeholders: AE plus SE support. 7+ stakeholders: full enterprise team (AE+SE+CS+specialist). The committee size drives team structure.
Typical cycle length determines pipeline math and comp timing. Under 30 days: transactional. 30-90 days: SMB velocity. 90-180 days: mid-market. 180-540 days: enterprise. The cycle length also determines quota attainment measurement cadence.
Inbound-heavy pipeline (80 percent inbound) fits SMB velocity and PLG models. Balanced inbound-outbound (50-50) fits mid-market consultative. Outbound-heavy (70 percent outbound) fits enterprise strategic and ABM. The pipeline source mix determines team structure and comp.
Product complexity determines self-serve viability. Simple products with low complexity support PLG. Medium complexity supports consultative models. High complexity (configuration, integration, change management) requires enterprise models with SE support. Complexity drives sales effort per deal.
The CRM has to be configured to match the sales model. Six configuration areas differ meaningfully: pipeline stages, forecast categories, team structure, metrics, workflow automation, and reporting cadence. Strkr supports all six models natively.
Pipeline stages differ by model. Transactional: lead, qualified, closed-won/lost (3-4 stages). Mid-market consultative: discovery, demo, proposal, negotiation, closed (6-7 stages). Enterprise: discovery, qualification, demo, technical validation, business case, procurement, close (7-9 stages). The right stage set depends on model.
Forecast categories: transactional typically uses commit and best-case only (2 categories). Enterprise typically uses commit, best-case, pipeline, and omitted (4 categories). The additional categories support longer cycles with more judgment required on uncertain pipeline. The category set is a model choice.
CRM role permissions should match the team structure for the model. Transactional: inside-sales reps with full-cycle access. Enterprise: AE, SE, CS, specialist all with scoped visibility. The permission matrix enforces the team structure rather than relying on behavior norms.
The default metrics in the dashboard should match the model. Transactional focuses on volume, cycle length, win rate, ADS. Enterprise adds pipeline coverage, forecast accuracy at multiple horizons, named-account coverage, multi-threading rate. The metric defaults drive what the team actually tracks.
Workflow automation differs: transactional needs lead-routing speed and SLA automation. Enterprise needs approval chains, SE routing, and ABM orchestration. The automation set should match the model complexity. Over-engineering automation for a transactional team adds friction; under-engineering for enterprise leaves gaps.
Review cadence should match cycle length. Transactional: daily pipeline reviews, weekly team metrics. Enterprise: weekly deal reviews, monthly team metrics, quarterly named-account reviews. The cadence should match the pace at which useful signal actually accumulates.
A real sales management CRM has to support all six models through configuration rather than being locked to one. Strkr delivers model flexibility across five dimensions.
Pipeline stages are fully configurable per tenant. Transactional teams run 3-4 stages. Enterprise teams run 7-9 stages. The CRM does not force a stage count. Model choice drives stage design.
Forecast categories are tenant-configurable. Teams can run commit and best-case only (transactional) or add pipeline and omitted (enterprise). The forecast math adjusts to the category set. Model choice drives category design.
Role permissions use a hybrid model: workspace roles for broad access, per-entity membership for fine-grained scoping. The flexibility supports simple structures (transactional) and complex structures (enterprise AE+SE+CS+specialist). One permission system covers both.
Dashboard defaults vary by role and can be tuned per tenant. Transactional dashboards emphasize volume, cycle, win rate. Enterprise dashboards emphasize coverage, forecast accuracy, named-account coverage. The dashboard engine supports both without separate products.
Workflow engine supports light automation (transactional SLA timers, lead routing) and heavy automation (enterprise approval chains, ABM orchestration). The engine scales with model complexity. Teams scale up automation as they move upmarket without replacing the CRM.
The comparison for revenue teams expecting their sales model to evolve as they scale.
| Feature | Strkr | Single-model-optimized CRM |
|---|---|---|
| Transactional model support | Native | Varies |
| SMB velocity model support | Native | Varies |
| Mid-market consultative support | Native | Usually native |
| Enterprise strategic support | Native | Often requires upgrade |
| PLG model support | Native | Often weak |
| Enterprise ABM support | Native | Often requires enterprise tier |
| Model transition without migration | Configuration change | Often requires tier upgrade or migration |
| Three-year TCO (30 reps) | Roughly $54K-$81K | $120K-$300K depending on tier |
Common thread: documented the model, matched metrics and comp, configured the CRM, and avoided drift as the team scaled.
A 10-rep early-stage SaaS team wrote down the PLG sales model explicitly on day one. Metrics (self-serve conversion, assist-rate, expansion-rate), comp (expansion-based), and team structure (sales assist model) all aligned. The clarity avoided the typical implicit-model drift as the team grew to 25 reps.
A 30-rep team transitioning from transactional (sub-$25K ACV, inside sales) to mid-market consultative (midmarket $50K-$100K ACV, AE-led with SDR) reconfigured their Strkr pipeline stages, forecast categories, and dashboards during the transition. The CRM did not have to be replaced. The configuration change supported the model shift.
A 150-rep enterprise team documented their enterprise ABM playbook (named account list, orchestrated motion across marketing + SDR + AE + exec sponsorship) and configured Strkr for it. Named-account coverage metrics, multi-threading rate, and multi-horizon forecast accuracy all showed up in the dashboard. The clarity cut model-ambiguity friction in reviews.
A 50-rep mid-market team realized they had been running PLG-style metrics on a mid-market consultative motion. Fixing the metric set in Strkr (adding pipeline coverage, forecast accuracy at 30-day and 90-day, multi-threading rate) produced a dashboard that actually matched the motion. Decisions got better in the quarter after the fix.
A 40-rep hybrid team ran a dual-model: PLG for SMB prospects (sub-$30K ACV), mid-market consultative for larger prospects ($30K-$150K ACV). Strkr supported both motions through per-team configuration: different pipeline stages, dashboards, metrics, and comp plans. The team avoided running the two motions on different CRMs.
Start a 14-day Strkr trial with configurable pipeline stages, forecast categories, role permissions, dashboards, and workflow automation for any of the six B2B sales models. From $15 per seat per month, no tier upgrade for enterprise motion.
A sales model is the operational pattern a revenue team uses to acquire and expand customers. It covers the ICP deal-size range, the buying committee size, the cycle length, the inbound-outbound pipeline mix, and the team structure (SDR, AE, SE, CS, specialist ratios). The six common B2B sales models are transactional, SMB velocity, mid-market consultative, enterprise strategic, product-led growth, and enterprise ABM.
Five decisions drive the choice: median deal size in your ICP, typical buying committee size, typical cycle length, inbound-outbound pipeline mix, and product complexity. Each decision maps to the model band. Deal size under $25K points at transactional. $25K-$50K SMB velocity. $30K-$150K mid-market consultative. $150K+ enterprise strategic. Picking the right model is making the five decisions explicitly.
Yes, especially at scale. Hybrid teams often run PLG for SMB (self-serve + sales assist) and consultative or enterprise for larger prospects (AE-led with SE support). The dual-model approach requires different metrics, different comp plans, and different team structures for each motion. The CRM has to support dual configuration without requiring two separate CRMs.
Model transitions are common: SMB velocity teams moving to mid-market consultative as ACV grows, enterprise strategic teams adding ABM to specific accounts. Transition requires reconfiguring pipeline stages, forecast categories, dashboards, team structure, and comp plans. If the CRM supports configuration change rather than requiring tier upgrade or migration, the transition is manageable. Strkr supports this.
Six areas differ: pipeline stages (3-4 for transactional, 7-9 for enterprise), forecast categories (2 for transactional, 4 for enterprise), team role permissions (simple for transactional, complex for enterprise), default dashboards and metrics, workflow automation complexity, and reporting cadence (daily for transactional, quarterly for enterprise). The CRM has to be configurable across all six to match the model.
Teams scale through model transitions. A SaaS team starting PLG often adds mid-market consultative at Series B and enterprise at Series C. A CRM that locks to one model forces replacement at each transition. Strkr is designed for configuration flexibility across all six models so the CRM scales with the team. Three-year TCO comparison vs tier-based CRMs is 2-4x lower because the tier upgrades disappear.
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.
