Email campaigns

Email campaigns

Cold-email outreach, set up and operated by the outsend team on your behalf. This module is on-demand: there is no self-serve endpoint and no "Run" button. You ask, we build, you receive.

Purpose

Email campaigns turn your outsend prospect data into sequenced outreach that actually lands in the inbox. The goal is simple: get your offer in front of qualified prospects, track who reads and replies, and feed the answers back into your pipeline — without you touching deliverability plumbing.

You bring the audience (already living in outsend after scraping, enrichment and qualification) and the message intent. We bring the sending infrastructure, the warmup discipline, and the sequence logic.

How to request it

There is no public API to start an email campaign. The module is delivered through a conversation with the team.

Two equivalent ways to open that conversation:

• From the dashboard. Open the Email campaigns module card. The primary CTA does not launch a job — it opens a feedback thread with topic on_demand_email, pre-filled with the questions we need answered to scope the work.
• Programmatically. POST /api/feedback/threads with topic: "on_demand_email" and your initial message in the body. The team is notified and replies in the same thread, viewable from your dashboard.

Either path lands in the same place: a thread where we agree on volume, sending domain, sequence shape, and timing before any email goes out.

What gets delivered

Every engagement covers the same core capabilities, tuned to your account:

• Configuration of your sending domain, including warmup before any campaign starts so messages don't land in spam on day one.
• Sequence build-out — first-touch email plus spaced follow-ups, written with you, reviewed before send.
• Per-prospect personalisation drawn from the data you already have in outsend (company, role, signals, whatever your enrichment captured).
• Open and click tracking on every message.
• Automatic reply detection that pauses follow-ups the moment a prospect responds, so nobody gets chased after they've answered.
• Detailed reporting on open rate, reply rate, and downstream conversion, surfaced back into your dashboard.

The deliverables list is the contract. If something isn't in it, ask in the thread — we'll either fold it in or tell you why we won't.

Why on-demand

Cold email at any meaningful volume is a deliverability problem dressed up as a copywriting problem. Getting it wrong is expensive: a burned domain takes weeks to recover, and the damage is silent — your messages stop landing long before anyone tells you.

The setup is irreducibly per-customer. Domain warmup, SPF, DKIM, DMARC alignment, dedicated IP allocation when volume justifies it, ramp schedules, bounce and complaint thresholds — none of this generalises into a "click here to send" button without handing customers a footgun.

So we don't ship the button. We ship the outcome instead: a configured sending stack and a sequence that's been pressure-tested before the first prospect sees it.

Pricing

Bespoke. Pricing depends on monthly send volume, number of sequences, whether you bring an existing domain or need one provisioned and warmed from scratch, and the depth of personalisation. There is no listed rate card because there is no listed configuration.

Open the thread, share your expected volume and sequence shape, and you'll get a quote in the same conversation.

What's next

• SMS campaigns — same on-demand model, mobile channel.
• WhatsApp campaigns — same on-demand model, conversational channel.