okkigo Setup by Scenario: Permissions, Intent Data, and What RevOps Should Actually Evaluate

Let me get this out of the way first: setting up okkigo (people also write it as okki-go) isn't a one-size process. What you install, what permissions you actually need, and what RevOps should evaluate before pushing the button—all of that depends on the shape of your team.

I'm the person who gets pulled into these deployments when "we need to be sending by Friday" lands on someone's desk. Last quarter I pushed a 6-seat SDR stack live in 72 hours. That kind of timeline changes how you look at a setup guide. You stop caring about feature lists and start caring about what's going to break in week six.

So here's the decision tree. Pick the scenario that sounds like you.

The three okkigo setup scenarios

• Scenario A: Solo SDR or founder running outbound without a dedicated ops person.
• Scenario B: A small SDR team (2–10 seats) with someone doing RevOps part-time or full-time.
• Scenario C: Agency or scaled outbound with 10+ seats, multiple sending domains, and a compliance lens.

Scenario A: Solo SDR or founder

Speed wins here. Get sending. Iterate.

What the install actually involves

It's basically OAuth. You connect okkigo to Gmail or Outlook through an auth flow, and you're live in under ten minutes. The key thing—do this on a mailbox you're okay losing. Once you start sending, your domain reputation shifts, and it doesn't always shift back.

Permissions you actually need

Send, read, and modify mail. Plus calendar, probably. CRM sync can wait. If you don't have a CRM, don't let anyone talk you into setting one up just to use a prospecting tool—that's backwards. Add LinkedIn-related permissions only if the account is a burner, not your personal one.

What to evaluate before you send the first email

Not the intent data. Not the dashboards. The question is: can you send 30 decent emails without getting your domain flagged?

Check your SPF, DKIM, and DMARC records. If DMARC sounds new—it's a DNS policy that tells receivers which mail is legitimately from your domain (RFC 7489). Without it, Gmail and Microsoft increasingly route you to spam or just drop you. Straightforward to set up. High return for the effort.

"It's basically a trade-off between speed and reputation. And the thing nobody tells you is that going fast without guardrails is the expensive mistake."

In March 2024, I helped a founder spin up a five-client outbound motion. He wanted to connect okkigo to his main mailbox because it was the one people knew. I talked him into a fresh domain instead. If I remember correctly, that new domain got throttled within about three weeks—I might be off on the exact day. His primary inbox stayed clean. So glad we didn't take the shortcut. His transactional email would have been down for two or three days while we sorted it.

Scenario B: Small SDR team (2–10 seats) managed by RevOps

This is where "installation" starts meaning something more than connecting one mailbox. Now you're designing a workflow.

Install and permissions

You want SSO or something close to it. You want a clean role definition that applies both at onboarding and offboarding—that part matters more than the onboarding piece. Every SDR does not need the same scopes as every other SDR. Nobody needs admin by default.

Typical permission scope: mail read/send/modify, calendar, CRM read+write (HubSpot or Salesforce is where you should spend real thinking), and optionally LinkedIn actions. For CRM, I'd push for a scoped app user rather than a superuser. Do not connect it through an admin account that can delete records.

When intent data actually earns its keep

Once you have more than three SDRs. Below that, intent signals are mostly noise because you can hold the priority list in your head. Above that, "who to call first" becomes a shared team decision, and you need a shared signal.

A useful intent signal has to be three things: fresh, tied to your ICP, and actionable. A 30-day-old signal from a website visit that had nothing to do with your product isn't a signal, it's a coincidence.

What RevOps should evaluate

Not the feature list. I know that's the thing every pitch deck leads with, but it shouldn't be the first filter.

• CRM sync hygiene: How are duplicates handled? Who wins in a conflict?
• Data freshness SLA: How long between a signal firing and it appearing in the CRM?
• Permission boundaries: Who can export contacts, and where does that export land?
• Unsubscribe handling: Does it flow back into the CRM automatically? CAN-SPAM requires opt-out requests to be processed within 10 business days—don't let a workflow gap turn into a compliance problem.

We didn't have a formal permissions review process at one of my previous orgs. It cost us when an SDR admin who left the company still had active access for eleven days—hooked into two shared inboxes. Nobody got hacked, but we caught two nearly-sent client campaign emails that had been queued by the wrong person. After that, I wrote a deprovisioning checklist that runs the same day as any SDR exit.

Scenario C: Agency or scaled outbound (10+ seats, multiple domains)

Everything changes here. You're not evaluating "which permission do I trust"—you're evaluating compliance, data isolation, and whether the vendor's infrastructure can hold up.

Install and permissions

Multiple workspaces. Data separation between clients. Each client on their own sending domain and their own sending identity. Do not cross-pollinate contact lists across workspaces unless you have a real legal reason written down somewhere.

Intent data is table stakes now

At this scale, you probably already have intent data in the stack. Clients sign with the assumption that you'll bring it. Without it, your emails are pattern-matched spam with nicer copy. So API access, bulk export, and at least one mainstream intent provider integration are baseline, not bonuses.

What RevOps (or your compliance lead) evaluates

• SOC 2 Type II—not Type I. Type I only covers design; Type II covers operating effectiveness over time.
• DPA availability and jurisdiction coverage. If any client is in the EU, GDPR Article 6 means you need a lawful basis for B2B outbound to individuals—usually legitimate interest, documented.
• Data residency: where does client data get stored, and can you point to it in writing?
• Export controls: who can pull prospect and email data out of the platform, and what happens to it after?
• Sending infrastructure: is it shared with other customers, or isolated per workspace?

How to figure out which scenario you're in

Answer three questions:

1. Do you have a CRM before you connect the tool? If no → Scenario A.
2. Does someone own the responsibility for data, permissions, and tool configuration? If no → Scenario A or light Scenario B.
3. Are you running more than one sending domain, or more than one client workspace? If yes → Scenario C.

If you're stuck between A and B, treat it as A on the way to B. That's fine. Just write down your permissions process before the first time you get a surprising email from an account you forgot existed.

One honest thing

okkigo isn't going to fix everything. It handles outbound execution and prospect enrichment well—that's its lane. It's not going to replace knowing who your ICP actually is, and it's not going to teach an SDR how to write a one-line opener that doesn't sound like everyone else's.

When I evaluate tools, the thing I trust most is a vendor who tells me what they don't do. If a platform claims to handle the entire motion end-to-end without a specialist anywhere in the loop, my experience is that it does none of it particularly well. The tools that survive inside a serious outbound stack are the ones that know their edges and say so.

So before you sign anything: ask okkigo what it doesn't do. If the answer is specific and points you somewhere else for the missing pieces, that's the one I'd connect my primary CRM to.