Product

How outreach actually runs

Connect an account, put people into a sequence, and the steps go out on their own. Here is what that looks like on an ordinary Wednesday.

Today's sendingLive while sending

24 sent40 cap

Midday on an ordinary Wednesday, against the shipped daily cap. The count only moves while sending is on, and it stops climbing the moment the cap is reached.

SentSpread through the day, inside your sending window.
HeldDaily ceiling reached. Nothing else goes out today.

Offerings

What we offer

One engine for LinkedIn and email. Choose who runs the day-to-day — and whether you want Spark Autopilot writing the morning plan.

Core productSequence outreachConnect LinkedIn and email, start prospects on a sequence, and steps go out on schedule — stopping the moment someone replies.Three ways to workIndependent, team, or with a specialistRun it yourself, share one workspace with a team, or bring in a specialist — a coach alongside you while you send, or operators working your account in your voice.Included, plus an add-onSpark & Spark AutopilotSpark drafts while you work the account — included on every plan. Add Autopilot for a written morning plan across your whole book.For agencies and coachesYour brand, your clientsStand the product up under your name and domain, with each client in their own workspace.

What actually happens

Four things run without you

Steps go out on scheduleYou set the delays. Sends spread through the day instead of blasting at once. Anything that couldn't send says why, on the row — so when you open the app, the morning's work is already done.
You know today's countThe header shows today's sends against the real daily ceiling — including the lower warm-up cap on a new account — only while sending is on.
Replies land where you'll see themAn answer pauses the sequence and arrives in one inbox. Notes, ownership, and a board keep the conversation next to the send.
It stops before it costs youEmail lookups and AI drafts have a monthly limit and a daily hard cap. When a limit hits, that action stops — it does not keep spending in the background.

Spark Autopilot

Your outreach has a plan before you open the laptop

Nobody on your list quietly falls off because the week got busy. Spark reads your whole book, tells you who to follow up, who's gone quiet, and which reply needs a person — and nothing reaches anyone until someone says yes.

How Spark Autopilot works

API and agents

Automate the boring parts

Everything above also happens through an API — for scripts, or for an agent working your workspace instead of clicking through it.

The assistant drafts, you sendTurn a prospect's profile into a first message, or polish one you wrote, without leaving the inbox. Every draft is yours to edit before it goes anywhere — nothing sends off a suggestion on its own. Drafting shares the same monthly limit and daily cap as everything else metered.
A REST API for the whole workspaceSearch, import, tag, start outreach, connect, message, approve — anything the console does, a script can do with a key you create in Settings → Integrations. Writes share the same rate limit a person clicking through the app would hit, so an API key can't outrun the account it's sending from.
An MCP server, for agents instead of scriptsPoint Claude Code, Cursor, Claude Desktop, or any MCP-capable agent at your workspace and it gets purpose-built tools — list prospects, import a list, start someone on a sequence — instead of a REST reference to work through by hand. A key only ever sees the one workspace it belongs to.
Same limits, whoever's drivingAn API key or an agent is held by the same daily caps, the same approval queue if you run with holds on, and the same halt on sending as a person clicking send. Automating the work doesn't raise the ceiling on it.

Read the integration guide

See it on your own account

Connect an account and watch the first day run. Nothing sends until you say so.

See plans and limits