Try this experiment. Ask ChatGPT for “a clean contact form for my website, name, email, message, modern styling.” Fifteen seconds later you have one, and it is genuinely good: sensible fields, tidy CSS, maybe a little validation. It looks done.

Now click Send.

Nothing happens. Or worse, something happens: the page reloads, the form clears, and your visitor believes they contacted you. The message went nowhere, because there was nowhere for it to go.

Forms are the one widget AI cannot finish

Most widgets are self-contained. A countdown timer, an FAQ accordion, a pricing table: they are HTML, CSS, and JavaScript, they run entirely in the visitor’s browser, and AI can legitimately generate the whole thing.

A form is different. The moment someone clicks Send, the data has to leave the browser and land somewhere: a server that receives it, checks it isn’t spam, stores it, and shows it to you. That somewhere is infrastructure, and a chat window cannot give you infrastructure. AI writes the front half of a form. The back half is the part that catches leads, and it is the part you are on your own for.

This is the sharpest version of a general truth: AI-generated code is a starting point, not a finished tool.

The usual fixes, and what they cost you

Ask how to wire up that AI form and you will get four standard answers.

1. “Just add a backend.” Correct, and now your ten-minute form is a weekend project: a server or cloud function, storage, spam filtering, and hosting you maintain forever.
2. A form service (Formspree, Getform, and friends). These work, but they are another account, another dashboard, and another monthly bill, and you still have to wire the endpoint, handle the redirect, and set up spam rules yourself.
3. A platform plugin. Fine on WordPress. But Shopify apps add app fees, Webflow meters form submissions by plan, Notion has no native forms at all, and a Canva website cannot run a form, period.
4. mailto:. AI still suggests this one. It opens the visitor’s desktop email app, which on a phone usually means nothing opens and the lead walks. It is the answer that looks like a solution and loses the most leads.

Notice the pattern: every fix bolts a second product onto the code. The form and the thing that catches its submissions live in different places, owned by different services, and you are the glue.

What a finished lead form actually includes

A lead form is not done until all of this exists:

• A submit endpoint the form can safely post to from any website.
• Spam screening, because a public endpoint collects bots within days. (Fugte uses Cloudflare Turnstile, the quiet successor to CAPTCHAs, plus rate limiting.)
• An inbox where you read and export submissions.
• Clear data ownership. If a freelancer built the form for you, they should not be able to read your leads. In Fugte, submissions belong to the widget’s owner, and whoever built it has no read access.
• Editability. The headline, fields, and button will need changing, and that should not require re-wiring anything.

That list is why we built forms into Fugte as a single piece. The contact and lead form starter ships with name, email, phone, subject, and message fields already connected to a submissions inbox. Publish it, embed the link, and the first lead can arrive the same afternoon. Change the heading or colors later and every embedded copy updates, because the embed is a link to the hosted form, not a copy of its code.

And if you already have that ChatGPT form sitting in a chat window: paste it into Fugte, ask the AI to hook it to a collection, and your design becomes a hosted form with a working Send button.

Want to see the whole pipeline live? This is the same form infrastructure (submit endpoint, spam screening, inbox, owner replies) doing public duty as the guestbook wall on our homepage:

Where this matters most

On WordPress you have plugin options, and if one is working for you, keep it. The gap is everywhere else:

• Canva websites have no form element at all. An embedded Fugte form is a working contact page on a platform that otherwise cannot collect a lead. (Here is how embeds work on Canva.)
• Notion pages need third-party form tools with their own branding and bills.
• Shopify stores get contact forms, but lead capture beyond that usually means an app subscription.
• Anything AI-built or hand-coded: your code, plus a real submit path.

The honest fine print

The free plan includes one live form (a form actively collecting submissions), with unlimited widgets and views and a small Fugte badge; paid plans include more live forms and remove the badge. Submission volume has fair-use limits designed around small-business contact pages, not bulk data collection. And a form widget cannot fix a slow site or bad offer: it just makes sure that when someone does want to reach you, the message actually arrives.

That last sentence is the whole post. AI solved the easy 80 percent of forms, the part you can see. The invisible 20 percent is where the leads are. Start with the lead form widget, or paste in the form your AI already wrote, and ship the part that catches them.