One workspace per client, one loop each.
Each client gets its own customer profile, sources and pipeline. You switch between them without a second login.
Every client is a different market
Running five clients out of one tool means five sets of filters you keep re-remembering, and a constant low risk of showing somebody another client's list. Running five accounts means five logins.
How Huntloop fits
Separated at the database, not in the interface
Each workspace is a tenant. The isolation is a row-level policy in Postgres rather than a filter in application code, so one client's data cannot reach another's even if we ship a bug.
Setup asks whose company it is
Tell Huntloop you are an agency and the research step asks whether this workspace is for a client or for you — because a profile drafted from your own site would hunt for companies that want an agency, which is not the job.
Costs attributed per client
Provider credits and model spend are recorded against the workspace that used them, so a client's usage is answerable rather than estimated.
A profile that works for this
Huntloop drafts yours from your website and shows which sentence each line came from. This is the shape it aims for.
- One workspace
- Per client, created from their domain
- Segments
- Their market, drafted from their site
- Sources
- Their trade press, not yours
- Voice
- Set per workspace, so drafts sound like the client
Where Huntloop is the wrong tool
There is no consolidated invoice. The workspace switcher shows what each client used this month — opportunities, AI runs, enrichments — so you can bill it on, but Huntloop will not produce one bill across ten clients. If that is what you need, tell us and it moves up the list.
See what it finds for you
Put in your domain. Two minutes, no card.