Lead delivery
Form to HubSpot
A clearly marked test lead goes through your real form on every run. Ferret then looks for it in HubSpot. If the browser says thank you but the lead never arrives, you know within minutes.
Everything looks fine. Your leads might not be arriving.
The campaign is live, the page loads and the form says thank you. We’re building Ferret to check whether the lead actually reached HubSpot, whether your tracking tags are still there and whether search engines can still find your key pages.
We’re still building Ferret. Early access means a conversation with us, not an automated signup: we want a small number of design partners who will tell us when we get it wrong.
Monitoring
Signal lost.
The form said thank you.
The lead never reached HubSpot.
Demo requests lost
37 demo requests lostEach one a buyer who asked to talk to you.
Broken for
Broken for 17 hours 42 minutesAnd counting.
Ad spend still running
4,820 euros of ad spendYou pay for clicks that go nowhere.
Your uptime monitor says
All good200 OK. Every page online.
An illustrative scenario, not data from a real customer.
Until now.
Incident 0042
Demo leads from /book-demo are not reaching HubSpot.
Ferret submitted the form twice and saw the thank-you page. No matching lead in HubSpot after 5 minutes. HubSpot last received a lead at 13:05.
Ferret alerted #marketing-ops 6 minutes after the first failure.
Run history for /book-demo
Every run is a real test lead. One failed run is never enough: Ferret retries independently before it alerts anyone.
A worked example of the alert we’re building. Not a real incident.
Caught in minutes, not days. With the evidence to fix it.
Three checks. On every run.
Ferret stays deliberately narrow: it does a few things very reliably instead of everything a little. You approve what “working” means for your site, and Ferret tells you the moment that stops being true.
In development
Tracking
Tags in place
Google Tag Manager, GA4, Google Ads, LinkedIn Insight and HubSpot tracking. You choose which tags belong on which pages, and Ferret flags the one that disappeared after a deploy.
Indexing
Visible to search
Your pricing, product and landing pages stay findable. Ferret watches for noindex tags, X-Robots-Tag headers and robots.txt rules that quietly hide them.
From first scan to first alert
The onboarding we’re building. None of these steps work yet.
In development
Scan your site
A free one-time scan of up to 300 pages shows what we observe today, and ends with a short fix brief.
Connect HubSpot
A least-privilege connection, so Ferret can confirm that test leads arrive.
Approve what “working” means
Ferret proposes your key forms, tags and pages. You approve the expected state.
Get told when it breaks
Email or Slack, only for confirmed incidents, with the evidence your developer or agency needs.
An alert should mean something broke.
Teams mute a monitor that cries wolf. We’re designing Ferret to retry independently, compare with the last good run and keep its own hiccups to itself. Only a confirmed failure on your side should earn an incident.
PassEverything you approved is still true.
Confirmed failureFerret saw it in repeated, independent runs, so it alerts you.
InconclusiveNot enough evidence yet. Ferret keeps checking quietly.
Our problemFerret itself failed. We fix it, and we do not page you.
The free scan, plainly
In development
A one-time inspection of your public site: what we observe, and what to check next. It will not tell you whether leads reach HubSpot — that takes a connected, continuous test. We have not opened the scan to the public yet.
What it will do
- Crawl up to 300 pages of one domain, politely
- Note which tracking tags we observe on each page
- Find noindex tags, X-Robots-Tag headers and robots.txt blocks
- List visible lead forms and whether HubSpot appears in your stack
- End with a short fix brief for your web team or agency
What it will not do
- Submit your forms or create records in your CRM
- Guess what you intended: a missing tag is “not observed”, not “broken”
- Keep watching once the scan finishes
- Ask for a credit card
Running sites for clients? We want to run the same three checks on every HubSpot client site you manage, give you one overview, and send each incident to the right owner. We’d like to design that with a few agencies.
Talk to us about agenciesKnow when your leads stop arriving.
We’re building Ferret now. If you recognise this problem, we’d like to build it with you.
We’re still building Ferret. Early access means a conversation with us, not an automated signup: we want a small number of design partners who will tell us when we get it wrong.