Use case

PR and communications

PR work is dense with jobs that are almost entirely retrieval — spokesperson matrices, media training preparation, coverage analysis, award entries — and unusually sensitive to confidentiality, because a great deal of it is embargoed. Multiply runs those jobs against the client’s own workspace, with no training on your data and each client’s material held separately.

Today

High volume, high sensitivity, low tolerance for leaks

A comms team assembles the same categories of document repeatedly — who speaks to what, what a journalist has written before, what the coverage adds up to, what an award entry has to prove. Most of that is assembly. But it is assembly over material that frequently cannot leave a jurisdiction or become public early, which is why ad-hoc assistant use so rarely survives a security review, and why security carries veto power over tool choice in this discipline specifically.

Multiply task with sources — answer grounded in client documents with the source open alongside

How it runs

The jobs comms teams hand over first

01

Spokesperson matrices and media prep

Built from the client’s own material plus the category picture — who should speak to which topic, what they have said before, and what a journalist covering it has previously written.

02

Coverage analysis with the sources attached

Analysis a client can check rather than take on trust, exported as PDF or DOCX with citation numbering intact.

03

Award entries against the evidence

Award writing is largely the retrieval of proof: what happened, what moved, what the client said at the time. When the project holds that material, the entry stops being an archaeology exercise.

04

Thought leadership as an agent, not a one-off

Teams build a thought-leadership agent tuned to a spokesperson’s voice and remit and reuse it. Because agents are centralised, an improvement one consultant makes reaches the whole team.

Where the confidentiality line sits

Embargoed and private material is the reason this discipline evaluates tools differently. Each client sits in its own workspace and context does not cross between them. Private sources — meeting recordings and personal mail among them — stay scoped to private work rather than flowing into a shared client context, and nothing you put in trains a model.

GDPR compliant, ISO 27001 in progress, and the full posture is on the security page. If your review process has a questionnaire, send it — that is a faster route than a demo.

Related: the product for how the pieces fit together, multi-client operations for running several of these at once, agency operations for the underlying idea, and the other use cases if PR work is not the job you want to start with.

FAQ

Common questions

Bring a live account, or your security questionnaire. Both are useful first steps.

Bring the account with the tightest confidentiality

If it works there it works everywhere else in the agency. Send the security questionnaire ahead of the call.