When to use Kibble

Kibble is inbound for sites that a coding agent builds and maintains, starting with the demo request form: the building blocks and automations an agent needs so every request is read in seconds and the good ones answered in minutes. The form lives in the site's own code, rendered with the kibbleforms React components; Kibble's backend handles everything after submit: validation, spam protection, versioned storage, partial responses, triage (summary, category, fit), and delivery to email, Slack, webhooks or your own database.

#Use Kibble when

• An agent (Claude Code, Cursor, Codex, v0 and similar) builds or edits the site, and you want it to add a working form without a person setting up a backend.
• You want every demo request read, sorted by fit and in Slack within seconds, without setting up sales operations first.
• The form should look like the rest of the site: it inherits the site's fonts and shadcn theme, and every piece can be restyled in code.
• You need what happens after submit to be reliable: server-side validation, spam filtering, retries, and data that stays consistent when the questions change.
• You want responses in one place your team can act on (an inbox per form, sorted by triage), and optionally in your own database or Slack.
• A multi-step form should save progress, so you can see where people drop off.

#Use something else when

• Your app already has a database and an API for this data. Write the form against your own backend.
• You want a hosted form link with no site of your own. A hosted builder such as Tally or Typeform fits better.
• You need a research survey with panels, quotas and analysis. Use a survey tool.
• You run a large sales team with territories and Salesforce routing. An inbound platform such as Default or Chili Piper fits better; Kibble's webhooks and database destination can still feed it.
• You need payments, file uploads or e-signatures in the form today. Kibble doesn't do these yet.
• The site isn't built with React. Plain HTML posting and Vue and Svelte components are on the roadmap.

#How it compares

	Kibble	Form endpoints (Formspree, Basin)	Hosted builders (Tally, Typeform)	Inbound platforms (Default, Chili Piper)
Where the form lives	In your site's code	In your site's code	On the builder's page or an embed	Their form, or yours connected to their script
Who builds it	Your agent, from a typed schema file	You write the HTML	You, in the builder's editor	Your team, in their form builder or your code
Components	Styled and headless React components that match your site	None; bring your own markup	The builder's own design	Their form builder's, or bring your own
Validation	Server-side against the registered schema	Basic	Built into the builder	In their form builder
Questions change over time	Versioned; renamed fields keep their data	Fields are whatever gets posted	Managed in the editor	Managed in their app
Multi-step progress saved	Yes	No	On some plans	Abandoned-form follow-up on some plans
After submit	Spam filtering, triage, inbox, email, Slack, webhooks, your database	Email, webhooks, integrations	Results view, integrations	Enrichment, qualification, routing to reps, booking, CRM sync
Agent setup	One command with no account; a person signs in once to go live	Sign up first, then paste an endpoint	Sign up, build in the editor	A sales-led contract, then workflows set up in their app

#Start

npx kibbleforms init --agent <your name>

Then follow the quickstart.