Internal preview · not linked publicly

Transformation intelligence loop

AI creates the hypothesis. Omar validates the diagnosis. Everything below is seeded prototype data.

InsteadSecure Plus Financial
Nominate a casePrototype data
  1. CSM nomination
  2. Firm intake
  3. AI Transformation Brief
  4. Omar validates diagnosis live
  5. Transformation plan
  6. CSM implementation
  7. 30-day outcome
  8. Pattern intelligence
0

CSM nomination

Case TC-0148 · Jacob (CSM) · May 2

Firm

Ellis & Co. CPAs

Primary contact

Jordan Ellis — Managing Partner

Problem the firm wants solved

They believe they need another preparer before next season.

Why now

Hiring decision lands in June. Partner review hours are already the ceiling on throughput.

Workflow

Tax preparation

Case rationale

Clear owner sponsorship, one workflow, and a measurable decision attached to it. If the constraint isn't headcount, the transformation is visible within one season.

Potential value

Avoid a hireSave owner timeReduce rework
A

Transformation Brief

Case TC-0148 · Prepared for session on May 14

Firm context

Tax-first firm, Southeast. Assigned CSM: Jacob. Respondent: Jordan Ellis, Managing Partner. Workflow in scope: tax preparation.

Stated problem

Preparation takes too long and review is a bottleneck. Leadership believes they are short-staffed heading into season.

Why it matters now

A hiring decision is due in June, and the partner cannot absorb more review hours next season.

Current workflow

Organizer sent → client returns partial documents → admin files what arrives → preparer starts on an incomplete file → missing items surface mid-preparation → return parks in an open queue → partner reviews and often re-does sections.

Actual operators

Admin / Client SuccessTax professionalOwner / Partner

Flag — respondent is not an operator

The respondent does not perform this workflow. The described process is leadership's understanding; the closest operator is not yet in the session. Closest to the work: Dana Ruiz — Tax Manager. Omar and the CSM decide whether that person needs to join the session.

Firm's perceived constraint

CapacityProcess isn't standardized

Firm's AI expectation

Speed up preparationAvoid another hireReduce rework
AI hypothesized root constraintInput / Data QualityAI hypothesis — requires live validation

Work is entering technical production incomplete. Preparation and review absorb the cost of an unfinished intake step, which reads inside the firm as a staffing shortage.

Supporting evidence

  • —Friction selected: missing/incomplete information, client follow-up, technical review/rework.
  • —Previous attempt: a completeness checklist was built but is not enforced once season pressure starts.
  • —No status exists that blocks preparation on an incomplete file.
  • —Perceived constraint is capacity, but the described breakdown occurs before preparation begins.

Three validation questions

  1. 1.What percentage of returns actually enter preparation complete today — and how would you know?
  2. 2.When a file is incomplete, who is allowed to stop it, and has anyone ever done so?
  3. 3.Is partner review catching technical issues, or is it finishing incomplete preparation?

Potential transformation direction

Likely direction, not a prescription: an enforced completeness gate before preparation, with an agent reconciling document sets against a return-type requirement list and chasing gaps.

Proposed success metric

Firm-stated evidence: average review time 50 → 25 minutes, and the partner out of routine review.

Implementation owner

Dana Ruiz — Tax Manager

Assigned CSM

Jacob

Pattern tags

Perceived: capacityHypothesis: input qualityAI expectation: speedRespondent not an operatorTax preparation
B

Live coaching outcome

Captured live by Omar with the firm

Confirmed root constraintInput / Data QualityHypothesis confirmed after live validation with the tax manager present.

Agreed future-state workflow

Requirement list per return type → agent reconciles received documents against the list → automated gap requests with a deadline → file flips to 'Prep Ready' only when complete → preparer picks up only Prep Ready work → reviewer scores technical items, not completeness.

Role of AI

Reconcile documents against requirements, draft and send gap requests, track outstanding items, flag files stalled beyond 5 days.

Role of humans

Own the requirement standard, approve exceptions, hold the gate, handle client escalations.

Primary implementation action

Publish requirement lists for the top 3 return types and turn on the completeness gate for one pod.

