[verdict][prompt curatoriat][sursă: hiremara.com][traducere: la coadă]
Pot să vibecodez Mara?
// se construiește într-un weekend, dar rămân goluri reale
The first send is a weekend. 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.
încredere: ridicată
ce e: An AI lifecycle marketer that proposes, writes, sends, and keeps rewriting a SaaS product's welcome, activation, and churn-save emails
Indice de constructibilitate · joc editorial
- Preț de la 99 $ · la consum greutate: plus 3
- Timp câteva zile greutate: plus 1
- Categorie newsletter nu cântărește
- Moat scara infrastructurii · calitatea execuției greutate: minus 3
- Încredere ridicată greutate: plus 1
- Ce pierzi 5 elemente greutate: minus 2
- Site hiremara.com (si apre in una nuova scheda) nu cântărește
Se anulează. E cazul în care decide cât de tare te enervează abonamentul.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
Ce construiești
Take product events, draft the next lifecycle email with an LLM in your voice, hold it for approval, and send it on a schedule.
ce îți trebuie
- Anthropic or OpenAI API key
- email sending API (Resend, Postmark, or SES)
- your own sending subdomain with SPF/DKIM/DMARC
- an always-on host for the scheduler
- product events from your app (webhook or DB)
Submitted by the maker. The honest split: the sender is a weekend, the loop that keeps rewriting it is not.
Promptul
Un weekend cu un agent de coding. Golurile care rămân sunt mai jos, la „ce pierzi”.
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. Prompt curatoriat: scris și revizuit manual pentru această aplicație. În engleză intenționat — e limba în care agenții de coding se descurcă cel mai bine.
Ce pierzi
- 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
- the maintenance nobody does, which is the actual reason lifecycle programs rot
De ce se plătește în continuare
Lifecycle email is not a build problem, it is an upkeep problem. The DIY version works the week you build it and then sits at whatever quality your first draft happened to have, because nobody goes back to rewrite the activation email that quietly stopped working. Founders pay for the part that keeps happening after launch week: something reading the outcomes, rewriting the losers, and handling the replies without being asked.
moat: Scara infrastructurii Calitatea execuției ce e un moat
deliverability/iteration loop/operations
Cine l-a construit deja
Să pornești de aici e tot vibecoding: promptul e pentru când o vrei exact în felul tău.
- Mautic (se deschide într-o filă nouă) — Open-source marketing automation with campaign builder, segments, and drip flows. Heavy, but it is the real self-hosted analog. (alive)
- Listmonk (se deschide într-o filă nouă) — Open-source, single-binary mailing-list and campaign manager. Good sending substrate to build the agent on top of. (alive)
- Keila (se deschide într-o filă nouă) — Self-hosted newsletter tool with an API, lighter to run than Mautic. (alive)
Ești de acord?
Balanța voturilor
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.