Can I vibecode Bento?

Build a deliberately narrow personal substitute for Bento, not a full clone.
Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL (using Prisma).
Primary job: Build an event-driven email marketing and customer data platform (mini-CRM) that exports clean HTML and sends only through a reputable user-supplied email provider via SMTP.
Start from an empty folder and create the complete working project. Make the default mode single-user and private.

Data Model:
- `People`: id, email, created_at, lifetime_value, plan_type
- `Events`: id, person_id, event_name (e.g., product_viewed, checkout_started), properties (JSON), occurred_at
- `Fields`: id, person_id, key, value, type (Text, Number, Date, Boolean)
- `Flows` (Automations): id, trigger_event, steps (JSON array of actions like send_email, wait)
- `Emails`: id, subject, liquid_template_body

User Journey & Screens:
1. People Screen: A rich CRM view of subscribers, displaying their custom fields, tags, and a chronological activity feed of their Events.
2. Visual Flow Builder Screen: A simple node-based or linear step builder to create automations (e.g., IF event='checkout_started' THEN wait 1 day THEN send 'abandoned_cart' email).
3. Email Template Editor: Support Liquid syntax for personalization (e.g., {{ person.plan_type }}).

Technical specifics:
- Expose a simple REST API (`POST /api/events`) for tracking user events from external apps.
- Put every secret and external credential in .env and provide .env.example.
- Include a robust background worker (e.g., BullMQ) to process event triggers and schedule flow steps.
- Deliberately exclude these paid-product advantages: sender reputation and deliverability operations; built-in spam/list-bombing protection; visual drag-and-drop workflow canvas (use a simpler list-based flow builder).
- Use accessible keyboard navigation, labels, focus states, and sensible contrast.
- Write focused unit tests for the event processing logic and Liquid rendering.
- Create a README with setup, architecture, and API documentation for the events endpoint.
- Run the tests and build before finishing, then fix errors rather than merely describing them.