Why Mara exists
Most products know they should send better lifecycle emails. Welcome series, activation nudges, win-backs, re-engagement, the basic blocking and tackling of keeping in touch with the people who signed up. Most don't.
The reason isn't complicated. Writing lifecycle email is a job. It needs to happen every week, forever, in a voice the company already has, and the person who's qualified to do it is the founder. Founders don't have time. The person they'd hire to do it costs $120,000 a year. So lifecycle email goes on the someday list and stays there.
When the team does write something, it goes stale. The welcome email from 2024 isn't written for the product as it shipped this morning. The win-back from a year ago references a pricing tier that no longer exists. Nobody A/B tests at a meaningful cadence because manual A/B testing is overhead nobody has.
The AI products that exist today don't solve this. Jasper-style copy generators produce template prose with AI tells nobody can ship in their voice. Customer.io and Loops and the rest of the sending tools are pipes; they don't write, they don't iterate, they don't read your product.
So we built Mara.
The framing matters
You don't subscribe to Mara. You hire her. The verb is deliberate. She has a name and pronouns because what she does is a role, not a feature.
The five-tier ladder maps to how much volume you're trusting her with, not how many features you unlock. Every tier ships the same brain. What scales is the cost of running her: more contacts, more sends, more journeys at once.
What she does that nobody else does
Mara reads your repo. GitHub OAuth on day one. She knows what your product is for, what you ship, what's in the README, what you fixed last week, what the issue tracker says is broken. No other lifecycle email tool does this, and without the repo every email is a guess.
She runs the Loop. Write, send, analyze. Every send teaches her what to write next. Opens, clicks, replies, silence. They all feed back into the next variant. The same email never sends twice. The version that landed rewrites the one that didn't.
Both of these compound per-tenant. Two months in, Mara has written hundreds of emails to your audience and learned what works for them specifically. That learning doesn't transfer to other customers. It's yours. The longer she runs, the more she's worth, and the more switching cost there is in canceling.
What she explicitly isn't
This is the part most product pages bury at the bottom. We lead with it.
Mara doesn't write paid ads. She doesn't write SEO content. She doesn't post to social. She doesn't write broadcast newsletters. She doesn't send transactional emails like receipts or password resets. She doesn't run a CRM. She doesn't do sales outreach.
The list is the pitch. Lifecycle email is the role. Everything else is a different role, and the people who do those things well don't also do this well. Mara stays in her lane.
Who Mara is for
Indie B2B SaaS founders. Consumer product founders. Membership and community founders. Anyone running something with a signup form, a payment processor, and an event stream. Anyone who knows that the welcome email matters but hasn't touched it in eighteen months.
The pricing ladder runs from $0 to $799 per month for self-serve. That's deliberately a tenth of what 11x and Artisan charge for their AI workers. Mara is built to fit a budget that has product engineering in it, not enterprise software.
Anyone whose mental model is "$10k/year SaaS" will undervalue Mara and over-demand from her. We're explicit about this.
What we're not
We're not a platform. We're not building a marketing operating system. We're not adding AI to a CRM. We're not expanding into ten adjacent verticals.
We're one agent doing one role. Forever.