The Process Diagnostic
Three to four weeks. $12,500 fixed fee. Approximately five and a half hours of your team's time.
Eight dimensions across two layers.
WHAT GETS MEASURED
Every dimension is scored on the same four-level maturity scale. That makes the profile readable at a glance and comparable when you measure again later.
LAYER ONE: OPERATIONAL
How work moves from sold to invoiced.
01 | Project Definition and Intake. What qualifies as a project here, and what has to be true before one exists
02 | Resource Management. How people are matched to work, and whether the plan survives the first week
03 | Time and Expense Capture. Whether the data going in is timely, complete, and worth trusting
04 | Billing and Revenue Recognition. How delivered work becomes an invoice, and how long that takes
05 | Reporting and Visibility. Whether anyone makes a decision from any of it
LAYER TWO: FOUNDATIONAL
Whether a fix will hold.
06 | Process Definition and Documentation. Whether what is written down describes what happens
07 | Ownership and Decision Rights. Who decides how this works, and how long a decision takes
08 | Cross-Functional Communication. Whether Finance and Delivery are describing the same company
If you aren’t ready, I will tell you. Most firms aren’t ready.
AI READINESS
Your AI readiness score is not something I ask you about; it is calculated from measurements already taken. Four inputs determine it:
Whether your process is documented
Whether your operational data is complete and timely
Whether your reporting is trusted
Whether someone has the authority to decide what changes
The result is a verdict rather than a pitch. For most firms the answer is not yet, delivered with the specific short list of what has to be true first.
I do not implement AI, and that is deliberate. It is what makes the assessment worth something.
Three to four weeks; five and a half hours of your team’s time.
HOW IT RUNS
WEEK ONE
A 30-minute kickoff call and a pre-work packet. You send existing process documentation, your standard project types, and the reports your leadership team reads. What you’re able to produce in a week is itself a useful signal.
WEEK TWO
Two 90-minute working sessions with a cross-functional group; we map your process live and let people correct one another. Up to three 30-minute conversations follow, one each with your executive sponsor, delivery lead, and finance lead. Those conversations are individual, and nothing said in them is attributed.
WEEK THREE
I score, build, and deliver. The engagement closes with a 60-minute readout and the full document in your hands. Most engagements close in three weeks; scheduling on your side can extend that to four.
Written to be read, not filed.
THE DELIVERABLE
Every section exists because someone will do something with it.
Executive summary. Written to stand alone for the person who will read nothing else.
Scored assessment. All eight dimensions with score, evidence, and rationale.
Current-state map. How the work moves in practice, including the points where your own people described it differently.
AI readiness verdict. One page; the score, the verdict, and the prerequisites.
Prioritized roadmap. Every item with effort, impact, dependencies, and a clear mark for whether you need outside help.
SCOPE
I do not configure, implement, or build during the diagnostic.
I do not advise on which system to buy or whether to change platforms; that question is outside scope and will remain outside scope.
I do not audit your books.
Executing the roadmap is separate work, scoped after the diagnostic concludes and only if you want it.
What this is not.
Is this right for you?
Thirty minutes will tell us both. If the answer is no, I will say so.