Can Mailchimp be vibe coded?

Build brief — a focused alternative to Mailchimp

**Verdict:** Partly, if you narrow it · **Buildability:** 33/100 · **Category:** Newsletter

**Source:** https://www.canitbevibecoded.com/mailchimp

Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Mailchimp. Verify current pricing and capabilities before acting.

Context

**Mailchimp** — Email marketing platform with campaigns, automations, forms, and analytics. It currently costs $20/mo.

A campaign sender is buildable, but Mailchimp's value is deliverability, templates, compliance, automations, segmentation, ecommerce integrations, and support.

This brief describes a focused, single-operator replacement for the part of Mailchimp 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

Build subscriber lists, campaign composer, templates, segmentation, sends via SES/Postmark/Mailgun, unsubscribe and analytics.

Compose, segment, preview, and queue a small newsletter workflow.

A responsive interface with real empty, loading, success, and error states.

Requirements

Functional

Email provider.

Domain authentication.

Database.

Editor.

Compliance/unsubscribe logic.

Bounce handling.

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 small-list email campaign tool to replace Mailchimp. Requirements:

Node + Express + better-sqlite3 on my VPS. Admin UI bound to localhost/VPN; only

the subscribe and unsubscribe endpoints are public.

Contacts with tags and custom fields, CSV import and export, and segments saved

as filters (has tag X, joined after date, opened last campaign).

Campaigns written in Markdown, rendered into one clean single-column HTML email

with mjml, plain-text alternative generated automatically.

Send through Amazon SES (keys in .env) with throttling and per-recipient status;

SES bounce and complaint notifications auto-suppress those addresses.

Compliance baked in: unsubscribe link and postal address in every footer, a

List-Unsubscribe header, double opt-in on the public signup form.

Open tracking is a per-campaign toggle, default off. Campaign report shows sent,

bounced, and unsubscribed counts.

One SQLite file holds everything; no telemetry, no third-party trackers.

Out of scope: the drag-and-drop template editor, automation journeys, and

ecommerce integrations. One good template, sent well.

README warning: inbox placement is earned, not coded. Document SPF, DKIM, and

DMARC setup and tell me to warm up sending volume gradually.

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.

Template/editor polish.

Automation builder.

Ecommerce integrations.

Reliability at the vendor's scale is an operations problem, not a prompt.

Connectors, OAuth flows, and vendor API changes require constant upkeep.

What you still own after launch

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.

Maintain every third-party integration as APIs and OAuth rules change.

Risk

**High consequence.** Use this as a prototype or personal aid. Keep a qualified human and an established provider in the loop for consequential decisions.

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 platform with email campaigns and contact management

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