You Built Your Website with AI. Do Leads from the Form Reach You?

A website with an enquiry form hasn't been a problem for years. Platforms like Wix build one from a template. There is also a whole market of tools that specialise only in forms, such as Jotform, Typeform and Google Forms. They keep every enquiry and can send you a notification for each new one. Anything more complex has always had developers. What is new is something else: since 2025, someone with no programming experience can build their own software simply by describing it in words.

In February 2025, OpenAI co-founder Andrej Karpathy named this "vibe coding". By the end of the year, Collins Dictionary had made it its word of the year, which the BBC describes as the art of making an app or website by describing it to AI rather than writing the code by hand. In May 2025, Anthropic made Claude Code (an AI assistant that writes code and runs it from your own computer) generally available. With an assistant like that you can now build a site, a sales page and an automation that handles enquiries yourself. That is exactly what we teach in our Build It Yourself course (in Bulgarian).

It is a big opportunity. But in the same post where he coined the term, Karpathy wrote something that rarely gets quoted: "I 'Accept All' always, I don't read the diffs anymore." For an experiment, that's fine. For the form your clients come through, it isn't. A paid platform makes sure an enquiry doesn't get lost on the way. When you built the form yourself, that job is yours.

Most owners think of their website form as a letterbox: the client drops the letter in, the letter arrives. In reality a form is more like a courier, and couriers sometimes say "delivered" before they reach the address.

What happens after a client clicks "Send"

Behind every form there are steps the client never sees. The enquiry has to be saved somewhere. You have to be notified. The client has to get a confirmation. Sometimes a report or a reference number is created too.

Each step depends on another system: a database, an email service, an automation tool. If one of them fails for a minute and nobody planned what should happen then, the enquiry simply vanishes. The client sees "Sent" and waits. You don't know there is anything to wait for.

So the "Sent" message on screen doesn't prove the enquiry reached you. It only proves the button was pressed.

What we see in our own work

Our own websites are built exactly this way, with an AI assistant and the same tools we show in the course. Here are a few things from just the last few days, from an ordinary review of our own forms.

• The form said "done" too early. The AI scanner form on the AI Ready Standard website answered the client before the enquiry was saved. The fix we prepared makes it say "done" only once the record is in place, and if saving fails, the client sees that something went wrong.
• The retry that doubles the client. When a step fails, the right thing is for the system to try again. With one exception: saving the enquiry itself. Try that twice and the client may be recorded twice and get two identical emails. So in the fix we planned retries everywhere else, and deliberately not there.
• Outside requests. Requests that don't come from our website used to be rejected only after the system had already started processing them. With the fix they are stopped at the door.
• A notification for every enquiry. On our "Process X-ray" form we added a phone notification through Telegram for every new enquiry, not just an email that can sit unread.
• A change that went out too early. A change to a live form became visible to clients at once instead of staying a draft. We reverted it within 90 seconds and added a rule that prevents it from happening again.

And the most useful lesson of all: when our AI assistant decided, from the name of an automation, that a form was sending the wrong report, I was the one who knew the truth. I had filled in every one of the forms myself, as a client, end to end. No check replaces that.

Check your own form in ten minutes

You don't need technical knowledge. You need a phone and ten minutes.

1. Fill in your form as a client. Use a real email address that isn't your work one.
2. Time it. How many minutes passed before you knew there was a new enquiry?
3. Check the "client's" inbox. Did a confirmation arrive? Is it in spam? Emails that don't meet Google's sender requirements increasingly end up there.
4. Compare the details. Is what you typed what reached you? If there is a reference number, is it the same everywhere?
5. Try it on a phone. Many clients fill in forms on their phones. If the fields are awkward there, plenty of them simply give up. Google's guidance on usable forms is a good checklist.

If your form lives in a specialised form tool or a platform like Wix, it handles most of these steps for you, and this article is not about it. Even then, clients get lost after the form: nobody calls in time, nobody is reminded about the follow-up. That is how the story of a real estate agency that was losing clients despite having plenty of them began, and there too the answer was automating the whole path, not just the form.

Three questions if someone else built your form

If you built it yourself, ask them of yourself, and if you built it with an AI assistant, ask it too. Just don't take its answer on trust: AI sounds sure of itself even when it's wrong.

• "What happens if the system is down for a minute?" A good answer describes a retry or a warning. A bad one is "that doesn't happen."
• "Can a client get two identical emails?" If the answer is "I don't know," check.
• "How will I know if the form stops working?" If the answer is "a client will call you," you have a problem. A good form has someone or something watching it and telling you when it has been quiet for longer than usual.

One more note: the form itself doesn't need AI. AI helps you build it, but inside it is ordinary, well-ordered process automation. For the difference between the two, see what business process automation really means.

What to do this week

1. Fill in your own form today, and then once a month.
2. Ask the three questions of whoever maintains it.
3. For the last month, compare the number of enquiries in your system with the number of notifications you received. If they don't match, you know where to start.

If you want to build the site, the form and the automation yourself, and have them hold up, join Build It Yourself (in Bulgarian). It runs over two days, you leave with a working site on your own address, and the check before going live is part of the programme.

If you would rather not build it yourself, or want to see where clients, tasks or money get lost along the way in your company, that is where my analysis starts. You can begin with a Process X-ray, where we look at one of your processes step by step, or start here.