Vibecode Cruva
track this build5 steps, step by step0%NOT REALLY · don't bother
price $199/moyou'd save $2,388/yrbuild time multi-daycategory 🛍️ creator commercereplaced by 0 people
The CRM and workflow layer are straightforward to rebuild, but Cruva's core value depends on TikTok Shop integrations, a large creator database, live commerce data and outreach infrastructure. A local build can replace internal tracking and message drafting, not the data and platform access that make the product useful at scale.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Cruva. 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 ===== # Cruva indie build ## Goal Build the smallest trustworthy replacement for the core Cruva workflow for one developer or a tiny team. ## Scope Import creator data, score and segment affiliates, track outreach and samples, generate personalized messages and monitor campaign performance from uploaded CSVs. ## 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: - Cruva's creator database and social intelligence - Native TikTok Shop integrations and live GMV data - Automated TikTok DMs and target collaboration outreach - Built-in sample request and affiliate automation at scale - Managed data enrichment and deliverability infrastructure If those capabilities are essential, use Cruva 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 local-first TikTok Shop affiliate CRM for one brand. Use Next.js 15 App Router, TypeScript, Tailwind CSS and SQLite with Drizzle ORM. The app must run locally with npm install and npm run dev. Create a dashboard with creators, campaigns, outreach, samples and performance tabs. Support CSV import for creator profiles, follower counts, category, GMV, sales and content metrics. Let me score, tag, filter, search and save creators into custom lists. Add a CRM pipeline with New, Contacted, Replied, Sample Sent, Posted and Won stages. Track sample status, product, shipping date, content due date and notes per creator. Add an outreach composer that uses the OpenAI API to draft personalized email or DM copy. Store the OpenAI key only in .env and provide .env.example. Add reusable message templates with variables for creator name, product and commission. Create campaign dashboards for replies, posts, attributed GMV, samples and conversion rates. Allow CSV export of creators, pipeline records and campaign performance. Persist all application data in local SQLite with no authentication or cloud database. Seed the app with realistic demo data so every screen is usable immediately. Do not scrape TikTok or automate TikTok DMs. Do not claim access to TikTok Shop APIs, live GMV feeds or Cruva's creator database. Treat TikTok Shop data as user-supplied CSV imports only. Use a clean desktop-first interface optimized for managing hundreds of creators. Include validation, empty states, loading states and clear error messages. Write a README with setup, CSV column examples, limitations and data backup instructions. Finish by running typecheck and build, then fix any errors. ## Required capabilities - Node.js 22+ - OpenAI API key - Creator and performance data exported as CSV ## 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 Cruva. 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 ===== # Cruva indie build ## Goal Build the smallest trustworthy replacement for the core Cruva workflow for one developer or a tiny team. ## Scope Import creator data, score and segment affiliates, track outreach and samples, generate personalized messages and monitor campaign performance from uploaded CSVs. ## 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: - Cruva's creator database and social intelligence - Native TikTok Shop integrations and live GMV data - Automated TikTok DMs and target collaboration outreach - Built-in sample request and affiliate automation at scale - Managed data enrichment and deliverability infrastructure If those capabilities are essential, use Cruva 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 local-first TikTok Shop affiliate CRM for one brand. Use Next.js 15 App Router, TypeScript, Tailwind CSS and SQLite with Drizzle ORM. The app must run locally with npm install and npm run dev. Create a dashboard with creators, campaigns, outreach, samples and performance tabs. Support CSV import for creator profiles, follower counts, category, GMV, sales and content metrics. Let me score, tag, filter, search and save creators into custom lists. Add a CRM pipeline with New, Contacted, Replied, Sample Sent, Posted and Won stages. Track sample status, product, shipping date, content due date and notes per creator. Add an outreach composer that uses the OpenAI API to draft personalized email or DM copy. Store the OpenAI key only in .env and provide .env.example. Add reusable message templates with variables for creator name, product and commission. Create campaign dashboards for replies, posts, attributed GMV, samples and conversion rates. Allow CSV export of creators, pipeline records and campaign performance. Persist all application data in local SQLite with no authentication or cloud database. Seed the app with realistic demo data so every screen is usable immediately. Do not scrape TikTok or automate TikTok DMs. Do not claim access to TikTok Shop APIs, live GMV feeds or Cruva's creator database. Treat TikTok Shop data as user-supplied CSV imports only. Use a clean desktop-first interface optimized for managing hundreds of creators. Include validation, empty states, loading states and clear error messages. Write a README with setup, CSV column examples, limitations and data backup instructions. Finish by running typecheck and build, then fix any errors. ## Required capabilities - Node.js 22+ - OpenAI API key - Creator and performance data exported as CSV ## 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 Cruva. 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 ===== # Cruva product brief ## Problem The CRM and workflow layer are straightforward to rebuild, but Cruva's core value depends on TikTok Shop integrations, a large creator database, live commerce data and outreach infrastructure. A local build can replace internal tracking and message drafting, not the data and platform access that make the product useful at scale. ## Product outcome Import creator data, score and segment affiliates, track outreach and samples, generate personalized messages and monitor campaign performance from uploaded CSVs. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node.js 22+ - OpenAI API key - Creator and performance data exported as CSV ## Explicit non-goals for v1 - Cruva's creator database and social intelligence - Native TikTok Shop integrations and live GMV data - Automated TikTok DMs and target collaboration outreach - Built-in sample request and affiliate automation at scale - Managed data enrichment and deliverability infrastructure ## 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 local-first TikTok Shop affiliate CRM for one brand. Use Next.js 15 App Router, TypeScript, Tailwind CSS and SQLite with Drizzle ORM. The app must run locally with npm install and npm run dev. Create a dashboard with creators, campaigns, outreach, samples and performance tabs. Support CSV import for creator profiles, follower counts, category, GMV, sales and content metrics. Let me score, tag, filter, search and save creators into custom lists. Add a CRM pipeline with New, Contacted, Replied, Sample Sent, Posted and Won stages. Track sample status, product, shipping date, content due date and notes per creator. Add an outreach composer that uses the OpenAI API to draft personalized email or DM copy. Store the OpenAI key only in .env and provide .env.example. Add reusable message templates with variables for creator name, product and commission. Create campaign dashboards for replies, posts, attributed GMV, samples and conversion rates. Allow CSV export of creators, pipeline records and campaign performance. Persist all application data in local SQLite with no authentication or cloud database. Seed the app with realistic demo data so every screen is usable immediately. Do not scrape TikTok or automate TikTok DMs. Do not claim access to TikTok Shop APIs, live GMV feeds or Cruva's creator database. Treat TikTok Shop data as user-supplied CSV imports only. Use a clean desktop-first interface optimized for managing hundreds of creators. Include validation, empty states, loading states and clear error messages. Write a README with setup, CSV column examples, limitations and data backup instructions. Finish by running typecheck and build, then fix any errors. ## 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 Cruva capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Cruva indie build ## Goal Build the smallest trustworthy replacement for the core Cruva workflow for one developer or a tiny team. ## Scope Import creator data, score and segment affiliates, track outreach and samples, generate personalized messages and monitor campaign performance from uploaded CSVs. ## 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: - Cruva's creator database and social intelligence - Native TikTok Shop integrations and live GMV data - Automated TikTok DMs and target collaboration outreach - Built-in sample request and affiliate automation at scale - Managed data enrichment and deliverability infrastructure If those capabilities are essential, use Cruva 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 local-first TikTok Shop affiliate CRM for one brand. Use Next.js 15 App Router, TypeScript, Tailwind CSS and SQLite with Drizzle ORM. The app must run locally with npm install and npm run dev. Create a dashboard with creators, campaigns, outreach, samples and performance tabs. Support CSV import for creator profiles, follower counts, category, GMV, sales and content metrics. Let me score, tag, filter, search and save creators into custom lists. Add a CRM pipeline with New, Contacted, Replied, Sample Sent, Posted and Won stages. Track sample status, product, shipping date, content due date and notes per creator. Add an outreach composer that uses the OpenAI API to draft personalized email or DM copy. Store the OpenAI key only in .env and provide .env.example. Add reusable message templates with variables for creator name, product and commission. Create campaign dashboards for replies, posts, attributed GMV, samples and conversion rates. Allow CSV export of creators, pipeline records and campaign performance. Persist all application data in local SQLite with no authentication or cloud database. Seed the app with realistic demo data so every screen is usable immediately. Do not scrape TikTok or automate TikTok DMs. Do not claim access to TikTok Shop APIs, live GMV feeds or Cruva's creator database. Treat TikTok Shop data as user-supplied CSV imports only. Use a clean desktop-first interface optimized for managing hundreds of creators. Include validation, empty states, loading states and clear error messages. Write a README with setup, CSV column examples, limitations and data backup instructions. Finish by running typecheck and build, then fix any errors. ## Required capabilities - Node.js 22+ - OpenAI API key - Creator and performance data exported as CSV ## 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
# Cruva product brief ## Problem The CRM and workflow layer are straightforward to rebuild, but Cruva's core value depends on TikTok Shop integrations, a large creator database, live commerce data and outreach infrastructure. A local build can replace internal tracking and message drafting, not the data and platform access that make the product useful at scale. ## Product outcome Import creator data, score and segment affiliates, track outreach and samples, generate personalized messages and monitor campaign performance from uploaded CSVs. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node.js 22+ - OpenAI API key - Creator and performance data exported as CSV ## Explicit non-goals for v1 - Cruva's creator database and social intelligence - Native TikTok Shop integrations and live GMV data - Automated TikTok DMs and target collaboration outreach - Built-in sample request and affiliate automation at scale - Managed data enrichment and deliverability infrastructure ## 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 local-first TikTok Shop affiliate CRM for one brand. Use Next.js 15 App Router, TypeScript, Tailwind CSS and SQLite with Drizzle ORM. The app must run locally with npm install and npm run dev. Create a dashboard with creators, campaigns, outreach, samples and performance tabs. Support CSV import for creator profiles, follower counts, category, GMV, sales and content metrics. Let me score, tag, filter, search and save creators into custom lists. Add a CRM pipeline with New, Contacted, Replied, Sample Sent, Posted and Won stages. Track sample status, product, shipping date, content due date and notes per creator. Add an outreach composer that uses the OpenAI API to draft personalized email or DM copy. Store the OpenAI key only in .env and provide .env.example. Add reusable message templates with variables for creator name, product and commission. Create campaign dashboards for replies, posts, attributed GMV, samples and conversion rates. Allow CSV export of creators, pipeline records and campaign performance. Persist all application data in local SQLite with no authentication or cloud database. Seed the app with realistic demo data so every screen is usable immediately. Do not scrape TikTok or automate TikTok DMs. Do not claim access to TikTok Shop APIs, live GMV feeds or Cruva's creator database. Treat TikTok Shop data as user-supplied CSV imports only. Use a clean desktop-first interface optimized for managing hundreds of creators. Include validation, empty states, loading states and clear error messages. Write a README with setup, CSV column examples, limitations and data backup instructions. Finish by running typecheck and build, then fix any errors. ## 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 Cruva 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
Brands are paying for the connected TikTok Shop data, creator discovery and reliable outreach automation, not just the CRM interface. A DIY tool can cover internal workflow, scoring and reporting, but it still needs an external source of creator data and cannot reproduce Cruva's platform access.
xCruva's creator database and social intelligence
xNative TikTok Shop integrations and live GMV data
xAutomated TikTok DMs and target collaboration outreach
xBuilt-in sample request and affiliate automation at scale
xManaged data enrichment and deliverability infrastructure
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Cruva ($199/mo) with one prompt"
Cruva pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| basic | $199/workspace | $159.20/workspace | 5 concurrent automations; standard discovery, outreach and CRM capacity. |
| growth | $399/workspace | $319.20/workspace | Up to 20 creators in the community and 7 concurrent automations. |
| scale | $599/workspace | $479.20/workspace | Unlimited community creators and unlimited concurrent automations. |
| enterprise | custom | — | Required above 7,500 daily outreach contacts; custom team and automation limits. |
free tierno free tier; every self-serve tier starts with a 14-day free trial
billingmonthly + 6-month (-10%) + annual (-20%); plan changes are prorated
hidden costsMore than 7,500 daily outreach contacts requires Enterprise; unusually large teams can be charged an unpublished flat per-seat onboarding fee; discounted terms require multi-month commitment.
verified 2026-08-14 · source ↗
Is Cruva free?
No free plan; every tier starts with a 14-day free trial. Paid is Basic at $199/mo (checked 2026-08-09).
Vibecode Cruva
Not really. Cruva's value is not the code: . See the honest breakdown above.
How much does Cruva cost?
Cruva costs about $199/month (Basic, checked 2026-08-09), which is $2388 per year.
What do I lose by replacing Cruva?
Honestly: Cruva's creator database and social intelligence; Native TikTok Shop integrations and live GMV data; Automated TikTok DMs and target collaboration outreach; Built-in sample request and affiliate automation at scale; Managed data enrichment and deliverability infrastructure. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Cruva?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.