Building a form with AI is a four-sentence brief and an editor's review: describe the goal, what you need to collect, where it lives, and what happens after submit — then review the generated fields, validation, and customer mapping before publishing. The walkthrough below builds a real quote-request form, start to finish.
Forms used to be the most tedious build on a website: field widgets, validation rules, notification wiring, then a page to host it all. With AI the assembly is a sentence — which moves all the skill into two places: what you say and what you check. Here's both, using a catering company's quote-request form as the running example.
The four-sentence brief
A good form brief answers four questions: what's the goal, what must be collected, where does it live, what happens after submit. Concretely:
The prompt
"Create a quote-request form for our catering business and a page to host it at /catering-quote. Collect: name, email, phone (optional), event date, guest count, event type (wedding / corporate / private party), and a free-text field for dietary or menu notes. Submissions should create or update a customer record and notify our events inbox. Date must be in the future; guest count between 10 and 500. Keep it as a draft for my review."
Two things to notice. The brief states business rules in plain language — "date must be in the future, guest count 10–500" — and AI translates them into proper validation. And it ends with the standing instruction from every AI workflow on this blog: draft, for my review.
Review the fields like an editor
What comes back is a complete draft: the form, its validation, and the hosting page. Your review has a checklist shape — and it's the same critical eye as the lead-form friction audit:
Field review checklist
- Is every required field truly blocking? (Phone stays optional — the brief said so; check it stayed that way.)
- Are the choice lists right? "Event type" options should match how YOU quote, not generic categories.
- Do validation rules match reality? Future-date and 10–500 guests should be enforced, with error messages that say what to fix.
- Did it invent fields you didn't ask for? AI loves adding "company name" and "how did you hear about us" — cut anything you wouldn't act on.
- Is the submit button labeled with the value? "Request my quote" beats "Submit".
The brief moves the work; the review keeps the judgment.
AI assembles in seconds what used to take an afternoon — your job is the five-minute edit it can't do.
Check the mapping — where submissions actually go
This is the step manual form-builders skip and regret. A submission should become a customer record or update, not an email that scrolls away: email and name map to the customer identity, event details land on the record where your team quotes from, and the dietary-notes field goes to notes — not into a custom field you'll never query. If you asked for follow-up automation, confirm which journey new submissions enter and that an exit rule exists for people who book. The five-minute mapping check is the difference between a form that collects and a form that feeds the business.
Edit the form and page as one thing
A form lives on a page, and the two drift apart when edited separately — a renamed field with a stale label above it, a removed option still promised in the page copy. When you refine, edit form and page together in one request: "make guest count a dropdown of ranges instead of a number, and update the page intro to mention we cater events from 10 to 500 guests." One instruction, both artifacts, no drift.
Test like a customer, then publish
Same discipline as any form: submit it yourself from your phone before sharing the link. Check the validation actually blocks a past date, the record appears with the mapped fields, the notification lands in the events inbox, and the journey enrolled you. Then publish the page. Total elapsed time for the whole walkthrough, review included: about fifteen minutes — most of it the parts that deserve a human.
Key takeaways
- Brief in four sentences: goal, fields, location, after-submit — plus "draft for my review".
- State business rules in plain language — they become validation.
- Review like an editor: required-field honesty, your real categories, cut invented fields.
- The mapping check matters most: submissions feed customer records and journeys, not an inbox.
- Form and page are one artifact — always edit them together.
Frequently asked questions
What if the generated form is close but not right?
Iterate in conversation — "make phone required, drop the company field, add a venue address" — rather than starting over. Each refinement is reviewed the same way. Rebuilding from scratch throws away the parts that were already right.
Can it handle conditional fields, like wedding-only questions?
Ask for exactly that in the brief: "if event type is wedding, also ask for venue and ceremony time." Just keep the conditional branches shallow — a form that reshapes itself three times mid-fill feels unstable to visitors no matter who built it.
Will it overwrite my existing form if I ask for changes?
Changes are prepared as drafts against the existing form and shown before applying — the same review-first rule as everything else. For changes that affect comparability of past submissions (renaming a field mid-campaign), decide deliberately; the help guide covers the trade-offs.
How do I A/B test a form AI built?
Change one decision at a time, monthly: the offer headline, a required field, the button label. Compare submission rates from your form analytics. AI makes the variants cheap; the discipline of one-change-at-a-time is still yours.
Does this work for intake and registration forms too?
Same workflow — the brief just changes shape: booking intake leans on the rules from the booking pages guide (3–5 questions, only what the team acts on), and registrations add capacity and payment context. Goal, fields, location, after-submit — the four sentences cover them all.
The form builder didn't disappear — it moved into a conversation. What's left for you is the editorial five minutes that decides whether the form converts and where its data flows. Brief well, review hard, test from your phone. The click-level setup lives in the help center.