One balance, however many of you there are
A Cuvy plan comes with seats — 1 on Free and Starter, 2on Growth, 3 on Pro, 5 on Scale. Credits are not divided between them. The whole workspace spends from one balance, so a person found by one seat costs the rest of the team nothing. Billing, invitations and API keys sit with the Owner and Admins.
- Seats
- 1 to 5 by plan
- Credit pool
- One per workspace
- Owner accounts
- Exactly one, handed over not deleted
- Roles
- Owner, Admin, Member, Viewer
50 addresses free every month · no card
A pool, not an allowance each
It sounds like a small distinction until the 20th of the month, when one rep has run out and another has thousands spare.
| Row | Cuvy | A per-seat allowance |
|---|---|---|
| Where the credits sit | One workspace balance | Divided between seats |
| A rep who runs dry mid-month | Draws what the team has not used | Waits, or an admin moves some across |
| Two people look up the same person | One credit, once | Usually once each |
| Somebody away for a month | Their share is not idle | Their allowance goes unused |
| Adding a person inside the seat count | No change to the allowance | Another seat fee, another allowance |
| Seeing who spent what | Per member on the team screen | Per seat, by construction |
What each plan carries
A seat is a login. What it unlocks is the workspace, not a share of the month.
- Free and Starter
- One person, one login. Enough for somebody running their own lists; when a second person needs to see them, the next plan up is cheaper than a second account with its own invoice.
- Growth
- Two seats on one balance. A founder and whoever is doing the sending — the shape most teams are in the week they stop keeping this in a spreadsheet.
- Pro
- Three seats, and the plan where the API and job-change monitoring arrive. It tends to be the plan a team lands on rather than a person.
- Scale
- Five seats, still one pool. More than that is a conversation rather than a checkbox: write to sales@cuvy.io with how many people and what they are doing.
Four of them, and two rules against locking yourself out
| Role | What it can do |
|---|---|
| Owner | Everything, including handing ownership to somebody else. A workspace always keeps at least one. |
| Admin | Billing, invitations, API keys, the CRM connection and the workspace's data settings. What an Admin cannot do is make somebody an Owner, or remove or demote the one you have. |
| Member | Runs searches, reveals people, builds lists and exports them. Spends from the same balance as everybody else. |
| Viewer | Reads. For the person who needs to see the lists without being the person who spends the balance. |
Two rules sit underneath those. Nobody can change or remove their own account, and the last Owner cannot stop being one — between them, that is what keeps a workspace from ending up with nobody able to administer it. Ownership is handed over rather than taken: an Admin runs everything else, but the two moves that would let them take the workspace — making an Owner and unmaking one — are an Owner's alone.
An invitation carries the role with it and expires if it is not used. Taking somebody off the workspace returns the seat straight away, so replacing a person never means changing plan for a week. The person who reconciles the invoice these roles spend against is usually in RevOps.
Lists belong to the workspace, not to whoever built them
There is no private list. Everyone with a seat sees the same lists, the same people and the same balance, which is less a feature than a consequence of the credit rule: if a person costs one credit for the workspace, that person has to be visible to the workspace. It also means the research does not walk out of the door when a rep does.
The case where you do want separation is an agency, or an in-house team working several brands. The answer there is a list per client inside one workspace rather than a workspace per client — one balance covers all of them, and a person found for one client is not charged for again when the next one wants them. How agencies run it goes through that in full.
What a team asks before adding everybody
How many people can I add on each plan?
Free and Starter carry 1 seat each, Growth 2, Pro 3 and Scale 5. The seat count limits how many people can sign in, not how much work they can do between them — every seat draws on the same monthly allowance.
Who can change billing, invite people or create an API key?
Owners and Admins. Members run searches and export; Viewers read. Only an Owner can make another Owner, so an Admin cannot promote themselves, and nobody can change or remove their own account — those two rules are what stops a workspace being locked out of itself.
Should a second team have their own workspace or join ours?
Join yours, unless there is a reason they must not see each other’s lists. Two workspaces mean two balances, two invoices and two chances to pay for the same person twice, because the one-credit-per-person rule is scoped to a workspace. Inside one workspace, a list per team does the separating without splitting the money.
What can a Viewer do?
Open lists and read the rows. A Viewer is the read-only role, for the manager who wants the file rather than the balance — running a search, buying a pack, inviting somebody and creating an API key all sit with the roles above it.
Does a Viewer seat count against the plan?
Yes. A seat is a login whatever role is attached to it, so four Members and one Viewer is five seats. If somebody only ever needs the finished file, export it to them rather than spending a seat on them.
Can an Admin remove the Owner?
No. Making an Owner and unmaking one are an Owner’s moves alone, and nobody can change or remove their own account — between them, those two refusals are what stops a workspace being locked out of its own billing.
50 addresses free every month · no card