Vibecode Salesforce
track this build5 steps, step by step0%NOT REALLY · don't bother
You can absolutely one-shot a contacts-and-deals tracker, and for one person that is often better than Salesforce. But nobody pays Salesforce for a pipeline table. They pay for the thing everything else in the company already points at: the ETL jobs, the marketing automation, the support queue, the finance reports, the twelve years of closed-won history, the admin who wrote 400 validation rules, and the auditors who accept it. A personal replacement replaces the part of Salesforce that was never the expensive part. If you are a solo operator or a two-person shop, build it; if you are trying to leave an existing org, this is a migration project, not a coding session.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Salesforce. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Salesforce indie build ## Goal Build the smallest trustworthy replacement for the core Salesforce workflow for one developer or a tiny team. ## Scope A local web app with contacts, companies, deals on a drag-across pipeline, activity notes, and next-action reminders, backed by SQLite. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Every integration: marketing automation, support cases, quoting, billing, BI tooling, and the hundred connectors vendors ship for Salesforce and nothing else - Multi-user permissions, sharing rules, field-level security, and audit trails that survive a compliance review - Reporting, forecasting and dashboards that leadership already knows how to read - The admin ecosystem: consultants, AppExchange, and a hiring pool that already knows the object model - Historical data with lineage, which is the actual asset in any CRM older than a year If those capabilities are essential, use Salesforce instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a single-user personal CRM that runs locally. No accounts, no cloud, no telemetry. Stack, non-negotiable: - Next.js (App Router) with TypeScript - SQLite via better-sqlite3, file at ./data/crm.db - Drizzle ORM for schema and migrations - Tailwind CSS, no component library - Runs with `npm run dev` on port 3000 and nothing else needs to be installed Data model: - companies: id, name, domain, notes, createdAt - contacts: id, companyId (nullable), name, email, phone, role, notes, createdAt - deals: id, title, companyId, contactId (nullable), amountCents, currency (default USD), stage, expectedCloseDate, createdAt, closedAt, outcome (won|lost|null) - activities: id, kind (call|email|meeting|note), subject, body, occurredAt, contactId, dealId, createdAt - tasks: id, title, dueDate, done, contactId, dealId - Stages are a fixed list in code: lead, qualified, proposal, negotiation, closed. Screens: 1. /pipeline: kanban board, one column per stage, deal cards showing title, company, amount. Drag between columns persists the stage. Column headers show count and summed amount. 2. /contacts and /companies: searchable tables, click through to a detail page showing linked deals, activity timeline newest first, and open tasks. 3. /deals/[id]: edit fields inline, log an activity, mark won or lost. 4. /today: tasks due today or overdue, plus deals with no activity in 14 days, labelled "going cold". Also build: - One global search box (cmd+K) over contacts, companies and deals, using SQLite LIKE queries. No vector search, no AI. - A GET /api/export route that dumps everything as JSON, and a CSV import for contacts that maps columns in the UI before committing. - Seed script with about 20 fake contacts, 8 companies and 12 deals so the board is not empty on first run. Explicitly out of scope: email sending or syncing, OAuth, multi-user or permissions, workflow automation, reporting beyond the pipeline totals, mobile app, any third-party API. If you want any secret later, read it from .env and commit .env.example only. Write a README with setup in under five commands and a one-paragraph note on how to back up the SQLite file. ## Required capabilities - Node runtime and a place to run it, local or a small VPS - Optional: an IMAP or Gmail API credential if you want email logging, which is where the weekend goes ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Salesforce. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Salesforce indie build ## Goal Build the smallest trustworthy replacement for the core Salesforce workflow for one developer or a tiny team. ## Scope A local web app with contacts, companies, deals on a drag-across pipeline, activity notes, and next-action reminders, backed by SQLite. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Every integration: marketing automation, support cases, quoting, billing, BI tooling, and the hundred connectors vendors ship for Salesforce and nothing else - Multi-user permissions, sharing rules, field-level security, and audit trails that survive a compliance review - Reporting, forecasting and dashboards that leadership already knows how to read - The admin ecosystem: consultants, AppExchange, and a hiring pool that already knows the object model - Historical data with lineage, which is the actual asset in any CRM older than a year If those capabilities are essential, use Salesforce instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a single-user personal CRM that runs locally. No accounts, no cloud, no telemetry. Stack, non-negotiable: - Next.js (App Router) with TypeScript - SQLite via better-sqlite3, file at ./data/crm.db - Drizzle ORM for schema and migrations - Tailwind CSS, no component library - Runs with `npm run dev` on port 3000 and nothing else needs to be installed Data model: - companies: id, name, domain, notes, createdAt - contacts: id, companyId (nullable), name, email, phone, role, notes, createdAt - deals: id, title, companyId, contactId (nullable), amountCents, currency (default USD), stage, expectedCloseDate, createdAt, closedAt, outcome (won|lost|null) - activities: id, kind (call|email|meeting|note), subject, body, occurredAt, contactId, dealId, createdAt - tasks: id, title, dueDate, done, contactId, dealId - Stages are a fixed list in code: lead, qualified, proposal, negotiation, closed. Screens: 1. /pipeline: kanban board, one column per stage, deal cards showing title, company, amount. Drag between columns persists the stage. Column headers show count and summed amount. 2. /contacts and /companies: searchable tables, click through to a detail page showing linked deals, activity timeline newest first, and open tasks. 3. /deals/[id]: edit fields inline, log an activity, mark won or lost. 4. /today: tasks due today or overdue, plus deals with no activity in 14 days, labelled "going cold". Also build: - One global search box (cmd+K) over contacts, companies and deals, using SQLite LIKE queries. No vector search, no AI. - A GET /api/export route that dumps everything as JSON, and a CSV import for contacts that maps columns in the UI before committing. - Seed script with about 20 fake contacts, 8 companies and 12 deals so the board is not empty on first run. Explicitly out of scope: email sending or syncing, OAuth, multi-user or permissions, workflow automation, reporting beyond the pipeline totals, mobile app, any third-party API. If you want any secret later, read it from .env and commit .env.example only. Write a README with setup in under five commands and a one-paragraph note on how to back up the SQLite file. ## Required capabilities - Node runtime and a place to run it, local or a small VPS - Optional: an IMAP or Gmail API credential if you want email logging, which is where the weekend goes ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Salesforce. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Salesforce product brief ## Problem You can absolutely one-shot a contacts-and-deals tracker, and for one person that is often better than Salesforce. But nobody pays Salesforce for a pipeline table. They pay for the thing everything else in the company already points at: the ETL jobs, the marketing automation, the support queue, the finance reports, the twelve years of closed-won history, the admin who wrote 400 validation rules, and the auditors who accept it. A personal replacement replaces the part of Salesforce that was never the expensive part. If you are a solo operator or a two-person shop, build it; if you are trying to leave an existing org, this is a migration project, not a coding session. ## Product outcome A local web app with contacts, companies, deals on a drag-across pipeline, activity notes, and next-action reminders, backed by SQLite. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node runtime and a place to run it, local or a small VPS - Optional: an IMAP or Gmail API credential if you want email logging, which is where the weekend goes ## Explicit non-goals for v1 - Every integration: marketing automation, support cases, quoting, billing, BI tooling, and the hundred connectors vendors ship for Salesforce and nothing else - Multi-user permissions, sharing rules, field-level security, and audit trails that survive a compliance review - Reporting, forecasting and dashboards that leadership already knows how to read - The admin ecosystem: consultants, AppExchange, and a hiring pool that already knows the object model - Historical data with lineage, which is the actual asset in any CRM older than a year ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a single-user personal CRM that runs locally. No accounts, no cloud, no telemetry. Stack, non-negotiable: - Next.js (App Router) with TypeScript - SQLite via better-sqlite3, file at ./data/crm.db - Drizzle ORM for schema and migrations - Tailwind CSS, no component library - Runs with `npm run dev` on port 3000 and nothing else needs to be installed Data model: - companies: id, name, domain, notes, createdAt - contacts: id, companyId (nullable), name, email, phone, role, notes, createdAt - deals: id, title, companyId, contactId (nullable), amountCents, currency (default USD), stage, expectedCloseDate, createdAt, closedAt, outcome (won|lost|null) - activities: id, kind (call|email|meeting|note), subject, body, occurredAt, contactId, dealId, createdAt - tasks: id, title, dueDate, done, contactId, dealId - Stages are a fixed list in code: lead, qualified, proposal, negotiation, closed. Screens: 1. /pipeline: kanban board, one column per stage, deal cards showing title, company, amount. Drag between columns persists the stage. Column headers show count and summed amount. 2. /contacts and /companies: searchable tables, click through to a detail page showing linked deals, activity timeline newest first, and open tasks. 3. /deals/[id]: edit fields inline, log an activity, mark won or lost. 4. /today: tasks due today or overdue, plus deals with no activity in 14 days, labelled "going cold". Also build: - One global search box (cmd+K) over contacts, companies and deals, using SQLite LIKE queries. No vector search, no AI. - A GET /api/export route that dumps everything as JSON, and a CSV import for contacts that maps columns in the UI before committing. - Seed script with about 20 fake contacts, 8 companies and 12 deals so the board is not empty on first run. Explicitly out of scope: email sending or syncing, OAuth, multi-user or permissions, workflow automation, reporting beyond the pipeline totals, mobile app, any third-party API. If you want any secret later, read it from .env and commit .env.example only. Write a README with setup in under five commands and a one-paragraph note on how to back up the SQLite file. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Salesforce capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Salesforce indie build ## Goal Build the smallest trustworthy replacement for the core Salesforce workflow for one developer or a tiny team. ## Scope A local web app with contacts, companies, deals on a drag-across pipeline, activity notes, and next-action reminders, backed by SQLite. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Every integration: marketing automation, support cases, quoting, billing, BI tooling, and the hundred connectors vendors ship for Salesforce and nothing else - Multi-user permissions, sharing rules, field-level security, and audit trails that survive a compliance review - Reporting, forecasting and dashboards that leadership already knows how to read - The admin ecosystem: consultants, AppExchange, and a hiring pool that already knows the object model - Historical data with lineage, which is the actual asset in any CRM older than a year If those capabilities are essential, use Salesforce instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a single-user personal CRM that runs locally. No accounts, no cloud, no telemetry. Stack, non-negotiable: - Next.js (App Router) with TypeScript - SQLite via better-sqlite3, file at ./data/crm.db - Drizzle ORM for schema and migrations - Tailwind CSS, no component library - Runs with `npm run dev` on port 3000 and nothing else needs to be installed Data model: - companies: id, name, domain, notes, createdAt - contacts: id, companyId (nullable), name, email, phone, role, notes, createdAt - deals: id, title, companyId, contactId (nullable), amountCents, currency (default USD), stage, expectedCloseDate, createdAt, closedAt, outcome (won|lost|null) - activities: id, kind (call|email|meeting|note), subject, body, occurredAt, contactId, dealId, createdAt - tasks: id, title, dueDate, done, contactId, dealId - Stages are a fixed list in code: lead, qualified, proposal, negotiation, closed. Screens: 1. /pipeline: kanban board, one column per stage, deal cards showing title, company, amount. Drag between columns persists the stage. Column headers show count and summed amount. 2. /contacts and /companies: searchable tables, click through to a detail page showing linked deals, activity timeline newest first, and open tasks. 3. /deals/[id]: edit fields inline, log an activity, mark won or lost. 4. /today: tasks due today or overdue, plus deals with no activity in 14 days, labelled "going cold". Also build: - One global search box (cmd+K) over contacts, companies and deals, using SQLite LIKE queries. No vector search, no AI. - A GET /api/export route that dumps everything as JSON, and a CSV import for contacts that maps columns in the UI before committing. - Seed script with about 20 fake contacts, 8 companies and 12 deals so the board is not empty on first run. Explicitly out of scope: email sending or syncing, OAuth, multi-user or permissions, workflow automation, reporting beyond the pipeline totals, mobile app, any third-party API. If you want any secret later, read it from .env and commit .env.example only. Write a README with setup in under five commands and a one-paragraph note on how to back up the SQLite file. ## Required capabilities - Node runtime and a place to run it, local or a small VPS - Optional: an IMAP or Gmail API credential if you want email logging, which is where the weekend goes ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Salesforce product brief ## Problem You can absolutely one-shot a contacts-and-deals tracker, and for one person that is often better than Salesforce. But nobody pays Salesforce for a pipeline table. They pay for the thing everything else in the company already points at: the ETL jobs, the marketing automation, the support queue, the finance reports, the twelve years of closed-won history, the admin who wrote 400 validation rules, and the auditors who accept it. A personal replacement replaces the part of Salesforce that was never the expensive part. If you are a solo operator or a two-person shop, build it; if you are trying to leave an existing org, this is a migration project, not a coding session. ## Product outcome A local web app with contacts, companies, deals on a drag-across pipeline, activity notes, and next-action reminders, backed by SQLite. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node runtime and a place to run it, local or a small VPS - Optional: an IMAP or Gmail API credential if you want email logging, which is where the weekend goes ## Explicit non-goals for v1 - Every integration: marketing automation, support cases, quoting, billing, BI tooling, and the hundred connectors vendors ship for Salesforce and nothing else - Multi-user permissions, sharing rules, field-level security, and audit trails that survive a compliance review - Reporting, forecasting and dashboards that leadership already knows how to read - The admin ecosystem: consultants, AppExchange, and a hiring pool that already knows the object model - Historical data with lineage, which is the actual asset in any CRM older than a year ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a single-user personal CRM that runs locally. No accounts, no cloud, no telemetry. Stack, non-negotiable: - Next.js (App Router) with TypeScript - SQLite via better-sqlite3, file at ./data/crm.db - Drizzle ORM for schema and migrations - Tailwind CSS, no component library - Runs with `npm run dev` on port 3000 and nothing else needs to be installed Data model: - companies: id, name, domain, notes, createdAt - contacts: id, companyId (nullable), name, email, phone, role, notes, createdAt - deals: id, title, companyId, contactId (nullable), amountCents, currency (default USD), stage, expectedCloseDate, createdAt, closedAt, outcome (won|lost|null) - activities: id, kind (call|email|meeting|note), subject, body, occurredAt, contactId, dealId, createdAt - tasks: id, title, dueDate, done, contactId, dealId - Stages are a fixed list in code: lead, qualified, proposal, negotiation, closed. Screens: 1. /pipeline: kanban board, one column per stage, deal cards showing title, company, amount. Drag between columns persists the stage. Column headers show count and summed amount. 2. /contacts and /companies: searchable tables, click through to a detail page showing linked deals, activity timeline newest first, and open tasks. 3. /deals/[id]: edit fields inline, log an activity, mark won or lost. 4. /today: tasks due today or overdue, plus deals with no activity in 14 days, labelled "going cold". Also build: - One global search box (cmd+K) over contacts, companies and deals, using SQLite LIKE queries. No vector search, no AI. - A GET /api/export route that dumps everything as JSON, and a CSV import for contacts that maps columns in the UI before committing. - Seed script with about 20 fake contacts, 8 companies and 12 deals so the board is not empty on first run. Explicitly out of scope: email sending or syncing, OAuth, multi-user or permissions, workflow automation, reporting beyond the pipeline totals, mobile app, any third-party API. If you want any secret later, read it from .env and commit .env.example only. Write a README with setup in under five commands and a one-paragraph note on how to back up the SQLite file. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Salesforce capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
Because the CRM is the seam the whole revenue org is stitched along. Marketing scores leads into it, support reads accounts out of it, finance reconciles against it, and the board deck is generated from its reports. Ripping it out means rebuilding all of that at once with no downtime, while the sales team is mid-quarter. That risk is worth more per year than the license, which is exactly why the license costs what it does. A solo consultant tracking forty relationships is in a completely different situation and is mostly paying for guilt.
xEvery integration: marketing automation, support cases, quoting, billing, BI tooling, and the hundred connectors vendors ship for Salesforce and nothing else
xMulti-user permissions, sharing rules, field-level security, and audit trails that survive a compliance review
xReporting, forecasting and dashboards that leadership already knows how to read
xThe admin ecosystem: consultants, AppExchange, and a hiring pool that already knows the object model
xHistorical data with lineage, which is the actual asset in any CRM older than a year
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Salesforce ($25/mo) with one prompt"
Vibecode Salesforce
Not really. Salesforce's value is not the code: The moat is that finance, marketing and support all already read from it, so leaving is a migration with three other departments attached. See the honest breakdown above.
How much does Salesforce cost?
Salesforce costs about $25/month (Starter Suite, checked 2026-08-18), which is $300 per year.
What do I lose by replacing Salesforce?
Honestly: Every integration: marketing automation, support cases, quoting, billing, BI tooling, and the hundred connectors vendors ship for Salesforce and nothing else; Multi-user permissions, sharing rules, field-level security, and audit trails that survive a compliance review; Reporting, forecasting and dashboards that leadership already knows how to read; The admin ecosystem: consultants, AppExchange, and a hiring pool that already knows the object model; Historical data with lineage, which is the actual asset in any CRM older than a year. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Salesforce?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.