M87 Constraint Review
For leaders considering AI, automation, process change, or a stalled initiative.
- What is actually governing the outcome?
- What evidence would support or reject that finding?
- Should you stop, measure, repair, evaluate, or pilot?
Independent diagnostic advisory · AI, automation + visibility
M87 identifies the governing constraint, establishes what would count as proof, and returns the smallest defensible next decision.
SCROLL TO SEPARATE THE FIELD ↓
Two entry points · One method
Both offers are governed by the M87 Constraint-to-Value Protocol. Neither includes implementation by default.
For leaders considering AI, automation, process change, or a stalled initiative.
For firms that may be absent or displaced in AI-mediated buying decisions.
Constraint-to-Value Protocol
The protocol keeps observation, diagnosis, proof, value, and authorization from collapsing into a sales pitch.
Define the business result, accountable owner, affected workflow, deadline, and materiality.
Map where value first stops and test the lead constraint against credible alternatives.
Fix the baseline, outcome, indicators, guardrails, source of record, and attribution rule.
Stop, measure, repair, evaluate, or run the smallest bounded intervention worth funding.
Proof-basis discipline
Confidence is not evidence. M87 marks the basis of each material statement and preserves uncertainty when the record does not support a stronger conclusion.
Directly inspected or reproduced by M87.
Supplied by a stakeholder and not independently verified.
Derived from cited inputs with visible arithmetic.
A reasoned conclusion from explicitly stated evidence.
A material fact that has not yet been established.
Core decision artifacts
The engagement produces an inspectable decision record, whether the right answer is to build, repair, measure, defer, or stop.
What governs the result, what competes with it, and what remains unknown.
The baseline, outcome, guardrails, source of record, and attribution rule.
The credible paths from no action through a bounded pilot.
Conservative, expected, and upside cases with assumptions exposed.
The recommendation, decision gate, and explicit authorization boundary.
Commercial integrity
Corrective work, implementation, and recurring service require a separate scope and explicit authorization.
AI is one possible intervention—not the premise of the engagement.
Time savings, revenue, and risk reduction require a defensible realization or attribution basis.
M87 does not access systems, contact outsiders, or change records without named authorization.
About M87
M87 Studio is an independent decision-systems practice led by Mac McFall. It works at the point where strategy, operations, evidence, AI, automation, and accountable execution meet.
The work is designed for leaders who need a defensible decision before a vendor, platform, or implementation path becomes the answer by default.
The next move should be smaller than the uncertainty.
Submit a short fit intake. M87 will determine whether the problem is diagnosable and material, then accept, narrow, defer, or decline the review.