Can I vibecode Audienceful?

Build a deliberately narrow personal substitute for Audienceful, not a full clone.
Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL (using Drizzle ORM).
Primary job: Build a small newsletter + CRM editor featuring a Notion-style block editor and subscriber database that exports clean HTML and sends only through a reputable user-supplied email provider via standard SMTP.
Start from an empty folder and create the complete working project. Make the default mode single-user and private.

Data Model:
- `Subscribers`: id, email (unique), status (active, unsubscribed), created_at
- `Tags`: id, name
- `SubscriberTags`: subscriber_id, tag_id
- `CustomFields`: id, subscriber_id, key (e.g., plan_type, signup_date), value
- `Campaigns`: id, title, content_blocks (JSON), status (draft, sent), scheduled_for, sent_at

User Journey & Screens:
1. Dashboard: Shows recent campaigns and total active subscribers.
2. Editor Screen: A Notion-style, document-based WYSIWYG editor using TipTap or similar block editor. Support adding text, headings, and images. Real-time preview of the email.
3. Audience Management Screen: View subscribers, filter by tags, and edit custom fields (CRM style). 
4. Sending Flow: Select a segment (based on tags/custom fields), preview conditional blocks, and send.

Technical specifics: 
- Store user data locally unless the core job requires the declared self-hosted database.
- Put every secret and external credential (SMTP URL, DB connection) in .env and provide .env.example.
- Ensure the block editor outputs clean, email-safe HTML (inline CSS, table layouts where necessary for older clients).
- Do not add analytics, telemetry, ads, or third-party accounts.
- Include clear empty, loading, validation, success, and failure states.
- Deliberately exclude these paid-product advantages: bounce, complaint, and suppression handling; large-scale branching automation, payments, recommendations, and real-time multiplayer collaboration.
- Write focused unit tests for the data model and the most important workflow (block to HTML conversion).
- Create a README with setup, permissions, architecture, data location, backup, and limitations.
- Run the tests and build before finishing, then fix errors rather than merely describing them.