HeyCMO
Request an invitation

A marketing factory for B2B SaaS

Ongoing jobs and templates for the marketing work a B2B SaaS company on Stripe keeps doing. Each reads your own numbers and drafts the work. A person approves every message before it is sent.

It starts as an invitation-only, $0 operational Alpha for a small number of companies, with one job: when a customer’s payment fails, HeyCMO drafts a service email from the invoice’s own facts, and your own Resend sender sends it once you approve. The other jobs open one at a time.

Invitations are limited. Requesting one connects nothing and sends nothing.

Or check if AI assistants can read your site
Today

Morning, Maya. One draft needs your OK. Stripe reported one failed payment since Friday.

  • Email drafted a reminder to Brightkite about a failed $1,200.00 payment.Sends 1 email once approved

Payment reminder to Brightkite

Drafted from a failed Stripe invoice

To
finance@brightkite.example
Subject
Action needed: your $1,200.00 payment didn’t go through

Hi Brightkite team, the $1,200.00 payment for your Parcelwise Scale plan didn’t go through a week ago. Your bank asked for an extra security check, and it hasn’t been completed yet.

Complete the security check

Maya Ruiz, Parcelwise

What changes
One email to Brightkite’s finance address, from Parcelwise’s own Resend sender, once you approve. In Practice mode, nothing is sent.
Why
The invoice failed 7 days ago (from Stripe).
How to undo
A sent email can’t be unsent. If Brightkite pays first, the next reminder is cancelled.

Checks passed: your domain is set up to send, the invoice is still unpaid, and Brightkite isn’t on the do-not-contact list.

A sample for Parcelwise, a made-up freight software company. Practice mode: approving here sends nothing.

The marketing work that repeats

After product and sales, the weekly marketing work is what slips. HeyCMO is built to keep doing it, and to ask before anything goes out.

A card fails on a Friday, a trial stalls on a Tuesday, a page drops off the first page of search. Nobody was watching, because everybody was busy.

48 ongoing jobs
Each repeats on its own schedule, checks your numbers, and drafts only when something changed. Most checks find nothing, and you hear nothing.
45 templates
Work you run once, such as a launch or a new landing page. Each starts from the outcome you want and pauses for your OK at every step.
One place to approve
Every draft waits in your Inbox with why it was drafted, what changes if you approve it, and how to undo it.

Six areas, in the order to turn them on

  1. Know your numbers. Every number the other jobs use, checked first, each with its source.
  2. Stop losing revenue. Failed payments, quiet accounts and customer emails that stop working. The Alpha starts here.
  3. Turn visitors into customers. Trials that stall, sign-up steps that lose people and landing pages that slip.
  4. Get found. Search, AI answers, ads, social and press, for the people who don’t know you yet.
  5. Earn more per customer. Pricing page tests and accounts ready for a bigger plan.
  6. Get referrals and reviews. Review asks, replies, and partners who have gone quiet.
See every job and what it needs connected

How the Alpha starts

  1. Connect Stripe and your sender

    We set this up with you. Stripe access is a restricted key you create, and emails go out through your own authenticated Resend sender, not ours.

  2. Start in Practice mode

    Each company starts in Practice mode. When a payment fails, HeyCMO drafts the email from the invoice’s own facts. Approving it is checked and recorded, and nothing reaches your customer.

  3. Approve each message

    A person at your company approves the exact message before it is sent. If anything in it changes after that, it asks again. Going live is a separate step, and you can stop or revoke at any time.

The Alpha uses two of your tools: Stripe, read through a restricted key, and Resend, your own sender.

Nothing goes out without a person

HeyCMO reads Stripe and drafts. Before any message reaches a customer, a signed-in person at your company approves that exact message. No setting lets an email go out without a click.

Does on its own

  • Reads failed invoices from Stripe
  • Drafts a service email from each invoice’s facts
  • Asks Stripe again just before any send
  • Records every decision in your history

Asks a person first

  • Sending any email to a customer
  • Deleting anything

Not in the Alpha

  • Marketing emails and broadcasts
  • Ad spend
  • Social posting

