Build your own Salesforce.

# Build an original app inspired by Salesforce

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 CRM called Accountcraft, inspired by Salesforce sales workflows. It is for one small business maintaining customer relationships and tracking opportunities. The primary journey is capturing a lead, converting it to an account/contact/opportunity, recording follow-up activity, and moving the opportunity to won or lost. Focus on one defined sales process.

## Design
Create an original business workspace with searchable records, linked account/contact detail pages, an opportunity board, and a report view. Keep ownership, next activity, amount/currency, and stage visible. Use a practical accessible layout instead of recreating a broad enterprise console.

## Features
1. Accounts and contacts: create organization and person records, relate contacts to accounts, assign owners, and search with filters. Normalize email lookup and warn about possible duplicates without merging unrelated customers automatically.

2. Lead conversion: capture lead source/status, qualify or disqualify, and convert a lead atomically to linked records. Conversion must be idempotent and preserve history and existing matching accounts when chosen by the user.

3. Opportunities: manage pipeline stages, expected close date, integer minor-unit amount/currency, probability, and outcome reason. Stage changes must update a genuine history log and not silently overwrite concurrent edits.

4. Activities: schedule tasks and calls, log notes, complete follow-ups, and show overdue activity by owner. Render customer notes safely and enforce record access in related activity queries.

5. Reports and roles: derive pipeline totals, won/lost outcomes, and activity completion from stored records. Support admin and salesperson roles, permission-aware CSV import/export, and an audit log.

## Tech stack
Use a TypeScript client with a Python/Django API and PostgreSQL for a new project. Enforce organization/owner permissions in all queries and mutations, use transactions for lead conversion, and version records for concurrency checks. Implement a bounded CSV importer with field mapping, validation preview, and row-level errors.

## Data & behavior
Organization; UserRole; Account; Contact; Lead {status, convertedAt, convertedAccountId}; Opportunity {accountId, ownerId, stageId, amountMinor, currency, closeDate, revision}; Stage; Activity; Note; StageHistory; ImportJob; AuditEvent. Keep one currency in reports or use explicitly configured conversion rates.

Acceptance checks and scope:
Test repeated lead conversion, duplicate candidates, restricted records in exports/reports, overdue activity across timezones, concurrent opportunity edits, invalid CSV rows, and reports after stage changes. Exclude enterprise automation builders, customer support suites, live email sync, and Salesforce data imports.

## 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.