# Drip campaigns that start on what people do Drip campaign software that starts each series on what people do: a signup, a purchase or an app event starts a timed email sequence on your own server. For drip campaigns Drip campaign email marketing software A signup, a purchase, something in your app: any event can start a timed series. Your sequences, your emails, on your own server. Watch demo The product One system for you, your agent, or both. Everything in Mimeo works both ways: a full automation studio when you want hands-on, and files, skills, and an MCP server your agent operates end-to-end. - Subscribers.: Full profiles, event history, every email received.: person - Emails.: Markdown or HTML, templates, personalization.: mail - Flows.: Triggers, branches, logic, dry runs.: branch - Sequences.: Drip campaigns in one readable view.: list - Events.: What subscribers do shapes what they hear next.: pulse - Guards.: No emails crashing into timed sequences.: shield - Tags & segments.: Filter and target without ceremony.: tag - Purchase history.: Messaging that knows where each customer is.: bag - Manager repo.: Manage Mimeo from a repo with agent skills, MCP and everything editable in files.: console The old way Most drips only know when someone joined. - A typical drip starts on a form or a tag and runs on its own clock. It can't start on a purchase or an upgrade unless the platform supports that event, and it keeps sending the 'ready to buy?' email to someone who bought on day two. - The start is a form or a tag.: A purchase, an upgrade or something in your app can't start the series unless the platform supports that event. - The series doesn't know what happened.: Someone buys on day two and still gets the 'ready to buy?' email on day five. - The bill grows with the list.: Kit, Mailchimp and MailerLite price by subscribers, so a drip to a large list costs more every month. How it works How a drip campaign runs in Mimeo. - Write the sequence: Each step is an email and the delay before it, such as day 0, day 2 and day 5. Emails are Markdown with Liquid, wrapped in your template. - Start it on an event: A flow starts the sequence on any event your site, store or app sends: a signup, a purchase, a trial starting. - Let it react: A guard checks every email at send time and can skip one, hold it, or end the series when someone buys or unsubscribes. Own your sending Manage your own sending. Really. Mimeo is your email marketing software where you manage your list, automations, and emails. It plugs into your own sending account. You pick one provider: Postmark or Resend. **The obvious question:** what about deliverability and list health? Deliverability is your sending provider's whole job. That's what they're for. Mimeo keeps your side of the street clean, automatically. - Every send is checked before it goes out: verified sender, unsubscribe links, suppression list. - Bounces, complaints, and unsubscribes are cleaned up the moment they happen. - Big sends are paced: spread over hours at a rate you set, never blasted. Your direct line to your customers' inboxes.\ Now in your control. - Postmark: /images/postmark.png: /images/postmark-darkmode.png: **Managed deliverability · start here.** Managed deliverability from one of email's most trusted names. Less to think about, priced well below any email platform. Start here. - Resend: /images/resend-black.png: /images/resend-darkmode.png: **Lowest cost · simplest setup.** The developer-favorite email API. Verify your domain, paste one API key, and you're sending. - Or have us set it up.: Setup & Launch, a flat-fee project: we deploy Mimeo on your server, connect your sender, authenticate your domain, and import your list. You own everything. [Contact us](mailto:info@mimeohq.com) Pricing Questions Drip questions, answered. How a timed series works in Mimeo. - What's the difference between a sequence and a flow?: A sequence is the series of emails on set delays. A flow decides who starts it and what happens around it: it waits, branches and starts sequences. See [flows vs sequences vs broadcasts](https://mimeohq.com/glossary/flows-vs-sequences-vs-broadcasts). - Can a drip stop when someone buys?: Yes. A guard scoped to the sequence can cancel the rest of the series when a purchase happened, checked as each email is about to send. See [guards](https://mimeohq.com/docs/usage/guards). - Can I edit a drip people are already in?: Yes, and nobody's schedule moves under them. Changing a delay, swapping an email or reordering steps applies to future runs, while people already in the series keep the dates they were given. A new step you activate reaches everyone who hasn't passed its position yet. See [sequences](https://mimeohq.com/docs/usage/sequences). - Can the same person go through a drip twice?: If you choose. Each sequence runs once per person, repeats in full, or repeats sending only the emails someone hasn't had. See [sequences](https://mimeohq.com/docs/usage/sequences). - Can my agent write the series?: Yes. Your agent writes the sequence and its flow as files in your manager repo, or through the MCP server and API, and rehearses the flow on a real person before it goes live. Drip campaigns on any event, on your own server. A drip should know what happened. In Mimeo, any event can start a series, and a guard can hold, skip or end it when someone buys or unsubscribes. Write it in an easy web UI or let your agent write it as files, and it runs on your own server. **Your list grows; your Mimeo bill doesn't.** --- This is the Markdown copy of https://mimeohq.com/for/drip-campaigns.