When the Firm Is Already Building It, Quietly and Correctly
Challenge
The practice operates inside a tightly regulated environment: closed-model toolset only, national-network compliance sign-off on all client-facing output, and a mandated upload of documentation to the national CRM surface. Within those constraints, the Principal had built something quietly unusual. The paraplanning team was running seven operational agents on the approved closed-model stack, handling PDF extraction, letter-of-authority chase, annual review preparation, and adviser-voice email drafting. A compliance pre-check agent was four weeks from go-live.
The Principal sat at Level 201 with emerging 301. The paraplanners at 201. The adviser cohort at 101, by deliberate sequencing, not drift. It was well-governed AI adoption. What it did not yet have was a named plan for what comes next.
Solution
Matthew Thistle delivered an AI Business MOT: a sixty-minute in-person diagnostic scoped entirely inside the national-network compliance envelope.
The session covered:
- Ten targeted questions about workflows, team structure, approved toolset, and build pipeline
- Analysis against the four-tier AI adoption framework (101 to 401), mapped cohort by cohort
- Inventory of the existing agent stack: live, in-build, and still-manual
- Blocker diagnosis across skills, permission, and workflow categories
Results
The report surfaced an atypical profile. Where most SMEs present with a dominant skills-gap blocker, this practice did not. The skills position was partial by design. The binding constraints were permission-shaped and workflow-shaped, both already managed rather than unresolved.
The diagnostic identified two high-leverage opportunities. First, a six-week adviser adoption pathway covering three defined use cases only: meeting debrief, client-voice email, and post-meeting action capture. This comes before paraplanner-led throughput makes the adviser layer the next capacity ceiling. Depth over breadth.
Second, protective instrumentation for the compliance pre-check agent before go-live: a lightweight rework-request log to baseline the four-week build window, and a trace-rendering agent that auto-generates an external-facing document from the pre-check agent's own operation. The log proves the value; the trace answers the question the regulator or network might eventually ask.
"I think we are a long way ahead. I know what our peers do, and they are not using anything."Principal, during the diagnostic
This one told a firm what it had already built, and what it needed to do next to protect it.
The 301 Insight
The most consequential finding was not a recommendation to adopt new tooling. It was naming what the practice had already built, and sequencing the finish. Most firms at this stage are told what to deploy. This one needed the opposite: a structured account of what it had done correctly, and a protective plan for the single build that mattered most.
