The follow-up you meant to send on Wednesday

Say a new user signs up on Tuesday. You mean to send a useful note on Wednesday, then a bug, a customer call and a release get in the way. By Friday the note is still a draft and the user has gone quiet.

In our view, email marketing for founders rarely fails for lack of ideas. You already know you should have a welcome sequence. It fails because building and maintaining one is a job, and on a small team nobody has that job.

This playbook is for a founder with no marketing hire. It covers one sequence, one product event and a two-hour block each month. An AI agent does the building. You do the deciding.

Email marketing without a marketer: what changes

	By hand	With an AI agent
Build	You lay out each email and wire each step yourself	You describe the flow and the agent creates the templates and the sequence
Maintain	You remember to revisit it, or you don't	You ask for one change a month and review it
Report	You go looking through dashboards	You ask what happened and get the numbers back
Decide what sends	You	Still you

The last row is the one that matters. In Pombo, an agent connected over MCP can create segments, draft templates, build sequences and read analytics. The full list is in our docs. It can't send or schedule a campaign. That stays a click in Pombo, and anything that sends still has to pass our sending gates.

That split isn't only our opinion. The Model Context Protocol specification recommends that a person can always refuse a tool call before it runs.[1]

Email marketing for founders: the minimum setup

Solo founder email marketing needs four things. You do most of them once.

A verified sending domain and a mailing address. Verify your domain and add your address. We review every new account before it can send. The review starts once those two are in place, we review within 2 business hours, and we email you when you're approved. You can build everything below while you wait.
Permission. Before you send, confirm that each person agreed to hear from you. We ask you to attest to that before anything sends.
One event. Your backend tells Pombo when someone signs up.
One goal. The event that means a new user got something out of your product, such as onboarding.completed.

The event is one request from your backend:

curl -X POST https://flypombo.com/api/v1/events \
  -H "Authorization: Bearer pombo_..." \
  -H "Content-Type: application/json" \
  -d '{"event": "user.created", "email": "[email protected]", "properties": {"plan": "free"}}'

The API key needs the events:write scope. An email address we haven't seen creates the contact, and a 202 means the event was recorded. Whatever you put in properties is available in the email as {{ event.plan }}. More detail is in the events docs.

Not sure which events are worth sending? Start with signup and add the rest later. Product events to track covers the short list, and event-triggered email explains why an event beats a schedule.

The first sequence: three emails and a goal

Don't build onboarding, win-back and upgrade emails in one sitting. Build the welcome sequence and nothing else.

Give your agent a prompt like this:

Build a welcome sequence triggered by user.created. Email 1 goes out immediately: thank them and name the one thing to do first. Wait 2 days. Email 2 shows how to do that thing, with one link. Wait 4 days. Email 3 is a short check-in asking what got in the way. Set the goal to onboarding.completed and stop anyone who reaches it. Leave the sequence in draft.

The agent creates the three templates and the sequence. Subject lines can be as plain as the emails:

Welcome. Here's the one thing to do first
Stuck on setup? This takes two minutes
What got in the way?

The 2 and 4 day waits are a starting point, not a rule. Welcome email sequence examples has five variations with the reasoning behind each delay. If you'd rather build it yourself, the welcome sequence guide walks through the same steps in the interface. For the whole workflow run from a coding agent, read email marketing from Claude Code.

The goal does two jobs. The sequence reports a conversion rate against it, and a contact who reaches it partway through is stopped, so nobody gets a setup nudge for something they finished yesterday.

Before the sequence goes live, simulate it. Simulation runs the sequence against your real contacts without sending anything. You see who would enroll and what each person would receive, with the merge tags filled in. Read every email as it renders. Then set the sequence active yourself.

The two-hour monthly routine

Two hours is a timebox, not a quota. If the sequence is doing its job, stop early.

30 minutes: check the inputs. Open Settings, Events. It lists every event name you've sent, how many arrived in the last seven days, and which sequences and goals use each one. If the user.created count looks nothing like your signups, fix that before touching any copy.
30 minutes: read the numbers. Ask the agent for the sequence's analytics for the month. We calculate rates against deliveries, not sends.[2] Click rate is the engagement number to go by.[2] Treat open rate as a trend, not an absolute.[2] A bounce rate over 2% is worth a look.[2] Then check the goal's conversion rate, which is the number the sequence exists to move. Reading your analytics explains each one.
45 minutes: make one change. Pick the email with the weakest click rate and ask the agent to redraft it. Read the wording and check the logic. One change a month is enough to learn what moved.
15 minutes: simulate and decide. Run the simulation again, review the result, and activate the change if it's ready.

If nothing needs changing, close the laptop. Don't add an email to fill the calendar.

What stops a bad send

Two things sit underneath all of this, and neither depends on you or the agent remembering.

Suppression is automatic. An unsubscribed contact is skipped for marketing email. A bounced, complained or undeliverable address is suppressed for everything, transactional email included. An agent can't work around either. The suppression docs have the details.

The sending gates apply to every send. Your account has to be approved, you have to have attested to permission, your domain has to be verified, and you have to be under your weekly cap.

Connect your agent

Connect an AI agent to Pombo. You add our MCP server to Claude, Cursor or another MCP client by URL, sign in to Pombo and grant access. There's no API key to paste.

Frequently asked questions

How should founders get started with email marketing?

Start with one welcome sequence triggered by a signup event from your product, for people who gave permission to be emailed. Give it a goal, simulate it, and set it active yourself.

Can an AI agent send marketing emails for me?

In Pombo, an AI agent can create segments, draft templates, build sequences and read analytics. It cannot send or schedule a campaign. That stays a click in Pombo.

What does the two-hour monthly routine cover?

Thirty minutes checking that product events are arriving, thirty reading the numbers, forty-five on one change, and fifteen simulating it and deciding. If nothing needs changing, stop early.

Which numbers should a founder look at each month?

Read rates against deliveries, not sends. Go by click rate, treat open rate as a trend, and look into a bounce rate over 2%. The goal's conversion rate shows whether the sequence is working.

Do I need permission before sending marketing emails?

Yes. Only email people who agreed to hear from you. Pombo asks you to attest to that before anything sends.

Sources

Model Context Protocol Specification - Tools, Model Context Protocol
Reading your analytics | Pombo, flypombo.com