Lead-to-Revenue: Routing, SLAs, and Handoffs

A routing rule I inherited spent months sending new accounts to the wrong place, and nobody noticed because nothing ever errored. The rule was supposed to hand one segment of new accounts to a customer-success owner named Tia. It matched on a lookup field that had gone stale, so the match quietly failed, the accounts fell through to a default queue, and they sat there while everyone downstream assumed the automation had them. Routing runs thousands of times a day and fails in silence. There is no gong when a record lands in the wrong queue and no alarm when it ages, just a slow leak that surfaces two quarters later as a cohort nobody worked. Fixing that one lookup, and wiring a flag to fire when a match misses, recovered a book of accounts that had been invisible.

In the last chapter we pointed compensation at the right growth engine, so a rep who does the right thing gets paid for it. Comp aims behavior. It cannot help a rep who never receives the lead, or receives it cold and three hours late. This chapter is the discipline that moves a lead across the acquisition side of the Bowtie, from the first touch to the closed-won transfer, and hands it off clean at every seam in between. The metrics spine already gave us the instruments for this stretch: the left-side conversions CR1 through CR4, the volumes VM1 through VM5, and the response clock Δt1. Here we operate them.

The left side is a relay, not a funnel

A funnel drawing hides the thing that actually breaks: every stage is a place a record changes hands. Marketing produces a lead and passes it to routing. Routing assigns it and passes it to a qualifier. The qualifier accepts it and passes it to an account executive. The AE wins it and passes it to customer success. Four handoffs, each a seam, each a contract between two teams that either holds or leaks. Draw the left side as a relay and the operating job becomes obvious: keep the baton moving and never let it drop at an exchange.

Two composites from the spine ride on this relay. Lead-to-opportunity is L2O = CR1 x CR2, the marketing-and-outreach stretch. Opportunity-to-close is OTC = CR3 x CR4, the prioritize-and-win stretch. When a composite sags, you open the stage underneath it rather than blaming the team at the end. This chapter builds the sequential, framework-grounded version of that relay. For the deep tactical build, the reason codes, the SLA trigger, the required-fields gate, the handoffs reference walks each seam end to end, and I lean on it here rather than repeat it.

Δt1 is the clock that beats every other lever

Of everything on the left side, response time moves the most for the least. A lead contacted inside five minutes qualifies at roughly 21 times the rate of one contacted at thirty (Lead Response Management Study), and 65% of buyers expect a first response in under an hour (HubSpot and LeanData, 2024-25). That is an order of magnitude, not a coaching tweak, and it is almost entirely an operations problem. The lead that routes in seconds and gets worked in minutes beats the identical lead worked three hours later, and the difference is the routing architecture, not the salesperson.

So I never queue a lead for a human to pick up. Routing fires the instant the record lands, and the SLA clock starts on arrival, not on assignment. That is a runtime sequence, and it has an order.

Routing is a latency problem before it is a fairness problem. The plumbing, matching leads to owners as a distributed system that fails loud instead of silent, is engineering work, and the engineering academy’s integration track owns the implementation. The operator’s contribution is the standard: measure the seconds, not the org chart, and make a missed match visible the moment it happens.

The Prioritization checkpoint: earning a rep’s calendar

Speed gets a lead to a human fast. Speed alone will also flood your most expensive resource with junk. Revenue Architecture handles this by inserting a stage the classic funnel never had: Prioritization, a mutual-commitment checkpoint that sits between Education and Selection, right before you deploy people. It is measured by CR3, the share of discovery meetings that convert into accepted, qualified opportunities. In a self-serve motion this checkpoint takes seconds; in a field motion it is a deliberate accept-or-reject decision. Either way it is the gate that decides whether an AE’s calendar is worth spending, and it is where the three handoff definitions become contracts instead of vocabulary.

The reason to define these as contracts, not labels, is the lesson from the metrics spine: number the slots so the definition survives whatever your CRM calls them. Our internal funnel names the accepted opportunity an SAO and the qualified one an SQO, so the sequence reads MQL, meeting, SAO, SQO. Those are the same VM4-and-beyond slots under different names. When I trace one quarter’s MQL cohort forward in Omni, the SAO-to-SQO step holds near 74% every quarter, which makes it a rate I can plan against, while the MQL-to-meeting step swings between 8% and 21% because meetings get captured badly upstream. A checkpoint you can trust is one whose definition both sides signed and whose events you actually record.

You cannot route or measure a seam you never stamp

Here is the gap that undoes all of the above if you skip it. A conversion rate and a response time are both computed from timestamps. If the timestamp is missing, the stage is invisible, and an invisible stage cannot be routed on, measured, or improved. I learned this from an SAO-date flow that stamped the date only when the opportunity was created. Any opportunity that became an SAO after it was created, which is most of them, never got a date at all. The result was 263 new-business opportunities sitting at SAO with a blank SAO date, so the conversion into that stage and the time it took to get there simply could not be calculated for them. The funnel looked fine. It was under-counting a whole stage.

The last handoff closes the chain

The relay does not end at closed-won. The final exchange is O1, the Sales-to-CS onboarding handoff, and it is the seam most teams treat as a formality and then pay for at renewal. In Revenue Architecture’s customer-success sequence, O1 is the transfer that sets up the kickoff, the joint impact plan, and the first delivered impact. Get it wrong and customer success inherits a logo with no story: no use case, no success criteria, no named champion, so the first quarter goes to reverse-engineering why the customer bought, which is the same quarter that decides whether they stay. That handoff is the entry to the right side of the Bowtie and the start of the time-to-first-impact clock (Δt6) that governs the renewal. I gate it with a short list of required fields at close, and I keep the list to the few that decide the renewal so reps do not learn to fake it. The full O1 mechanics live in the handoffs reference, and the right side that O1 opens onto is customer success operations later in this module.

Handing off

You can now run the acquisition relay as a system: route on a clock so Δt1 stops leaking, run the Prioritization checkpoint so an AE’s calendar goes to real opportunities, define MQL, SQL, and SAL as contracts both sides signed, stamp every stage on the transition so the funnel is measurable, and gate the O1 transfer so customer success starts with a story instead of a cold read. A clean SAL that clears the checkpoint still has to get priced, approved, and papered, and the fastest way to reopen a leak you just closed is to let all that pile up in a deal-desk queue where deals sit exactly the way those misrouted accounts did. Keeping approvals and quote-to-cash fast without becoming the new bottleneck is Deal Desk, Quote-to-Cash, and CPQ Ops, and it is next.