# Frozen comparison prompt
Design and build a polished, working responsive web prototype for **Ledgerline**, a cash-flow and invoicing workspace for a small independent creative studio.
This is a medium-complexity product surface, not a marketing page. The primary surface is **Operate**: the studio owner needs to see what requires attention and take action quickly.
## Audience and tone
The user is a design-studio owner who manages 8–15 active clients without a finance team. The product should feel quietly premium, calm, precise, and editorial rather than like a generic SaaS dashboard. Use a restrained visual system with one intentional accent. Avoid glossy gradients, glassmorphism, oversized decorative statistics, and a grid of interchangeable feature cards.
## Required connected views
Create three navigable views:
1. **Overview**
- Show current cash position and a useful 30-day cash-flow forecast.
- Show `Outstanding: $18,460`, `Overdue: $4,200`, and `Expected this month: $31,800` with clear hierarchy rather than three identical cards.
- Include a compact list of items that need attention and recent payments.
- The forecast must be understandable without relying on hover alone.
2. **Invoices**
- Include search and status filters for All, Draft, Sent, Overdue, and Paid.
- Show a realistic list with invoice number, client, amount, issue/due date, and status.
- Include at least these records:
- `INV-2048`, Northstar Studio, `$6,800`, due `Aug 2`, Sent
- `INV-2047`, Onda Coffee, `$4,200`, due `Jul 21`, Overdue
- `INV-2046`, Morrow Books, `$3,600`, due `Aug 10`, Draft
- `INV-2045`, Field Office, `$2,860`, due `Jul 30`, Sent
- `INV-2044`, Common Thread, `$1,000`, paid `Jul 24`, Paid
- Selecting an invoice must reveal a useful detail view or drawer with line items, dates, client details, and next actions.
3. **Clients**
- Show a compact client directory with outstanding totals and recent activity.
- Selecting a client should reveal their contact information, invoice history, and payment pattern.
## Required interactions
- Navigation between all three views must work.
- Search and status filtering must work and include a helpful zero-results state.
- The overdue Onda Coffee invoice can be marked paid; the invoice status, relevant totals, and recent activity must update immediately.
- A **New invoice** flow must open a modal or focused form with client, amount, issue date, due date, and notes.
- The form must demonstrate inline validation and a success state. A valid invoice should be added to the invoice list in the current session.
- Important controls need visible hover, focus, active, disabled, loading, and success feedback where applicable.
## Responsive and accessibility requirements
- Make the complete workflow useful at both a 1440px desktop viewport and a 390px mobile viewport.
- On mobile, preserve the essential actions and information instead of merely shrinking the desktop layout.
- Prevent horizontal overflow.
- Use semantic controls, clear keyboard focus, readable contrast, and touch targets of at least 44px.
- Respect reduced-motion preferences.
## Constraints
- Use realistic static data only; do not invent a backend, authentication, bank connection, or collaboration system.
- Do not use remote images or depend on network requests. Initials or simple local shapes are sufficient for client identity.
- Build the actual interactive prototype, not a prose design recommendation or a static screenshot.
- Keep scope to this brief. Do not add unrelated product areas.