Before Leadovaro ran for anyone else, it ran for us, and it still does. We point it at our own funnel and let it watch, score, and run against the pipeline we live or die on, and we have since long before we let another team near it. This is what Customer Zero was actually like, told partly in Leadovaro's own voice, including the first run it ever made for us and the one number that moved. Then an invitation to come run a signal of your own.
The first run it ever made for us
Here is the first thing Leadovaro ever did on our funnel, in its own words.
⬥ Leadovaro
I noticed Anweledig Labs came back to your pricing page for the third time in an hour, and a second person from the same account showed up behind them. They cleared four of the five axes on your Growth ICP. That matched the pricing-revisit Play you approved, so I drafted the intro from the assigned owner and held it for your yes. You said yes in four minutes. I sent it and logged the run.
That is run #0001. It is unglamorous, and that is the point. No demo magic, no dashboard to admire. A signal came in, it got scored against our definition of a good account, a move went out while the moment was still warm, and the whole thing left a receipt. Step through it yourself:
Figure: Run #0001 (interactive replay)
⬥ Leadovarorun #0001
10:02:11watched anweledig: pricing_view x3
⬥ Leadovaro: Anweledig Labs came back to your pricing page a third time in an hour, with a second person behind them.
10:02:12scored icp.growth: cleared 4/5 axes
⬥ Leadovaro: They cleared four of the five axes on your Growth ICP. Warm enough to matter, by your own definition.
10:06:44approved brad (4m)
⬥ Leadovaro: This matched the pricing-revisit Play you approved. I drafted the intro and held it for your yes. You took four minutes.
10:06:45ran send.intro from owner
⬥ Leadovaro: Sent the intro from the assigned owner, while the moment was still warm.
10:06:46logged run #0001
⬥ Leadovaro: And I kept the receipt. Run #0001. You can always ask me why.
We have thousands of these now. But that first one is the one I keep, because it is the moment the argument stopped being a thesis and started being a log line.
The only honest way to ship this
Before Leadovaro ran for any other team, it ran for ours, and it still does. We are Customer Zero. Leadovaro watches, scores, and runs against the same pipeline we live or die on, and it has since long before we let another team near it.
That is the only honest way I know to ship something you intend to put in front of other people: be the first one it can embarrass. If it was going to send a bad message, route to the wrong owner, or act on a signal that did not deserve it, I wanted it happening to us, in a room where we could see it, long before it happened to you.
I told most of this story in an earlier note, so I will keep it short.
We had built a go-to-market stack that could see almost everything and act on almost nothing. De-anonymized traffic, enrichment, product events, an intent feed, a Slack channel where it all landed. Excellent eyes. No hands. A good signal would fire on Tuesday and a real response would go out Thursday, if it went out at all, because every step between detection and action was a human handoff with no owner and no deadline.
The gap was not a data problem. It was a doing problem. And you cannot buy your way out of a handoff. We tried.
So we stopped buying and started building
At Leadovaro we build agents. So instead of buying another way to see, we built the thing that acts: an agent that watches the product, the site, and the systems of record together, scores intent against our own definition of a good account, runs the Play we approved, and logs every step. Leadovaro is not another dashboard to watch. It is the governed execution layer that runs Plays through your stack.
Then, before we did anything else with it, we ran it on us.
What Customer Zero looked like
The first weeks were humbling in the useful way.
We started in Approve mode, because I did not trust it yet and that was the honest place to start. Leadovaro would watch, score, draft the move, and wait for a yes. We read every one. Most were right. The ones that were wrong taught us exactly which guardrail we had written too loose, and we tightened it. That is the loop working: not a model we hoped was correct, but a record we could read and argue with.
⬥ Leadovaro
You told me no eleven times in the first week. Nine of those were the same guardrail: I was scoring re-engagement from existing customers as new intent. You tightened the Play. I have not made that one since. It is all in the log if you want to see the day it changed.
After a few weeks the yeses got boring, which is the signal you are waiting for. We moved the Plays we trusted into Run mode and kept the rest on Approve. The kill switch stayed within reach the whole time. We never had to use it in anger, but knowing it was there is most of why we were willing to let go of the wheel at all.
The one number that moved
The number we had been afraid to measure was our own time to action: the median gap between a high-intent signal firing and a real, credible response going out the door. Toggle it:
Figure: Time to action, before and after (interactive)
Before Leadovaro
Tue 10:02signal fires: pricing_view x3
Tue 11:40someone notices the Slack alert
Wed 09:15standup: who owns this?
Wed 14:00owner assigned
Thu 14:30a response finally goes out
About three days. And an embarrassing share never got a response at all.
After Leadovaro
10:02:11signal fires, watched
10:02:12scored against your ICP
10:06:45the Play you approved runs
10:06:46sent, and logged
Minutes. Same funnel, same signals. The doing stopped waiting for a human to be free.
Before Leadovaro, that number was measured in days, and an embarrassing share of signals never got a second timestamp at all. After, high-intent signals were moving from "we'll review this later" to action within minutes. Same funnel, same team, same signals. The difference was that the doing stopped waiting for a human to be free.
And the receipts came with it, which I did not expect to care about as much as I do. We could always answer why a given account got contacted on a given day, in one log, in plain language. Speed without a record is just a faster way to lose track of what you did. Leadovaro gave us both.
Why I am telling you this
For most of my career, the answer to a go-to-market problem was to buy another tool. More eyes, more dashboards, more feeds. It took me an embarrassingly long time to admit that we had enough eyes years ago, and that the thing we kept not buying was hands.
We finally stopped buying and built the hands. It is called Leadovaro. It ran for us first, it kept its receipts, and it earned the wheel one boring yes at a time. It is not only for us anymore.
Come run a signal
Leadovaro is the Signal-Based GTM agent for Growth teams. If you run growth at a B2B SaaS company and you have ever watched a good signal go cold, I think you will recognize the problem the first time you connect a source.
You do not have to take my word for any of it. There is a 7-day trial, no credit card to start, and it begins at $49 a month. Connect one source, write one Play, and watch Leadovaro run a real signal of your own. That is the whole pitch: come run one, and be your own Customer Zero.
Leadovaro reads your site and works out which companies are already looking at you, and whether they're worth your time. Then it writes up the first follow-up it would run, in your own colors, inside a minute. It takes a few minutes to read. Then pass it to whoever signs off.
