What to Expect in a First Consulting Engagement (It’s Not What You Think)
Most founders judge a first engagement by how fast a big plan lands in their inbox. The right test is whether the process — diagnosis, real interviews, an interim checkpoint — holds up before you've spent a Rupee on the outcome.
Most MSME founders sign their first consulting engagement expecting a plan on day one. They get a list of questions instead, and panic. What to expect in a first consulting engagement is not a finished strategy delivered in week one — it’s a structured process of diagnosis that has to happen before any recommendation is worth trusting. If a consultant hands you a 40-page strategy deck before they’ve asked why your best salesperson quit last quarter, that deck is a template, not an answer.
This matters because founders judge a first engagement by the wrong signal. They want to see a big output fast. But a good engagement is judged by whether the process was rigorous, not by how quickly something impressive-looking landed in their inbox.
Why the First Engagement Is a Diagnostic Phase, Not a Delivery Phase
A consulting diagnostic phase exists because most founders are wrong about their own root problem. They come in saying “we need a marketing strategy” when the real issue is that their operations team can’t fulfil the orders marketing already generates. McKinsey’s own internal engagement methodology — publicly described in their partner training materials — dedicates the first two to four weeks of nearly every engagement purely to problem definition, before a single recommendation is drafted. That’s not bureaucracy. It’s because the wrong diagnosis, acted on quickly, is worse than no action at all.
Define the term clearly: a diagnostic phase means structured fact-finding — reviewing financials, interviewing staff across levels (not just the founder), sitting in on actual operations, and cross-checking the founder’s stated problem against what the data shows. It typically runs one to three weeks for an MSME-scale engagement, shorter than a large-cap consulting project because the organisation is smaller, but the discipline is identical.
The analogy that makes this land: no competent doctor prescribes medication before taking your blood pressure, asking about symptoms, and ordering a test. A consultant who proposes a full plan in the first meeting is doing the equivalent of writing a prescription from the doorway. The diagnosis is not a delay before the real work starts — it is the real work, because everything after it depends on getting the underlying problem right.
What Good Process Looks Like — and the Signs of a Good Consultant Early On
The signs of a good consultant show up before any deliverable exists, in how they run the first few weeks. A rigorous first engagement typically includes three visible markers.
First, they ask more questions than they answer. Ram Charan, the consultant who shaped GE’s and Verizon’s leadership development approaches, has written that the sharpest advisors he’s watched spend the first meetings almost entirely in listening mode — testing the founder’s own diagnosis against what employees, customers, and numbers actually say. If a consultant arrives with answers before they’ve done this cross-check, they’re selling a template, not doing the work.
Second, they talk to people the founder didn’t think to include. A founder’s view of their own business is shaped by whoever reports to them directly. A good engagement process reaches two or three levels below that — the shop-floor supervisor, the customer service lead — because that’s where the real friction usually surfaces. This is where the process becomes visible: you can literally watch whether the consultant is talking only to you, or to your business.
Third, they produce an interim finding before a final recommendation — a short, honest statement of “here’s what we’re seeing so far, and here’s what surprised us.” This interim checkpoint is where a founder can catch a consultant heading in the wrong direction before months of work go into the wrong fix. It’s also where you can judge, concretely, whether their read on your business matches reality — not months later when the invoice has already been paid. The way Simpleworks Consulting structures early engagements with MSME clients keeps this interim checkpoint explicit, precisely so founders aren’t asked to trust a black box.
Why Judging the Process Protects You Better Than Judging the Promise
This is the heart of the thesis: a first engagement with a business consultant should be evaluated on the quality of the process you can observe, not on the confidence of the promise you’re sold. Promises are cheap and unfalsifiable in month one. A consultant can promise “20% revenue growth in six months” in the first pitch meeting, and there’s no way to verify that claim until six months have passed and the money is already spent.
Process, by contrast, is verifiable in real time. You can check, in week two, whether the consultant actually spoke to your warehouse manager. You can check whether their interim finding matches what you already suspected, or reveals something you hadn’t considered — evidence they did real work rather than repackaging generic advice. This is the difference between a weather forecaster and a fortune teller: the forecaster shows you the data and the model that produced the prediction, and you can inspect both. The fortune teller just gives you the prediction and asks you to trust it. A first engagement worth paying for is closer to the forecaster — you get to see the reasoning, not just the conclusion.
Founders who judge engagements by the promise end up disappointed at month six, when the growth number doesn’t land and there’s no way to trace back why. Founders who judge by the process catch a bad engagement in week three, when it’s still cheap to redirect or walk away.
The Honest Counter-Argument: Isn’t This Just an Excuse for Slow Consultants?
A fair challenge: doesn’t “judge the process, not the promise” become a convenient shield for consultants who are simply slow, indecisive, or padding the clock? A founder paying real money is entitled to ask why week three still hasn’t produced anything concrete. Some engagements do use “we’re still diagnosing” as cover for a lack of a clear point of view, and founders have been burned by advisors who never actually land on a recommendation.
This objection has real teeth. Diagnosis without a deadline is not rigor — it’s stalling. The distinction that matters is whether the diagnostic phase has a defined endpoint and a visible interim output, not whether it takes time at all. A consultant who says “give me six weeks with no checkpoint” is asking for the trust that only a track record earns. A consultant who says “here’s our two-week diagnostic, here’s the interim finding you’ll see on day 10, here’s what happens after” is showing you a process with accountability built in.
So the thesis holds, with this sharpening: it’s not that a slow start is automatically good. It’s that a start with visible, checkable structure — deadlines, interim findings, evidence of who was actually interviewed — is trustworthy in a way that a fast, confident promise never can be, precisely because you can verify the structure before you’ve committed six months of budget to the outcome.
Judge the Handshake, Not the Headline
Founders who get burned by consulting engagements almost never get burned by a bad idea. They get burned by an idea that was never actually tested against their real business before it was sold to them as certainty. The fix isn’t to demand faster answers. It’s to ask, in the first meeting: what does your process look like, who will you talk to, and when do I see the first checkpoint?
If a consultant can’t answer that plainly, that’s the answer. If you want to see what a structured, checkpoint-driven first engagement actually looks like in practice, the approach is laid out across the Simpleworks blog — because the process, more than any single deliverable, is what determines whether the rest of the engagement is worth the money.
About Prem Menon
Prem Menon is the founder of Simpleworks Consulting, working with MSME founders and growth-stage businesses across India to turn strategy into execution. With experience spanning manufacturing, SaaS, retail, and professional services, Prem brings a practitioner’s eye to the problems most consultants only theorise about.
Ready to see what a structured first engagement looks like?

Prem Menon
Founder, Simpleworks Consulting. 39 years across Telecom, Automotive and Consumer Durables — now helping Indian MSME and family-business founders grow with clarity.