Okkigo Prospecting Tool: 7-Step Setup Checklist for an Emergency Pipeline Sprint

When This Checklist Fits — And When It Doesn't

If you have three quarters to build pipeline, don't use this checklist. Use it when you have roughly two weeks to get qualified meetings on the calendar. Quarter-end gap. A trade show you forgot you had a booth at. A board metric that's 40% off target.

I run sales ops at a mid-market B2B SaaS company. I've handled 200+ rush prospecting sprints in four years, including 72-hour turnarounds for enterprise accounts. Some went fine. A few went sideways because we warmed up the wrong domain and burned 11 days we didn't have.

Here's the seven-step version I actually use now. It takes about six hours of setup work, spread across two days.

Step 1: Define What Sales Email Means Before You Touch Any Tool

This sounds obvious. It isn't. Half the messes I've cleaned up started with a team that didn't agree on what counted as "sales email."

Sales email is a message sent to a specific person, at a specific stage of a sales process, asking for a specific next action. That's it. It's different from marketing email (which goes to segments, not people) and different from transactional email (receipts, password resets, calendar confirmations).

When should a B2B sales team use sales email? Three cases, in my experience:

• You have a named target — a persona, a title, a company shape — and no existing relationship.
• You have a signal — a job change, a funding round, a site visit, a product launch — that makes the timing defensible.
• You can measure the outcome in pipeline terms, not opens. Opens lie. Pipeline doesn't.

If none of those three is true, you're about to send spam with better formatting. Skip the sprint.

Step 2: Write Down What Okkigo Permissions You're Actually Granting

This is the step most teams blow past, and it's the one that bites back. Before you connect anything, list what the tool is asking for.

As of January 2026, Okkigo (sometimes written "okki go") typically requests OAuth access to:

• Your inbox — Gmail or Outlook. This is non-negotiable if you want the tool to send on your behalf.
• Your CRM — HubSpot, Salesforce, or Pipedrive. Needed for reply attribution.
• LinkedIn session access — optional, and worth pausing on.
• Domain and website data — for enrichment.

Two of those are load-bearing. One is optional. Here's how I triage them:

Inbox access: ask whether the scope is send-only or send-and-read. Send-only is fine for cold outreach. Send-and-read means the tool can see your entire inbox, including personal threads. If your legal team has an issue with that, you'll find out in week three when a deal email shows up in a client's audit.

CRM access: grant read-write to the objects the tool actually uses. Don't hand it admin.

LinkedIn access (which, honestly, I've seen cause the most friction): some orgs ban it outright. Others allow it but throttle it. If your compliance team hasn't weighed in, ask them before you enable it, not after your first account flag.

I should add: permissions can change between tool versions. Re-check the scope list after every major update.

Step 3: Pick Sales Intelligence Software Features That Earn Their Place

Sales intelligence software is a crowded category. The features that matter for a sprint are not the ones vendors demo.

The features I actually check before committing to a tool:

1. Contact data freshness — when was the record last verified? Anything older than 90 days is a coin flip.
2. Intent signal coverage — does it flag site visits, job posts, tech stack changes, funding rounds? Or just "contacts who match a title"?
3. Waterfall enrichment — when one provider misses, does it try three or four others before giving up? Single-source enrichment has maybe 60% coverage on mid-market domains.
4. CRM write-back — does activity flow both ways, or do you export CSVs every morning?
5. Sending controls — per-domain daily caps, ramp schedules, bounce-rate circuit breakers.
6. Deliverability monitoring — spam-score checks, blacklist alerts, SPF/DKIM/DMARC verification.

If a tool gets four of six right, it's competitive. If it gets six, and the price is sane, buy it and move on. Feature-hunting past that point is procrastination wearing a spreadsheet.

Step 4: Lock Down Email Deliverability Before You Import a Single Contact

This is the step people skip, and it's the one that kills sprints.

Email deliverability is about whether your message reaches the inbox at all. Three things matter for a cold sprint:

Authentication. You need SPF, DKIM, and DMARC configured on your sending domain. As of Google and Yahoo's February 2024 bulk sender requirements, senders above 5,000 messages/day must have all three — but I recommend having them at any volume. Miss one and your domain starts landing in spam folds.

Domain separation. Don't send cold outreach from your primary domain. Use a subdomain or a separate domain (I've seen teams use variations like `get-yourcompany.com`). If it gets burned, your transactional email still works.

Warmup. New domains need gradual volume. Start at 20-30 per day per inbox, add 10-15 daily, and stop if bounce rate crosses 2%. Skip warmup and you'll get throttled by the receiving side — which is worse than an outright block because you won't know it's happening for a week.

Step 5: Configure Waterfall Enrichment, Not Single-Source

Waterfall enrichment means: query provider A. Whatever records come back empty, query provider B. Then C. Then D. It's slower to set up and dramatically better on coverage.

I ran a sample of 2,000 contacts last quarter. Single-source enrichment returned ~62% valid records. Three-tier waterfall hit ~89%. The difference matters because every missing record is either a wasted slot in your sequence or a bounce waiting to damage your sender reputation.

Configure it once. Test on a sample of 200. Then don't touch it mid-sprint.

Step 6: Build the Human-in-the-Loop Handoff

Full automation is where sprints go wrong. You want the tool to handle volume. You want a human on the reply.

The handoff I use:

• Automated: first-touch email, follow-up 2, follow-up 3, LinkedIn view.
• Human: any reply, any positive intent signal, any account over a certain size threshold.

Set that threshold before the sprint starts, not during. "We'll decide case-by-case" is how a director ends up personally answering 200 emails at 11pm.

Step 7: Run a 50-Contact Pilot Before You Open the Tap

Send 50 contacts through the full sequence, watched closely. Look for:

1. Bounce rate under 2%.
2. At least one reply (even a negative one).
3. No spam-folder placements on a spot check of 5 test inboxes you control.
4. CRM logging working both directions.

If any of those fail, stop. Fix. Re-run the pilot. Do not "just push through and monitor."

Things That Go Wrong (That a Pilot Won't Catch)

Small lists deserve the same care as big ones. I've set up sprints for 40-contact lists that outperformed 4,000-contact lists. The mistake is treating a small batch as "not worth the setup." It's the opposite — smaller lists are where you can afford to be precise, and precision compounds. The vendors and reps who treated my $200 orders seriously when I started are the same ones I call for $20,000 orders now. Same logic applies here.

Reply rates are not pipeline. A 6% reply rate that converts to zero meetings is worse than a 2% reply rate that books three. Track meetings, not opens.

Permissions creep. Three weeks in, someone on the team grants a tool a new scope "to test something." Audit scope list monthly.

Ramp disruption. Running two sprouts on the same sending domain at once will nuke your reputation. One sprint at a time, per domain.

That's the whole checklist. Six hours of setup. Two weeks of execution. If you do the pilot properly, you'll know by day four whether the sprint is working — which is about the only thing that saves you when the deadline is real.