# Screen Map

## Brief Input Summary

- Target user: Solo founders validating a focused MVP.
- MVP promise: A lightweight CRM that helps solo founders validating a focused MVP complete the primary MVP workflow with less friction without the weight of a complex tool.

## User Journey

1. Visitor lands on the product promise and chooses the primary CTA.
2. User completes a short setup path that avoids enterprise configuration.
3. User reaches the dashboard and performs the first repeated workflow action.

## MVP Screens

### LANDING - Landing

- Purpose: Explain the lightweight CRM promise quickly and route the user into the first meaningful action.
- Primary action: Add first lead
- Data needed: Value proposition, primary CTA, proof points, and a short preview of the first workflow.
- Empty state: Show concise promise copy and a single CTA when no workspace exists yet.
- Success state: User understands the product promise and starts onboarding.
- Error state: If onboarding cannot start, show a clear retry path and keep the CTA visible.

### ONBOARDING - Onboarding

- Purpose: Capture only the minimum setup needed before the user can create the first lead.
- Primary action: Add first lead
- Data needed: User name or workspace label, first workflow preference, and optional sample data choice.
- Empty state: Offer one guided setup path and one option to skip non-essential fields.
- Success state: Workspace is ready and the user can create the first lead.
- Error state: Inline validation identifies the missing required field and preserves entered values.

### DASHBOARD - Dashboard

- Purpose: Show active leads, follow-ups, and simple pipeline status with enough context to decide the next action.
- Primary action: Add first lead
- Data needed: Summary counters, prioritized list, next action date, recent notes, and simple status or stage.
- Empty state: Explain that no leads exist yet and keep the first-create CTA prominent.
- Success state: User can scan current work, add or update a record, and leave with a visible next action.
- Error state: If records fail to load, show a recoverable error with retry and no destructive action.

## Out Of Scope For MVP Screen Map

- Production application code, database schema, and integration implementation.
- Complex enterprise configuration, advanced analytics, and multi-team administration.
- Figma, Lovable, v0, or full app-builder replacement behavior.