For Marketing Teams
Run your email program end to end. No engineering ticket required.
Build segments, send broadcasts, design drip workflows on a visual canvas, preview and test templates, and watch the results — all from one dashboard, sending through your company's own SES. No AWS login. No waiting on a sprint.
Your email program shouldn't live in someone else's backlog
You know how this goes. Every campaign was a Jira ticket. Every audience change was a SQL request. Every automation was a sprint — scoped, estimated, shipped three weeks after the moment passed. Email is a marketing channel, but marketing couldn't touch it.
SendOps changes the split. Marketing gets the platform: segments, broadcasts, workflows, templates, results. Engineering gets the guardrails: template reviews, send approvals, frequency caps, roles. You ship campaigns the day you think of them — and nobody worries about what might break.
What stays the same
Full control for you. No surprises for engineering.
It's still your company's SES account. Everything you send goes through the AWS account your team already owns — same domains, same reputation, same infrastructure. SendOps is the layer on top.
Your application's transactional email is untouched. Password resets, receipts, and other code-driven sends keep working exactly as before. Your campaigns and their sends share analytics, not risk.
Templates stay version-controlled. Templates live in Git. When you edit one in the app, your change becomes a pull request — reviewed and merged like any other change, with full history.
Consent rules apply to everyone. Topics, per-topic consent, and the suppression list are enforced on every send — yours, engineering's, and every workflow's. There's no way around them, by design.
Your toolkit
Everything you need to run email — actually run it
Not read-only dashboards. The whole program: audiences, sends, automations, consent, and results.
Build audiences
Define segments with a query language readable enough to learn in an afternoon — plan is "pro" and last order is within 90 days. Or ask your team or your agent to write the query for you. Segments update as contact data changes.
→ Learn moreSend broadcasts
Pick a segment, pick a template, send a test to yourself, then schedule or send. Consent is applied automatically — anyone who opted out of the topic is excluded before the send starts. Every broadcast gets its own results page.
→ Learn moreDesign drip workflows
Build multi-step journeys on a visual canvas: waits, branches, enrollment rules, exit conditions. It's the same workflow your engineers see as code — one definition, two views, always in sync.
→ Learn morePreview & test templates
Open any template, choose a test data profile — VIP customer, first-time buyer, your own — and see the rendered email. One click sends a real test to your inbox. No deploy, no staging environment.
→ Learn moreOwn consent
Organize sending into topics with per-topic consent. Manage the suppression list. Ship a branded unsubscribe page under your own domain. Recipients control what they get — and every send respects it.
→ Learn moreWatch results
Opens, clicks, deliveries, bounces, complaints — by campaign, by template, by domain. Compare broadcasts, spot the subject line that worked, and catch a deliverability dip before it becomes a problem.
→ Learn moreA day with SendOps
Launching a feature announcement, start to finish
Scenario: your product ships a new feature Thursday. Here's the campaign — no ticket filed, no developer pulled in.
Build the segment.
You're announcing a new feature to active customers on paid plans. Open Segments, write the query — or duplicate last month's launch segment and adjust it. The audience count updates as you type.
Check the coverage preview.
Before you send, SendOps shows how many contacts in the segment are missing attributes your template uses — say, 3% have no first name. Fix the template's fallback or narrow the segment. No broken merge tags in anyone's inbox.
Send a test to yourself.
Pick a test data profile and send a real email to your inbox. Check it on desktop and mobile. Tweak the subject line, test again. Seconds per round, no deploy.
Schedule the broadcast.
Set the send time and confirm. Consent is applied automatically — contacts who opted out of product announcements are excluded, suppressed addresses never get queued. It sends through your company's own SES.
Watch the results come in.
The broadcast gets its own results page: deliveries, opens, clicks, bounces — live as events arrive from SES. Compare against your last launch. Share the link with your team.
Follow up with a drip workflow.
Non-openers after three days? A workflow enrolls them into a follow-up sequence with a different subject line. Anyone who unsubscribes along the way exits automatically. You built it on the canvas — no sprint required.
Guardrails, not gatekeeping
You move fast. Engineering stays in control where it matters.
The old trade-off was speed or safety — marketing waits, or engineering worries. SendOps gives you both. You build and send freely inside guardrails your engineering team defines once. The Marketer role has everything a lifecycle marketer needs, and nothing that can take production down.
Engineering-owned guardrails
Templates change through PRs — templates and git-synced definitions live in the repo. Your in-app edits become pull requests automatically — engineering reviews, you never break production
Send approval — workflows and broadcasts can require a manual approval step before anything goes out
Frequency caps — org-wide limits stop any combination of broadcasts and workflows from over-mailing the same contact
Scoped roles — roles control who can send, who can approve, and who can only view — per organization
Roles are assigned per organization. A user can be a Marketer in one org and a Developer in another.
Common questions from marketing
Can I actually send without engineering?
Yes. Broadcasts and workflows are yours to build, test, and send from the dashboard. Consent, suppression, and frequency caps apply automatically to everything you send, so there's no safety review needed for routine campaigns. Engineering sets the guardrails once; you work inside them.
Can I edit templates?
You can propose edits directly in the app. Your changes become pull requests automatically — engineering reviews and merges them like any other code change. You get the speed of in-app editing without the risk of breaking a production template.
Do I need AWS access?
No. Engineering connects SendOps to your company's AWS account once during setup. After that, everything you need — segments, broadcasts, workflows, templates, results — is in the SendOps dashboard. You'll never see the AWS console.
Can I manage who receives what?
Yes. Topics organize your sending into categories, and each contact has per-topic consent. You manage the suppression list, and the unsubscribe page is branded and hosted for you. Every broadcast and workflow respects consent automatically.
What does it cost as our list grows?
Nothing extra. SendOps has no per-contact pricing — your list can grow from a thousand contacts to a million without changing your bill. You pay AWS for what you send through SES, at SES rates.
Your email program, finally yours.
Free plan available. No contact limits. No per-contact pricing.
