How do you build a concrete SDR-to-AE handoff protocol for a $1M ARR vertical SaaS in 2027?

What changes by company stage

The single biggest mistake vertical SaaS teams make at $1M ARR is importing a handoff protocol designed for a company ten times their size. MEDDPICC-grade qualification checklists, dedicated sales ops headcount, a routing engine with territory logic, and a formal "SQL committee" all exist because larger companies have enough volume that the cost of process is amortized across hundreds of handoffs a month. At $1M ARR in a vertical — say roofing contractors, veterinary practices, independent pharmacies, municipal utilities, or specialty clinics — you are probably running one to three SDRs against two to four AEs, and passing somewhere between 25 and 80 meetings a month total. Process that assumes volume will collapse under that arithmetic.

What actually changes stage to stage is not the *existence* of a handoff standard but its enforcement mechanism. Below roughly $500K ARR, the founder is usually still selling and the handoff is verbal — a Slack message, a calendar invite, a two-minute hallway sync. That works because the founder holds the entire context in their head and the volume is low enough to remember every deal. It stops working the moment the founder stops taking every call, which for most vertical SaaS companies happens somewhere between $700K and $1.5M ARR. That's the transition you're managing.

At $1M ARR specifically, three forces converge. First, you now have enough meetings that AEs start silently triaging — they show up cold to the ones that look weak, which produces no-shows and bad first calls, which SDRs then read as "the AEs don't respect my meetings." Second, you have enough historical closed-won data (probably 30 to 120 customers) to actually define what a good-fit account looks like in your vertical, which you couldn't do at $300K. Third, compensation starts to matter: at $1M ARR the SDR is likely on a base plus a per-meeting or per-SQL variable, and any ambiguity in what counts as "delivered" becomes a monthly argument that eats management time and morale.

Between $1M and $3M ARR, the protocol should stay deliberately thin — one qualification bar, one payload, one SLA, one rejection path. Past $3M to $5M, you add routing rules, segment-specific bars, and a disqualification taxonomy that feeds marketing. Past $10M you add the ops headcount to maintain it. But adding the $10M apparatus at $1M produces a document nobody reads and a set of required fields SDRs learn to fill with garbage in eleven seconds. The protocol has to be small enough that it is genuinely followed every single time, because a rule followed 60% of the time is worse than no rule: it produces false confidence in the pipeline number.

There's also a vertical-specific wrinkle worth naming. In horizontal SaaS, the SDR can lean on firmographic proxies — headcount, funding stage, tech stack — because those correlate loosely with fit across many industries. In a vertical, those proxies are nearly useless. Two twelve-person veterinary practices can be completely different buyers depending on whether they run their own lab, whether they're part of a corporate group, and which practice management system they're locked into. So the qualification bar in a vertical handoff protocol is built from domain facts, not firmographics: the specific software they're replacing, the specific workflow that's breaking, the specific regulatory or seasonal deadline that creates urgency. That's harder to collect and much more valuable when it arrives.

Stage-by-stage playbook

Build the protocol in five passes, in this order. Do not skip to step three because steps one and two feel like documentation busywork — the definitions are the protocol; everything else is plumbing.

Pass one: define the bar from closed-won data, not from a framework. Pull your last 30 to 60 closed-won deals and your last 30 to 60 closed-lost-after-first-meeting deals. Look for the two or three domain facts that separate them. In a vertical you'll usually find something blunt and specific — "they're on the legacy incumbent and their contract renews within nine months," or "they have more than four locations," or "the office manager, not the owner, runs scheduling." Write down the two or three facts that showed up in most wins and rarely in the fast losses. Those become your bar. Two or three criteria. Not eight. If you can't get statistical confidence at this sample size — and you usually can't — treat it as a hypothesis you'll revise quarterly rather than a law.

Pass two: define the payload. This is the set of fields the SDR must populate before the meeting is considered handed off. Keep it to five to eight fields, and make every one of them something the AE would otherwise have to ask on the call. A workable payload for a $1M vertical SaaS: current system in use; the specific workflow that's broken and one verbatim quote about it; who's on the call and their role in the decision; approximate account size in whatever unit your vertical measures (locations, providers, trucks, doors, beds); any compelling event with a date; and the source of the lead. Verbatim quotes matter more than picklists — one sentence in the prospect's own words does more for an AE's first call than four dropdown selections.

