Newsletters to audiences built from the contacts you already own.
Campaigns go to audiences built from your own contacts, sent through your Resend account. Consent, bounces and complaints sync back to each contact, and a campaign goes out only after the right role approves it.
Campaigns
Campaigns to audiences built from your contacts. A draft goes out through Resend only after the marketing lead approves it.
The consent records we run on
SegmentStream HQ keeps every contact's subscription and email status in sync with Resend, on the same records as our CRM.
How we run SegmentStream on SegmentStream →- Audiences are definitions over your contacts, so the list is never a stale export.
- Every send leaves out anyone unsubscribed, bounced or complained, because the send action checks consent.
- A draft goes out only after the role you choose approves it.
- Campaigns send through your own Resend account; the key stays with the platform.
- Bounces, complaints and unsubscribes sync back to the contact sales works.
What it covers
Audiences from your contacts
Customers, trials, a region or a stage of the pipeline: audiences are definitions over the contacts sales already works, kept current.
Consent on every send
The send action leaves out anyone who unsubscribed, bounced or complained, so no page, script or agent can skip it.
Approval before sending
A draft goes out only after the role you choose approves it. Nobody approves their own campaign.
Sending through Resend →
Campaigns send from your own domain through your Resend account. The API key stays with the platform.
Results on the contact
Deliveries, bounces, complaints and unsubscribes sync back to each contact, on the same records as sales.
Drafted with any agent →
Any agent connected over MCP can draft a campaign or build an audience, with the permissions of the member it works for.
Built from typed blocks
No new product to buy: the blocks below, written by an agent into your workspace's repository and deployed with one command.
None required.
$ segmentstream deploy
Every block ships together from one git repository your company owns. SegmentStream runs it.
- Mailchimp
- Customer.io broadcasts
- HubSpot marketing email
Subscribers and their consent load once through the ontology API, from Mailchimp, HubSpot or a CSV export, with the original consent dates kept. Resend sends from your own domain.
Enterprise, with our engineers
Our engineers move your lists and consent records in, set up sending from your domain, build the campaign and audience pages, and run the first sends with your team.
Self-serve, with your own agent
Connect Resend and tell your agent who you write to and who approves. It writes the audiences, the campaign actions and the pages.
Related solutions
Questions
Which email provider does it use?
Your own Resend account, through a ready-made connection, sending from your domain. Other email APIs connect through an API-key connection.
How is consent kept?
On the contact, with the date and source of every change. The send action reads it, so an unsubscribed or bounced address never gets a campaign, whoever sends it.
Can an agent write the newsletter?
Yes. An agent connected over MCP can write the draft and build the audience. Approval and sending stay with the roles you chose.
Rather have it built for you? Start a pilot.
Our engineers move your lists and consent records in, set up sending from your domain, build the campaign and audience pages, and run the first sends with your team.
- One solution, on your data, in your own workspace
- First version live in two weeks
- Parity proven before anything is switched off
- Fixed scope and price, credited to your contract if you continue
Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.
How the pilot worksYour company’s software, built by agents, owned by you.
$ segmentstream workspace create acme --region eu --subdomain acme
▸ Created workspace acme · database, warehouse and a private git repository
$ segmentstream workspace WORKSPACE-ID clone acme && cd acme
▸ your agent writes the five folders and runs the checks
$ git add -A && git commit -m "First version"
$ segmentstream deploy
▸ app, ontology API and MCP tools live for your invited members
Our engineers build the first version on your data in two weeks, at a fixed price.
Or join the waitlist for self-serve:
Self-serve opens to the waitlist first.