Name the business problem in plain language. Then check where it repeats, who owns it, what has already been tried, and what would make the next fix easier.
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.
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.
Before you hire help, know what problem you are hiring for.
A consultant can be the right move when the problem is defined. If the owner is still guessing, the first check is the problem itself, not the proposal.
Do not buy a staffed project because the problem feels important. Buy the project when the scope, owner, handoff, success measure, and first constraint are clear.
Use Business Problem Review when the same problem touches sales, operations, money, team ownership, and owner judgment.
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.
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.
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).
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.
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.
Consulting fee, internal time supporting the consultant, leadership-team attention during the engagement, data preparation, executive interviews.
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.
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.
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.
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.
Read the pattern before applying.
Routes into the structural pattern beneath this decision.
The pain when the engagement is already going wrong.
Advisor Sounds Good But Nothing MovesThe pattern that often follows a misaligned consultant or advisor.
Decision Architecture vs ConsultingWhen the problem may not be a consulting problem yet.
Business ConsultantThe plain buyer route for deciding whether a consultant is the right kind of help.
When To Hire A Business ConsultantUse this when the question is timing, scope, and what should be checked first.
How To Figure Out What Is WrongUse this when the brief keeps naming the symptom instead of the business problem.
Diagnostic Review Vs Consulting ProjectUse this if the proposal is clear but the business problem is not.
Business Problem ReviewUse this before the consulting spend hardens if the actual problem is still unclear.
Outside HelpThe Atlas page for choosing among coach, consultant, advisor, fractional.
Ways To WorkUse this if a structural read is needed before the consultant starts.
Apply for Tier 01Single read on whether consulting is the right help for this problem.
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 application path.