Build your own Pipedrive.

# Build an original app inspired by Pipedrive

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original pipeline CRM called Dealtrail, inspired by Pipedrive. It serves a small sales team that wants every deal to have a clear next action. The core journey is creating a deal, associating a contact, scheduling an activity, moving the deal between stages, and marking it won or lost. Make the board and follow-up workflow the center of the product.

## Design
Use an original clean pipeline board with stage totals, deal age, due activities, and a compact deal detail drawer. Provide list and board views, keyboard alternatives to dragging, visible saved/error states, and separate lost/won lists. Avoid dense dashboard widgets without real data.

## Features
1. Pipeline setup: configure a single pipeline with ordered stages, create deals with amount/currency and owner, and move deals using drag or accessible actions. Persist ordering and stage changes rather than only rearranging cards locally.

2. People and organizations: maintain linked contacts and company records, associate them with deals, and search names/email. Keep contact permissions consistent with the deal that exposes them.

3. Next activities: schedule calls, meetings, or tasks with due date/time, mark them complete, and highlight deals missing a future activity. Rescheduling and completion should update the real timeline.

4. Deal history: record notes, stage transitions, owner changes, and won/lost outcomes with timestamps. Allow reopening a closed deal without destroying its previous outcome history.

5. Filtering and reports: filter by owner, stage, value, and overdue activity; derive stage totals and outcomes from records; export authorized deals as CSV. Support a small admin/member permission model.

## Tech stack
Use PHP/Laravel with PostgreSQL and a TypeScript board frontend, or preserve an existing suitable stack. Keep pipeline mutations, contact access, and totals on the backend. Use revision checks for conflicting edits and transactions for stage order. Store all amounts as minor units and choose one reporting currency.

## Data & behavior
Workspace; Member {role}; Pipeline; Stage {position}; Organization; Person; Deal {ownerId, personId, organizationId, stageId, valueMinor, currency, state, revision}; Activity; Note; DealEvent. Define closed-state transitions and calculate future/overdue activity using the user timezone.

Acceptance checks and scope:
Test board/list consistency after reload, overdue activities near midnight, concurrent stage moves, a reopened won deal, deleted contacts, authorized CSV exports, and stage totals after changes. Exclude automatic mailbox sync, forecasting AI, telephony integrations, and invoicing.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.