Five Conversations to Have Before You Sign the Engagement Letter

Consulting engagements rarely fail because the consultant lacked expertise. They fail because of things nobody discussed: who actually holds decision authority, what the last consultant did wrong, whether the budget is real, and what "success" means to each person in the room. A structured sales process covers scope and fees. It almost never covers the five things below.

I now treat these as five required conversations before any engagement letter goes out. Sometimes they happen across two calls; sometimes they take three weeks. Either way, if I can't complete all five, I don't sign. Here's the framework, with the questions I use and the red flags I listen for.

1. The Decision-Rights Conversation

The person who hires you is often not the person who can approve your work, fund your recommendations, or protect you politically. Before signing, map the actual decision structure.

Ask: "Walk me through how a recommendation like this would get approved — who signs off, and who could veto it?" And: "Who else has to be in the room for this to actually get implemented?"

Red flag: The sponsor hesitates, or says "I'll handle the internal side" without specifics. An engagement where your only ally is the person who hired you is an engagement with a single point of failure.

2. The Failed-Past Conversation

Every established organization has a history of initiatives that didn't work — consultants who left, software that went unused, strategies that died in a drawer. That history predicts your future more than any mission statement.

Ask: "What did the last attempt at this look like, and why did it stall?" Then the sharper version: "If I asked the people involved, would they describe it the same way?"

Red flag: "We've never tried anything like this." Almost no mid-sized company in America is genuinely attempting something unprecedented. If there's no failure history, it's either being hidden or nobody has done the homework yet.

3. The Budget-Reality Conversation

Budget conversations go wrong when they're about fees instead of capacity. The question isn't only what the client can spend on you — it's what they can spend on the whole change, including internal time, tools, and the disruption of doing things differently.

Ask: "Setting my fees aside, what's the total realistic investment your team can absorb this year to make this stick?" And: "Is this budget approved, or does it need to survive a board cycle?"

Red flag: "Budget isn't an issue." It is always an issue. Also: discovering late that funding depends on results neither of you can guarantee in advance.

4. The Politics Conversation

You don't need to know the org chart drama in detail. You need to know whether your work will create winners and losers — because most operational change does.

Ask: "Whose day-to-day changes the most if this succeeds?" And: "Is anyone likely to see this project as a threat?"

Red flag: The sponsor dismisses the question entirely. Every organization has politics; a client who claims otherwise either hasn't looked or won't tell you. Both are problems.

5. The Definition-of-Success Conversation

This is the conversation that prevents the most disputes. Ask every stakeholder separately, because you will get different answers — and the gap between those answers is the real scope of work.

Ask: "Twelve months from now, what has to be true for you to say this was worth it?" Then: "How would we measure that, and who keeps the scoreboard?"

Red flag: Stakeholders give incompatible answers and nobody is troubled by the contradiction. Or the only definition of success is intangible — "alignment," "momentum," "transformation" — with no observable evidence attached.

A Framework, Not a Gate

These conversations are not a filter for finding perfect clients. Perfect clients don't exist, and a red flag is a reason to design around a risk, not necessarily to walk away. A client with murky decision rights might need a governance step built into phase one. A client with no budget for implementation might get a narrower engagement focused on a plan they can actually fund.

The point is that you cannot design around a risk you never surfaced. Five conversations, asked in plain language before the contract is signed, will prevent the majority of expensive lessons in a consulting practice — and will signal to serious prospective clients, incidentally, that they've found someone who takes the work seriously too.