Coco + 11x

11x's Alice is one of the best-known AI SDRs in market. She runs autonomous outbound at volume — researches accounts, drafts personalized first-touches, runs multi-touch sequences, books meetings on your calendar, hands the booked opportunity to a human AE. The output: more meetings booked, fewer SDRs needed. Coco doesn't compete with that. Coco operates as the orchestration layer around it: deeper account research before Alice sends, CRM hygiene on the contacts Alice generates, meeting prep on the meetings Alice books, post-meeting follow-through, and cross-team reporting on what's actually working. Where 11x exposes APIs and webhooks, Coco connects directly. Where it doesn't, Coco coordinates at the workflow seams through your shared CRM. The result: Alice becomes more strategic, and the broader GTM workload around her stops getting dropped.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

What Coco does with 11x today

The division of labor is clean. 11x runs the volume engine. Coco runs everything else.

Before Alice sends — research depth. Alice's research is fast and broad; the cost is depth. For target accounts where personalization needs to be sharper than what Alice produces alone, Coco runs a deeper research pass first: recent funding, hiring signals, public commentary, mutual connections, specific problem indicators. About 5-12 credits per account. The deepened brief becomes the context Alice uses to draft, and the response rate on those accounts moves accordingly.

While Alice runs — CRM hygiene on the contacts she touches. Alice generates a lot of contact-record activity. Coco watches the contacts Alice has engaged and runs hygiene in parallel: deduplication against existing records, enrichment of fields Alice didn't fill, lifecycle-stage updates, routing fixes. About 1-2 credits per record. The result is clean records flowing through your CRM instead of fragmented duplicates.

After Alice books — meeting prep and follow-through. When Alice books a meeting, Coco kicks off automatically: pre-meeting brief lands in your inbox the morning of the call (~8 credits), post-meeting follow-up draft queues in your Gmail after the call (~3-5 credits), and any CRM updates (stage change, next-step task, call notes) queue for your approval. The handoff from Alice to a human AE stops being a manual context-pull.

Around the edges — reporting and re-engagement. Coco watches the deals Alice originated and surfaces ones going stale (silent past your threshold), drafts re-engagement messages, and reports on which Alice-sourced workflows actually convert. About 5-7 credits per stalled-deal sweep.

Every external action — sending an email, writing to your CRM, posting to a Slack channel — gates on your approval at the start. Reading and drafting are free of approval. Once you've approved a workflow a few times and you're comfortable with how Coco handles it, you can graduate that specific workflow to autonomous execution inside the guardrails you set. See how approval gates work → for the trust model.

How the integration actually connects

11x has a limited but real public surface: webhook events for booked meetings and major lifecycle changes, plus an API for pulling activity logs and feeding prospect/contact data. Coco connects to both.

For deeper coordination — pushing a Coco-built ICP list to 11x as a campaign target, or syncing real-time activity — the integration depends on what 11x exposes. Where the API supports it, Coco wires up directly. Where 11x's API doesn't yet expose the surface, Coco coordinates at the workflow seams: shared CRM (HubSpot, Salesforce) as the source of truth, Coco watching for changes on its side, Alice watching for changes on hers.

Honest constraint: this is not a one-click "drop Coco into 11x" install. It's an orchestration pattern. Setup is typically a 30-minute connection flow plus one workflow approval per recurring pattern. Once set up, the cross-tool execution runs without supervision.

The workflow divide

Side by side, here's how the work splits:

The pattern: Alice runs the autonomous volume work that AI SDRs are built for. Coco runs the workflow that lives upstream, downstream, and around it. Neither tool tries to do the other's job.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Pricing math when you run both

11x's pricing is structured like a junior headcount slot — low five figures per year per AI rep, typically annual contracts. The number assumes you're replacing or augmenting SDR headcount.

Coco's Founder tier is $40/month with 5,000 credits, plus à la carte top-ups. For a team running 11x at the typical contract value, adding Coco is a fraction of a percent of total spend. The math works out roughly: Alice handles the outbound volume that justifies her cost; Coco handles a workflow class (CRM hygiene, follow-through, meeting prep) that previously took a human RevOps or operations hour daily.

For teams considering 11x but not yet ready for the contract, Coco can run leaner outbound at lower volume (no autonomous send; per-draft approval) until volume bottleneck makes 11x worth the price.

See Coco's full pricing → for the credit-cost breakdown.

Why this works: the orchestration angle

Most teams trying to add AI to their GTM stack accumulate tools. Each tool does its specialty well in isolation; coordinating between them is manual. 11x for outbound. Apollo for data. Outreach or Salesloft for sequencing. HubSpot for CRM. Slack for comms. Gmail for relationship-stage email. The tools each work; the seams between them don't.

Coco is built for the seams. It connects to what you have, watches the work as it moves between tools, and runs the cross-tool execution that no single tool is positioned to handle. For 11x specifically, this means Alice keeps doing what she does well while Coco handles the work that surrounds her — making the 11x investment more strategic instead of more siloed.

This is the same pattern Coco applies to Artisan → and Salesloft →. Different tools, same wedge: Coco is the layer that turns specialized AI tools into a coordinated GTM motion.

Frequently asked questions

Do I need to keep 11x if I have Coco?

If outbound volume is your primary bottleneck and Alice is hitting it, yes — keep 11x. Coco doesn't replace the autonomous-outbound capability that 11x specializes in. Coco handles the workflow around it.

Can Coco trigger 11x campaigns?

Where 11x exposes campaign-creation APIs, yes. Where it doesn't, Coco hands you the ICP and research brief and you launch the campaign in 11x's platform. The integration is honest about what's directly automated vs. coordinated at the seam.

How do Coco and 11x share data?

Through 11x's API and webhooks where they exist, plus your shared CRM as the source of truth for contact records. Coco reads from both surfaces and writes back through approved actions.

What's the setup time?

About 30 minutes for the initial connection (Coco's auth flow + 11x's API key + shared CRM connection), plus one workflow approval per recurring pattern you want to enable. After that, the cross-tool execution runs without supervision.

Will Coco do the things Alice already does?

No — by design. Coco won't run autonomous outbound at the volume Alice does. That's Alice's specialty. Coco runs the broader workflow that Alice doesn't touch.

Can I use Coco without 11x?

Yes — Coco can run lower-volume outbound directly (per-draft approval; quality-first model) and handle the full GTM workload independently. Many teams start with Coco-only and add 11x when outbound volume becomes the specific bottleneck.

Get started

If you're already running 11x and the work around Alice is dropping, the integration takes a half hour to set up and starts adding value the same day. Connect Coco, point it at your shared CRM, approve the first orchestration workflow.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Or book a walkthrough → if you'd rather see the orchestration pattern in action first.