Outbound that Claude
can operate with your approval.

You are the founder of a B2B company between two and twenty people. You raised a seed, maybe a small extension, and the next round depends on showing real revenue traction that a deck cannot fake. You are not yet at the point where hiring a senior SDR makes economic sense, and the contractor experiments you have already run produced reports that read better than the underlying numbers. Your week alternates between product work, customer calls, and a Sunday-night list-building session you have started to resent.

You know your buyer. You can sit on a sales call and answer the technical questions yourself. What you do not have is a repeatable way to source a bounded cohort, inspect the imported rows, publish a reviewed workflow, and hand supported work to an approved destination. Coil gives those steps one organization-scoped operating surface while leaving targeting judgment and consequential approvals with you.

Talk to enough founders running their own outreach and the same four complaints come up, in the same order, every time. None of them are mysterious. All of them are fixable once you separate the rote layer from the judgement layer.

1. Time.

A manual setup spreads targeting, source runs, row review, workflow configuration, and downstream handoff across several tools. The operational cost is repeated setup and lost context. Coil keeps those supported steps in one organization-scoped workflow without claiming how much time a particular team will save.

2. List quality.

Source data becomes less useful when nobody can reproduce how a cohort was assembled. The Sales Nav scraper and the prospect scraper run bounded source jobs with explicit criteria and import their results into the same organization-scoped lead surface for review.

3. Message specificity.

A founder who has never written a cold email is still better at the opener than a contractor who has written ten thousand of them, because the founder knows what the prospect actually wants to read. The hard part is operationalising that taste at volume. Coil can run a reviewed schema-constrained transform over inputs you supply; it does not currently promise autonomous funding, hiring, launch, or podcast research.

4. Result handling.

A source run, recipe run, or webhook attempt should not disappear behind a generic success message. Coil exposes typed lifecycle states for supported work and records downstream delivery results. It does not currently classify replies or turn delivery data into campaign analytics.

A founder can operate this workflow directly or let an approved agent use the authenticated API or JSON CLI. The same organization scope, role gates, and explicit provider-spend confirmations apply. You retain the strategy, credentials, and consequential approvals.

Source. Set explicit targeting fields in the dashboard or JSON CLI. Run the prospect skill or Sales Navigator source depending on whether you have a URL in hand. Explicitly approve a bounded provider run, wait for terminal status, then review the imported organization-scoped rows before export or downstream use.

Review a recipe. Start from an installed curated template or typed draft. Validate its exact capabilities and supplied inputs before a human admin publishes it. An optional OpenRouter transform can run only when its schema and provider connection are configured. The agent calls a recipe you reviewed, admits it with explicit provider approval, and reports durable status.

Hand off. Use the configured SmartLead integration for the supported campaign handoff, or an admin-published webhook automation for an approved destination and field set. Coil does not promise inbox-eligibility or bounce forecasts.

Inspect. Review source, recipe, automation, and delivery statuses through their current dashboard, API, or JSON CLI surfaces. Coil does not currently claim reply-rate analytics or automatic opener-variant reporting.

Source, recipe, automation, and delivery records preserve their own typed lifecycle state. Review those records directly rather than inferring completion from a queued request or a downstream HTTP response alone.

Coil is built for the founder doing their own outreach. If you have already hired a fifty-person revenue team with a RevOps engineer, a dedicated SDR pod, and a workflow appetite that runs to hundreds of branching steps, Clay and Apollo are the denser tools. They reward operators who can build complex multi-stage enrichment pipelines, and the integration coverage on the long-tail data sources is wider than ours today. The honest move at that scale is to keep your existing seats and check back when your ICP simplifies.

Similarly, if you need a first-party sender, reply inbox, dialer, or multichannel sequence product, Coil is not the replacement. Keep the system that owns those jobs and use Coil only for the bounded source, recipe, and supported handoff surfaces it ships today.

The deep guide for this persona lives in the AI cold outreach for founders pillar. The product surfaces this page refers to are documented on the prospect scraper and the recipe library pages. Anton, who builds Coil, is on the about page with a short note on why this product exists.