An 8-Step okki go Checklist for SDR Teams Running Agent-Native Prospecting
2026-09-30 · Julian Hartwell
-
Step 1: Lock down your ICP before you touch any lead generation software
-
Step 2: Verify every address before any sales email ships
-
Step 3: Build your data layer — waterfall enrichment plus intent
-
Step 4: Decide what the agent does and what stays human
-
Step 5: Set up an okki go workflow your SDR team will actually run
-
Step 6: Test a small batch before you go wide
-
Step 7: Sequence around signals, not volume
-
Step 8: Run a weekly human review
-
When this checklist is the wrong tool
-
Common mistakes (all of which I've made)
I've been running outbound ops for B2B sales teams for six years. In that time I've personally made (and documented) 11 significant mistakes, totaling roughly $42,000 in wasted budget. Two of them were email verification errors nobody warned me about. One was an okki-go workflow that looked great on a spreadsheet and fell apart in week three.
So now I keep a checklist, and every new SDR on our team runs through it before sending their first campaign. It's 8 steps. First pass takes about 90 minutes. After that it's a weekly review.
This isn't for everyone. If you're sending fewer than 200 emails a month, or your sales cycle is relationship-first and takes under a year to close, most of this won't apply. I'd rather say that upfront than pretend it's universal.
Step 1: Lock down your ICP before you touch any lead generation software
From the outside, buying lead generation software looks like the move that makes outbound work. The reality is that tools amplify what you've already defined. If you haven't defined anything, they amplify noise.
In one month back in 2019, I loaded 3,400 leads into okki-go that 'fit our ICP.' Every seller fit, according to an email nobody had actually measured. By the time the first batch went out, reply rate was 0.3%. Half of them were student addresses.
What to actually do:
- Write the ICP as hard filters, not a paragraph. Industry, headcount, revenue band, tech stack, title. Specific numbers.
- Take your 20 best leads from last quarter and reverse-engineer the three traits they share.
- Kill the 'maybe' list. Right now. Every time I've skipped this step, I've paid twice two months later.
Checkpoint: if you can't say your ICP in one sentence with three numbers in it, you're not ready.
Step 2: Verify every address before any sales email ships
This is where okki go email verification actually saves you time — provided you put it in the right place in the sequence.
In Q3 2022 I skipped verification because 'the list was hand-built.' 2,100 leads. Bounce rate hit 12.4% within 48 hours. Our sending domain got burned and we spent a week putting out fires. That was roughly $1,900 in wasted sends and a week of outbound time, by our own ad cost math. I'm not 100% sure that figure holds up against a cleaner accounting method, but it's the number I documented at the time.
What to actually do:
- Run okki go email verification before anything hits the outbound queue — not after.
- Treat 'risky' and 'invalid' as the same bucket. I've watched risky addresses clog inboxes like grey-mail and cost as much as hard bounces.
- Re-verify any address that's been dormant more than 90 days. People change jobs. Domains expire.
Checkpoint: export your current list. If it's over 3% invalid, don't send. Verify first.
Nobody can guarantee deliverability. Anyone who says they can hit 100% is selling. What you can do is push avoidable bounces close to zero. That's a different goal.
Step 3: Build your data layer — waterfall enrichment plus intent
Here's the counterintuitive bit most teams skip: if you don't set a confidence threshold on enriched data, you're propagating noise.
In January 2024 we ran a campaign with a plain 'hydrate everything' step. What we saw was 7% of leads with a title but no company size, and half of those titles were generic. Eleven days of wasted outbound effort, because nothing flagged the low-confidence records. If we'd set a threshold, we'd have caught it in an hour.
What to actually do:
- Waterfall enrichment — don't rely on one provider. Primary vendor first, then secondary for unmatched fields, then a third if you have it.
- Use intent data as a filter, not a score. Prioritize accounts that searched your category in the last 30 days.
- Document your confidence threshold in the SOP. Something like: drop any record where title confidence is below 70%.
Checkpoint: pull 20 records at random. Manually check three fields on LinkedIn. If the accuracy is under 85%, your threshold isn't doing its job.
Step 4: Decide what the agent does and what stays human
This is where agent-native prospecting goes wrong. And this is my opinion, not a rule — the agent can research, enrich, draft, sequence, and decide who gets what. What it should not do is ship a final sales email on its own, before you've validated the signal.
June 2023: we let an agent send emails with what we thought were 'good enough' rules. Within three days it emailed four executives at the same company with four slightly different pitches. One of those VPs replied with 'How many of you are there?' We made drafts require human sign-off for the first month after that.
What to actually do:
- Agent researches and drafts. Human signs.
- Set a hard pause before any send, even at low volume.
- Log where the agent got it wrong. Review weekly.
Checkpoint: if you can't explain in under a minute why the agent sent a specific email to a specific person, you've delegated too far.
Step 5: Set up an okki go workflow your SDR team will actually run
In Q1 2024 we ran a three-week experiment on an okki-go workflow for SDR teams. The hard rule was: one queue for feeding, verifying, enriching, and sending, so reps weren't tab-hopping. It cut our reps' manual switching time by about 18% across the pilot. Your numbers will differ — measure yours.
What to actually do:
- One entry point, one exit point. Everything comes in through the same door, goes out the same door.
- Standardize the rejection reasons. 'Not interested' isn't a reason. 'Budget frozen' or 'wrong title' is.
- Reassign queues every Monday morning. Leads that sat over the weekend are cold by Monday.
Checkpoint: if a rep has to open more than four tabs for a single outbound pass, the workflow isn't done.
Step 6: Test a small batch before you go wide
Most teams skip this. Don't.
October 2023 I got pulled into a two-hour window to decide on a new sending domain. Normally I'd warm it for two weeks. There was no time. I went with 'the DNS records look fine.' Open rate collapsed by day four. Looking back, I should have capped the send at 50 and paid for the delay. But with the CRO waiting, I made the call with incomplete information. That's the kind of decision that looks reasonable at the time and stupid in the retro.
What to actually do:
- Warm up: 50/day on a fresh domain for seven days, then double weekly.
- Seed inboxes in every batch. If they land in spam, stop.
- Test one subject line before scaling. Not ten and then pick.
Checkpoint: hold at 25% open rate minimum before you scale.
Step 7: Sequence around signals, not volume
I've watched too many teams hit '1,000 a day per rep' as the goal. That's the wrong metric to optimize for, and everyone knows it, and everyone does it anyway.
What to actually do:
- Trigger sequences off intent signals. Hiring signal, new exec, recent funding. Those are reasons to reach out.
- Write sales emails that read like a person wrote them. Short, specific, no 'hope this finds you well.'
- Stop at two unrelated follow-ups. A third burns brand equity for nothing.
Checkpoint: if you have to explain why you're reaching out for ten straight leads, your signal layer isn't working.
Step 8: Run a weekly human review
This is the most boring step and it's the one that saves you the most.
What to actually do:
- Every Friday. Fifteen minutes. No more.
- Review three numbers: reply rate, bounce rate, meeting conversion. Pick one to tune.
- Document anything above a small error threshold into the SOP.
Checkpoint: if Friday review gets pushed, it becomes a monthly review in two months, then disappears. I've seen this happen at every company I've been at.
When this checklist is the wrong tool
I want to be honest about this. This isn't a universal answer.
- Under 200 sends a month: do it manually. The tool cost won't pay for itself.
- Cycles over a year, relationship-driven: you don't need a sequence, you need executive-led conversations.
- Stuck in spam for infra reasons (DNS, IP reputation): fix the infra first. The checklist won't help.
- Teams smaller than two: too much complexity. Run steps 2 and 6 only, and leave the rest for when you have headcount.
Common mistakes (all of which I've made)
- Writing the ICP wide and planning to narrow later. Later never comes. Narrow now.
- Verifying after the send. Reversed order, wasted everything.
- Letting an agent send without a human pause — the Step 4 failure mode.
- Treating list size as progress. It isn't. Reply rate is.
- Treating 'risky' emails as fine. They're not — they burn reputation quietly.
That's the whole thing. Eight steps, 90 minutes, 15 minutes a week. Run them in order. Skip the ones you should skip — but know which ones you're skipping.