Vibecode Front
track this build5 steps, step by step0%NOT REALLY · don't bother
price $25/moyou'd save $300/yrbuild time closest consolation build: one sittingcategory 🛟 customer supportreplaced by 0 people
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Front, operate a shared mailbox with assignments, comments, and simple rules. The hard boundary is email infrastructure, many channels, workflow automation, crm context, and enterprise governance, plus channel integrations and support operations.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Front. 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 ===== # Front indie build ## Goal Build the smallest trustworthy replacement for the core Front workflow for one developer or a tiny team. ## Scope Receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. ## 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: - email infrastructure, many channels, workflow automation, CRM context, and enterprise governance - omnichannel integrations - large-scale deliverability - AI resolution tuning - enterprise routing and compliance If those capabilities are essential, use Chatwoot 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 closest honest personal substitute for Front in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks. The core loop is: receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Implement one workspace, agents, contacts, inboxes, conversations, messages, labels, and assignment. Provide a website chat widget with reconnect, unread counts, file limits, and clear availability state. Create a shared inbox with filters, collision warnings, notes, canned replies, and searchable history. Add email notifications, browser notifications, and an immutable assignment and status log. Implement spam controls, attachment scanning hooks, retention settings, export, and contact deletion. Ship Docker Compose, backups, health checks, migrations, and a documented admin recovery flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out many social and messaging channels. Deliberately leave out AI agents trained on proprietary support data. Deliberately leave out enterprise workforce management, SSO, and compliance. Finish by running the tests and listing the exact commands used. ## Required capabilities - Docker - PostgreSQL - public HTTPS deployment - email or chat channel credentials ## 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 Front. 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 ===== # Front indie build ## Goal Build the smallest trustworthy replacement for the core Front workflow for one developer or a tiny team. ## Scope Receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. ## 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: - email infrastructure, many channels, workflow automation, CRM context, and enterprise governance - omnichannel integrations - large-scale deliverability - AI resolution tuning - enterprise routing and compliance If those capabilities are essential, use Chatwoot 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 closest honest personal substitute for Front in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks. The core loop is: receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Implement one workspace, agents, contacts, inboxes, conversations, messages, labels, and assignment. Provide a website chat widget with reconnect, unread counts, file limits, and clear availability state. Create a shared inbox with filters, collision warnings, notes, canned replies, and searchable history. Add email notifications, browser notifications, and an immutable assignment and status log. Implement spam controls, attachment scanning hooks, retention settings, export, and contact deletion. Ship Docker Compose, backups, health checks, migrations, and a documented admin recovery flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out many social and messaging channels. Deliberately leave out AI agents trained on proprietary support data. Deliberately leave out enterprise workforce management, SSO, and compliance. Finish by running the tests and listing the exact commands used. ## Required capabilities - Docker - PostgreSQL - public HTTPS deployment - email or chat channel credentials ## 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 Front. 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 ===== # Front product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Front, operate a shared mailbox with assignments, comments, and simple rules. The hard boundary is email infrastructure, many channels, workflow automation, crm context, and enterprise governance, plus channel integrations and support operations. ## Product outcome Receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Docker - PostgreSQL - public HTTPS deployment - email or chat channel credentials ## Explicit non-goals for v1 - email infrastructure, many channels, workflow automation, CRM context, and enterprise governance - omnichannel integrations - large-scale deliverability - AI resolution tuning - enterprise routing and compliance ## 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 closest honest personal substitute for Front in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks. The core loop is: receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Implement one workspace, agents, contacts, inboxes, conversations, messages, labels, and assignment. Provide a website chat widget with reconnect, unread counts, file limits, and clear availability state. Create a shared inbox with filters, collision warnings, notes, canned replies, and searchable history. Add email notifications, browser notifications, and an immutable assignment and status log. Implement spam controls, attachment scanning hooks, retention settings, export, and contact deletion. Ship Docker Compose, backups, health checks, migrations, and a documented admin recovery flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out many social and messaging channels. Deliberately leave out AI agents trained on proprietary support data. Deliberately leave out enterprise workforce management, SSO, and compliance. Finish by running the tests and listing the exact commands used. ## 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 Front capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Front indie build ## Goal Build the smallest trustworthy replacement for the core Front workflow for one developer or a tiny team. ## Scope Receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. ## 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: - email infrastructure, many channels, workflow automation, CRM context, and enterprise governance - omnichannel integrations - large-scale deliverability - AI resolution tuning - enterprise routing and compliance If those capabilities are essential, use Chatwoot 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 closest honest personal substitute for Front in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks. The core loop is: receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Implement one workspace, agents, contacts, inboxes, conversations, messages, labels, and assignment. Provide a website chat widget with reconnect, unread counts, file limits, and clear availability state. Create a shared inbox with filters, collision warnings, notes, canned replies, and searchable history. Add email notifications, browser notifications, and an immutable assignment and status log. Implement spam controls, attachment scanning hooks, retention settings, export, and contact deletion. Ship Docker Compose, backups, health checks, migrations, and a documented admin recovery flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out many social and messaging channels. Deliberately leave out AI agents trained on proprietary support data. Deliberately leave out enterprise workforce management, SSO, and compliance. Finish by running the tests and listing the exact commands used. ## Required capabilities - Docker - PostgreSQL - public HTTPS deployment - email or chat channel credentials ## 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
# Front product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Front, operate a shared mailbox with assignments, comments, and simple rules. The hard boundary is email infrastructure, many channels, workflow automation, crm context, and enterprise governance, plus channel integrations and support operations. ## Product outcome Receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Docker - PostgreSQL - public HTTPS deployment - email or chat channel credentials ## Explicit non-goals for v1 - email infrastructure, many channels, workflow automation, CRM context, and enterprise governance - omnichannel integrations - large-scale deliverability - AI resolution tuning - enterprise routing and compliance ## 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 closest honest personal substitute for Front in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks. The core loop is: receive customer messages into a shared mailbox, assign conversations, comment internally, apply simple rules, reply from one place, and retain a searchable conversation history. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Implement one workspace, agents, contacts, inboxes, conversations, messages, labels, and assignment. Provide a website chat widget with reconnect, unread counts, file limits, and clear availability state. Create a shared inbox with filters, collision warnings, notes, canned replies, and searchable history. Add email notifications, browser notifications, and an immutable assignment and status log. Implement spam controls, attachment scanning hooks, retention settings, export, and contact deletion. Ship Docker Compose, backups, health checks, migrations, and a documented admin recovery flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out many social and messaging channels. Deliberately leave out AI agents trained on proprietary support data. Deliberately leave out enterprise workforce management, SSO, and compliance. Finish by running the tests and listing the exact commands used. ## 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 Front 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
People still pay for Front because support software survives because missing or misrouting one customer message is expensive and every channel behaves differently. The recurring cost buys message delivery, webhooks, threading, identity, permissions, attachments, notifications, spam, search, uptime, and retention, not just the visible interface.
xemail infrastructure, many channels, workflow automation, CRM context, and enterprise governance
xomnichannel integrations
xlarge-scale deliverability
xAI resolution tuning
xenterprise routing and compliance
share on X ↗"I just replaced Front ($25/mo) with one prompt"
Don't feel like building it? These folks already made it free.
ChatwootA proper support inbox with chat, email and a help center; free software, billable server chores.open source↗
ZammadA serious ticket desk with email, chat, SLAs and a knowledge base; setup is the first ticket.open source↗
FreeScoutEmail becomes an assigned team inbox with notes and collision warnings; the nicer modules open a wallet.open source↗all 8 free alternatives to Front →· no votes, no pay-to-list · just what's real
Front pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| starter | — | $25/user | Up to 10 seats; 1 workspace; 1 channel type; up to 10 channels/license; 10 automation rules; 200 AI compose/translate/summarize actions per teammate/day |
| professional | — | $65/user | Up to 50 seats; 5 workspaces; omnichannel; up to 30 channels/license; 20 automation rules; 200 basic AI actions/teammate/day |
| enterprise | — | $105/user | Unlimited workspaces/rules/macros; up to 50 channels/license; Copilot, Smart QA and Smart CSAT included |
free tierno free tier (14-day Professional trial; no credit card required)
billingannual pricing published (24% saving); monthly billing control exists but current month-to-month USD figures were not exposed in official page text
hidden costsStarter and Professional AI add-ons: Copilot $20/seat/month, Smart QA $20, Smart CSAT $10, QA+CSAT $25; Autopilot starts at $0.05/conversation. Native WhatsApp adds Meta charges plus a 20% admin fee; API capacity costs $200 per extra 100 requests/minute/month; contracts over $25,000 require paid onboarding.
verified 2026-08-12 · source ↗
Vibecode Front
Not really. Front's value is not the code: Recheck price before merge. See the honest breakdown above.
How much does Front cost?
Front costs about $25/month (Starter, checked 2026-08-12), which is $300 per year.
What do I lose by replacing Front?
Honestly: email infrastructure, many channels, workflow automation, CRM context, and enterprise governance; omnichannel integrations; large-scale deliverability; AI resolution tuning; enterprise routing and compliance. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Front?
Yes: Chatwoot (A proper support inbox with chat, email and a help center; free software, billable server chores.) Zammad (A serious ticket desk with email, chat, SLAs and a knowledge base; setup is the first ticket.) FreeScout (Email becomes an assigned team inbox with notes and collision warnings; the nicer modules open a wallet.) All 8 curated free alternatives are at vibecodeit.com/front/alternatives. The prompt is for when you want it exactly your way.