The Field Manual / Implementation & adoption
What your team needs to start using AI in one workflow
The short answer
Bring one workflow, a few recent examples, its owner and the people who do the work. Check your current tools before buying more. Agree on the review step and test the draft process on real cases before expanding it.
How much setup time will our team need?
The Diagnostic runs for one week and produces documents, not a live automation. Its credit conditions include pre-work within 48 hours of booking and attendance at both live sessions. Implementation effort depends on the workflow, access requirements and data quality; it is scoped separately.
Prepare three recent examples, the documents and messages they touched, the current approval rule and the people involved. Ask for a time estimate by role before agreeing to a build. A one-week Diagnostic is not a promise that every integration launches in one week.
Do we need a particular CRM or software stack?
There is no single required CRM for the initial workflow review. List the tools you already pay for and the AI features available in each. Then check whether the proposed connection supports the records, permissions and actions you need.
Slack, email and CRM names are examples of tool categories, not a guarantee that every edition or configuration connects. Review API availability, subscription costs, authentication and vendor data handling before granting access.
What if the team does not adopt it?
Run a small pilot with a named owner and a way to return to the current process. Let the people doing the work test it on a normal busy day. Record what they correct, what they avoid and where they still copy information by hand.
If the pilot adds work, identify why before expanding it. The issue may be duplicate entry, unreliable drafts, unclear approvals or an awkward screen. Fix the cause and repeat the walkthrough. Adoption is something to observe, not something an onboarding meeting guarantees.
What belongs in the check-in?
Review completed and stalled items, time spent checking drafts, exceptions, connection failures and feedback from the team. Assign each change to an owner and record the next review date. Keep sensitive client information inside the approved tools and access rules for that engagement.