Vibecode Systeme.io
track this build5 steps, step by step0%KINDA · weekend project
None of the individual pieces here are hard: a landing page, an opt-in form, a contacts table, a Stripe checkout, a gated video page, a ref-code cookie. An agent can wire all of that into one self-hosted app in a weekend and you will own the list outright. What you cannot one-shot is the boring operational layer: domain authentication, bounce and complaint handling, unsubscribe compliance, and the fact that sending 20,000 emails from your own setup means you now care about deliverability as a personal hobby. You also lose the drag-and-drop editor, which sounds cosmetic until you want to change a headline at 11pm without opening an editor. Verdict lands at kinda because the value survives the rebuild but the maintenance does not disappear.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Systeme.io. 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 ===== # Systeme.io indie build ## Goal Build the smallest trustworthy replacement for the core Systeme.io workflow for one developer or a tiny team. ## Scope Serves your funnel and course pages, captures opt-ins into a local database, sells access through Stripe Checkout, and drips emails plus tracks affiliate referrals from a cron worker. ## 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: - Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job - Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling - Affiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates - Webinars, blogs, and the odd extras that come free in the bundle - One vendor to blame when checkout breaks on launch day If those capabilities are essential, use Systeme.io 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 self-hosted, single-operator funnel and course platform. One person runs it, no multi-tenancy. Stack, no substitutions: - Next.js 15, App Router, TypeScript, Tailwind - SQLite via better-sqlite3, single file at ./data/app.db, migrations as plain SQL in ./migrations - Stripe Checkout plus webhooks for payments - Resend for outbound email - No auth provider: magic-link email login for buyers, single admin password from .env What to build: 1. Funnel pages defined as MDX files in ./content/pages. Each has frontmatter: slug, title, headline, subhead, cta, optional priceId. Render server-side with a clean default layout. 2. Opt-in form component posting to /api/optin. Store contacts in SQLite: email, name, tags, source page, created_at, unsubscribed_at. Double opt-in optional via env flag. 3. Email engine: broadcasts and sequences. A sequence is a JSON file in ./content/sequences with steps (delay in hours, subject, MDX body). A worker script (npm run worker) runs every minute via node-cron, sends due steps through Resend, logs every send in an email_events table. Every email gets a one-click unsubscribe link with a signed token, and List-Unsubscribe headers. 4. Checkout: /api/checkout creates a Stripe Checkout Session for a given priceId. Webhook handler grants a course entitlement on checkout.session.completed, and revokes on refund. 5. Course area at /learn: modules and lessons from MDX in ./content/course, gated by entitlement, video via an embed URL field. Track lesson completion per contact. 6. Affiliate tracking: /r/CODE sets a 60 day first-party cookie, attributes the sale on webhook, writes rows to a commissions table with status pending. Admin page lists commissions. No payouts. 7. Admin at /admin behind the env password: contacts list with search, broadcast composer with a test-send, sales list, commissions list, CSV export of contacts and sales. Out of scope, do not build: drag-and-drop editors, webinars, blog CMS, tax handling, affiliate payouts, IP warmup, analytics beyond page-view counts stored locally. Rules: all secrets in .env (STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, RESEND_API_KEY, ADMIN_PASSWORD, APP_URL). No telemetry, no external analytics. Seed the database with two demo contacts, one demo course and one demo sequence so npm run dev shows a working funnel immediately. Include a README with setup steps, a Stripe CLI webhook command, and a deploy note for a single VPS with a persistent volume. ## Required capabilities - Stripe account for checkout and webhooks - Transactional email provider with a verified sending domain, for example Resend or SES - A VPS or serverless host plus your own domain - Video hosting for course content, or accept large local files - Willingness to handle unsubscribe and bounce logic yourself ## 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 Systeme.io. 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 ===== # Systeme.io indie build ## Goal Build the smallest trustworthy replacement for the core Systeme.io workflow for one developer or a tiny team. ## Scope Serves your funnel and course pages, captures opt-ins into a local database, sells access through Stripe Checkout, and drips emails plus tracks affiliate referrals from a cron worker. ## 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: - Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job - Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling - Affiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates - Webinars, blogs, and the odd extras that come free in the bundle - One vendor to blame when checkout breaks on launch day If those capabilities are essential, use Systeme.io 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 self-hosted, single-operator funnel and course platform. One person runs it, no multi-tenancy. Stack, no substitutions: - Next.js 15, App Router, TypeScript, Tailwind - SQLite via better-sqlite3, single file at ./data/app.db, migrations as plain SQL in ./migrations - Stripe Checkout plus webhooks for payments - Resend for outbound email - No auth provider: magic-link email login for buyers, single admin password from .env What to build: 1. Funnel pages defined as MDX files in ./content/pages. Each has frontmatter: slug, title, headline, subhead, cta, optional priceId. Render server-side with a clean default layout. 2. Opt-in form component posting to /api/optin. Store contacts in SQLite: email, name, tags, source page, created_at, unsubscribed_at. Double opt-in optional via env flag. 3. Email engine: broadcasts and sequences. A sequence is a JSON file in ./content/sequences with steps (delay in hours, subject, MDX body). A worker script (npm run worker) runs every minute via node-cron, sends due steps through Resend, logs every send in an email_events table. Every email gets a one-click unsubscribe link with a signed token, and List-Unsubscribe headers. 4. Checkout: /api/checkout creates a Stripe Checkout Session for a given priceId. Webhook handler grants a course entitlement on checkout.session.completed, and revokes on refund. 5. Course area at /learn: modules and lessons from MDX in ./content/course, gated by entitlement, video via an embed URL field. Track lesson completion per contact. 6. Affiliate tracking: /r/CODE sets a 60 day first-party cookie, attributes the sale on webhook, writes rows to a commissions table with status pending. Admin page lists commissions. No payouts. 7. Admin at /admin behind the env password: contacts list with search, broadcast composer with a test-send, sales list, commissions list, CSV export of contacts and sales. Out of scope, do not build: drag-and-drop editors, webinars, blog CMS, tax handling, affiliate payouts, IP warmup, analytics beyond page-view counts stored locally. Rules: all secrets in .env (STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, RESEND_API_KEY, ADMIN_PASSWORD, APP_URL). No telemetry, no external analytics. Seed the database with two demo contacts, one demo course and one demo sequence so npm run dev shows a working funnel immediately. Include a README with setup steps, a Stripe CLI webhook command, and a deploy note for a single VPS with a persistent volume. ## Required capabilities - Stripe account for checkout and webhooks - Transactional email provider with a verified sending domain, for example Resend or SES - A VPS or serverless host plus your own domain - Video hosting for course content, or accept large local files - Willingness to handle unsubscribe and bounce logic yourself ## 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 Systeme.io. 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 ===== # Systeme.io product brief ## Problem None of the individual pieces here are hard: a landing page, an opt-in form, a contacts table, a Stripe checkout, a gated video page, a ref-code cookie. An agent can wire all of that into one self-hosted app in a weekend and you will own the list outright. What you cannot one-shot is the boring operational layer: domain authentication, bounce and complaint handling, unsubscribe compliance, and the fact that sending 20,000 emails from your own setup means you now care about deliverability as a personal hobby. You also lose the drag-and-drop editor, which sounds cosmetic until you want to change a headline at 11pm without opening an editor. Verdict lands at kinda because the value survives the rebuild but the maintenance does not disappear. ## Product outcome Serves your funnel and course pages, captures opt-ins into a local database, sells access through Stripe Checkout, and drips emails plus tracks affiliate referrals from a cron worker. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Stripe account for checkout and webhooks - Transactional email provider with a verified sending domain, for example Resend or SES - A VPS or serverless host plus your own domain - Video hosting for course content, or accept large local files - Willingness to handle unsubscribe and bounce logic yourself ## Explicit non-goals for v1 - Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job - Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling - Affiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates - Webinars, blogs, and the odd extras that come free in the bundle - One vendor to blame when checkout breaks on launch day ## 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 self-hosted, single-operator funnel and course platform. One person runs it, no multi-tenancy. Stack, no substitutions: - Next.js 15, App Router, TypeScript, Tailwind - SQLite via better-sqlite3, single file at ./data/app.db, migrations as plain SQL in ./migrations - Stripe Checkout plus webhooks for payments - Resend for outbound email - No auth provider: magic-link email login for buyers, single admin password from .env What to build: 1. Funnel pages defined as MDX files in ./content/pages. Each has frontmatter: slug, title, headline, subhead, cta, optional priceId. Render server-side with a clean default layout. 2. Opt-in form component posting to /api/optin. Store contacts in SQLite: email, name, tags, source page, created_at, unsubscribed_at. Double opt-in optional via env flag. 3. Email engine: broadcasts and sequences. A sequence is a JSON file in ./content/sequences with steps (delay in hours, subject, MDX body). A worker script (npm run worker) runs every minute via node-cron, sends due steps through Resend, logs every send in an email_events table. Every email gets a one-click unsubscribe link with a signed token, and List-Unsubscribe headers. 4. Checkout: /api/checkout creates a Stripe Checkout Session for a given priceId. Webhook handler grants a course entitlement on checkout.session.completed, and revokes on refund. 5. Course area at /learn: modules and lessons from MDX in ./content/course, gated by entitlement, video via an embed URL field. Track lesson completion per contact. 6. Affiliate tracking: /r/CODE sets a 60 day first-party cookie, attributes the sale on webhook, writes rows to a commissions table with status pending. Admin page lists commissions. No payouts. 7. Admin at /admin behind the env password: contacts list with search, broadcast composer with a test-send, sales list, commissions list, CSV export of contacts and sales. Out of scope, do not build: drag-and-drop editors, webinars, blog CMS, tax handling, affiliate payouts, IP warmup, analytics beyond page-view counts stored locally. Rules: all secrets in .env (STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, RESEND_API_KEY, ADMIN_PASSWORD, APP_URL). No telemetry, no external analytics. Seed the database with two demo contacts, one demo course and one demo sequence so npm run dev shows a working funnel immediately. Include a README with setup steps, a Stripe CLI webhook command, and a deploy note for a single VPS with a persistent volume. ## 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 Systeme.io capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Systeme.io indie build ## Goal Build the smallest trustworthy replacement for the core Systeme.io workflow for one developer or a tiny team. ## Scope Serves your funnel and course pages, captures opt-ins into a local database, sells access through Stripe Checkout, and drips emails plus tracks affiliate referrals from a cron worker. ## 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: - Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job - Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling - Affiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates - Webinars, blogs, and the odd extras that come free in the bundle - One vendor to blame when checkout breaks on launch day If those capabilities are essential, use Systeme.io 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 self-hosted, single-operator funnel and course platform. One person runs it, no multi-tenancy. Stack, no substitutions: - Next.js 15, App Router, TypeScript, Tailwind - SQLite via better-sqlite3, single file at ./data/app.db, migrations as plain SQL in ./migrations - Stripe Checkout plus webhooks for payments - Resend for outbound email - No auth provider: magic-link email login for buyers, single admin password from .env What to build: 1. Funnel pages defined as MDX files in ./content/pages. Each has frontmatter: slug, title, headline, subhead, cta, optional priceId. Render server-side with a clean default layout. 2. Opt-in form component posting to /api/optin. Store contacts in SQLite: email, name, tags, source page, created_at, unsubscribed_at. Double opt-in optional via env flag. 3. Email engine: broadcasts and sequences. A sequence is a JSON file in ./content/sequences with steps (delay in hours, subject, MDX body). A worker script (npm run worker) runs every minute via node-cron, sends due steps through Resend, logs every send in an email_events table. Every email gets a one-click unsubscribe link with a signed token, and List-Unsubscribe headers. 4. Checkout: /api/checkout creates a Stripe Checkout Session for a given priceId. Webhook handler grants a course entitlement on checkout.session.completed, and revokes on refund. 5. Course area at /learn: modules and lessons from MDX in ./content/course, gated by entitlement, video via an embed URL field. Track lesson completion per contact. 6. Affiliate tracking: /r/CODE sets a 60 day first-party cookie, attributes the sale on webhook, writes rows to a commissions table with status pending. Admin page lists commissions. No payouts. 7. Admin at /admin behind the env password: contacts list with search, broadcast composer with a test-send, sales list, commissions list, CSV export of contacts and sales. Out of scope, do not build: drag-and-drop editors, webinars, blog CMS, tax handling, affiliate payouts, IP warmup, analytics beyond page-view counts stored locally. Rules: all secrets in .env (STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, RESEND_API_KEY, ADMIN_PASSWORD, APP_URL). No telemetry, no external analytics. Seed the database with two demo contacts, one demo course and one demo sequence so npm run dev shows a working funnel immediately. Include a README with setup steps, a Stripe CLI webhook command, and a deploy note for a single VPS with a persistent volume. ## Required capabilities - Stripe account for checkout and webhooks - Transactional email provider with a verified sending domain, for example Resend or SES - A VPS or serverless host plus your own domain - Video hosting for course content, or accept large local files - Willingness to handle unsubscribe and bounce logic yourself ## 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
# Systeme.io product brief ## Problem None of the individual pieces here are hard: a landing page, an opt-in form, a contacts table, a Stripe checkout, a gated video page, a ref-code cookie. An agent can wire all of that into one self-hosted app in a weekend and you will own the list outright. What you cannot one-shot is the boring operational layer: domain authentication, bounce and complaint handling, unsubscribe compliance, and the fact that sending 20,000 emails from your own setup means you now care about deliverability as a personal hobby. You also lose the drag-and-drop editor, which sounds cosmetic until you want to change a headline at 11pm without opening an editor. Verdict lands at kinda because the value survives the rebuild but the maintenance does not disappear. ## Product outcome Serves your funnel and course pages, captures opt-ins into a local database, sells access through Stripe Checkout, and drips emails plus tracks affiliate referrals from a cron worker. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Stripe account for checkout and webhooks - Transactional email provider with a verified sending domain, for example Resend or SES - A VPS or serverless host plus your own domain - Video hosting for course content, or accept large local files - Willingness to handle unsubscribe and bounce logic yourself ## Explicit non-goals for v1 - Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job - Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling - Affiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates - Webinars, blogs, and the odd extras that come free in the bundle - One vendor to blame when checkout breaks on launch day ## 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 self-hosted, single-operator funnel and course platform. One person runs it, no multi-tenancy. Stack, no substitutions: - Next.js 15, App Router, TypeScript, Tailwind - SQLite via better-sqlite3, single file at ./data/app.db, migrations as plain SQL in ./migrations - Stripe Checkout plus webhooks for payments - Resend for outbound email - No auth provider: magic-link email login for buyers, single admin password from .env What to build: 1. Funnel pages defined as MDX files in ./content/pages. Each has frontmatter: slug, title, headline, subhead, cta, optional priceId. Render server-side with a clean default layout. 2. Opt-in form component posting to /api/optin. Store contacts in SQLite: email, name, tags, source page, created_at, unsubscribed_at. Double opt-in optional via env flag. 3. Email engine: broadcasts and sequences. A sequence is a JSON file in ./content/sequences with steps (delay in hours, subject, MDX body). A worker script (npm run worker) runs every minute via node-cron, sends due steps through Resend, logs every send in an email_events table. Every email gets a one-click unsubscribe link with a signed token, and List-Unsubscribe headers. 4. Checkout: /api/checkout creates a Stripe Checkout Session for a given priceId. Webhook handler grants a course entitlement on checkout.session.completed, and revokes on refund. 5. Course area at /learn: modules and lessons from MDX in ./content/course, gated by entitlement, video via an embed URL field. Track lesson completion per contact. 6. Affiliate tracking: /r/CODE sets a 60 day first-party cookie, attributes the sale on webhook, writes rows to a commissions table with status pending. Admin page lists commissions. No payouts. 7. Admin at /admin behind the env password: contacts list with search, broadcast composer with a test-send, sales list, commissions list, CSV export of contacts and sales. Out of scope, do not build: drag-and-drop editors, webinars, blog CMS, tax handling, affiliate payouts, IP warmup, analytics beyond page-view counts stored locally. Rules: all secrets in .env (STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, RESEND_API_KEY, ADMIN_PASSWORD, APP_URL). No telemetry, no external analytics. Seed the database with two demo contacts, one demo course and one demo sequence so npm run dev shows a working funnel immediately. Include a README with setup steps, a Stripe CLI webhook command, and a deploy note for a single VPS with a persistent volume. ## 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 Systeme.io 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 business being run on top of it is usually worth more per hour than the infrastructure underneath it. A solo course seller wants to change a price, add an upsell, and send a broadcast in the same twenty minutes, and a bundled tool does that with no deploy step and no deliverability anxiety. The generous free tier also means many users are paying only once the thing is already making money, which is a hard offer to argue with. Self-hosting makes sense if you are technical, plan to stay small, and specifically want to own the contact list and the checkout data.
xVisual page and email editors, plus the template library that makes launching a funnel a copy-paste job
xManaged deliverability: shared sending reputation, bounce suppression, spam complaint handling
xAffiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates
xWebinars, blogs, and the odd extras that come free in the bundle
xOne vendor to blame when checkout breaks on launch day
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Systeme.io ($17/mo) with one prompt"
Vibecode Systeme.io
Kinda. The core of Systeme.io is buildable in a weekend with the prompt on this page, but there are real gaps: Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job, Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling. Read the honest list above before committing.
How much does Systeme.io cost?
Systeme.io costs about $17/month (Startup, checked 2026-08-18), which is $204 per year.
What do I lose by replacing Systeme.io?
Honestly: Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job; Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling; Affiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates; Webinars, blogs, and the odd extras that come free in the bundle; One vendor to blame when checkout breaks on launch day. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Systeme.io?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.