Choose a narrow workflow.
“Bring AI into the business” is a direction. “Create a source-linked comparison of the renewal provisions in this approved set of leases” is a workflow someone can inspect. The first engagement should have that kind of boundary.
Agree on the baseline.
Record how the work happens today: time spent, common errors, review effort, and the people involved. Use the same representative material to assess the proposed approach. Do not assume a faster draft means a faster process.
Name the deliverable and the decision.
A diagnostic can end with a recommendation and a build-or-stop decision. An implementation can end with a tested workflow, operating instructions, and a handover. Agree on acceptance criteria before work starts.
Include the operating reality.
Discuss access controls, vendor data terms, ongoing model and storage costs, updates, and ownership. The appropriate design depends on the information involved and the organization that will operate it.
Keep the right to stop.
A pilot earns further investment by demonstrating useful behavior against the agreed criteria. A finding that a simpler tool is sufficient, or that the data is not ready, is a valid outcome.
An EPP.AL perspective on workflow and technology. It does not provide legal, investment, or compliance advice.