What is the best form backend for agencies?
Agencies need what single-site tools lack: a client → website → form hierarchy, settings that cascade per site instead of per form, unlimited forms without per-form fees, and a way to onboard a new client fast. Furrow Forms is built around exactly that model — one $199/yr workspace runs an entire client roster, and an AI agent can provision a new client’s forms in one call.
Do we still have to build a custom form backend for each client site?
No — that is exactly the repetition Furrow removes. Instead of standing up storage, spam filtering, and email delivery per project (or re-wiring a CMS form plugin), you drop the Furrow MCP into the build and the agent provisions the entire backend in one idempotent bootstrap_site call: client, website, forms, spam stack, notification routing, and a webhook it verifies itself. Every project gets the same production-grade form infrastructure with zero custom code.
How do agencies manage forms across many client websites?
In Furrow Forms, each client is a first-class object holding their websites (projects), and each website owns its security and routing: Turnstile keys, allowed domains, notification emails, webhook. Every form under a site inherits those settings automatically, with per-form overrides only where needed. Submissions are filterable by client, project, and form.
Do agencies pay per client, per site, or per form?
None of those. One workspace is $199/yr with unlimited clients, projects, and forms, and 10,000 submissions a month pooled across the roster. Expansion packs add +5,000 submissions/month for $99/yr each. Running multiple separate agencies or businesses? Each gets its own isolated workspace under the same login.
Can I use my own HTML instead of a form builder?
Yes — that’s the intended workflow. Write whatever markup your design calls for, point the form’s action at its Furrow endpoint, and it works: no builder UI, no template tags, no restyling someone else’s markup. In practice an agent does the pointing — it reads your HTML, wires each form to its endpoint, and configures the spam protection, notification emails, and webhook in the same pass. Those are the four separate setup chores a CMS form plugin walks you through one screen at a time.
Can an AI agent onboard a new client’s forms?
Yes — end to end. An agent calls bootstrap_site with the client name, domain, Turnstile keys, notification emails, and webhook; the client, website, and every form exist in one idempotent call. It then generates the frontend snippet for HTML, Astro, or Next.js and fires a signed test webhook to verify delivery. Kickoff to live forms, one conversation.
How do client leads reach the client’s CRM or reporting?
Every submission is delivered by email (per-project recipient lists with template tokens) and by HMAC-signed webhooks with automatic retries and a per-project delivery log — point each client’s webhook at their CRM. A native integration with Burrow, our agency reporting product, is in the works.