Built because forms fail quietly.
A contact form can submit perfectly, show a cheerful "thanks," and still drop the lead on the floor. We built Formitor to watch for exactly that.
The insight
The most expensive form failures are the invisible ones. A plugin update, an SMTP credential change, a host's mail server quietly getting filtered: suddenly the notification email stops arriving. Nothing on the site looks broken. Visitors still see the success message. The submission is even stored. But the email that was supposed to reach the client never does.
So nobody notices. Not the visitor, not the site, and not the agency, until the client calls weeks later to ask why they haven't heard from a single new enquiry. By then the leads, and the trust, are already gone.
That gap between a form that submits and a lead that's actually delivered is the whole reason Formitor exists.
We read the whole path, through to the inbox.
Most monitoring stops at "the page loaded." We don't. Formitor submits a real, tagged test lead and follows it all the way to delivery, because the failures that cost agencies clients live in the last mile, after the form already said it worked.
The result is a record you can stand behind: not a guess that the form is fine, but proof the lead arrived.
How we think about it
Verify delivery, not just submission
A "thank you" page is not evidence. The only honest confirmation is the notification email actually landing where it's supposed to. That's the bar we hold every check to, and it's why delivery verification, not uptime, is the heart of the product.
Confirm before alarming
Monitoring that cries wolf gets muted, and muted monitoring catches nothing. A single missed delivery might just be a slow mail queue, so Formitor treats the first miss as a question, not an answer. It only alerts after a re-check confirms the failure is real. Quiet when things are fine, clear when they aren't.
Built for agencies running many sites
Watching one form is easy; watching a hundred across a portfolio is the actual job. So the dashboard floats failing sites to the top, the spoke plugin auto-discovers forms instead of asking you to configure each one, and every client can get a shareable, read-only status page. It's designed for the person responsible for all of it at once.
Stay out of the way
We never want to be the thing that breaks a client's site. Formitor generates its own tagged synthetic test entries (it does not store the real leads your clients receive) and cleans those test entries up. Checks are spaced to avoid throttling, the spoke is HMAC-authenticated so only Formitor can trigger it, and seed mailboxes are read-only. Being trustworthy on someone else's infrastructure is a feature, not an afterthought.
What we're building toward
Today, delivery verification, checkout monitoring, inbox-placement monitoring, SPF/DKIM/DMARC deliverability diagnostics, CAPTCHA failure detection, and multi-channel alerts (Slack, Discord, Teams, SMS, webhooks) are all live: the parts that catch a lead going missing, a notification sliding into Spam, or a sending domain that's quietly misconfigured. From there, we're extending the same principle of reading the whole path:
- White-label custom domains, so the status pages and dashboard can carry your agency's brand. (Roadmap.)
- Wider inbox-placement coverage, beyond Gmail to Outlook and more mailbox providers. (Roadmap.)
- Deeper integrations, more ways for a confirmed failure to reach the tools your team already lives in. (Roadmap.)
Everything we add has to clear the same bar the product started with: tell the truth about whether the lead actually got through.
Put a smoke detector on every client's lead form.
Install the spoke, set a cadence, and let Formitor verify delivery on a schedule.