The Four-Layer Diagnostic
Vishal Sachar
Co-Founder & CEO of CLRT
Most AI projects solve the wrong problem, and they do it for an honest reason: they accept the first problem they are handed. A client says "we need an AI agent for customer queries," the team builds an AI agent for customer queries, and six months later the original pain is still there because it was never about the queries. The discipline that prevents this is a deliberate descent through four layers, from the symptom someone names down to the thing the decision-maker actually wants.
The first layer is the presenting symptom, what the client says is wrong. The second is the value driver, the business outcome that symptom touches, revenue, cost, risk, or reputation. The third is the binding constraint, the actual bottleneck holding that outcome back, which is usually not the symptom at all. The fourth is the decision-maker's utility, what the person signing off truly optimises for, which in a family business or a government-adjacent buyer is often control, legacy, or mandate alignment rather than pure profit.
Only at the bottom of that descent do you know whether AI helps, and if so, where to point it. The symptom and the constraint are almost always different things, and that gap is where money gets wasted. Speed up the symptom and it feels like progress while nothing actually moves.
Take the problem you are handed and keep asking what it is really about. The answer is rarely the question.
A deeper dive
Each layer exists because the one above it hides something. The symptom is where the client's attention sits, which is not the same as where the leverage sits. The value driver forces the symptom to connect to something that matters financially or strategically, and a surprising number of requested features connect to nothing. The binding constraint is Theory of Constraints applied directly: in any system only the bottleneck governs throughput, so improving anything else produces local motion and no real gain. The fourth layer is the one most consultants skip and the one that quietly kills the most projects. A technically flawless solution that ignores what the signer actually values dies in the room, unfunded. In Gulf family conglomerates and public-sector-adjacent buyers especially, the utility function frequently centres on reputation, control, and alignment with a national mandate, so the identical AI recommendation has to be framed against that utility, not against a spreadsheet, to survive.
The sequence
- 01
Presenting symptom
What the client says is wrong.
- 02
Value driver
The business outcome that symptom touches: revenue, cost, risk, or reputation.
- 03
Binding constraint
The actual bottleneck holding that outcome back, usually not the symptom.
- 04
Decision-maker utility
What the person signing off truly optimises for, often control, legacy, or mandate.
Work with CLRT
The first thing CLRT does in any engagement is refuse to accept the presenting problem. If you want to know what your AI initiative is really about, that descent is where we start. Begin with a conversation.
Vishal Sachar
Vishal Sachar is the Co-Founder and CEO of CLRT, where he helps UAE businesses make sense of applied agentic AI and put it to work. He writes on agentic systems, AI governance, and the economics of automation. Reach him at vishal@clrtstudio.com or on LinkedIn.
