The first call: what I actually listen for
Not the stated problem. The seams, the workarounds, and the thing they have stopped noticing because they live with it.
The stated problem is rarely the problem
On a first call, the client tells me what they think is wrong. Useful, but it is the symptom. What I am actually listening for is the operational debt underneath: the manual steps they have normalized, the tools that do not talk, the report someone rebuilds by hand every week.
What the workarounds reveal
Every workaround is a map to a missing system. When someone describes the elaborate way they keep two tools in sync, they are telling me where the spine is broken. The workaround is the diagnosis.
Where it leads
By the end of the call I am not pricing the stated problem. I am pricing the operation: what it would take to remove the seams and the rebuilds so the team stops paying the coordination tax. That is the engagement, and it is almost always bigger and more valuable than the thing they called about.