A spike is not always a buyer.
In CPaaS and API businesses, sudden volume can mean production adoption. It can also mean abuse. LUPO starts by separating suspicious usage from real customer momentum.
For usage-based and API-first companies
Your best customers never fill in a form.
They sign up with Gmail, grab an API key, and scale to production. Sales never sees a name.
LUPO watches the usage, gates fraud, qualifies the buyer, and writes the account to your CRM.
Signals: product usage, billing events, website, chat, form, email, phone.
Actions: gate fraud, score momentum, qualify, route, book, write to CRM.
The usage-based blind spot
Your highest-intent account never touches the route your GTM stack watches.
Most inbound systems start at the website. That works when the buyer behaves like a website visitor.
Usage-based buyers often behave like developers. They sign up, test, top up, register, integrate, and scale before a form-fill ever happens.
The account matters before it is named. A website-only tool stops watching the moment it signs up. LUPO doesn't.
One funnel, end to end
Website tools stop at the website. The funnel doesn't.
A website visitor tool sees the account while it is on your site. So does LUPO. It keeps watching after the account signs up and starts consuming.
The account you care about is already inside the product. The next meaningful signal is not another pageview. It is consumption.
Gmail can be valuable
A freemail signup is worth more than a clean corporate form-fill when the usage says production is coming.
Spikes need judgement
A volume spike can be a whale or fraud. You have to know which before sales touches it.
Conversation creates identity
Enrichment resolves some accounts. For the rest, the useful conversation at the right moment gets the name.
Coming from Warmly? See exactly where LUPO goes further: LUPO vs Warmly.
The pipeline
First decide whether the usage is real. Then decide whether sales should act.
The order matters. Score value before abuse and reps chase fraud. Require identity before behaviour and you miss anonymous accounts that matter.
The account can be important before you know its company name.
Usage velocity, acceleration, production-to-test ratio, top-up cadence, integration depth, trust acts, and drop-off risk should be scored before identity decides whether the account is worth attention.
Enrichment helps where the buyer left a trail.
Some freemail users can be resolved through enrichment, developer footprints, CRM history, support history, billing metadata, or deterministic links from visitor to signup to billing account.
The conversation is the identity layer no data broker can rent.
When an account is important but unnamed, LUPO opens a contextual conversation instead of sending a generic sequence. The prompt is anchored in the moment and useful to the developer.
Give the rep the story, not a mystery score.
LUPO writes the evidence string, transcript, source signals, and next action into the CRM so a rep knows exactly why to act.
"Freemail signup. Usage up 340 percent week over week. Second accelerating week. Two top-ups from 500 to 2,000. Production traffic now above test traffic. Registered sender yesterday. Fraud-clear. In conversation, said they are integrating alerts for Acme Logistics. Likely scaling production buyer."
Same SDR, different trigger
The usage layer does not replace the inbound SDR. It tells the SDR when to open the door.
LUPO already runs the inbound job across chat, form, email, and phone: qualify, filter, route, book, and write back to the CRM.
For sales-led teams, the trigger is a hand-raise. Someone fills a form, starts a chat, sends an email, or calls.
For usage-based teams, the trigger can be behaviour. A self-serve account starts scaling, stalls, errors, tops up, registers, integrates, or crosses the line from test to production.
Same front door. Same qualification brain. Same CRM writeback. A different moment that tells the agent when to act.
From invisible account to qualified opportunity
Reps get surfaced accounts with the evidence attached.
Scaling now
Usage velocity and acceleration show which accounts are moving from experiment to production.
Fraud-clear
Suspicious usage is filtered before sales sees it, so reps do not chase abuse.
Identity pending is allowed
Missing company identity changes the action. It does not erase the signal.
Contextual conversation
LUPO uses the usage moment to ask useful questions and get the buyer to self-identify.
CRM-ready verdict
The rep gets a short evidence string, source links, transcript, and recommended next step.
Not another dashboard
Usage scoring is the trigger. The product is the action layer that qualifies, asks, routes, and writes back.
Built for first-party signals
You own the signal. LUPO reads only what it needs.
LUPO reads narrow first-party signals from systems you already trust: billing events, CDP events, warehouse views, CRM fields, support context, or purpose-built webhooks.
The output is not a data warehouse. It is an operational verdict written where your team already works.
No raw logs by default
Prefer billing, CDP, warehouse views, or narrow webhooks.
Source-visible
Every signal should carry its source on the account record.
Deterministic first
Exact joins beat speculative identity every time.
Human approval
Proactive outreach stays under your control.
What ships
The full loop: signal, conversation, CRM.
LUPO captures inbound across chat, forms, email, and phone. For usage-based teams, it also reads product and billing signals, gates fraud, scores usage momentum, qualifies the buyer, and writes the evidence to your CRM.
LUPO does the website visitor identification and the usage layer that turns anonymous product momentum into qualified pipeline. The whole funnel, one layer. Book a demo.
Best fit
Built for companies where revenue follows usage.
Good fit
- API-first companies where developers can sign up and scale without sales.
- CPaaS, messaging, voice, email, payments, infrastructure, dev tools, data, security, or AI platforms.
- Teams with meaningful freemail signup volume.
- Teams where usage can signal expansion, fraud, churn, or sales readiness.
Not the fit
- Purely sales-led businesses with no self-serve or product-usage stream.
- Teams that want a raw visitor list with no qualification, conversation, or CRM writeback.
- Teams that cannot expose even narrow first-party usage or billing events.
- Teams that want anonymous usage scoring but no conversational follow-up.
Common questions
Straight answers.
What does LUPO do for usage-based companies?
It watches product and billing signals, gates fraud, scores usage momentum, qualifies the buyer in conversation, and writes the verdict to the CRM.
Are you replacing Warmly?
Yes, and then some. LUPO does the website visitor identification and engagement Warmly does. Then it keeps going where Warmly stops: into the product and billing stream after signup, where your best accounts scale invisibly. Same funnel, one layer, from first touch to booked meeting.
Do you need person-level deanonymization?
No. Behaviour makes an account important before identity is known. The flow is behaviour first, identity second, conversation when the database is blind.
What systems would this connect to?
LUPO can read from the systems that already know usage and revenue: Stripe, Metronome, Orb, Segment, RudderStack, warehouse views, CRM fields, support systems, or custom webhooks.
Is this a PLG dashboard?
No. Dashboards show signals and wait for humans to act. LUPO's product bias is action: qualify, ask, route, book, and write the verdict into the CRM. Usage scoring is the trigger, not the product.
Usage-based pipeline
Find the accounts your website never saw.
Bring a real usage pattern, fraud rule, or freemail signup problem. See how LUPO turns it into a qualified account story in your CRM.