Can I vibecode Saleshandy?

Build a robust, self-hosted cold email outreach and automation planner inspired by Saleshandy, designed to manage personalized multi-step sequences safely without scraping or evading provider limits.
Use Next.js 15 (App Router), TypeScript, PostgreSQL, Drizzle ORM, and Resend (or a standard SMTP provider).

### Data Model & Schema
Design a normalized PostgreSQL schema with Drizzle:
- `users`: id, email, name, role.
- `email_accounts`: id, userId, email, provider, smtpHost, smtpPort, username, password (encrypted), dailySendLimit, status.
- `leads`: id, userId, email, firstName, lastName, company, customFields (JSONB), status (active, replied, bounced, unsubscribed).
- `campaigns`: id, userId, name, status, created_at.
- `sequence_steps`: id, campaignId, stepNumber, delayDays, subjectTemplate, bodyTemplate (with merge tags like {{firstName}}).
- `emails_sent`: id, campaignId, stepId, leadId, emailAccountId, sentAt, messageId.
- `events`: id, emailId, type (open, click, reply, bounce), timestamp.

### Screens and UX Patterns
1. **Unified Inbox**: A consolidated view of all replies from multiple connected email accounts, allowing the user to manage conversations without switching tabs.
2. **Campaign Builder**: A multi-step sequence editor. Users can add "Step 1" (Day 1), then "Step 2" (Wait 3 days), with rich text editors supporting dynamic merge tags.
3. **Lead Management (CRM lite)**: A table view to import CSVs of permissioned leads, map columns to standard fields, and view interaction history per lead.
4. **Analytics Dashboard**: Real-time graphs showing open rates, click-through rates, bounce rates, and reply rates per campaign.
5. **Account Settings & Limits**: An interface to manage connected SMTP accounts and configure daily sending limits to protect domain reputation.

### Step-by-Step User Journeys
1. **Setup & Import**: User connects an SMTP account, sets a limit of 50 emails/day, and uploads a CSV of 200 leads (confirming they were collected lawfully).
2. **Sequence Creation**: User creates a 3-step campaign: Initial outreach, a follow-up after 3 days, and a final break-up email after 7 days.
3. **Execution**: A background cron job (or BullMQ) runs every hour during business hours, processing pending steps, dynamically replacing {{firstName}}, and sending via the SMTP account while respecting the daily limit.
4. **Engagement Tracking**: A prospect replies. The system ingests the reply via IMAP or webhook, marks the lead as 'replied', instantly halts further sequence steps for that lead, and surfaces the email in the Unified Inbox.

### Technical Specifics
- Use a background job queue (e.g., BullMQ with Redis) for scheduling delays, business-hour windows, and per-domain rate limits.
- Stop sequences immediately on reply, bounce, complaint, or manual pause.
- Put all secrets and SMTP credentials in `.env` (encrypted in DB) and provide `.env.example`.
- Do not claim to reproduce proprietary data like the AI Lead Finder, network liquidity, or automated inbox warm-up networks.
- Include clear empty, loading, success, and recoverable error states.
- Provide a README with setup, architecture, instructions on setting up webhooks for tracking, and backup steps.
- Write focused tests for the core template transformation and the scheduling state machine.