The Plainsend workspace
Bring your contacts with their consent, build journeys in the console or through your agent, approve what goes out, and see what happened.
Journeys 5
From the galleryNeeds you 3
Claude drafted it over MCP. Audience, message and send settings are ready; checks passed.
412 rows matched, 31 with no consent record. Nothing imports until you check it.
Day 6 of about three weeks. Most engaged contacts go first.
Welcome new patients · last 30 days
Human clicks leave out mail proxies, link scanners and prefetch. Bookings are traced to the last human click.
Agents and keys
New keyBuild
Agents and the CLI
Claude, or your own agent, drafts templates and journeys over MCP or the command line. Its key can't send to customers.
$ plainsend template publish welcome.mjml
# saved as version 4. Checks passed.
$ plainsend journey activate welcome
# waiting for approval from an ownerGallery
Install a pack, then change anything.
Brand kits
Logo, colours, fonts and footer, applied to every email.
Versions
See who changed what, a person or an agent, and restore any version.
Sources
A spreadsheet or your website form on every plan; Salesforce from Growth, with opt-outs written back; HubSpot is coming soon.
SalesforceConnected
Write opt-outs back
Broadcasts
Newsletters and announcements go through the same checks and approvals as journeys.
Sample Names and numbers in these pictures are examples, not customer data.
Run safely
Consent
Who agreed, how and when, per person. Opt-outs go back to your CRM.
Approvals
Agents build; an owner approves the audience, message, send settings and checks.
Warm-up
A daily cap from 50 that rises as your mail is accepted, most engaged contacts first.
Sending identity
SPF and DKIM on your domain, your postal address in every footer, and sending pauses itself if bounces climb.
harbourphysio.com.auVerified
Who can do whatComing
People, roles, agent keys, brands and domains. The rules exist today; a map of them in the console is coming.
Your data
Contacts and consent stay in Australia. Read the details on the security page.
Sample Names and numbers in these pictures are examples, not customer data.
Measure
Results
Mail proxies, link scanners and prefetch are left out of opens and clicks.
Attribution
Bookings and revenue credited to the last human click within a window, with the rule written in words.
Deliverability
Delivery, bounces and complaints for Gmail, Microsoft, Yahoo and the rest, side by side, against Google and Yahoo's lines.
Exports
Export your workspace and read contacts through the API.
$ plainsend workspace export
# brands, sources, templates, journeys, settings, without secretsSample Names and numbers in these pictures are examples, not customer data.
Small teams who want journeys without an enterprise contract, and teams leaving Marketing Cloud or HubSpot who want the same engine with less to run. Solo starts at $1 a month, billed yearly.
No. The console does everything an agent can. If you use Claude or your own agent, connect it over MCP or the CLI and let it draft while you approve.
No. Agent keys can draft, check and send tests to your team. Going live is an approval a person gives.
In Sydney, Australia. The security page lists every service that handles it.
A visual journey builder in the console, A/B tests with a winner, hosted forms with double opt-in, and HubSpot as a source. Each is marked as coming wherever the site mentions it.
Open a $1 workspace, connect a spreadsheet or your website form, and install a journey from the gallery.