Product

Features only matter when they kill a real pain

Each capability below as pain → what ships → outcome, plus the console surfaces it covers. Plans and cost math live on Pricing — this page is the product walkthrough only.

Start free See which plan fits

01

Client workspaces

Pain: Account managers lose hours switching ESP logins and asking “which brand is this?” Wrong context means wrong list, wrong from-address, wrong report.

What ships: A single agency desk with a top-bar workspace switcher. Campaigns, contacts, deliverability, automations, forms, and reports stay scoped to the client you’re serving. Assign AMs so books stay clean.

Outcome: Isolation is the product: one bad list or domain never crosses into another client. Morning standups start from “open TechNova,” not “find the password.”

Covers in-product

  • Workspace switcher
  • Client isolation
  • AM assignments
  • Onboarding toward first send

02

BYO SES / SendGrid / Mailgun / SMTP

Pain: Per-contact SaaS × N clients kills margin. Raw SES is cheap but too technical for most AMs. Mixing brands on one ESP burns shared reputation.

What ships: Connect each client’s provider account. They keep send cost and reputation. Guided setup aims at domain/sender readiness and a safe first test send — not a docs scavenger hunt.

Outcome: You sell process and software seats. The ESP invoice stays where it belongs. Client A on SES and Client B on SendGrid can coexist in one agency.

Covers in-product

  • Multi-provider
  • Reputation isolation
  • Sending profiles
  • Test send

03

Campaign pipeline & approvals

Pain: Drafts live in Docs; “approve?” lives in Slack; nobody knows if it’s sendable. After launch, there’s no clean audit of who signed off.

What ships: Draft → review → ready → schedule/send with optional client review links. Content editors polish; AMs and owners move status. Needs-attention surfaces stuck approvals and blocked work.

Outcome: Approvals become a product workflow with status, not chat archaeology. Clients preview on a calm link — they don’t need the ops console.

Covers in-product

  • Pipeline statuses
  • Client review links
  • Test send
  • Schedule / send
  • Needs attention

04

Deliverability that blocks bad sends

Pain: Teams learn SPF/DKIM only after a bounce spike. Webhooks are “someone’s weekend project.” Sends go out when the domain isn’t ready.

What ships: Readiness checks for provider, domain, and sender. Send gates return a clear code, message, and fix path. Inbound bounce/complaint webhooks live under each client’s setup. canSend vs canReport stays honest.

Outcome: Fewer emergency fire drills. You don’t burn a list to discover DNS was wrong. Reporting can still work while send is blocked.

Covers in-product

  • Readiness score
  • Send gates
  • Domains & senders
  • Webhooks
  • Sending profiles

05

Contacts, lists, segments, suppression

Pain: CSVs collide across brands. Suppressions aren’t respected. “Who engaged?” requires exporting from the ESP again.

What ships: Per-workspace contacts with lists, segments, and suppression. Import flows emphasize trust. Engagement stays attached to the client you’re serving.

Outcome: Hygiene and targeting without leaking audiences between brands — or rebuilding segments in five tools.

Covers in-product

  • Contacts
  • Lists
  • Segments
  • Suppression
  • Import

06

Automations & signup forms

Pain: Welcome journeys get rebuilt in every ESP login. Form leads die in inboxes or spreadsheets. Nobody knows which list an embed writes to.

What ships: Per-client journeys you publish once, with enrollments pinned safely. Hosted forms (URL or embed) enroll to lists, tags, and live automations — spam protection and optional double opt-in included.

Outcome: Always-on retention without spreadsheet glue. Forms become the front door to the journey you already designed.

Covers in-product

  • Journey builder
  • Publish / enroll
  • Hosted forms
  • Destinations
  • Double opt-in

07

Reports & white-label proof

Pain: Monthly proof is screenshots from the ESP, which trains the client to need the ESP — not you. Agency branding is an afterthought.

What ships: Agency overview plus shareable packs. Growth/Scale white-label colors, hide-platform branding, and custom domain for portal/report chrome.

Outcome: You look like the agency of record. Clients open a branded link instead of asking for another PDF collage.

Covers in-product

  • Overview hub
  • Share links
  • White-label
  • Custom domain
  • Portal chrome

08

Team roles & client portal

Pain: Everyone shares one ESP login. Clients get admin. Editors can accidentally send. Billing changes aren’t gated.

What ships: Owner, admin, account manager, content editor — plus portal approvers and viewers. Billing changes stay owner-only. Portal users get review/results, not ops chrome.

Outcome: Staffing matches reality: draft, ship, approve, and bill are different jobs with different permissions.

Covers in-product

  • RBAC
  • Seat limits
  • Portal invites
  • Owner-only billing

Ready to pick a plan?

Free proves the desk. Growth adds white-label. Scale removes client/seat ceilings.

View pricing Start free