Route to market is the set of buying paths customers can take to evaluate and purchase your offer. Coverage is how you place people, partners, and digital touchpoints along those paths so the customer experience is coherent and the cost of selling stays inside your economic guardrails. When these choices are unclear, you see the same symptoms everywhere: duplicate outreach, lead leakage, stalled deals waiting for specialists, channel conflict, and expensive growth driven by late-stage discounting.
6.1 Choosing Routes: Enterprise, Mid-market, SMB, Inside, Digital, Channel
Most companies inherit their route to market. They started with founders selling enterprise deals, or with inbound SMB demand, and the motion ossified. The right route is not a philosophical preference for “field” or “inside.” It is a match between buyer friction and your ability to remove that friction profitably.
Buyer friction usually comes in two forms. Risk friction: security, integration, compliance, and change management that require trust, orchestration, and documented proof. Time friction: buyers who want fast clarity, low administrative burden, and predictable onboarding. Risk friction tends to favor enterprise field-led motions with specialist support; time friction tends to favor inside, digital, or partner motions with standardized offers.
Use deal behavior, not company size, to set routing rules. A $40K deal that requires a formal security review and multiple departments behaves like an enterprise. A $250K renewal with limited change behaves like a low-friction transaction. The practical routing variables are: number of stakeholders, technical depth, procurement rigor, required services effort, and the customer’s tolerance for standardization. Pair those with economics: ACV, gross profit, payback targets, and expected expansion.
Rule of thumb: if the fully loaded cost of the motion is likely to exceed one-third of year-one gross profit for the segment, either move the segment to a lower-cost route or redesign the offer (package services, reduce customization, raise price, or shorten cycle).
Most mature B2B companies run a small portfolio of motions, each with a clear “default journey”:
- Enterprise field-led: named-account AEs run multi-stakeholder sales processes, supported by SDRs, solutions engineers, and exec coverage. Use when proof and risk mitigation are central to winning and retaining.
- Mid-market hybrid: inside-led with selective field support, or field-led with tighter standardization and shorter cycles. Use when deals justify consultative selling but must still scale.
- SMB inside high-velocity: full-cycle reps or SDR-to-AE pods, standardized bundles, tight stage gates, and fast follow-up. Use when buyers can evaluate quickly and implementation is repeatable.
- Digital/product-led: self-serve evaluation and conversion, with “sales assist” for higher tiers, complex security reviews, or expansion. Use when time-to-value is fast and usage signals intent.
- Channel-led: partners originate, influence, resell, or deliver; your team enables and co-sells selectively. Use when partners have reach, trust, or delivery capacity you cannot build economically.
The biggest operational risk is running multiple motions on the same account with no rules. Customers receive conflicting outreach and internal teams fight over ownership. Fix this with explicit route rules tied to ICP and deal type: who owns inbound from a named account, when an inbound request is routed to inside versus field, how partner-registered deals are protected, and what thresholds trigger escalation to a higher-touch motion.
Template: route-to-market rules (one page per segment).
- Default route: field, inside, digital, channel, or hybrid—defined in one sentence.
- Entry criteria: ICP threshold, deal size band, and complexity triggers.
- Ownership: who owns first response, who owns the opportunity, and who owns renewal/expansion.
- Specialist triggers: when SE/security/implementation resources engage.
- Exceptions: what requires approval and what information is needed.
Routes should evolve as your business matures. As implementation becomes more standardized and proof accumulates, you can “graduate” segments into lower-cost motions. Conversely, as you move upmarket, you may need to add field coverage, executive sponsorship, and deeper technical validation. Treat route changes like product changes: define criteria, pilot, measure conversion and retention impact, then scale.
6.2 Coverage Model: Roles, Ratios, Territories, Specialization, Overlays
Coverage is not an org chart; it is a division of labor. The objective is to put the right work in the right role, with clear decision rights, so customers experience continuity and your cost to serve remains sustainable. When coverage is poorly designed, expensive roles do low-value tasks, specialists become bottlenecks, and managers cannot enforce standards because accountability is diffuse.
Start by defining roles in terms of outcomes owned. Titles vary, but four ownership questions must be answered: who owns pipeline creation, who owns new bookings, who owns adoption and renewal risk, and who owns expansion. In many companies, confusion between sales and customer success is the root cause of churn and internal conflict. Make it explicit: customer success owns adoption outcomes and renewal risk management; sales owns commercial negotiation and expansion above an agreed threshold; both share one account plan and one set of success metrics.
RACI rule: every customer-facing activity has one accountable owner, even if multiple roles contribute. “Shared responsibility” is a polite way to say “nobody owns it.”
Ratios force realism and surface bottlenecks early. Use ratio ranges as starting points, then calibrate to your motion by measuring time demand. If a typical enterprise deal consumes 15–25 hours of solutions engineering and you expect 50 such deals per quarter, you can estimate SE capacity and avoid starving the field at quarter end.
- SDR to AE: often 1:1 in enterprise outbound; 1:2–1:3 in mid-market; higher leverage in SMB when inbound is strong.
- SE to AE: often 1:2–1:4 in enterprise; 1:4–1:6 in mid-market; pooled SE support in SMB.
- Manager to reps: target 1:6–1:8 in complex sales to preserve coaching; wider spans typically reduce forecast accuracy and deal quality.
Territory and account assignment should optimize coverage quality, not just perceived fairness. A rep needs enough potential and enough near-term opportunity to hit quota without chasing low-fit deals. In enterprise, named-account coverage is usually superior because it enables multi-threading and longer-cycle account plans. In mid-market, vertical specialization can improve relevance and proof. In SMB, rigid ownership often adds more friction than value; pooled coverage with clear routing rules can be more efficient.
Specialization is a trade-off between depth and coordination cost. Specialize when repetition materially improves win rate, cycle time, or price realization—especially in regulated or mission-critical categories. Stay more generalist when speed and volume are the constraint and when standardization and automation can carry the motion. If you do specialize, design clean handoffs and compensation so teams do not compete for credit.
Overlays are how you add expertise without reorganizing the whole field. They work when they are deployed at specific moments and measured on outcomes, not on activity. They fail when they become shadow sellers or when they are pulled into every deal by default.
Template: overlay rules of engagement.
- When they engage: segment/deal-size thresholds and risk triggers (security, integration, regulated data).
- What they deliver: proof selection, technical validation, solution design, or competitive strategy.
- How they hand back: required notes, artifacts, and next steps for the core seller.
- How success is measured: win rate and cycle-time impact in supported deals, plus reduced delivery variance.
A coverage model is “done” when it can be explained simply to the field: which roles exist, what each owns, how accounts are assigned, and what triggers specialist support. That clarity is what allows managers to inspect pipeline quality and deal behavior against a consistent standard.
6.3 Lead Management And Handoffs: Where Funnels Go To Die (And How To Fix)
Companies can spend millions generating demand and still miss targets because the conversion system between interest and opportunity is leaky. Funnels die in three places: slow response, unclear ownership, and inconsistent qualification. Fixing those does not require a new tool; it requires shared definitions, routing discipline, and enforced service levels.
Begin with definitions that are tight enough to inspect. Agree on what a lead is, what qualifies as marketing-qualified, what constitutes sales-qualified, and what evidence is required to create an opportunity. Use evidence-based language. “High intent” is not evidence; “requested a demo and fits ICP-A” is evidence. Keep definitions segment-specific if needed: SMB may allow lighter evidence; enterprise should require the right persona and a clear trigger before consuming expensive AE time.
Closed-loop reporting is what turns definitions into improvement. Require every lead that is recycled or rejected to have a reason code, and review those codes weekly with both marketing and sales. Over time you will see patterns: leads are being rejected because the persona is wrong, because the trigger is weak, because contact data is missing, or because the account fails ICP. Each pattern suggests a different fix—targeting changes for marketing, sequence changes for SDRs, or ICP guardrails that prevent low-fit leads from consuming capacity.
Next, set response-time standards and make them visible. Inbound intent decays quickly, and delayed follow-up teaches buyers you are not serious. A practical standard is one hour for inbound demo requests from target accounts during coverage hours, and 24 hours for everything else. The exact number matters less than consistent measurement and management attention.
Routing rules must include a “what if they don’t act” clause. If a lead is assigned and ignored, it has effectively been thrown away. Build timers and auto-reroutes: if a lead is not accepted within X hours, reroute; if contact attempts fail after Y touches over Z days, recycle to nurture with a reason code; if the lead re-engages, it re-enters with priority and context.
Template: lead-to-opportunity SLA.
- Assignment logic: by segment, territory/account owner, and partner registration status.
- Acceptance criteria: ICP score, persona, trigger, and minimum data fields required.
- Activity standard: the minimum outreach sequence before recycling.
- Qualification standard: what must be true for an opportunity to be created.
- Recycle loop: reason codes and routing back to nurture or back to SDR follow-up.
Handoffs between SDRs and AEs are a frequent source of customer frustration. The buyer repeats themselves, context is lost, and momentum stalls. For higher-value segments, require a structured handoff note (trigger, pain, success criteria, stakeholders, next step) and, when feasible, a brief live introduction where the SDR tees up the AE and confirms the next meeting outcome. This small discipline raises conversion and improves customer experience.
Inspect lead management in one weekly forum: speed-to-lead, acceptance rates, meeting-to-opportunity conversion, and recycle reasons by segment and source. Then tune the system monthly. A lead system is never “finished”; it must evolve with campaigns, ICP changes, and capacity constraints.
6.4 Capacity Planning: Headcount Model, Ramp, And Productivity Curves
Capacity planning turns aspiration into math. It forces you to answer: do we have enough productive selling capacity to hit the number, and if not, what combination of hiring, productivity improvement, and motion change closes the gap? Without this discipline, organizations react late—usually with discounting or rushed hiring—and pay for it in margins and retention.
Start with a cohort-based view. Separate fully ramped reps from ramping reps, and model productivity by segment and motion. Use medians, not averages, because a few stars can hide a weak middle. Then build the simplest capacity equation you can: productive headcount times median productivity, adjusted for ramp and attrition.
Template: capacity model inputs (per segment/motion).
- Starting headcount: fully ramped, ramping, and open roles.
- Hiring plan: start dates and expected ramp curve (time to first pipeline, time to first close).
- Attrition: expected departures and backfill timing.
- Productivity: median bookings per fully ramped rep per period.
- Pipeline constraint: expected qualified pipeline per rep given win rate and cycle time.
Model ramp explicitly and conservatively. Many plans fail because they assume reps are fully productive in six months when, in reality, pipeline takes time to build and proof takes time to earn. If you lack good data, use a step approximation and then tighten it as you collect cohort evidence.
Productivity curves matter as much as averages. Build the plan with an explicit productivity lift, not just hiring. The best levers are usually tighter ICP enforcement, a small set of proven segment plays, and manager coaching focused on early-stage deal quality.
Connect capacity to pipeline coverage. If your plan implies each rep will close $X, it also implies a pipeline requirement of roughly $X divided by win rate, adjusted for cycle time. If pipeline creation capacity (marketing, SDRs, partners) cannot supply that volume at the right ICP quality, adding AEs will not help. It will simply create “thin territories” and encourage low-fit pursuits.
Plan with time phasing. A hiring plan that looks fine in annual totals can still miss quarters because hires start late, ramp is slower than assumed, or territories are reshuffled mid-year. Build the plan by quarter and include a conservative “slip” factor for hiring and onboarding. Then define contingency moves in advance: temporary specialist pods for the highest-value deals, redeploying capacity from lower-priority segments, or tightening qualification to protect seller time when pipeline is thin.
Finally, model constrained roles in parallel. Solutions engineers, implementation, legal, and customer success often cap growth before AEs do. Build a demand-based capacity view for each: how many security reviews, implementations, and renewal escalations are implied by the sales plan? If those teams are overloaded, you will see longer cycles and higher churn. It is better to slow new bookings intentionally than to sell work you cannot deliver reliably.
Checklist: the five most common capacity-plan errors.
- Assuming linear ramp when ramp is lumpy and pipeline-dependent.
- Ignoring attrition and the productivity dip during territory reshuffles.
- Planning AE headcount without confirming pipeline creation capacity.
- Understaffing specialist and delivery roles that sit on the critical path.
- Setting quotas and territories that force reps into low-ICP deals to survive.
A good capacity plan produces decisions early: which segments get incremental headcount, which get motion changes, which get enablement investments to improve productivity, and which should be deprioritized until economics and delivery are ready.
6.5 Coverage Economics: CAC Payback Logic For B2B Sales Models
Coverage choices must be economically defensible. It is easy to justify high-touch field selling as “what enterprise needs” or to assume partners are “cheaper.” The truth is segment- and motion-specific. Coverage economics gives you a common language to compare motions and to set thresholds that prevent expensive growth.
Define CAC by motion with enough completeness to avoid wishful thinking. Include base and variable compensation, management cost, SDR and marketing costs attributable to sourced pipeline, specialist time, partner incentives, and a reasonable allocation of sales operations and enablement. Precision is less important than consistency. If you undercount SE and delivery involvement, enterprise motions will look artificially attractive.
Template: CAC and payback snapshot (per segment/motion).
- Total acquisition cost: direct selling + pipeline generation + specialist support + channel costs.
- New ARR or bookings: for the same segment and period.
- CAC per $ of ARR: total cost ÷ new ARR (or per customer if that is more meaningful).
- Gross profit rate: after variable delivery costs and typical discounting.
- Payback months: CAC ÷ monthly gross profit from the acquired ARR.
- Retention assumption: gross retention and expected expansion that justify the motion.
Use payback alongside a retention-informed lifetime value view, but keep it disciplined. Higher CAC is justified only when retention and expansion are proven. Compare a conservative base case (current gross retention, no expansion) to a growth case (expansion backed by real plays and capacity). If the motion only works in the growth case, treat it as a risk and staff accordingly.
Payback is the fastest reality check because it ties your sales engine to capital efficiency. If payback is too long, you have only a few levers: raise realized price (better proof and discount discipline), lower sales cost (route the segment to a cheaper motion, increase reuse and automation), shorten cycle time (stage discipline and better de-risking), improve win rates (ICP and plays), or improve retention and expansion (adoption and customer outcomes).
Economics also helps you set routing thresholds. If inside selling produces slightly lower win rates but materially lower CAC, it may be the superior motion for a segment—provided retention and customer experience remain acceptable. Conversely, a field motion may be justified even with higher CAC if it produces significantly higher deal size, stronger retention, and repeatable expansion. For channels, include the gross margin impact of partner discounts, rebates, and services economics; “cheaper CAC” is not helpful if the margin pool shrinks.
Rule of thumb: treat unnecessary discounting as an acquisition cost. A 5-point discount on a one-year contract reduces gross profit just like extra headcount does, and it often lengthens payback more than leaders expect.
When service effort is material, use contribution margin payback rather than gross margin payback. If a segment requires heavy implementation labor or ongoing support, gross margin can look healthy while delivery capacity is silently becoming the constraint. Contribution margin payback forces the conversation about packaging services, charging appropriately, and setting commercial red lines that prevent “free work” from accumulating as hidden CAC.
Review coverage economics quarterly by segment and motion, and compare to the guardrails you set in Chapter 3. Then make one clear decision each cycle: scale the motion, redesign the motion, or stop investing in it until the economics improve. When you do this consistently, route-to-market debates become faster, less political, and anchored in what the business can sustain.
