Vibecode Typeform
track this build5 steps, step by step0%KINDA · weekend project
A one-question form UI is easy, but Typeform's respondent UX, templates, analytics, integrations, anti-spam, payments, and scale justify a kinda.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Typeform. 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 ===== # Typeform indie build ## Goal Build the smallest trustworthy replacement for the core Typeform workflow for one developer or a tiny team. ## Scope Build a form schema/editor, render one question at a time, store responses, export CSV, and send webhooks. ## 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: - template quality - completion UX - analytics - integrations - conditional logic polish - payments - spam controls If those capabilities are essential, use HeyForm 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 me a one-question-at-a-time survey app to replace Typeform, personal scale. Requirements: - Node + Express + better-sqlite3 on my VPS behind Caddy. A form is a YAML file in forms/ (types: text, email, select, rating 1-5, yes/no), loaded at request time. No visual builder. - Public page at /s/<slug>: one question on screen, large type, Enter or click to advance, up arrow to go back, progress bar, thank-you screen. Vanilla JS, no framework, works on a phone. - Simple branching: a question may declare next: per answer. One level deep, do not build a logic engine. - Responses saved on completion to SQLite with timestamp and form version. - CSV export at /admin/<slug>.csv behind an ADMIN_TOKEN from .env; optional webhook POST per completed response, URL set in the form's YAML. - Honeypot field and a per-IP rate limit for spam, nothing fancier. - No accounts, no telemetry; respondent data stays in my SQLite file. - Out of scope: a drag-and-drop editor, payments, analytics dashboards, and partial-response capture. Adding a form means dropping a YAML file on the server. - README: Caddy snippet and the YAML form format with one full example. ## Required capabilities - hosted backend - database - form builder UI - webhook/email service - optional Stripe integration ## 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 Typeform. 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 ===== # Typeform indie build ## Goal Build the smallest trustworthy replacement for the core Typeform workflow for one developer or a tiny team. ## Scope Build a form schema/editor, render one question at a time, store responses, export CSV, and send webhooks. ## 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: - template quality - completion UX - analytics - integrations - conditional logic polish - payments - spam controls If those capabilities are essential, use HeyForm 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 me a one-question-at-a-time survey app to replace Typeform, personal scale. Requirements: - Node + Express + better-sqlite3 on my VPS behind Caddy. A form is a YAML file in forms/ (types: text, email, select, rating 1-5, yes/no), loaded at request time. No visual builder. - Public page at /s/<slug>: one question on screen, large type, Enter or click to advance, up arrow to go back, progress bar, thank-you screen. Vanilla JS, no framework, works on a phone. - Simple branching: a question may declare next: per answer. One level deep, do not build a logic engine. - Responses saved on completion to SQLite with timestamp and form version. - CSV export at /admin/<slug>.csv behind an ADMIN_TOKEN from .env; optional webhook POST per completed response, URL set in the form's YAML. - Honeypot field and a per-IP rate limit for spam, nothing fancier. - No accounts, no telemetry; respondent data stays in my SQLite file. - Out of scope: a drag-and-drop editor, payments, analytics dashboards, and partial-response capture. Adding a form means dropping a YAML file on the server. - README: Caddy snippet and the YAML form format with one full example. ## Required capabilities - hosted backend - database - form builder UI - webhook/email service - optional Stripe integration ## 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 Typeform. 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 ===== # Typeform product brief ## Problem A one-question form UI is easy, but Typeform's respondent UX, templates, analytics, integrations, anti-spam, payments, and scale justify a kinda. ## Product outcome Build a form schema/editor, render one question at a time, store responses, export CSV, and send webhooks. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - hosted backend - database - form builder UI - webhook/email service - optional Stripe integration ## Explicit non-goals for v1 - template quality - completion UX - analytics - integrations - conditional logic polish - payments - spam controls ## 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 me a one-question-at-a-time survey app to replace Typeform, personal scale. Requirements: - Node + Express + better-sqlite3 on my VPS behind Caddy. A form is a YAML file in forms/ (types: text, email, select, rating 1-5, yes/no), loaded at request time. No visual builder. - Public page at /s/<slug>: one question on screen, large type, Enter or click to advance, up arrow to go back, progress bar, thank-you screen. Vanilla JS, no framework, works on a phone. - Simple branching: a question may declare next: per answer. One level deep, do not build a logic engine. - Responses saved on completion to SQLite with timestamp and form version. - CSV export at /admin/<slug>.csv behind an ADMIN_TOKEN from .env; optional webhook POST per completed response, URL set in the form's YAML. - Honeypot field and a per-IP rate limit for spam, nothing fancier. - No accounts, no telemetry; respondent data stays in my SQLite file. - Out of scope: a drag-and-drop editor, payments, analytics dashboards, and partial-response capture. Adding a form means dropping a YAML file on the server. - README: Caddy snippet and the YAML form format with one full example. ## 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 Typeform capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Typeform indie build ## Goal Build the smallest trustworthy replacement for the core Typeform workflow for one developer or a tiny team. ## Scope Build a form schema/editor, render one question at a time, store responses, export CSV, and send webhooks. ## 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: - template quality - completion UX - analytics - integrations - conditional logic polish - payments - spam controls If those capabilities are essential, use HeyForm 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 me a one-question-at-a-time survey app to replace Typeform, personal scale. Requirements: - Node + Express + better-sqlite3 on my VPS behind Caddy. A form is a YAML file in forms/ (types: text, email, select, rating 1-5, yes/no), loaded at request time. No visual builder. - Public page at /s/<slug>: one question on screen, large type, Enter or click to advance, up arrow to go back, progress bar, thank-you screen. Vanilla JS, no framework, works on a phone. - Simple branching: a question may declare next: per answer. One level deep, do not build a logic engine. - Responses saved on completion to SQLite with timestamp and form version. - CSV export at /admin/<slug>.csv behind an ADMIN_TOKEN from .env; optional webhook POST per completed response, URL set in the form's YAML. - Honeypot field and a per-IP rate limit for spam, nothing fancier. - No accounts, no telemetry; respondent data stays in my SQLite file. - Out of scope: a drag-and-drop editor, payments, analytics dashboards, and partial-response capture. Adding a form means dropping a YAML file on the server. - README: Caddy snippet and the YAML form format with one full example. ## Required capabilities - hosted backend - database - form builder UI - webhook/email service - optional Stripe integration ## 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
# Typeform product brief ## Problem A one-question form UI is easy, but Typeform's respondent UX, templates, analytics, integrations, anti-spam, payments, and scale justify a kinda. ## Product outcome Build a form schema/editor, render one question at a time, store responses, export CSV, and send webhooks. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - hosted backend - database - form builder UI - webhook/email service - optional Stripe integration ## Explicit non-goals for v1 - template quality - completion UX - analytics - integrations - conditional logic polish - payments - spam controls ## 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 me a one-question-at-a-time survey app to replace Typeform, personal scale. Requirements: - Node + Express + better-sqlite3 on my VPS behind Caddy. A form is a YAML file in forms/ (types: text, email, select, rating 1-5, yes/no), loaded at request time. No visual builder. - Public page at /s/<slug>: one question on screen, large type, Enter or click to advance, up arrow to go back, progress bar, thank-you screen. Vanilla JS, no framework, works on a phone. - Simple branching: a question may declare next: per answer. One level deep, do not build a logic engine. - Responses saved on completion to SQLite with timestamp and form version. - CSV export at /admin/<slug>.csv behind an ADMIN_TOKEN from .env; optional webhook POST per completed response, URL set in the form's YAML. - Honeypot field and a per-IP rate limit for spam, nothing fancier. - No accounts, no telemetry; respondent data stays in my SQLite file. - Out of scope: a drag-and-drop editor, payments, analytics dashboards, and partial-response capture. Adding a form means dropping a YAML file on the server. - README: Caddy snippet and the YAML form format with one full example. ## 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 Typeform 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
They pay because the form looks good and converts without custom QA.
xtemplate quality
xcompletion UX
xanalytics
xintegrations
xconditional logic polish
xpayments
xspam controls
share on X ↗"I just replaced Typeform ($39/mo) with one prompt"
Don't feel like building it? These folks already made it free.
HeyFormTypeform's manners, minus the monthly rentopen source↗
OpnFormOpen-source forms with unlimited respondents; the free self-hosted builder team stops at twoopen source↗
TypebotConversational forms with serious branching; free to self-host under a fair-source licencefree↗all 4 free alternatives to Typeform →· no votes, no pay-to-list · just what's real
Typeform pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/workspace | $0/workspace | Unlimited forms; 10 responses/month across the account; 1 user. |
| basic | $39/workspace | $28/workspace | 100 responses/month; 1 user; response add-ons can raise the cap to 750/month. |
| plus | $79/workspace | $56/workspace | 1,000 responses/month; 3 users; response add-ons can raise the cap to 2,500/month. |
| business | $129/workspace | $91/workspace | 10,000 responses/month; 5 users; response add-ons can raise the cap to 50,000/month. |
| growth flow | $379/workspace | $266/workspace | 10,000 responses/month; 5 users; 1,500 enrichment actions/month; add-ons can raise responses to 50,000 and enrichment to 5,000/month. |
| talent | $169/workspace | $119/workspace | 3,000 responses/month; 3 users; 4,500 video views/month; 1,500 video answers/month; add-ons can raise responses to 7,500/month. |
| enterprise | custom | — | Custom responses, seats, security, support and service levels. |
| research flow | custom | — | Custom research responses, seats, workflows and service levels. |
free tierUnlimited forms; 10 responses/month across the account; 1 user.
billingMonthly + annual; annual prices are billed yearly. The live page also contained a lower duplicate comparison table with older/conflicting prices, so the primary current pricing cards were used.
hidden costsContacts & Automations add-ons cost $25/month for 2,400 actions or $75/month for 12,000 actions, with plan eligibility restrictions; response add-on rates are not public; counters reset monthly even on annual plans; the Growth trial requires a card and can auto-convert to paid.
verified 2026-08-12 · source ↗
Vibecode Typeform
Kinda. The core of Typeform is buildable in a weekend with the prompt on this page, but there are real gaps: template quality, completion UX. Read the honest list above before committing.
How much does Typeform cost?
Typeform costs about $39/month (Basic, checked 2026-07-30), which is $468 per year.
What do I lose by replacing Typeform?
Honestly: template quality; completion UX; analytics; integrations; conditional logic polish; payments; spam controls. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Typeform?
Yes: HeyForm (Typeform's manners, minus the monthly rent) OpnForm (Open-source forms with unlimited respondents; the free self-hosted builder team stops at two) Typebot (Conversational forms with serious branching; free to self-host under a fair-source licence) All 4 curated free alternatives are at vibecodeit.com/typeform/alternatives. The prompt is for when you want it exactly your way.