Nothing leaves until you press approve
Canopus is an autonomous growth manager for SaaS that writes email campaigns for an audience drawn from your CRM and sends them from your own domain, but only after you have read and approved every message.
An agent drafts the campaign, one to five messages, says what it is betting on, and stops. You can also write it yourself, in plain text or in your own HTML. Nothing leaves until you approve it, and then the mail goes out from the domain you already own, with the deliverability, the bounces and the complaints handled for you. The audience is a saved view of your CRM, and every send is written back to the contact.
How does a campaign get written and sent?
An agent writes the campaign, or you do
The agent receives your adopted strategy, your product brief, the audience it is writing to and how many people are in it right now, one format from the library, and what previous campaigns taught. It returns up to five messages, a goal, and a hypothesis stated so it can turn out wrong. You can write a campaign by hand instead, in plain text or by pasting your own HTML.
The first message gets two versions
Step one carries variants a and b, testing one difference the agent can name. Every later step has a single version. Recipients are assigned round robin at enrolment, because chance produces a 60/40 split often enough to make a hundred-person test unreadable.
You read it and approve it
The campaign sits at proposed until a person moves it. Approval checks four things: your sending domain is verified, a sender address and postal identity exist, the segment still resolves and is not empty, and the status has not moved under you. Who approved it goes to the audit log.
Email sequence3 stepsDay 0Your trial stalled on step twoSent immediatelyVariant AYour trial stalled on step twoVariant BTwo minutes to finish your setupDay 3The one report founders read first3 days after the previous oneDay 7Your trial is about to end4 days after the previous oneWaiting for your approvalIt sends from your domain, in batches
Twenty-five messages at a time, and the next batch a minute later. Each recipient carries their own position and their own due date, so a five-step sequence spaced day 0, day 3, day 7 needs no schedule to reconcile. The messages leave from your verified domain, and Canopus watches its reputation.
Clicks come back, and stop the ones who bought
The button goes through a signed redirect that records one click per person per message. A recipient whose Stripe status turned into a paying subscription after enrolment is dropped from the rest of the sequence rather than sold to again.
Attributed revenueLast 30 daysNew monthly revenue€3,180With campaigns€1,940Previous periodat least +€1,240
Last touch, 14 days, against the equivalent previous period
What does this replace?
Writing five emails in one sitting and losing the thread by message three
An agent writes the whole sequence against one format, one segment and one stated hypothesis.
Replaces: A blank documentPaying for a sequencing tool that sends from its own infrastructure
Sending goes out from your own verified domain, under your reputation, with no sending tool to pay for.
Replaces: A sequencing toolKeeping a spreadsheet of who is on which step and when the next one is due
One row per recipient holds the step, the variant and the next send time.
Replaces: A tracking sheetRemembering to take an unsubscribe out of the other three campaigns
One unsubscribe flags the contact and stops them in every sequence they are part way through.
Replaces: Manual list hygieneChasing bounces and spam complaints in a sending tool’s console
A hard bounce or a complaint stops the recipient everywhere, and reputation is watched per domain.
Replaces: A sending consoleDeciding by feel which subject line worked
A variant needs 15 sends before its rate is compared, and has to beat the other by half again to be called a winner.
Replaces: Guesswork
What exactly gets sent, and what gets measured?
The producer is an agent with the narrowest schema in this product, because it is the only place where a model's words reach somebody else's customers. It is given the product brief, the positioning of your adopted strategy and the segment it writes for with its pains and objections, the definition of the audience, the current size of that audience, one format drawn from the library, and the lines the playbook has recorded from campaigns that already finished. It returns a name, a goal, a hypothesis, and up to five messages, the first of which may carry a second variant for the A/B test. What the agent writes is plain text between 40 and 2,500 characters, with a blank line between paragraphs and a single labelled call to action rather than free HTML, and the renderer escapes every character before it becomes markup. A message you write yourself can be your own HTML, pasted or imported from a file: it is sanitised on the server when it is saved (scripts, event handlers, frames and forms are removed), every link in it goes through the tracked redirect, and Canopus adds the footer with your sender identity and the unsubscribe link.
Approval is a gate with four locks and it is the only door. A campaign starts at proposed and the worker refuses anything that is not approved or running. Before the transition, Canopus checks that your sending domain is verified, that a sender address and a postal identity exist (both are legally required and neither can be guessed), that the segment still resolves and holds somebody, and that the campaign is still proposed. That last check is a guard on the update itself, so two administrators pressing the button at the same moment produce one approval and one conflict rather than two sends. Editing is refused once sending starts: half a sequence in one wording and half in another is two campaigns whose results cannot be read.
Every message leaves from your own domain. You add it once, publish the three or four DNS records Canopus shows you, and it is checked until it reads verified. From then on the sending is Canopus’s job: the messages carry your sender name and your postal identity in the footer, deliverability is watched, bounces and complaints come back and stop the recipient everywhere with nothing for you to wire, and the reputation earned or lost is tied to your domain rather than to a pool shared with other customers. That is not an implementation detail: an email arriving from a name the recipient has never heard of gets marked as spam. It also means Canopus cannot send until a domain is verified, which is checked at approval rather than discovered by a bounce. Each plan carries a monthly email quota, 5,000, 25,000 or 100,000 emails, and the offer is sized on it.
One organization may send 500 emails a day across every campaign, a default guardrail that sits under the monthly quota of your plan. The cap is about the shape of a mistake. An agent proposing a five-step sequence to a segment that turns out to hold forty thousand people should hit a wall we put there, well before you meet a bill you did not expect. The count comes from the send events actually recorded, because a counter can drift and the events are what left. Reaching the cap simply defers the run six hours, and the next run picks up exactly where it stopped. Reaching the quota stops sending until the plan is raised or the month turns, and says so on the campaign page rather than in an invoice. You are told at 80 and at 100 percent of the quota.
Unsubscribing works twice over. The header is RFC 8058 one-click, so the button mail clients show next to the sender name works, and it is a POST endpoint on purpose: the link scanners that follow every URL in an email issue GET requests and would opt people out silently. The link in the footer opens a confirmation page instead. Both run the same function, which flags the contact for good and stops them in every campaign they are currently part way through, because a sequence carries its own enrolment list and would otherwise keep writing to somebody the segment no longer contains. Clicking twice changes something once.
Clicks and conversions are the measures. A send and a click are recorded by Canopus itself, against the person, so a campaign has a real funnel with nothing configured: sends, clicks, then trials and paying customers through attribution. Delivery, bounce and complaint data arrive with domain sending: a hard bounce or a complaint stops the recipient everywhere, through the same function unsubscribing calls, and the campaign page shows delivered and bounced beside sent. Opens are not the measure, on purpose: an open is a pixel a mail client may or may not load, and a rate built on it says more about the client than about the reader. On Growth and Scale, a campaign can be aimed at a saved audience built over your CRM, your Stripe cohorts and your product activity. Also on Growth and Scale, a newsletter goes to its own subscriber list, confirmed by double opt-in, from the same domain and within the same quota.
Questions founders ask
See your own numbers first
Connect Stripe and your real revenue is on screen in five minutes, before an agent has said a word. Create your account, answer the questions, and your strategy gets written.