Can I vibecode HubSpot CRM?

You are building a production-ready software product named “TinyCRM”, a deliberately focused alternative to HubSpot CRM. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components.

WORKING AGREEMENT
Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests.

PRODUCT BRIEF
Primary user: a small B2B sales team with one straightforward deal pipeline.
Primary outcome: keep contacts, company context, deal stage, and next action in one dependable place.
Product principle: optimize the exact workflow below instead of copying the full breadth of HubSpot CRM. A first-time user should understand what to do from the interface itself, without a tour or documentation.

END-TO-END USER JOURNEYS
Implement all of these flows through the real interface and persistent data layer:
1. An admin imports contacts and companies from CSV, reviews normalized duplicate matches and row errors, confirms the valid records, and merges an intentional duplicate.
2. A salesperson creates a deal from a company record, assigns an owner and stage, logs a call, adds a follow-up task, and moves the deal through the pipeline.
3. A manager reviews overdue tasks and pipeline metrics, opens the underlying deal history, filters by owner and stage, and exports an authorized CSV snapshot.

SCREENS AND INFORMATION ARCHITECTURE
Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state.
1. CRM dashboard: pipeline value, stage conversion, win rate, overdue tasks, recent activity, owner filter, import status, and quick-create actions.
2. Contacts and companies: searchable directory, duplicate indicators, ownership, open deals, last activity, CSV import mapping, merge preview, and archive controls.
3. Deal pipeline: configurable ordered stages, deal cards with value, owner, company, task due date, drag feedback, filters, and stage totals.
4. Deal detail: contact and company context, stage and value, owner, activity composer, immutable timeline, open and completed tasks, email-capture status, and archive action.

CORE CAPABILITIES
1. contacts and companies with duplicate detection
2. deal pipeline with configurable stages and drag-to-move
3. activity timeline for notes, email summaries, calls, and stage changes
4. tasks with owner, due date, and overdue view
5. pipeline value, stage conversion, win rate, and CSV export

DETAILED BEHAVIOR AND BUSINESS RULES
Treat these as server-enforced product requirements, not interface suggestions:
1. Normalize email addresses and company domains for duplicate suggestions, but require an explicit reviewed merge that preserves activities, tasks, and deal relationships.
2. Apply stage moves through one transactional service that records old stage, new stage, actor, and time and updates pipeline metrics only after commit.
3. Keep activity history append-only apart from explicit corrections that retain the original value, editor, reason, and correction timestamp.
4. Enforce record ownership and role permissions on every query and mutation; permit full CRM exports only to admins and record each export in the audit log.

DATA MODEL AND LIFECYCLE
Design a small relational schema centered on Contact, Company, Deal, Activity, Task, PipelineStage. Before implementing it, document:
1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes.
2. Foreign keys, uniqueness constraints, che...