Can I vibecode Campaign Monitor?

Build a personal replacement for Campaign Monitor in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Amazon SES; do not offer alternative stacks.
The core loop is: manage subscribers, compose design-centric campaigns, and report on delivery/clicks.
Make the first run work locally with one documented command. Store all user data locally by default.

Data Model:
- `Subscribers`: id, email, status, opt_in_date
- `Segments`: id, name, rule_logic (JSON, e.g., location='US' AND opens>5)
- `Campaigns`: id, subject, html_content, plain_content, segment_id, status
- `Metrics`: id, campaign_id, subscriber_id, event_type (open, click, bounce, complaint), created_at
- `Templates`: id, name, html_structure

User Journey & Screens:
1. List Management: Import subscribers via CSV, view active segments, and manage custom demographic fields.
2. Campaign Builder: A block-based visual editor focusing on aesthetic layouts (hero images, multi-column text, styled buttons). Provide an option for dynamic content blocks based on segment logic.
3. Analytics Dashboard: Visual charts comparing campaign performance (open rates, click maps) against historical averages.

Technical specifics:
- Queue sends through SES with retries, rate limits, idempotency, and resumable batches.
- Process delivery, bounce, complaint, open, and click webhooks (via SNS/SES) without logging message content.
- Implement double opt-in, unsubscribe handling, and suppression lists.
- Deliberately leave out complex multi-branch lifecycle automation, advanced enterprise deliverability support, and agency white-labeling features.
- Write focused tests for the core segmentation logic and one end-to-end happy path for campaign sending.
- Create a README with setup, architecture, SES configuration, and backup steps.
- Run the tests and build before finishing, then fix errors rather than merely describing them.