Starting a Consulting Relationship

Photo by Rock Staar on Unsplash

How I Actually Get to Know Your Business

There is a version of consulting where someone walks in with a pre-loaded slide deck, nods through a thirty-minute intake call, and starts billing by the time they reach the parking garage. That version is not what I do. The work I care about starts much earlier than most clients expect, and it starts with a genuine effort to understand what is actually going on inside an organization before a single recommendation gets made. That means resisting the pull toward early conclusions, asking questions that might feel tangential, and accepting that the first framing of a problem is almost never the right one.

Consulting relationships tend to fail when they skip the human layer and go straight for the technical one. Processes do not break themselves, and systems do not fail in a vacuum: people make decisions, carry institutional knowledge, develop workarounds, and hold undocumented context that rarely shows up in any org chart or process document. Before I think about what a business needs to change, I want to understand who runs the thing, who the work actually falls on, and what the daily experience of those people looks like. That means sitting with someone through their morning, listening past the official narrative, and resisting the urge to slot what I hear into a framework I already had in my pocket. A business is not an abstraction, and the people inside it are not variables, they are the starting point, and everything useful comes from treating them that way.

Stated needs and actual needs are frequently different things, and closing that gap is one of the more underrated skills in this line of work. A founder might say they need a better sales process when what they actually need is clarity on who their customer is. An operations manager might say they need a new project management tool when the real issue is that accountability is structurally unclear. These are not unusual situations — they are the norm. My job in the early stages of any engagement is to listen carefully enough to distinguish the symptom from the underlying condition, which requires asking questions that are sometimes uncomfortable and being willing to hear answers that reframe the original request entirely. That kind of discovery does not happen through a questionnaire; it happens through conversation, and through the patience to follow an answer wherever it leads.

Once there is a clearer picture of what a business actually needs, the next step is mapping what it is currently doing, not the official version, but the real one. The official version lives in policy documents and onboarding materials. The real version lives in the behavior of the people doing the work, and in practice these two things are often meaningfully different. That gap is almost always diagnostic. When I map a current process, I am looking for where handoffs break down, where decisions get made informally because the formal channel is too slow, and where someone has quietly built a workaround that the rest of the organization does not know exists. Those details matter. They tell you where the friction is, and they tell you whether a proposed change will be adopted or quietly routed around the moment someone’s back is turned.

Understanding the current state is only half of it. There is nothing more avoidable in consulting than recommending something a client already tried, and yet it happens more than it should, usually because the consultant did not ask early enough, or did not ask at all. Every organization I work with has a graveyard of initiatives that were announced with enthusiasm and buried six months later, and the reasons those things failed carry more predictive value than almost anything else about the current situation. Sometimes a prior solution failed because it was genuinely the wrong fit. More often, it failed because of implementation, timing, internal politics, or resource constraints that never got resolved. Understanding what was tried, what happened, and what the organization concluded from the experience tells me a great deal about what is and is not possible going forward. Adjacent to that history is the question of what is already in place and still running: the tools, vendors, contracts, and internal systems that were each acquired to solve a specific problem at a specific moment and have since grown into a landscape that nobody fully mapped. Some of what exists is working well and should be left alone. Some of it is actively creating friction but is embedded deeply enough that replacing it carries real cost. Some of it is being paid for and barely touched. None of those categories become visible without asking, and none of them can be responsibly ignored when building recommendations on top of them.

There are also engagements where, after all of that, the honest answer is that I am not the right fit. This is not a popular stance in an industry where the incentive structure rewards saying yes and figuring it out later, but I have seen enough situations where the wrong consultant held on too long, burning client budget, delaying real solutions, eroding trust in the process , to feel comfortable being direct about it. Some problems require domain expertise I do not have. Some organizations are in a phase where external consulting will not move the needle regardless of the approach. Some situations call for a different kind of help entirely. When I reach that conclusion, I say it clearly and try to point toward something more useful than my own continued involvement. That is not a failure; it is the job done correctly.

If you are looking for someone to validate a decision you have already made, I am probably not the right call. But if you are willing to sit with some uncomfortable questions before we start building anything, you will get work that actually fits your business, not a set of recommendations that looked good in a deck and fell apart in the first month of implementation. That is what the upfront investment buys, and it is the only way I know how to do this well.

Originally published at https://kyle-casey.com on May 2, 2026.