Can I vibecode Zeeg?

Build a privacy-first, automated scheduling and customer management platform substituting Zeeg's core loop.
Use exactly this stack: Next.js 15 (App Router) + TypeScript + SQLite + TailwindCSS + shadcn/ui.
Primary job: Build a smart booking tool focused on privacy, GDPR compliance, "Stack Mode" productivity, and seamless lead capture without relying on US-based cloud defaults.

Core Features & Requirements:
1. Privacy-First "Booking CRM":
- Design the database to act as a lightweight CRM: every appointment automatically creates or updates a contact record with full meeting history.
- Ensure all data storage is strictly local (SQLite) to mimic a high-privacy, GDPR-compliant European-hosted architecture.

2. Intelligent Scheduling & "Stack Mode":
- Implement a "Stack Mode" scheduling algorithm that intentionally minimizes gaps between meetings, proposing back-to-back blocks to reduce unproductive downtime.
- Sync with a primary calendar to show real-time availability in the invitee’s local time zone.
- Provide custom workflow triggers (e.g., automated email templates on booking, cancellation, or rescheduling).

3. AI/Lead Capture Simulation:
- While a full AI voice agent is out of scope, build a lead capture intake form that dynamically routes or qualifies the user based on their inputs before showing availability.
- Allow configuring simple routing rules (e.g., if budget < $X, show 15 min slot; else show 45 min slot).

4. Technical & Architecture Constraints:
- Start from an empty folder and create the complete working project.
- Store user data locally and explicitly document data sovereignty in the app.
- Put every secret and external credential in .env and provide .env.example.
- Implement polished UI with clear empty, loading, validation, success, and failure states.
- Ensure accessible keyboard navigation and sensible contrast.
- Validate all untrusted input carefully, given the privacy focus.

5. Exclusions & Limitations:
- Deliberately exclude paid-product advantages like real AI voice transcription, race-free booking under massive load, and enterprise team round-robin.
- Do not fake network effects, proprietary data, or security claims.
- If calendar API integration is mocked or optional, explain the degraded mode.

6. Testing & Documentation:
- Write focused unit tests for the "Stack Mode" algorithm and routing rules.
- Add one end-to-end smoke test that proves the core loop works.
- Create a comprehensive README detailing the privacy architecture, local storage, backup, and limitations.
- Run tests and build before finishing, fixing any errors.