Stan Tscherenkow
Before You Commit ยท Hiring a consultant

Before You Hire A Consultant

The consultant pitch looked sharp. The problem feels real. The work is about to start. Four checks come first.

This page is for the owner about to sign a consulting engagement and wondering why the previous one did not produce what was promised.

Short answer

Before hiring a consultant: define the deliverable, the success measure, the decision-right transfer at handoff, and the escalation path if the work stalls. Three of the four are usually missing from a typical SOW. Without all four, the engagement produces beautiful artifacts that nobody implements and a relationship that ends in mutual frustration.

Fast extraction

Direct answers for the owner reading this on a busy week.

Each answer is a single direct read. The full read is in the body.

01

What should be in a consulting SOW?

Four things at minimum: the specific deliverable, the success measure (how you and the consultant both know it worked), the decision-right transfer at handoff (who decides what once the work lands), and the escalation path if the work stalls or scope changes.

02

Why do consulting engagements fail?

Three patterns: the brief was wrong (the consultant solved the wrong problem), the founder will not release authority (the work cannot be executed), or the methodology does not fit (big-company process transplanted into small-company reality).

03

How do I know if the consultant is good?

A good consultant narrows your problem before widening their scope. References survive being asked the awkward questions. They say no when scope expands without integrity. They produce decisions, not just decks.

04

Should I get multiple proposals?

Yes, three minimum. If two consultants pitch different problems from the same brief, the brief itself is unclear and a different kind of help is needed before consulting starts.

Money already moving

Consulting fee, internal time supporting the consultant, leadership-team attention during the engagement, data preparation, executive interviews.

Money usually lost

Consulting engagements that produce decks nobody implements. The fee is paid, the artifacts exist, the business does not change. Average cost: the entire fee plus the opportunity cost of the next six months.

Blind spot

The pitch is the visible negotiation. The success measure, the handoff plan, and the escalation path are usually agreed by handshake or not at all.

Decision map

The transaction is not the whole decision.

The proposal, the firm, the partner you met. These are the visible objects. The dangerous part is the unstated assumption that the consultant's recommendation will be executed regardless of who is internally ready to receive it.

Inspection list

What Stan would inspect before the yes.

Before the commit hardens

  • Is the deliverable specific enough that you would recognise it when you saw it.
  • Is the success measure named in the SOW (not just the deliverable).
  • Who internally takes the handoff and what authority do they have on day one.
  • What is the escalation path if scope changes or work stalls.
  • What does the consultant say no to (a consultant who says yes to everything is not narrowing your problem).
  • What are three references doing today that did not work out, and what was the pattern.
  • Is the engagement priced against the deliverable or against time.

A consulting engagement is a structural commitment before it is a financial one. The four checks decide whether the work will produce a decision or another artifact.

If you want Stan to read this live decision, use the application route below.

When the decision is one commitment with real cost, Tier 01 is the commercial route.