For agencies and consultancies

Agencies and consultancies

/industries/agencies-and-consultancies

Multi-org workflows

ship with V2.

An agency or consultancy running searches for multiple client orgs needs to keep candidate data segregated by client while letting agency-side managers see across roles. V2 multi-org workflows cover that pattern. V1 is single-org; pilot it for one client today.

Request early access →See the V1 mid-market alternative →

Ships with V2 multi-org workflows·Per-client consent and data residency·Agency-side billing structure

What is in scope

What ships with this.

Multi-org data model.

Each client org is a separate Picked workspace with its own roles, candidates, audit trail. The agency-side org sits above, with named partner-staff who can see across client orgs by configuration.

Per-client consent flow.

Candidates apply to a specific client; their consent applies to that client. Agency-side visibility requires the candidate to be informed and to consent separately. Audit-trail logged.

Per-client data residency.

Client orgs with EU-only or UK-only requirements get their workspace in the appropriate region. The agency-side view honours per-workspace residency without surfacing data outside its origin region.

Agency-side billing structure.

Single agency invoice covering multiple client workspaces, with per-workspace usage broken out. Annual contract terms; volume commit across the agency portfolio.

Cross-client analytics.

Agency-side dashboards that aggregate across client orgs while honouring per-workspace consent. What roles are slowest to shortlist, which candidates are repeat-applicants across clients (where consent allows surfacing), where the bottleneck sits.

White-label option.

Agency can present the candidate-side experience under its own brand for client-facing roles. Candidate notice surfaces both the agency and the underlying client.

Custom rubric per client.

Each client workspace has its own rubric calibration. Agencies running searches for different segments do not have to retune from scratch each time.

Why we are not shipping this yet

Candid about the constraint.

The constraint

The multi-org data model is the harder engineering problem of the V2 cycle. Per-workspace data residency, cross-workspace agency-side visibility, per-client consent flows, and the billing structure all interact; getting any one wrong creates compliance exposure for the agency and the underlying client. We are designing it carefully because the multi-tenant security model has to be right, not fast.

What would have to be true

V2 multi-org workflows ship when the multi-tenant security model is signed off by our compliance lead, when the V1 single-org surface has surfaced any edge cases we need to design against, and when the agency-side billing structure is built to support per-workspace breakdown. V2 in mid-2027 is the target.

The V1 alternative

What you can do today.

V1 supports an agency or consultancy running a Picked workspace for a single client. The workflow is full-feature: the agency-side hiring manager runs the role, reads the finalist cards, makes the decision, hands the hire to the client. The client receives the finished outcome rather than the in-flight pipeline.

Agencies running multiple clients at V1 can run multiple V1 workspaces (one per client) without the cross-org visibility, and aggregate offline. This is operationally workable for an agency with 3 to 5 active client searches; agencies with 10-plus concurrent searches will want to wait for V2.

See the V1 mid-market solution.

How a single-client search runs on Picked today. Manager-led, manager-decided; the agency hands the finished outcome to the client.

Read the V1 alternative →

Register interest in V2 multi-org workflows.

One client today. Many clients with V2.

Pilot V1 for one client.

Talk to us about V2 when it lands.

Post a role for free →See the V1 alternative