Skip to content
Web app

Where a run lands when it finishes

Where do Cuvy's lists and credits live?

app.cuvy.io is where a finished run lands. Every list you have run sits there with its rows, their sources and the date each address was seen, and you can filter, tag and export any part of it. The credit balance stays in the header on every screen, and any run that would spend credits prices itself first.

Address
app.cuvy.io
Credit balance
In the header, every screen
Before a run
Cost shown first
Also here
Exports, seats, billing

50 addresses free every month · no card

Lists

Every row shows its working

A list you cannot interrogate is a CSV with extra steps.

A run becomes a list, and each row is a person. Beside the address sits the thing most tools drop on the way out: whether two independent sources agreed on it or one sighting found it, what that sighting was, and when. The last column is whether the row cost you a credit.

That is what makes a list arguable six weeks later. When somebody asks where an address came from, or why an invoice is the size it is, the answer is on the row rather than in a support ticket.

A row carriesNameCompanyTitleAddressConfirmed or single-sourceWhere it was seenDate seenCredit charged
The meter

The balance does not live in a settings page

It is in the header wherever you are, and it moves in front of you.

One number, on every screen
The credits left in the workspace follow you into a list, into an export and into billing. You never have to go and look for them, which is the point — a balance you have to hunt for is a balance you find out about afterwards.
It says where the credits came from
This month’s allowance, what carried over from last month and anything bought as a pack are counted separately, because they behave differently: plan credits carry to twice your allowance, packs never expire at all.
Nothing moves before you have seen the number
A search, a CSV, a scheduled sweep, a single lookup — each one shows how many people it would charge for and how many it already owns, then waits for you.
A person you have paid for stays paid for
They are marked across the whole workspace. Another list, another seat, another month: the row still appears and the meter does not move.
What you do to a list

Four things, and three of them are subtraction

Filter

Confirmed only, one company, one seniority, or just the rows this run charged for. What is filtered is what exports, so a file never needs cleaning after it has left.

Tag

Tags belong to the workspace, not to the run, so a client, a campaign or a shortlist outlives the search it came out of and can be exported across several of them.

Export

CSV, HubSpot or the API. From Growth upward, rows that already exist in the CRM you are pushing to are left behind.

Export history

On Pro and above, every export is kept with what was in it — so what left the workspace, and when, is a question with an answer rather than a reconstruction.

Division of labour

Which half of the product does which job

The browser holds the part that has to be in a browser. The rest is here.

Which jobs happen in the web app and which in the extension
RowIn the web appIn the extension
Starting a runA CSV, a saved search or one personThe search page you already opened
Seeing the cost firstOn the review screen, before you confirmOn the panel, before you press start
Filtering and tagging rowsYesNo — the panel shows progress and stops there
Getting a list outCSV, HubSpot, APINo
The credit balanceIn the header, broken downIn the panel, as one number
Plans, invoices and seatsYesNo
One account and one balance behind both, so this is a division of labour rather than a comparison. A run started in the browser is visible here while it is still going.
Starting here

You can use all of this with nothing installed

The extension is not on the Chrome Web Store yet, and the web app does not wait for it. Sign in, drop in a CSV of names and companies, and the same lookups run against the same balance with the same price shown first. Anything a run produces exports the same way.

It is also the honest way to try the thing on your own data before putting anything into the browser you use LinkedIn with.

50 addresses free every month · no card

Questions

What people ask about the app itself

Do I need the extension to use the web app?

No. Sign in at app.cuvy.io, upload a CSV of names and companies or look a single person up, and you never touch the browser extension. The extension is only the way to start a run from a search page you are looking at.

Where does it tell me what a run will cost?

On the review screen, before you confirm. It shows how many people are in the run, how many of them this workspace has already paid for and will not be charged for again, and the most it could therefore spend. That number is a ceiling — misses come off it.

Can I search across every list at once?

Yes. People are searchable across the whole workspace rather than list by list, so somebody you have already paid for shows their address wherever they turn up — in another list, in a later run, or in a single lookup — without the balance moving.

What does the app show while a run is still going?

The list fills as it goes. Rows arrive as addresses come back, and the header counts how many people are done and what has been spent so far. You can leave the screen, or start something else, without pausing anything.

Where do I change plan, download an invoice or cancel?

All three are in Billing, in the web app. Plan changes, top-up packs and every past invoice sit on one screen, and cancelling is a button there rather than an email to support. Every price is monthly; there is no annual term to be released from.

Is the web app the same account as the extension?

One account, one balance, one set of lists. Sign in to the extension with the same email and the two are looking at the same workspace — a run started in the browser appears here while it is still going.