Credentials & precedent search
Credentials and precedent search answers the question every pursuit opens with: have we done this before, and for whom. It searches the engagement archive, the deliverable library and the credentials material, then returns the closest matches with a link to the original work and a note of any restriction on naming the client. The consultant reads the source and decides what is fair to put in a pitch.
Step by step
Describe the pursuit in plain terms
The consultant states the sector, the problem and the kind of work being proposed. No search syntax and no knowledge of the archive is needed.
Search the engagement archive
The agent searches your document management system, Confluence, Notion and Drive under the permissions the consultant already holds.
Rank by closeness to brief
Matches are ordered by how closely the problem, the sector and the type of work line up, with the reason for each ranking shown.
Show what each engagement covered
For every match it summarises the scope, the deliverables produced and the team shape, so a manager can judge relevance without opening ten folders.
Mark the naming restrictions
Where an engagement letter restricts naming the client, the match carries that flag before anyone drafts it into a pitch.
Consultant opens the source
Each result links to the original deliverable so the consultant reads the real thing before reusing it. The agent writes nothing back and sends nothing out.
Exactly what this agent can see, touch and change
The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelPartners and managers assembling a pitch at short notice, and anyone new to the firm who does not yet know which engagements to ask about.
Escalation
When it asks a personThis agent changes nothing outside ollo, so it runs without an approval gate. Its output is still cited and reviewable.
Applications & Rights
Which tools it uses, and what it may do in each
SharePointRead only
ConfluenceRead only
NotionRead only
Google DriveRead onlyVerification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
Partners and managers assembling a pitch at short notice, and anyone new to the firm who does not yet know which engagements to ask about.
What you’ll need
- Engagement archive connected
- Access rules mapped to teams
- Client naming restrictions recorded
- Search scope agreed per practice
What you get
- A ranked shortlist of prior engagements
- A link to each original deliverable
- A note of client naming restrictions
What it doesn’t do
It finds and ranks; it clears nothing for external use. Whether a client may be named in a pitch is a decision for the partner and the engagement letter, and the agent only flags that a restriction exists.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
Can a consultant see a client file they are walled off from?
No. The agent searches with the consultant's own permissions, so a walled folder is invisible in the results rather than shown and blocked. If your firm keeps ethical walls in the document management system, they carry over exactly as they are.
How does it treat old engagements that are no longer representative?
Results carry the engagement date and the agent marks a match as dated when the work is old relative to the sector. It does not hide old work, because a decade-old engagement is often the closest precedent, but it will not present it as current.
Does it write anything to our systems?
No. This one only reads and answers on screen. Nothing is written back, nothing is sent, and there is no approval step because there is nothing to approve.
What does a new joiner get out of it?
Most of the value, honestly. Someone in their first month can find the firm's work on a topic without knowing which partner to ask, and every answer points at the original file so they learn the archive as they use it.