Find the constraint before you fund the solution.
The Constraint Diagnostic is an in-depth look at the problems and process behind one business outcome. It ends in a decision: what to fix, what to stop, and whether AI, automation, or more headcount is allowed to exist in this workflow.
Diagnosis is never outsourced.
A decision with a number on it.
Not a deck of recommendations. You name the outcome and what moving it is worth. We identify the constraint, show the evidence and economics, and tell you what to fund, and what not to. Sometimes the answer is do not spend this year.
Three situations where it pays for itself.
A workflow is not producing the result
Claims, order-to-cash, onboarding, billing, scheduling, denials, FNOL, submissions.
An AI or automation decision is on the table
Same method, with the technology question made explicit.
Performance should be better and you are not sure where
Start with the Constraint Assessment.
If you already selected the software and need implementers, this is not the engagement.
Five outputs. A five-page readout. Many clients stop here.
- Constraint memo
- Economic leakage range
- Roadmap ranked by impact × readiness
- Fund / do-not-fund list
- Implementation Sprint recommendation, or a clean stop
Evidence first. Alternatives tested and killed. Then the decision.
Clarity Session & scoping
If the constraint is unlikely to be worth roughly 10× the cost of finding it, we do not start.
Evidence
Documents, interviews, observation of the queue. No PHI through the website.
Constraint and economics
Alternatives tested and killed. AI scored only after the workflow is understood.
The decision
Constraint, evidence, dollars, fund / do-not-fund, sprint or stop.
Scoping chooses the depth.
Workflow Performance Diagnostic
One transaction-heavy workflow. For the COO, CFO, or process owner.
Enterprise Diagnostic
How the organization is run. For the CEO, COO, board, or operating partner.
Same diagnostic. Six questions, in order.
If the answer to “where will technology create measurable value?” is “nowhere yet,” that is a successful diagnostic.
You get the scope before work starts.
A named owner, a number (even a messy one), access to the people who do the work, and scorecards and sample transactions inside your environment. No production extract is required to start.
What this is not, and what happens after.
Not this
Software implementation. A predetermined install. Multi-week discovery with no decision. Staff augmentation. A platform pitch. Wrong when the tool is chosen, you want training, there is no owner, or there is no outcome in money or time.
What happens after
Stop, sprint, or later Sustain & Transfer. A good fit when the problem is not understood and a spend needs an objective constraint.
Before you fund the solution, find the constraint.
Twenty minutes. No deck. No pitch.