Know which companies are on your site.
LUPO sees the companies showing intent on your site, resolves the leads who engage, and then does the entire inbound SDR job. Identity is where it starts, not where it stops.
Identify the organisations showing intent.
LUPO identifies the companies visiting your site, with the evidence behind each match attached. This runs across your traffic. No match-rate theatre and no numbers we have not measured ourselves: just the organisations showing real interest, surfaced to whoever owns inbound, so a buyer on your pricing page does not stay anonymous until they happen to fill in a form.
Person-level, where it is appropriate, by design.
On US traffic, and only on US traffic, LUPO can resolve a business contact at the identifying company. This is a deliberate choice, not a limitation we are hiding. LUPO does not perform person-level identification on UK or EU traffic. Company-level identification runs everywhere; person-level is fenced to where it belongs. The boundary is the point, and we hold it.
The Gmail sign-up other tools give up on.
A buyer fills in your demo form with jane@gmail.com at 9pm. Domain-based enrichment returns nothing, because there is no company domain to match. LUPO resolves it the way a sharp SDR would: by enriching the signal they already gave, and, when needed, simply asking in the conversation who they work with.
We resolve the people who came to you. No cold identification of strangers, ever.
Identity is the first step, not the job.
This is the part a visitor-identification tool leaves to you. The moment a company is identified or a lead engages, LUPO qualifies them in a real conversation across web form, email, chat, and phone, filters out the noise so only real buyers go through, scores fit and intent, routes to the right rep, books the meeting, and writes every decision back to your CRM with a decision log on the record.
That is the difference between knowing who is on your site and turning it into a booked meeting. See the full pathway in how it works, or how it compares in LUPO vs Warmly.
Where the line is.
- Company-level identification runs across your traffic.
- Person-level identification is US-only, by design. Not on UK or EU traffic.
- LUPO is transparently AI. It never poses as a human.
- Every identification carries its source, on the record.
- A DPA is available. See the privacy policy and the DPA.
Common questions
Is LUPO a visitor-identification tool?
No. LUPO is an AI inbound SDR. Visitor identification is the front of the job, not the product. Once a company is identified or a lead engages, LUPO qualifies, scores, routes, books, and writes every decision back to the CRM.
Do you identify every visitor?
We do not make match-rate claims we have not measured. Company-level identification runs across your traffic. Person-level identification is limited to US traffic only, by design. LUPO does not perform person-level identification on UK or EU traffic.
How do you resolve a freemail sign-up?
By enriching the signal they gave and, when needed, asking in the conversation who they work with. LUPO resolves the people who came to you. It does no cold identification of strangers.
Is website visitor identification compliant?
LUPO identifies organisations at the company level, and limits person-level identification to US traffic, by design. It does not identify individuals on UK or EU traffic. A DPA is available, and every identification carries its source. See the privacy policy and DPA.
Does it work with HubSpot?
Yes. LUPO is HubSpot-native: identification, qualification, scoring, routing, booking, and the decision log are written to the HubSpot record. It also works with Salesforce or any CRM reachable by webhook.
See who is on your site, then watch LUPO book them.
A 20-minute call with the founder. Bring a real lead from last week and watch LUPO identify, qualify, and book it.