Salesmate

Build me a focused contacts, relationships and sales pipelines workflow for the personal core of Salesmate. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose. Model contacts, companies, activities, stages, and follow-up history; store source IDs and timestamps for each.
- Paid product context: Track contacts and deals and send low-volume permissioned email through a user provider. Build only this DIY scope: Manage contacts, companies, and deals, move opportunities through a pipeline, log interactions, send low-volume permissioned email through a user provider, and surface the next action.
- Create contacts, companies, opportunities, notes, tasks, and configurable pipeline stages.
- Add fast global search, duplicate detection, merge, CSV import, and CSV export.
- Implement saved views, filters, owner assignment, and a next-action dashboard. Add role-based access, an immutable activity log, backups, and a recovery command.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; self-hosted server.
- Recovery: Add role-based access, an immutable activity log, backups, and a recovery command.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: built-in calling, texting, sequences, automations, and sales integrations; automatic email and calendar capture. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Salesmate

## Project scope
Manage contacts, companies, and deals, move opportunities through a pipeline, log interactions, send low-volume permissioned email through a user provider, and surface the next action.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Salesmate, track contacts and deals and send low-volume permissioned email through a user provider. The hard boundary is built-in calling, texting, sequences, automations, and sales integrations, plus integrations, data quality, and workflow lock-in.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Docker
- PostgreSQL
- self-hosted server
- optional email API credentials

## Stack and architecture
- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose.
- Model contacts, companies, activities, stages, and follow-up history; store source IDs and timestamps for each.
- Interface for this contacts, relationships and sales pipelines workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Add role-based access, an immutable activity log, backups, and a recovery command.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: built-in calling, texting, sequences, automations, and sales integrations.

## Agent implementation rules
- Project rule, data: Model contacts, companies, activities, stages, and follow-up history; store source IDs and timestamps for each.
- Project rule, behavior: Create contacts, companies, opportunities, notes, tasks, and configurable pipeline stages.
- Project rule, recovery: Add role-based access, an immutable activity log, backups, and a recovery command.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this contacts, relationships and sales pipelines operation with sample or user-owned data: Create contacts, companies, opportunities, notes, tasks, and configurable pipeline stages.
- Show a concrete result or export: Add fast global search, duplicate detection, merge, CSV import, and CSV export.
- State the practical limit: built-in calling, texting, sequences, automations, and sales integrations.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose. Model contacts, companies, activities, stages, and follow-up history; store source IDs and timestamps for each.
2. Phase 2, implement: Create contacts, companies, opportunities, notes, tasks, and configurable pipeline stages.
3. Phase 3, implement: Add fast global search, duplicate detection, merge, CSV import, and CSV export.
4. Phase 4, review and output: Implement saved views, filters, owner assignment, and a next-action dashboard. Add fast global search, duplicate detection, merge, CSV import, and CSV export.
5. Phase 5, recovery and acceptance: Add role-based access, an immutable activity log, backups, and a recovery command. Verify this invariant with a saved fixture: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs. State the practical limit: built-in calling, texting, sequences, automations, and sales integrations.

## Paid-product capabilities outside this build
- built-in calling, texting, sequences, automations, and sales integrations
- automatic email and calendar capture
- data enrichment
- large integration ecosystem
- enterprise reporting

## Implementation prompt
Build me a focused contacts, relationships and sales pipelines workflow for the personal core of Salesmate. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose. Model contacts, companies, activities, stages, and follow-up history; store source IDs and timestamps for each.
- Paid product context: Track contacts and deals and send low-volume permissioned email through a user provider. Build only this DIY scope: Manage contacts, companies, and deals, move opportunities through a pipeline, log interactions, send low-volume permissioned email through a user provider, and surface the next action.
- Create contacts, companies, opportunities, notes, tasks, and configurable pipeline stages.
- Add fast global search, duplicate detection, merge, CSV import, and CSV export.
- Implement saved views, filters, owner assignment, and a next-action dashboard. Add role-based access, an immutable activity log, backups, and a recovery command.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; self-hosted server.
- Recovery: Add role-based access, an immutable activity log, backups, and a recovery command.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: built-in calling, texting, sequences, automations, and sales integrations; automatic email and calendar capture. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.