Can I vibecode Zoho CRM?

Build a highly capable, privately hosted personal substitute for the core sales and contact management features of Zoho CRM in an empty repository.
Use exactly this stack: Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.

Primary Objective: Create a focused, high-performance Customer Relationship Management (CRM) platform to manage contacts, companies, and deals through customizable pipelines. It must provide deep visibility into sales workflows and next actions without the bloat of an enterprise suite.

Detailed Feature Requirements:
1. Comprehensive Record Management: Implement robust modules for Contacts, Companies (Accounts), and Opportunities (Deals). Support custom fields, rich text notes, and file attachments for each record. 
2. Dynamic Sales Force Automation & Pipelines: Build a highly configurable Kanban-style pipeline for Deals. Allow users to define custom stages, drag-and-drop deals between stages, and automatically calculate pipeline value and win probabilities.
3. Unified Interaction Timeline: Create a chronological activity feed for every contact and company. Users should be able to manually log calls, emails, meetings, and internal notes. Include a "Next Action" dashboard that highlights overdue tasks and upcoming follow-ups.
4. Advanced Filtering & Saved Views: Implement powerful global search across all modules. Allow users to create complex filters (e.g., "Deals > $10k closing this month in Stage: Negotiation") and save them as quick-access views.
5. Data Integrity & Portability: Build a robust duplicate detection system (e.g., matching by email or domain) with a merge UI. Ensure seamless CSV data import with field mapping, and one-click CSV export so data is never locked in.
6. Reporting & Analytics Dashboard: Provide a clean, visual dashboard showing key metrics: sales velocity, conversion rates by stage, revenue forecasted vs. closed, and activity leaderboards. 

Strict Constraints:
- Make the first run work locally with one documented `docker-compose up` command.
- Store all user data locally. Put secrets in `.env`, ship `.env.example`, and never commit credentials.
- Implement role-based access control (Admin, Manager, Rep) and an immutable activity log for accountability.
- Include a realistic demo workspace seeder script to populate sample contacts, deals, and activities.
- Deliberately leave out: automatic mailbox/email ingestion, commercial enrichment databases, enterprise forecasting, and massive external integrations. Keep it focused on manual, high-quality data entry and local management.
- Include clear empty, loading, success, and error states. Validate all input meticulously.
- Write focused tests for the core transformation (e.g., pipeline stage changes) and one end-to-end happy path.
- Create a README with architecture, setup, backup steps, and recovery commands.
- Run tests and list the exact commands used upon completion.