About
Why PageFox exists
The problem I kept hitting
I am a product manager. For years I sat in the same meeting: traffic was up, signups were flat, and someone would pull the analytics. The analytics would say a number moved — sessions, bounce rate, a conversion rate quoted to two decimal places. Nobody in the room could say which company had spent eleven minutes on the pricing page last Thursday, what they were trying to work out, or who to write to while they still cared.
The tools that claimed to answer that were priced for a sales floor, took a quarter to roll out, and kept the honest caveats in a footnote. I wanted the small version: something you install in an afternoon that tells you which companies are actually reading your pricing page, and tells you plainly when it does not know. Nobody was selling that, so I built it.
What it does
PageFox is one script tag doing three things, and it is worth being precise about which three.
- It works out which company a visit is likely coming from, when there is enough to go on.
- It answers the visitor’s question from your own website’s content, cites the pages it used, and says plainly that it is an AI.
- When someone shows a real buying signal, it routes a lead to your email or Slack as it happens, instead of into a report you read on Monday.
Where it stops
The limits belong before you install, not after, so here they are.
PageFox identifies companies, not visitors: it can tell you that an organisation visited your site, it tells you who a visitor is only when that person gives you their details in a chat or a form, and no setting or paid tier reveals the identity of a visitor who has not.
It also does not resolve every visit. A meaningful share of traffic cannot be attributed to any company at all, and on those visits PageFox says so rather than filling the gap with a guess. Anything that promises to identify every visitor is either wrong or counting something else.
Who builds it
One person. Not “we” standing in for a group, and not a brand with an org chart behind it — one person designs PageFox, writes it, answers the support email, and signs your contract.
That cuts both ways, and you should know both halves. What you get: the person who reads your support email is the person who can fix the bug that afternoon. No tier-one script, no handoff, no ticket ageing while it moves between departments. What you do not get: an around-the-clock support rota, a named account manager, or the procurement surface a very large enterprise will ask for. If those are requirements for you, PageFox is the wrong choice, and it is cheaper for both of us to find that out today.
Things you can check instead of taking my word for it
Every link below is a page on this site you can open right now. There is nothing here you have to believe.
- Pricing — the plan limits on one page, generated from the same registry the product enforces rather than typed in by hand, so the page cannot advertise a number the code does not honour.
- Developer documentation — the REST contract, the webhook signature recipe, and the public site-answers endpoint. Each page is written against the code that serves it and states plainly what does not exist yet.
- Privacy policy and the opt-out and deletion form — what is collected, how long it is kept, and a request form that is honoured automatically rather than landing in somebody’s inbox. The Global Privacy Control browser signal is honoured without filling anything in.
- Terms of service — who you are contracting with, under which law, and where a dispute would be heard.
- The blog — including a piece on where visitor identification is useful and where it fails, written because the honest version is more useful than the sales version.
- Changelog and status — both reserved and currently empty. They start carrying real entries with the Phase 1 release. An empty page is the honest version of a product this young; a backfilled release history would not be.
Talking to a human
Write on the contact page and pick the topic — sales, support, privacy or legal — so it reaches the right place. One person reads every message. Expect a reply within one working day (Monday to Friday, India Standard Time).