Human ↔ Agent Operating Scale

Stop asking "human or agent."
Ask who owns the outcome.

Every GTM leader is being asked whether a role goes to a person, an AI agent, or both. The answer isn't about the AI. It's about whether the work has a stable definition and whether your data can be trusted.

500+HubSpot & Salesforce instances built or fixed
2016Engineering GTM systems since
3–4Agents one good operator can run
What AI actually does in GTM

AI spots patterns in your data and acts on them.

1 · SIGNALS IN

CallsRecordings, transcripts
Email & chatReplies, threads, Slack
CRM recordsContacts, deals, activity
Intent & webVisits, research, hiring
Product & billingUsage, renewals, invoices

2 · RECOGNIZE

→→
THE MODEL
Finds the pattern a person would miss

Which accounts are heating up. Which deals are slipping. Which customers look like the last ten that churned.

3 · REACT

PredictForecast, lead and churn scores
WriteOutreach, follow-ups, call notes
WatchFlag risk, stalls, bad data
DecideRoute leads, next best action
↑ a person still owns the number
THE CATCHIt learns from what's in your systems.Duplicates, stale fields, and broken routing train it to be confidently wrong.
The operating scale

Five levels of how GTM work gets done.

Most teams try to jump straight to Level 5. The returns show up at Level 4: one operator who owns a number, running a small team of agents.

LEVEL 1

Manual

Human 100%Agent 0%

People run every step. Automation is rules someone built by hand.

e.g. SDRs research, write and log every touch.
LEVEL 2

Assisted

Human 75%Agent 25%

AI drafts, summarizes, and suggests. A person decides and executes.

e.g. AI writes the call summary; the rep updates the deal.
LEVEL 3

Shared

Human 50%Agent 50%

An agent runs the documented runbook. A person handles the exceptions.

e.g. Agent enriches and routes inbound; ops fixes the edge cases.
where the returns are ↓
LEVEL 4
×4

Operator-led

Human 25%Agent 75%

One operator runs 3–4 agents and owns the number.

e.g. One RevOps lead runs research, routing, follow-up and hygiene agents against a pipeline target.
LEVEL 5

Autonomous

Human 0%Agent 100%

A person sets the outcome. Agents run the work end to end.

e.g. Narrow, high-volume, low-risk work only, on clean data.
LEVEL 0Clean data comes first.Routing, dedupe, and a lead status field you trust. Put an agent on a dirty CRM and it just sends bad emails faster.
Role check

Hire, deploy an agent, or both?

Pick one role or workflow. Answer five questions. Get the call we'd make.

Could you write the steps down as a runbook someone else could follow?
Are the inputs clean? (Trusted lead status, deduped records, working routing.)
Is it high volume? (Hundreds of the same task a week.)
Does it depend on judgment, relationships, or deciding what to build next?
Are mistakes expensive? (A bad send, a misrouted deal, a wrong number to the board.)
OUR CALL
Answer the questions

Your result updates as you go.

    How we decide

    Three rules from the field.

    01

    Stable definition decides it.

    If you can write the steps down and the inputs are clean, an agent should run it. If the job is judgment, relationships, or deciding what to build next, hire.

    02

    The blocker is the data.

    Most teams asking for an "AI SDR" can't trust their own lead status field. Automating outbound before routing and dedupe work just sends bad emails faster.

    03

    The unit is the operator.

    Agents don't own results; people do. The setup that wins is one operator accountable for a number, running three or four agents.

    Get to Level 4

    We fix the data, build the agents, and hand you the operator model.

    JayOh is a GTM systems engineering firm building RevOps and AI agent systems for B2B SaaS and PE-backed companies.