Demand
Is there enough qualified opportunity to use available capacity?
01 / SCAN
Start with the operating system, not the software stack.
The diagnostic asks about team size, revenue context, revenue mix, calendar capacity, booking performance, estimate acceptance when relevant, callbacks and pricing confidence.
Those answers are not used to invent a dollar-loss estimate. They are used to identify which part of the business has enough evidence to deserve attention first.
Conversion
Are inquiries and estimates becoming booked work?
Capacity
Can the field team absorb additional demand?
Operations
Is rework or workflow friction consuming capacity?
Economics
Is there enough pricing confidence to support growth decisions?
02 / DIAGNOSE
The first supported constraint wins.
The engine evaluates answers in dependency order. A downstream opportunity is not allowed to hide a stronger upstream blocker.
For example, a full calendar does not automatically mean “hire.” If conversion is weak or callbacks are consuming capacity, that problem is surfaced first.
Conservative by design
Missing data lowers confidence. It does not create fake precision.
03 / DECISION LAB
Pressure-test the money you are about to spend.
After diagnosis, the Decision Lab asks a more practical question: should the next dollar go toward more leads, another technician or software?
The answer can be yes, not yet, or conditional. The engine is explicitly allowed to conclude that the business should not add another tool or another cost yet.
04 / SOFTWARE FIT
Only recommend software when software is relevant.
If the diagnosed constraint can plausibly be solved by a workflow tool, the software-fit layer compares capabilities against that specific problem.
The recommendation order is separate from affiliate routing. Commission has zero weight in the fit score.