# Build brief — a focused alternative to Mara

> **Verdict:** Partly, if you narrow it · **Buildability:** 58/100 · **Category:** Newsletter
> **Source:** https://www.canitbevibecoded.com/mara
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Mara. Verify current pricing and capabilities before acting.

## Context

**Mara** — An AI lifecycle marketer that proposes, writes, sends, and keeps rewriting a SaaS product's welcome, activation, and churn-save emails. It currently costs $99/mo.

The first send is a contained effort. An agent can absolutely wire product events to an LLM draft to an email API with an approval queue, and that covers the visible part of the product. What does not come out of one prompt is the part after the first send: your own domain's reputation, suppression and compliance, variants split across real sends with the results read back, replies classified and answered, and someone still tuning it in month four. Build the sender, then be honest about whether you will keep running it.

This brief describes a focused, single-operator replacement for the part of Mara that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Take product events, draft the next lifecycle email with an LLM in your voice, hold it for approval, and send it on a schedule.

- Compose, segment, preview, and queue a small newsletter workflow.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Your own sending subdomain with SPF/DKIM/DMARC.
- An always-on host for the scheduler.

### Data and integrations

- Anthropic or OpenAI API key.
- Email sending API (Resend, Postmark, or SES).
- Product events from your app (webhook or DB).

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a self-hosted lifecycle email agent to replace Mara, for one SaaS product. Requirements:

- Node + Express + better-sqlite3 on my VPS, one SQLite file holding contacts,
  events, sequences, drafts, sends, and suppressions. node-cron ticks once a minute,
  no queue service.
- POST /events takes {type, email, properties} with a bearer token from .env. Every
  event upserts a contact and appends a row I can read back later.
- Sequences are JSON files in ./sequences/: an entry event type, then steps with a
  wait ("2d"), an intent in plain words ("nudge them to connect their first
  integration"), and an optional skip-if event type. Ship two: welcome and
  trial-ending.
- Each tick, find contacts due for a step, drop anyone whose skip-if event already
  fired, then draft with the Anthropic API (key in .env): pass ./voice.md plus that
  contact's last 20 events, get back a subject and a plain-text body.
- Drafts land as pending. A localhost-only admin page lists them with subject, body,
  recipient, and the step that produced it, with Approve and Reject buttons. Nothing
  sends without a click.
- Approved mail goes out through Resend or SMTP from .env, one send row per recipient
  with the provider message id. Bounce and complaint webhooks write to a suppression
  table checked before every send. One-click unsubscribe link in every footer, no
  login.
- Cap at 2 emails per contact per 7 days across all sequences, enforced in code
  before drafting.
- Out of scope: A/B variants, reply parsing, open tracking. Do not build multi-user
  accounts or a visual sequence builder, this runs for one product and one operator.
- README with the deliverability homework: SPF, DKIM, and DMARC on a subdomain like
  mail.example.com, a two-week warmup at low volume, and a blunt line that mail from
  a cold domain lands in spam no matter how good the copy is.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Deliverability: warmup, domain reputation, bounce and complaint handling.
- The improvement loop: variants written, split across live sends, losers rewritten.
- Reply handling: inbound classified, answers drafted, suppressions applied.
- Outcome tracking wired back to the copy that caused it.
- Reliability at the vendor's scale is an operations problem, not a prompt.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Mautic](https://github.com/mautic/mautic) — Open-source marketing automation with campaign builder, segments, and drip flows. Heavy, but it is the real self-hosted analog
- [Listmonk](https://github.com/knadh/listmonk) — Open-source, single-binary mailing-list and campaign manager. Good sending substrate to build the agent on top of
- [Keila](https://github.com/pentacent/keila) — Self-hosted newsletter tool with an API, lighter to run than Mautic

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/mara