If an AI company selling lead automation can't show you their own leads flowing through their own product, you've already learned what you need to know about how confident they are in it. Here's the test — and the embarrassing story of how we discovered our own demo form was failing it.
We had a /book-a-demo page. Clean design, clean form, five short fields. Last week a prospect filled it out and emailed us directly: "How is the form data entered? Does it just create a lead?"
We pulled up the handler. It didn't.
The form was wired to a placeholder Cloudflare Worker that was never deployed, so every submission fell through to a mailto: fallback — the kind that opens the visitor's mail client with a pre-filled email to us. On mobile, where most web traffic lives, half those mail clients aren't configured at all. The submission would silently die on the sidewalk.
Kazozo's entire product is a pipeline that turns inbound messages into qualified, routed, followed-up leads. And on our own site, we were asking prospects to click "Send" in their own email client.
A demo request isn't a form submission. It's a lead — specifically the highest-intent kind. Someone has self-selected buying intent, given you their contact details, described their business, and asked you to sell to them.
In a real lead pipeline, that means running through capture, validation, enrichment, identity matching (have they talked to us before?), two-stage qualification, scoring, routing to the right responder, follow-up within minutes, and a nurture track if they don't book immediately — with every step instrumented so you can measure what's working.
That's the job description. A mailto: link does none of it. A Notion row does maybe one of the ten. A "we'll email you soon" tab-and-refresh auto-responder does zero.
When you're evaluating an AI company that sells lead automation, ask them one question: how does your own /book-a-demo page work? Not the product demo — the actual form on their actual website.
Three flavors of answer tell you most of what you need to know.
"We use Notion / Airtable / Google Sheets." They don't trust their own product for their own highest-intent lead flow. Either the product isn't ready, or the company is organized as a sales team that happens to sell AI tools — not a product team that happens to have salespeople.
"We have a Zapier chain that hits HubSpot." They treat their own leads the same way their customers used to treat leads before AI. The product they sell is a step up from what they themselves use. That's uncomfortable to read out loud.
"Our form POSTs to our own ingest endpoint. The lead runs through the same validate-enrich-qualify pipeline any customer's widget-originated lead goes through. The Qualifier agent replies within seconds. Qualified leads get a scheduling link. Low-intent ones get a nurture track." That's the only answer that maps to the product they're selling.
So here's what we did this week.
The form on /book-a-demo now POSTs to /v1/leads/ingest on the Kazozo platform — a public, origin-allowlisted route protected by a site key, rate-limited per IP. Every submission creates a lead in a real tenant ("Kazozo HQ") with source: demo_request. It's the same type of lead a widget conversation would create, just with different metadata on entry.
From there it runs through the exact same pipeline a Growth or Pro customer's leads run through. Validated for email and phone. Enriched for company intel. Identity-matched against any prior chats on the widget. Qualified by the Lead Qualifier agent — the same one any tenant gets. Scored; demo requests pre-score high, so they skip to the front of the routing queue. The Qualifier sends a first response within seconds, including a Zoho Bookings link for qualified prospects.
If you're reading this after April 2026 and you fill out the form, that's the path your submission takes. The same product you'd be evaluating is the one that just handled your evaluation request.
Two reasons.
One: it's a credibility test. Any AI vendor handling their own most-important leads in a spreadsheet is telling you something they don't want to say out loud. You should hear it.
Two: it changes how we develop the product. Every improvement we ship to the lead pipeline, we feel within hours — not in a quarterly customer call. The nurture cadence that doesn't work, we see it. The qualifier question that annoys people, we see it. The follow-up that fires too late, we see it.
Most software companies have an internal/external gap where the product shipped to customers diverges from the product the company actually uses. Closing that gap is the single biggest leverage point on quality. It's why you can feel the difference between a company that uses its own product and one that doesn't.
Three ways to use this post.
If you're shopping AI vendors, ask the /book-a-demo question. File the answer in writing with the quote.
If you're running an AI company, try the test on yourself. If the answer is uncomfortable, that's a signal worth acting on before a prospect asks.
If you'd like to see what the answer looks like on our side, fill out the form. The response you get is the product.