Skip to content

Client Locator

Part of: ClientVerse Core (every client).

What it is

Client Locator turns "I need people who fit these criteria" into a concrete list. It searches across the firm's relationships, classifications, and locations at once — rather than making you scroll a single list view or run three reports and reconcile them by hand.

Use it when scoping outreach, building an event invitation list, finding coverage for a target, or working out who to see on a trip.

Who it's for

  • BD scoping targets and pursuits.
  • Attorneys answering "who do we know at this company / in this city?"
  • Marketing assembling audiences that later become lists.

How it works

Search on any combination of:

  • Classification — practice area, industry, region, or any firm taxonomy dimension.
  • Location — city, region, or country, sourced from address data. This is the location-based discovery path: "who do we know in Frankfurt?"
  • Relationship strength — (Core 1.1.6+) narrow to contacts the firm actually knows well, using the strength derived from Connections.

The relationship-strength filter is the one that changes how the tool is used. Without it, a broad search returns everyone who matches on paper — including hundreds of contacts nobody at the firm has spoken to in years. With it, the same search returns the subset worth acting on.

The same filter is available when picking trip targets, so a trip can be planned against real relationships rather than a raw geographic match. Both surfaces shipped together in 1.1.6; if they behave differently, that is a defect.

A search you will run again should be saved as a Saved_Search__c. A saved search can be re-run, shared with a colleague, used to drive a List, or (with Modules) feed a Dispatch digest.

This matters more than it sounds: the alternative is re-deriving the same audience by hand every quarter and getting a slightly different answer each time.

How to use it

  1. Open Client Locator.
  2. Set your criteria — classification, location, and relationship strength as needed.
  3. Review results and spot-check a couple against the underlying records.
  4. Save the search if you will want it again.
  5. Act on it — build a list, add trip targets, or start outreach through the warmest connection.

Results are scoped to you

Client Locator respects the sharing model. Two users running an identical search can legitimately see different results, because each sees only what they have access to. This is correct behaviour, not a bug — but it does mean "I can't find X and you can" is usually an access question rather than a search question.

  • Connections — the relationship signal behind strength filtering.
  • List Builder — turn results into a durable audience.
  • Trip planning — the same filtering, applied to trip targets.
  • QA coverage: REL-03, REL-04, REL-06, REL-09 in core-relationships.md.