Coco + Artisan

Artisan's Ava is one of the most-talked-about AI BDRs in market. She runs autonomous outbound — researches accounts, drafts first-touches, runs multi-step sequences across email and LinkedIn, books meetings on your calendar. The output: more meetings booked, fewer BDRs needed. Coco doesn't compete with that. Coco operates as the orchestration layer around Ava: deeper account research before she sends, CRM hygiene on the contacts she generates, meeting prep on the meetings she books, post-meeting follow-through, stalled-deal sweeps on the pipeline she sources. Where Artisan exposes APIs or has direct CRM integrations, Coco connects directly. Where it doesn't, Coco coordinates at the workflow seams through your shared CRM. The result: Ava 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 Artisan today

The division of labor is clean. Artisan runs the outbound volume engine. Coco runs everything else.

Before Ava sends — research depth. Ava's research per account is fast and broad; the cost of speed is depth. For target accounts where personalization needs to be sharper than what Ava produces alone, Coco runs a deeper research pass first: recent funding, hiring signals, public commentary from leadership, mutual connections, specific problem indicators, technology stack hints. About 5-12 credits per account brief delivered to Ava. The deepened brief becomes the context Ava draws on when drafting the first-touch, and the reply rate on those accounts moves accordingly. See research accounts →.

While Ava runs — CRM hygiene on the contacts she touches. Ava generates a lot of contact-record activity at speed: new contacts, new touches, sequence enrollments, replies. Coco watches the contacts Ava has engaged and runs hygiene in parallel: deduplication against existing CRM records, enrichment of fields Ava didn't fill (company size, lifecycle stage, owner, industry), routing fixes when records land in the wrong queue, lifecycle-stage corrections when Ava-touched contacts haven't moved appropriately. About 1-2 credits per record. The result: clean records flowing through your CRM instead of fragmented duplicates and orphan contacts. See clean CRM data →.

After Ava books — meeting prep and follow-through. When Ava books a meeting on your calendar, Coco kicks off automatically: the pre-meeting brief lands in your inbox the morning of the call (about 8 credits per brief), the post-meeting follow-up draft queues in your Gmail right after the call (about 3-5 credits per draft), and any CRM updates triggered by the meeting (deal-stage change, next-step task, call notes, owner reassignment) queue for your approval. The handoff from Ava to a human AE stops being a manual context-pull. See prep sales meetings → and automate follow-ups →.

Around the edges — reporting and re-engagement. Coco watches the deals Ava originated, surfaces stale ones (silent past your threshold), drafts re-engagement messages, and reports on which Ava-sourced workflows actually convert. About 5-7 credits per stalled-deal sweep on a small batch. You stop relying on Ava's in-platform reporting alone and start seeing Ava-sourced conversion across your full stack.

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

Artisan ships native integrations with major CRMs. HubSpot and Salesforce both have direct connectors, which is the surface Coco uses for the bulk of the orchestration. Webhook and API surface exists for the Artisan platform itself; what's directly connectable depends on your Artisan tier and what their API exposes.

Where Artisan exposes APIs or webhooks directly (booked-meeting events, contact-touched events, sequence state), Coco connects directly. Where it doesn't, Coco coordinates at the workflow seams: shared CRM (HubSpot → or Salesforce →) as the source of truth, Coco watching for changes on its side, Ava operating on hers. The CRM becomes the orchestration substrate.

Honest constraint: this is not a one-click "drop Coco into Artisan" install. It's an orchestration pattern. Setup is typically a 30-minute connection flow (Coco's auth, Artisan's API or webhook setup where available, shared CRM connection) plus one workflow approval per recurring pattern you want to enable. Once set up, the cross-tool execution runs without supervision.

The workflow divide

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

The pattern: Ava runs the autonomous volume work that AI BDRs 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

Artisan prices like a junior BDR headcount slot — typically in the high four-figures to low five-figures per month per AI BDR (annual contracts; pricing varies by tier and volume). The price assumes you're replacing or augmenting BDR headcount.

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

For teams considering Artisan but not yet ready for the contract, Coco can run leaner outbound at lower volume (no autonomous send by default; per-draft approval) until the volume bottleneck makes Artisan worth the price. Many teams start with Coco-only and add Artisan when outbound volume becomes the specific bottleneck, not the general aspiration.

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. Artisan for outbound. Apollo or ZoomInfo for data. Outreach or Salesloft for sequencing inside reps' workflows. HubSpot for CRM. Slack for comms. Gmail for relationship-stage email. The tools each work in isolation; 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 Artisan specifically, Ava keeps doing what she does well while Coco handles the work that surrounds her — making the Artisan investment more strategic instead of more siloed.

Same pattern Coco applies to 11x → and Salesloft →. Different tools, same wedge. For GTM leaders → running multi-tool stacks, the orchestration layer is often the missing piece between "we bought the tools" and "the tools are working together."

Frequently asked questions

Do I need to keep Artisan if I have Coco?

If outbound volume is your primary bottleneck and Ava is hitting it, yes — keep Artisan. Coco doesn't replicate the autonomous-outbound capability across email and LinkedIn that Artisan specializes in. Coco handles the workflow around it. The two tools are complementary, not substitutes.

How do Coco and Artisan share data?

Through Artisan'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. For deeper coordination on capabilities Artisan's API doesn't expose yet, the CRM becomes the substrate where both tools land their updates and Coco watches for changes.

Can Coco trigger Artisan campaigns?

Where Artisan exposes campaign-creation APIs, yes. Where it doesn't, Coco hands you the ICP and the research brief; you launch the campaign in Artisan's platform. The integration is honest about what's directly automated versus coordinated at the seam — no fake "one-click campaign creation" that's really a manual handoff dressed up.

What's the setup time?

About 30 minutes for the initial connection (Coco's auth flow, Artisan's API or webhook setup where available, 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 Ava already does?

No — by design. Coco won't run autonomous outbound at the volume Ava does. That's Ava's specialty. Coco runs the broader workflow that Ava doesn't touch: deeper research, CRM hygiene, meeting prep, follow-through, stalled-deal sweeps, cross-stack reporting. The two layers stay clean.

Will Coco re-engage the meetings Ava books?

Yes. Once a meeting is booked through Ava, Coco handles the pre-meeting brief, the post-meeting follow-up draft, and any CRM updates triggered by the meeting (stage change, next-step task, call notes). The handoff from Ava to a human AE stops being a context-pull.

Can I use Coco without Artisan?

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 Artisan when outbound volume becomes the specific bottleneck. The reverse is also true: many Artisan customers add Coco because the work around Ava was getting dropped.

Get started

If you're already running Artisan and the work around Ava is dropping (research depth missing, CRM records messy, follow-ups not getting sent, stalled deals not getting re-engaged), the integration takes about half an 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.