What the engagement actually is
Most professional services firms do not need a model. They need a specific piece of work to stop leaking time, and they need whatever fixes it to survive contact with a regulator, a client, or a partner who asks how it reached its answer. That is a different problem from adopting AI, and it has a different shape.
An integration engagement starts by finding where judgement is actually being spent. In most firms that is intake, document handling, and the repeated assembly of things that have been assembled before. Those are the places where a system can carry load without taking over the decision.
Where the boundary sits
The rule we build to is that the system may prepare, retrieve, draft, check and route. A person decides. This is not caution for its own sake: in a professional services context the decision is the billable product and the thing the firm is liable for. A system that quietly makes decisions transfers liability to a vendor who cannot hold it.
In practice that means every automated step produces something a human can inspect before it matters. A drafted document is a draft. A flagged file is a flag. A routed matter is a suggestion with the reasoning attached.
Data boundaries come first, not last
Firms in regulated work usually cannot send client material to a general model endpoint, and the ones that can often should not. So the boundary is established before anything is built: what may leave the building, what must be processed on infrastructure the firm controls, and what must never be retained.
That constraint changes the architecture rather than blocking it. Retrieval over a firm's own corpus, local inference for the parts that touch client data, and hosted models only for work that carries none, is a common shape. It is slower to design and considerably easier to defend.
What ships
- A workflow map showing where hours are actually going, with the leaks ranked rather than listed.
- A scoped build against the highest-value leak, not a platform.
- A proof metric: one number the firm can check that tells them whether the thing is working. Every system we ship has one.
- The boundary documentation, so the answer to "where does our data go" is a document rather than a conversation.
Where to start
If the problem is not yet defined well enough to quote, the Workflow Leak Audit is the fixed-scope way to define it. If the work is legal intake specifically, the client intake portal is a known quantity, and Attorney Minds is the productised form for firms that want it hosted. Firms preparing for AI agents to interact with their business at all should start with agent readiness.