Implementation owner

Dana Ruiz — Tax Manager

Success metric

% of returns entering preparation complete, and average review minutes per return.

Target date

June 30

Assigned CSM

Jacob

C

Complete handoff

A case isn't ready for CSM implementation until all seven are present

  • Confirmed root constraintInput / Data Quality
  • Future-state workflowDefined in session
  • Primary implementation actionPublish requirement lists for the top 3 return types and turn on the completeness gate for one pod.
  • Named ownerDana Ruiz — Tax Manager
  • Success metric% of returns entering preparation complete, and average review minutes per return.
  • Target dateJune 30
  • Assigned CSMJacob

The CSM should be able to act on this without Omar reinterpreting the session afterward.

D

CSM 30-day outcome check

30 days after session · captured by Jacob

In progressCompletedNeeds rework

What was actually implemented

Requirement lists live for 1040 and 1120-S. Gate enabled for one pod of 4. Automated gap requests running.

What happened to the success metric

Complete-at-intake 55% → 78%. Average review time 50 → 34 minutes.

What blocked progress

Partner still pulls incomplete files forward for a handful of legacy clients.

Needs to return to coaching

No

One required check at 30 days. Earlier updates only when something materially changes. Target time to complete: about two minutes.

E

Role ownership

Who owns what across the loop

CSM

  • · Case nomination
  • · Participant completion
  • · Implementation follow-through
  • · Outcome capture
  • · Normal customer implementation support

Omar / SPF

  • · Diagnostic validation
  • · Root-constraint determination
  • · Transformation design
  • · Coaching methodology
  • · Framework development

Olivia / Vaishnavi / Leadership

  • · Program oversight
  • · Visibility into results
  • · Strategic escalation
  • · Review of aggregate intelligence

Visibility, not approval. Leadership is never a required approver on an individual case.

F

Pattern intelligence

Illustrative aggregate across pilot cases — seeded data

Chain compared across cases: nominated problem → firm-stated problem → firm-perceived constraint → AI hypothesis → Omar-confirmed constraint → expected AI role → actual transformation → implementation status → outcome.

63%

of firms named a different constraint than the one confirmed in session

44%

of intakes were completed by someone who does not perform the workflow

71%

of implemented cases moved their agreed success metric

Most common nominated problems

  • Need another preparer26
  • Review is a bottleneck22
  • Chasing missing documents19
  • Team isn't adopting AI14
  • Too much rework11

Most common firm-stated problems

  • Preparation takes too long34
  • Review is a bottleneck27
  • Can't find or keep staff21
  • Clients are slow to respond18
  • Owner in too many steps14

Confirmed root constraints

  • Input / Data Quality31
  • Operating Model26
  • Change / Adoption19
  • Implementation / Education15
  • Product / Integration9

Workflow areas

  • Tax preparation29
  • Intake / document collection24
  • Tax review / QA17
  • Client communication12
  • Advisory delivery10

AI expectation vs appropriate AI role

  • Expected: replace manual work38
  • Appropriate: verify + chase inputs31
  • Expected: speed up preparation27
  • Appropriate: enforce a standard22
  • Expected: avoid a hire19

Who actually performs the workflow

  • Tax professional34
  • Admin / Client Success28
  • Owner / Partner24
  • Offshore / outsourced team13
  • Bookkeeping / accounting staff11

Friction categories

  • Missing / incomplete information41
  • Technical review / rework33
  • Client follow-up30
  • Owner dependency22
  • Inconsistent process20

Case outcomes

  • In progress18
  • Completed14
  • Needs rework6
  • Returned to coaching3

Reusable insight cards

Coaching

Firms often frame labor shortages as preparation problems; the recurring root constraint is incomplete work entering technical production.

Customer Success

Adoption holds when a single named owner controls one gate. Multi-owner rollouts stall inside three weeks.

Product

A blocking readiness status is requested far more often than more automation. Firms want enforcement, not more suggestions.

Sales / implementation

Discovery converts better when the conversation starts at intake completeness rather than software replacement.

Prototype only. No real firm or client data. Nothing on this page is persisted.