Pass three: set the clock. Two SLAs, both short. The AE accepts or rejects the handoff within a defined window — a few business hours is typical, and one business day is the outer bound before the SDR loses the ability to re-engage a cooling prospect. And the meeting itself should sit within a few business days of the qualifying conversation; the further out you book, the worse your show rate, and in verticals with owner-operators who work in the field, that decay is steep.

Pass four: build the rejection path. This is the part most teams skip, and skipping it is why handoff protocols rot. An AE must be able to reject a meeting, and rejection must require a reason from a short fixed list — wrong size, no compelling event, wrong persona, already evaluated us, out of scope for the product, or bad contact data. Rejected meetings go back to the SDR with the reason attached, and the SDR gets one recycle attempt before the account goes back to nurture. Without this, AEs reject informally by ghosting the meeting, and you lose the data.

Pass five: wire it to money and to the weekly meeting. SDR variable pays on *accepted* meetings, not booked ones. And once a week, for twenty minutes, the sales lead reviews every rejection from the prior week with both parties in the room. That meeting is the actual enforcement mechanism — not the document.

The auto-accept branch deserves a note. It feels wrong to reward AE silence with an accepted meeting, but the alternative — meetings that sit in limbo indefinitely — is worse, because it converts an operational failure into an SDR compensation dispute. Auto-accept on SLA breach, flag it, and let the weekly review handle the pattern if one AE is chronically silent. The protocol should fail toward the SDR being paid and the problem being visible.

Numbers that matter at each stage

Instrument five things. More than five and nobody looks at any of them.

Acceptance rate. Accepted meetings divided by handed-off meetings. This is the health metric for the protocol itself. If acceptance is very high — near-universal — your bar is either genuinely well-calibrated or, more likely, your AEs have decided rejection isn't worth the friction. Sample five accepted meetings a month and ask the AE whether they'd have taken it knowing what they know now. If acceptance is low, you have a definition problem, not a people problem: the SDR and AE do not agree on what qualified means, and no amount of coaching fixes a definitional gap.

Show rate on first meetings. This is where booking latency shows up. Track it against days-from-qualification-to-meeting and you'll usually find a clean decay curve. Vertical SaaS with owner-operator buyers — contractors, restaurant owners, small clinic owners — decays faster than verticals selling to office-bound administrators, because the buyer's day is unpredictable. If your show rate is materially worse than your peers' reported benchmarks, look at booking latency and confirmation cadence before you look at SDR quality.

SQL-to-opportunity rate. Of the meetings AEs accepted and held, how many produced a real opportunity? This is the downstream truth test. Acceptance measures whether the AE *believed* the meeting was good at handoff; this measures whether it *was*. A wide gap between the two — high acceptance, low opportunity conversion — means your qualification criteria are picking up enthusiasm rather than fit. That's the most common failure mode in verticals where the product demos well.

Rejection reason distribution. The mix matters more than the total. Heavy "wrong size" means your targeting list is bad — that's a marketing and data problem, not an SDR problem. Heavy "no compelling event" means your bar is too permissive or your SDRs are being pushed on meeting quota. Heavy "wrong persona" in a vertical usually means the SDRs haven't learned the org chart of the buyer yet, which is a two-week training fix.

Time-in-stage for Handoff Pending. Median and 90th percentile. The median tells you the normal case; the 90th tells you whether one AE is a black hole. Both should be well inside your SLA.

On the compensation side, the arithmetic at $1M ARR is worth spelling out. If an SDR is expected to produce somewhere in the range of 10 to 20 accepted meetings a month and your acceptance rate is 80%, they need to book 13 to 25. If acceptance drops to 60%, they need to book 17 to 33 for the same pay — a 30%+ increase in activity for identical earnings. That is the real reason acceptance rate is a compensation metric and not just an ops metric: every point of acceptance you lose is a direct pay cut for the SDR, and they will feel it before you see it in a dashboard. Publish acceptance rate weekly, by SDR and by AE. Making it visible is most of the fix.

One more number: the cost of a bad handoff. An AE's first meeting plus prep plus follow-up is roughly an hour of loaded cost. At $1M ARR with three AEs, twenty bad meetings a month is sixty hours — most of a full-time person's month — burned on calls that were never going to work. That's the budget you're protecting, and it's usually larger than the cost of the process you're avoiding building.

Decision framework

When something in the handoff is broken, the diagnostic order matters. Teams reflexively reach for coaching or for a new tool, and both are usually wrong first moves.

