We pointed our AI employee at our own website traffic

Most companies demo their product on fake data. We turned ours on ourselves: kentohq.com runs the same visitor beacon we ship to customers, and Jack — our outreach agent — works the companies that show up. This post is the full pipeline, the privacy lines we drew before writing the code, and why we think this is the most honest demo an agent product can give.

The idea in one sentence

Your website already receives buying intent every day — you just can't see it. Companies visit, read your pricing, come back twice, and leave without a trace. The visitor pipeline makes that visible at the company level and hands it to an agent who does something about it.

How the pipeline works

1. One pixel. A single image beacon on each page — no cookies, no fingerprinting, no JavaScript payload tracking your mouse.
2. Company resolution. The visiting IP is resolved to a company (via IPinfo's reverse-IP data). The moment it resolves, the raw IP is dropped. If it doesn't resolve to a company, nothing is kept.
3. Interest ranking. Companies are ranked by behaviour: pages viewed, return visits, time between visits. A company that read your pricing page twice this week outranks one that bounced off the blog.
4. Jack takes the hot ones. He researches each company, finds what they do, and drafts an intro that references what they actually looked at — not "I hope this email finds you well," but "you spent time on our verified-completion page; here's how that works for a team like yours."
5. You approve. Drafts wait for a human. Auto-send exists, is off by default, and is limited to repeat visitors.

Where we drew the privacy line

Before this feature existed, we wrote a scope document, and the first line was the constraint: company-level only, never a named person. The rest follows from it:

• Do-Not-Track and Global Privacy Control headers are honored — those visits are never recorded at all.
• Raw IPs are dropped at resolve time; we store "Acme GmbH visited /pricing," not an address.
• Everything purges at 90 days.
• EU traffic stays company-level with no person-level roadmap. Enterprise tools have sold person-level identification for years; we think that's the wrong side of the line, and we wrote it down so we can't quietly cross it.

Why warm outbound beats cold spray

Cold outreach is a numbers game that poisons the well — thousand-email blasts, 0.5% reply rates, everyone's inbox worse off. This is the opposite shape: the only companies Jack contacts are ones that already came to us. The volume is tiny by design. The relevance is built in, because the email cites the page they read. One good reply from twenty drafts beats three angry ones from three thousand.

The honest caveats

Reverse-IP resolution is not magic. Consumer traffic on residential connections mostly doesn't resolve, VPNs don't resolve, and mobile rarely does. What does resolve, reliably, is B2B traffic: office networks and corporate VPN egress points. Our own resolve rate hovers in the range you'd expect — a minority of visits, but the right minority. If your customers are consumers, this feature isn't for you. If they're businesses, the companies you most want to talk to are exactly the ones that resolve.

Watch it work on us

This isn't a landing-page claim; it's running right now, on this page. If you're reading this from an office network, your company may show up in our dashboard ranked by interest — and if it's a fit, the email you get from Jack will mention this post, because that's the whole point.

Want the same loop on your site? It's one script tag and an IPinfo token. Hire Jack — free → or read how verification keeps agents honest.