Checks before any email goes out

  1. Pause switches. If anything is paused, nothing goes. A switch HeyCMO can’t read counts as paused.
  2. Do-not-contact list. People who unsubscribed, bounced or complained are skipped.
  3. A real invoice and a verified sender. The email needs a failed invoice behind it and a sending domain that is set up.
  4. Limits. Each company gets daily send limits before it goes live. At the limit, it stops.
  5. Your approval. A signed-in person at your company says yes to this exact message.
  6. Stripe, once more. Just before the send, HeyCMO reads the invoice again. If it has since been paid, voided or written off, or its subscription paused or cancelled, the send is refused.

Pause everything

One switch at the top of the web app stops every send and run in your workspace. Anyone on your team can pause, and an admin turns it back on.

Every decision goes into your history. Each entry is chained to the one before, so an edit shows up when you check. Signed daily checkpoints outside the database were enabled on 28 October 2026. The security page describes their limits.

Before any live send

Each company starts in Practice mode. Before it goes live, we agree and write down with you who approves, which invoices are eligible, who already emails these customers, who is already suppressed, the daily send limits and who can stop it.

You can stop or revoke at any time: pause the workspace, or revoke the Stripe key or your Resend key from your own accounts.

What the Alpha does and does not do

One job first, done carefully, for a small number of companies. The rest of the marketing factory opens one job at a time, each once it has been tested with real accounts.

In the Alpha

  • Failed-payment service emails: a first notice, then later reminders while an invoice stays unpaid, each drafted from the invoice and waiting for approval
  • Your own Stripe account, read through a restricted key, and your own authenticated Resend sender
  • Practice mode first, then Live once the limits are agreed with you
  • Recovery results reported honestly, below

Not available yet

  • WordPress publishing: later, and not available today
  • The other ongoing jobs and the templates, from search and content to advertising, social and PR: opening one at a time, and not available today
  • Marketing emails and broadcasts
  • Plans, prices and billing

$0

There is no charge in the Alpha. We don’t ask for payment details. Whether a paid plan ever exists is a separate decision, and this site lists no prices.

Recovery results, kept honest

Stripe tells HeyCMO when an invoice is paid. HeyCMO sorts each payment that follows a message into one of three groups, and keeps them apart.

Email-driven
Paid after an email, and not by Stripe’s own automatic retry. This is the only group counted, and even it is not proof the email caused the payment.
Automatic retry
Stripe’s own retry collected it. Reported, and never counted as the email’s.
Unknown
We can’t tell which. It stays unknown, and is never folded into either of the other two.

A payment after an email is not claimed as caused by it. With a handful of companies the numbers will be small, and a report says so.

Before you connect Stripe

The security page lists what protects your data today, what is built but not switched on, and what we don’t have yet.

What is a marketing factory?

Our name for what HeyCMO is: ongoing jobs that repeat and templates you run once, for the marketing work a B2B SaaS company keeps doing. Each reads your own numbers and drafts the work, and a person approves it. In the Alpha, one job runs: failed-payment recovery. What it does lists the rest.

Is it free?

Yes. The Alpha has no charge, and we don’t ask for payment details. If a paid plan is ever offered, it will be a separate offer.

Where does it run?

HeyCMO runs on Amazon Web Services in the US East region, with your data in a private database that can’t be reached from the internet. There is no EU hosting option yet. You review and approve in the web app.

What does it read?

In the Alpha: failed invoices and payment events from Stripe, through a restricted key you create, and delivery, bounce and complaint events from your own Resend account. Keys you store are encrypted, and no screen or API shows them again. Each job opening next says what it needs on What it does.

What if it gets something wrong?

You see every draft before it goes out, so you can edit it or decline it. A sent email can’t be unsent, so read it first. Your history shows what went out, when, and why. Stripe’s card retries, and what your Stripe settings do after the last retry, stay with Stripe.

Who is it not for?

Companies that don’t bill through Stripe or don’t send through Resend. Teams who want email sent with nobody reviewing it. And anyone who needs a SOC 2 report or single sign-on today: we don’t have either yet.

Is my data used to train models?

HeyCMO drafts with Anthropic’s Claude models through Anthropic’s API, and Anthropic’s commercial terms say it may not train models on customer content from its services. The security page quotes the provider’s terms and lists the other services that may see data.