The through-line: definition problems masquerade as effort problems. An SDR who books meetings the AE doesn't want is almost never lazy — they're optimizing correctly against a target that was specified wrong. Fix the specification before you touch the person.

There's a corollary about tooling. At $1M ARR you do not need a routing engine, a conversation intelligence platform, or a dedicated handoff app. You need CRM fields, a stage, a notification, and a report. If your CRM can't express "required fields on stage change" and "notify the owner," that's worth solving; anything beyond that is premature. Teams that buy tooling to fix a definitional problem end up with a well-instrumented version of the same disagreement.

Adjacent workflows this protocol touches

The SDR-to-AE handoff is one link in a chain, and tightening it exposes the links on either side.

Upstream: marketing-to-SDR. The same contract logic applies one step earlier. If marketing passes MQLs with no agreed bar, the SDR spends their day disqualifying, and their accepted-meeting rate suffers through no fault of their own. The lightweight version: a source-level acceptance report. Which channels produce leads that become accepted meetings? In vertical SaaS the answer is often unglamorous — association memberships, trade shows, referral from an adjacent vendor, and inbound from a comparison page — while paid social produces volume that never survives contact with the qualification bar. Run the same rejection-reason analysis on the marketing handoff and you'll find the targeting fix faster than any campaign optimization.

Downstream: AE-to-onboarding. The handoff protocol you build for SDR-to-AE is a template you'll reuse at closed-won, and the failure modes rhyme. The AE knows the customer's workflow, their timeline, their internal champion, and the three things they were promised; if none of that survives into implementation, the customer's first thirty days are spent re-explaining themselves. In vertical SaaS, where switching costs are high and word travels fast within the industry, a bad onboarding handoff is disproportionately expensive — one unhappy practice or contractor talks to a dozen peers at the next association meeting. Build the closed-won payload the same way: five to eight fields, all things the implementer would otherwise have to ask.

Sideways: the AE-to-AE and rep-turnover case. At $1M ARR you will lose or reassign a rep, and every open deal needs to move. A team that already has a payload discipline for new meetings handles reassignment in an afternoon. A team that doesn't loses deals silently, because the context lived in one person's notes app.

Adjacent scenario: partner and channel-sourced meetings. Many vertical SaaS companies get a meaningful slice of pipeline from an adjacent vendor, a reseller, or an industry consultant. Those meetings arrive with a different shape — warm, high-trust, but often thin on qualification, because the partner isn't running your bar. Decide explicitly whether partner meetings bypass the protocol or run through a modified version. The usual right answer: they run through the same payload requirement, filled by whoever on your team took the intro call, but with a relaxed bar, because partner trust substitutes for some of the qualification signal. Don't leave it undefined — undefined means every partner meeting becomes a negotiation.

Comparable case: the vertical-versus-horizontal contrast. A horizontal SaaS at $1M ARR can often run a looser handoff because their AEs can discover across many industries and the cost of a mismatched meeting is a wasted hour. In a vertical, the AE's edge *is* domain fluency — they should walk into the call already knowing what a bad month looks like for this buyer. That only pays off if the payload tells them which flavor of bad month this prospect is having. The protocol is how you convert vertical expertise from a personality trait into a repeatable asset. That's the concrete revenue argument for building it: it's what makes your second, third, and fourth AE as good as your first one, and it's what lets you hire an AE from the industry rather than only from software sales.

What to watch as you roll it out

Expect four weeks of noise before the numbers mean anything. Announce the protocol, run it unenforced for two weeks so people learn the mechanics without pay consequences, then switch compensation over on a clean month boundary. Changing pay and process in the same week guarantees you can't tell which one caused the reaction.

Watch for these specific failure patterns. Field-stuffing: required fields filled with "n/a" or one-word answers. The fix is not more fields or a validation rule — it's the weekly review, where the sales lead reads two payloads aloud and asks the AE whether they were useful. Social accountability outperforms validation logic here. Bar inflation: AEs quietly raising the standard because they're busy, which shows up as rising rejections with vague reasons. Catch it in the rejection reason mix. SDR gaming: booking meetings that technically meet the bar with prospects who will never show. Catch it with show rate by SDR. Protocol drift: six months in, half the team is using a Slack thread again. Catch it with the Handoff Pending stage volume — if handoffs are happening but the stage isn't being used, the process has gone informal.

