Features
Part of Discovery platforms: a clear guide with practical examples
Best discovery platforms agencies 2027: practical details
Buying discovery platforms for an agency: keeping rival clients apart, paying for seats used in bursts, and keeping the shortlist record on your own side.
An agency's search problem is not the same problem a brand has. A brand searches for itself. An agency searches on behalf of several clients, sometimes rival ones, in bursts that cluster around pitches, using a subscription that bills every month whether anyone opens it. Those three facts decide which product suits an agency, and almost none of the marketing addresses them.
What to take away
- The hardest requirement is separation between clients, and it is a workflow problem before it is a permissions problem.
- Discovery seats have the worst usage pattern in an agency stack: heavy in pitch weeks, untouched for months.
- Whatever you buy, the list and the reasons behind it have to end up somewhere you own.
One index, two rival clients
This is the requirement nobody demos. If you pitch two brands in the same category, the same searches serve both, the same shortlist is a good answer for both, and a single careless share turns one client's target list into another's briefing document.
Four failure points are worth checking in a trial, with two real accounts rather than a sandbox.
- Saved lists and their visibility. Can a list be scoped to one client and hidden from everyone not on that account?
- Shared history. Does a recently viewed panel, a team activity feed, or a suggestion built on team behavior expose what another account has been looking at?
- Exports. When a list leaves the tool, does anything mark which client it belongs to?
- Notes on a creator profile. Are they per client, or does one global note attached to a creator carry a comment written for a rival brand?
That last one causes real damage, and it may also breach a non-disclosure agreement you signed without thinking about search tooling. A note reading that this creator was rejected for a competitor last month is exactly the kind of thing that should never be visible on a shared profile, and plenty of products store notes at the creator level because it was the simpler design.
Permissions solve part of this. Habit solves the rest, and habit needs a rule: one client per list, one client per export, and no global notes.
Seat economics when usage is spiky
Agency demand for search is not steady. It spikes for pitches and new briefs, then falls to nothing for weeks. A monthly seat priced for continuous use is being paid for during months when nobody logs in.
Three patterns respond to that, and the right one depends on how often you pitch.
| Pattern | Suits | Watch out for |
|---|---|---|
| One shared seat, booked like a meeting room | Occasional briefs, small teams | Contractual limits on shared logins, and the audit trail becoming useless |
| A named seat for one researcher | A steady flow of briefs and a person who owns sourcing | The researcher becoming a queue, and everyone waiting |
| No seat, buying sourcing as a service per brief | Rare briefs, or unfamiliar markets | Losing the record, unless you insist on receiving the working list |
Whichever you pick, price the full year including the quiet months before comparing anything, and note that shared credentials often breach the terms you are signing. Where the estate supports it, routing access through single sign-on makes the quarterly review of who still has a seat possible at all. Ask rather than assume, because the answer is sometimes a cheaper multi-user plan.
What has to end up on your side
A discovery subscription is a rented index. What you build inside it is not the index, and it is the part with lasting value: the shortlist reasons, the rejection log with dates, the contact routes that actually worked, the conflicts you discovered the hard way.
Get all of it out on a schedule, in a format you can open elsewhere, and keep it in your own systems. A list that lives only inside a rented index leaves when the subscription does, which is the same seam described in the guide to campaign workflow tools. The wider point about where a search seat sits in an agency's buying order, behind money and rights, is made in the guide to what to buy first.
Judging the index itself
The vendor comparison here is mostly about coverage, and coverage claims are not comparable across products because each one counts differently. Two checks are worth more than any headline number.
Search a category you know deeply and read the results for who is missing. Absent names tell you about the index; present names only tell you about the ranking. Then run the same search on a second product and look at the overlap: if two candidate tools return substantially the same people, you are choosing between interfaces, not indexes.
Where the two disagree, do not assume the larger result set is better. Ask where each index gets its records, since the answer decides what it can never see, and that structure is explained in the guide to how discovery data is built. Keeping the comparison honest, and writing the decision so it can be reversed later, follows the method in the guide to comparing suppliers.
When the answer is not a subscription
Two situations make a seat the wrong purchase. If your clients' partners are mostly represented, shortlists will arrive from agencies anyway and you are paying to duplicate work. If you enter a new market once a year, buying local sourcing per brief is cheaper and better, because you are buying knowledge rather than an index.
The reverse also holds. Agencies that pitch constantly, in categories they do not know, get real value from an index, because speed to a credible shortlist is part of what wins the pitch. What the agency is actually selling in that moment, and how the fee model shapes what it recommends, is separated in the guide to agency business models. Where a shortlist runs through representation instead, the counterparty and the clock both change, as described in the guide to talent representation.
Common questions
Can we bill a client for a share of the seat?
Sometimes, and it has to be in the contract before you try. A tooling line that appears on an invoice unannounced reads as a margin grab even when it is not.
Should each client have their own workspace?
If the product supports it without extra cost, yes. It solves the note and history problems structurally rather than through discipline, and discipline fails during a busy pitch week.
How do we handle a creator who is right for two of our clients?
Decide internally which brief they hear about first, and never present the same shortlist twice in the same category. The problem is real, it is a conflict question rather than a tooling question, and it should be settled by a person.
Is a trial long enough to test any of this?
Only if you set it up to fail. Two real accounts, one real brief each, one export each, and one deliberate attempt to see something you should not be able to see.