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.
And when someone did find a good company, getting from that name to a conversation took five tools and three people: one to find the right person, one to write, one to follow up. Someone who sells on their own does not have three people. I wanted one place where agents do that work, every day, and say plainly when they do not know. Nobody was selling that, so I built it.
AI agents that get you more qualified leads.
Find
Your agents find companies that fit, on your site and beyond it, and the right person with a verified email.
Reach
They answer every enquiry and write in your voice, and nothing goes out to new people unless you approve it.
Follow up and book
They follow up from your own mailbox and, soon, book the meeting on your calendar.
Where it stops. Before you install, not after.
Companies, not visitors
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.
Not every visit
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.
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.
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 policyOpt-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 knowing the company on your site helps and where it fails, written because the honest version is more useful than the sales version.
ChangelogStatus
The changelog is reserved and currently empty. It starts 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. The status page shows whether the app, the database and the daily jobs are running, checked at most once an hour.
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).