Review the bar quarterly against fresh closed-won data. In a vertical, your ideal customer profile genuinely moves as the product matures — the criteria that predicted wins when you had 40 customers often don't hold at 150, because early wins skew toward the most desperate buyers and later wins toward the best-fit ones. A protocol that never gets revised becomes a fossil of who you sold to two years ago.

Finally, resist the urge to make it comprehensive. The version of this protocol that works at $1M ARR fits on one page and can be explained to a new hire in ten minutes. Every field, every rule, and every metric you add has to earn its place by changing a decision someone actually makes. If you can't name the decision, cut it.

Related questions

What if we only have one AE?

Still build it, but skip the routing and rejection queue. The payload and the SLA do the work. The real value with one AE is preserving context for the second AE you hire — you're writing the training document now rather than reconstructing it later under pressure.

Should the SDR join the first AE call?

For the first few weeks of a new SDR, yes — it's the fastest calibration loop available. After that it's expensive. A better steady state: the SDR listens to a recording of one accepted and one rejected meeting per week.

How do we handle inbound demo requests?

Inbound with a clear buying signal can skip the SDR qualification entirely and route straight to an AE, but it should still generate a payload — someone fills the fields from the form and enrichment before the call.

What if AEs and SDRs report to different managers?

Then the weekly rejection review must include both managers, and acceptance rate belongs on both scorecards. Split reporting lines without a shared metric is the most reliable way to make a handoff protocol decorative.

How long until we see the impact on revenue?

Acceptance rate and show rate move within a month. SQL-to-opportunity takes a full sales cycle to read. Closed-won impact takes one to two cycles, so plan on a quarter minimum before judging it.

FAQ

Where should the handoff live in the CRM?

On the opportunity or lead record itself, as a stage plus required fields — not in a separate object, not in a Slack channel, not in a shared doc. One record, one stage transition, one set of fields. The stage transition is what generates the timestamp you need for SLA reporting, and the required fields are what force the payload. If your CRM supports validation on stage change, use it; if not, a weekly report of incomplete handoffs is a workable substitute.

How many qualification criteria should the bar have?

Two or three at $1M ARR. Every criterion you add multiplies the number of edge cases someone has to adjudicate, and adjudication is the tax that kills adoption. Pick the two or three domain facts that most reliably separated your closed-won deals from your fast losses, and accept that you'll miss some good accounts. Missing a few good accounts is cheaper than a protocol nobody follows.

Should SDRs be paid on booked meetings or accepted meetings?

Accepted. Paying on booked creates a direct incentive to book anything with a pulse, and the AE absorbs the cost. But pairing it with the auto-accept-on-SLA-breach rule is essential — otherwise you've made the SDR's paycheck dependent on an AE's inbox habits, which is both unfair and a reliable source of internal conflict.

What's a reasonable SLA for AE acceptance?

A few business hours is a good target; one business day is the outer bound. Beyond that the prospect cools, the SDR loses the ability to re-engage naturally, and the feedback loses its coaching value. Set it in business hours, not calendar hours, and be explicit about what happens at the boundary.

Does this work if we sell to owner-operators rather than a buying committee?

Yes, and the payload gets simpler — fewer stakeholders to map. What replaces stakeholder mapping is timing and operational context: what's happening in their business right now that makes this the month they'd change software. In seasonal verticals, that's often the single strongest predictor of whether the deal closes.

Do we need a tool for this?

No. A stage, five to eight fields, a notification, and two reports cover it at $1M ARR. Buying tooling before the definitions are settled tends to produce a well-instrumented version of an unresolved disagreement. Revisit tooling when you're past roughly $5M ARR and maintaining the rules by hand is genuinely eating someone's week.

Sources

• https://hbr.org/2012/07/the-end-of-solution-sales
• https://www.saastr.com/how-to-hire-a-great-vp-sales-the-quick-guide/
• https://www.gartner.com/en/sales/topics/sales-enablement
• https://openviewpartners.com/blog/
• https://firstround.com/review/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://blog.hubspot.com/sales/sales-qualification
• https://www.bridgegroupinc.com/research

Related on PULSE

• How do you define an SQL that both marketing and sales will actually accept?
• What SDR compensation plan works best at under $5M ARR?
• How do you build an ideal customer profile from fewer than 100 closed-won deals?
• What does a healthy pipeline coverage ratio look like for early-stage vertical SaaS?
• How do you hand off a closed-won deal from sales to implementation?
• When should a founder-led sales motion hire its first non-founder AE?