log 005 · · 5 min read · Operations

The handoff at 60 reps, automated.

When the spreadsheet handoff stops scaling, pipeline starts leaking at the seam. See the replacement workflow, what stayed human, and how to value the time saved.

Interactive: compare both workflows and calculate the time value.

Why 60 reps is the inflection

Below ~30 reps, almost any handoff works because someone in the office knows everyone. Around 60, that breaks. The marketing manager cannot remember which AE owns which ICP. The AE cannot remember which leads got nurtured already. The Slack channel becomes performance theater.

The number is not exact. The pattern is. When the time spent finding the right rep for a lead exceeds the time spent actually contacting the lead, you are past the inflection.

The flow, before and after

Both flows have five steps. The numbers map across so you can see what was replaced and what was not. Hover a step on either side to compare.

Notice what stayed: a human still owns the lead. The AE still picks up the phone. The system tells them who and when, not what to say. The lever is the routing, not the conversation.

What the time is worth

3.5 hours per day across 8 reps and a manager is real money. Plug your numbers in:

The dollar number is the part the CFO cares about. The part the VP Sales cares about is the second one: hours reclaimed per year. That is the time that goes back into actual selling instead of routing housekeeping.

What we kept human

Three places we deliberately did not automate, and why:

  • The first call. AI-written first calls are pattern-matched and ignored. The handoff system gets the human to the right lead at the right time. The human takes it from there. (Yes, including the cold email. See LOG-001.)
  • The exception override. Managers can pull a lead off auto-routing and assign manually. The system logs why, so the rule learns over time. Without this escape hatch, edge cases break the trust.
  • The Slack reply that closes the loop. When the bot pings the AE, the AE replies with what they did. That reply goes to the CRM and to a human-readable log. Auto-status was the failure mode of the original spreadsheet flow.

This is the boring middle of automation work. Not 'replace the salesperson with an agent.' Replace the routing layer that was eating the salesperson's day.

The Orbit team
log 0055 min read
Share

Get the next dispatch

Practical field notes on AI, automation, and modern work, sent when there is something worth sharing.

Related dispatches