Know-how lives with whoever did it last
The way a matter type is handled is understood rather than written down, or written down somewhere nobody looks. New people learn it by interrupting someone senior.
For law firms with 10 to 50 people
Internal questions about process, precedent and know-how get answered by whoever has seen the file most recently. The firm already holds the answer; finding the current version of it is most of the work.
A grounded agent answers from the firm’s own internal material and cites it. It is scoped to internal questions, not to advice, and it refuses when the material does not settle the question.
Book a readiness assessmentThe way a matter type is handled is understood rather than written down, or written down somewhere nobody looks. New people learn it by interrupting someone senior.
A template gets amended for one matter and saved alongside the original. Later, nobody can tell which is current without opening both and comparing.
Questions about how something is done internally go to whoever is nearest, and the answer varies with who was asked.
We review the Microsoft 365 tenant, licensing, a representative set of internal know-how and process material, and the questions that get repeated. You get a written recommendation on where a grounded agent could help, what would block it, and what should stay with a person.
Fixed scope and fixed fee. The report can recommend not building anything yet.
One grounded agent in production over an agreed internal document set, citing what it answered from. The scope boundary is part of the acceptance checks: questions that stray towards advice, or towards a specific matter, should be refused rather than attempted.
The build scope and delivery window are agreed after the assessment.
Confidentiality is the governing constraint here, so extensions start with who may reach the agent and which material it may draw on. Environment strategy, DLP and access boundaries are documented alongside the build.
Each extension is scoped after the assessment, with its delivery window agreed before work starts.
Staff get cited answers from your policy library instead of asking HR the same questions again.
Requests are captured in Teams, logged in Dataverse and routed for approval without email chains.
Incoming documents are classified and routed, with uncertain cases sent to a person to review.
No, and the scope is drawn to prevent it. It answers internal questions about the firm’s own process and know-how, from material the firm has approved. Anything that looks like advice on a matter should be refused, and we test that boundary explicitly.
By deciding, before anything is built, which material the agent may draw on and who may reach it. Not every knowledge source carries its original permissions, so the assessment checks whether someone could receive an answer drawn from material they could not open themselves.
Then the agent should say so rather than choose. Conflicting sources are part of the acceptance checks, and the build needs a named owner for the material and a process for retiring superseded versions.
A review of what is worth building on your tenant and what isn’t. There is no obligation to proceed to a build.