Strategy Engine · plain-English guide
How to read Diagnostic
Diagnostic gtm health assessment. This guide explains what it produces, what each part means, and how it stays honest — so you can act on the output with confidence.
Takes
Company URL + revenue stage + team size
Gives
Constraint map with evidence
The data it uses: Company URL, revenue stage, team size.
Watch how it works
How to read the output
Constraint
The one thing most limiting revenue right now. Fixing anything else first is wasted effort.
Evidence
Why this is the constraint — grounded in your inputs and public signals, not a framework guess.
Sequence
What to do about it, in order.
The terms it uses
- Constraint
- The bottleneck that caps the whole system — the Theory-of-Constraints idea applied to revenue.
- Symptom vs cause
- Missing pipeline is usually a symptom; the cause is often positioning, ICP, or follow-through.
How it stays honest
Every agent separates what it measured from your data from what it inferred. You always know which is which.
Measured
- ✓Your inputs
- ✓Public signals about the company
Inferred
- ~Constraint identification
- ~Sequenced actions
Questions people ask
How is this different from a big consulting assessment?+
It runs in minutes on a URL and stage, and it names ONE constraint with evidence instead of a 90-page matrix.
Now read the real thing.
Run Diagnostic on your own data and compare the output to this guide. If it matches, you can trust it.