Shipped

Consultants can now run RFPs alongside their clients

Buyers can invite a consultant by email at organisation, project or RFP level. Consultants work inside the client's account at exactly that scope, and access can be revoked at any time.

19 September 20261 min read

Procurement for infrastructure of this kind is often run by someone outside the buying company — an independent consultant, a fractional payments lead, an advisory firm. Until now they had to work through a client's own login, which is neither auditable nor safe.

Consultants are now a first-class role.

What shipped

  • Invitations by email at three scopes. A buyer can grant a consultant access to their whole organisation, to a single project, or to a single RFP. One invitation can carry several targets, and the consultant accepts once.
  • A consultant workspace. Consultants see only the clients and RFPs their grants cover, and work in the same RFP, response and messaging screens the buyer uses.
  • Projects as an organising layer. RFPs can be grouped into projects, which is also the unit a consultant is most often given access to.
  • Revocation at any time. Removing a grant removes the access immediately. Invitations expire on their own if they are not accepted.

What stayed the same

A consultant-created RFP belongs to the client, not to the consultant — ownership is the client's throughout, and a consultant losing access never takes an RFP with them. Providers see nothing about who runs a buyer's procurement.

Access is managed in Settings › Consultants.

Try it

Everything above is live in the product today. Publishing an RFP is free for buyers.

Related reading