Projects & collaboration

One initiative, with access kept in scope.

Projects group related RFPs and in-progress AI conversations. They also give buyers a precise way to bring an external consultant into the work.

How it works

What a project holds

Related RFPs

Keep multiple category briefs under one initiative, such as account infrastructure, card issuing and identity verification for one launch.

AI conversations

Resume in-progress scoping conversations from the project before they become editable RFP drafts.

Response progress

See each RFP's status and the number of submitted provider responses without losing the wider initiative context.

How it works

The buyer remains the owner

A consultant can work on a client's project or RFP, but the client owns the record. Provider access and matching still follow the RFP's buyer and category rules.

Decision helper

Which access should I give?

Several initiatives over time?

Choose Organisation access.

One defined initiative?

Choose Project access.

One selection or category review?

Choose Single RFP access.

How it works

Choose the invitation scope

ScopeWhat it coversTypical use
OrganisationThe client's current and future projects and RFPsA retained advisor supporting the broader sourcing programme
ProjectOne named initiative and the RFPs and conversations inside itAn advisor working on a defined programme
RFPOne individual RFP and its permitted buyer-side workflowA specialist reviewing one category or selection

How it works

How consultant access starts

01

Choose the consultant

The buyer enters the advisor's email address.

02

Choose access first

Organisation, project and individual-RFP targets are selected before the invitation is sent.

03

Review and send

The invitation summarises every included target and expires if it is not accepted in time.

04

Accept in the consultant workspace

The consultant sees the inviting company and covered targets, then chooses whether to accept or decline.

How it works

What an authorised consultant can do

Work on covered RFPs

Open and edit the same client-owned RFP view, including files, links and review feedback.

Continue covered drafts

Use the shared AI builder for a client's eligible conversation and finalise it into a client-owned RFP.

Review submitted responses

Read provider answers, coverage, evidence and contact details only where accepted access applies.

Follow messages and activity

Use the buyer side of permitted RFP conversations and receive consultant-scoped notifications.

How it works

Boundaries that remain in place

No unrelated client data

Project and RFP access does not expand to the rest of the client's organisation.

No ownership transfer

The consultant does not become the owner of projects, RFPs, drafts or responses.

No provider membership

Providers never join projects and do not see which consultant is supporting the buyer.

Revocable access

The buyer can remove a consultant's access while retaining the complete sourcing record.

Examples

Collaboration in practice

Fintech card launch

A fintech adds its payments advisor to one project covering its card launch.

Bank modernisation

A bank gives a sourcing consultancy organisation access across a longer programme.

Specialist review

A licensing specialist reviews one RFP before it is submitted.

How it works

Access that starts with the client

Today, the client invites consultants. Consultant access requests and internal colleague invitations are not currently available.

Useful details

Frequently asked questions

Can a consultant see all our work?
Only when you deliberately provide organisation-wide access. A project or RFP invitation stays limited to the named scope.
Can a consultant create something for us?
Yes, where organisation or project access allows it. The project or RFP is still created for and owned by your organisation.
Can we revoke access?
Yes. Removing access closes that scope for the consultant without deleting the client's underlying work.
Does the provider see our consultant?
No. The provider sees the buyer side of the RFP only after the normal acceptance rules are met.

Build the selection around one client-owned record