Where the two roles diverge
| Dimension | Strategic advisor | Consultant |
|---|---|---|
| Engagement | Ongoing, open-ended | Fixed scope, fixed end date |
| Cadence | 2–8 hours per month | Full project workload |
| Paid for | Judgement and availability | A deliverable |
| Commercial model | Fixed monthly retainer | Project fee or day rate |
| Relationship | Peer to the leadership team | Supplier to a sponsor |
| Ends when | The need for counsel ends | The work is delivered |
Choose an advisor when
- The team can execute; leadership wants better judgement on the big calls
- You need continuity — someone who knows the context six months from now
- The board wants an independent read, not a vendor's recommendation
- The questions are recurring rather than a one-off decision
Choose a consultant when
- There is a defined deliverable with a deadline
- You need capacity — hands to do the work, not only counsel
- The problem is specialist and bounded (pricing study, market entry model)
- The output has to be defensible to a third party such as an investor
The independence question
The sharpest practical difference is incentive. A consultant who recommends a large implementation may end up delivering it. An advisor with no downstream revenue at stake has no reason to recommend anything other than the cheapest sufficient answer — which is frequently “do less, but do it properly”. That is why advisory and delivery are usually kept in separate contracts.
Using both
The common pattern in growth-stage companies: an advisor helps frame the question and set the bar for a good answer, then a consultant or an internal team does the work, and the advisor reviews the output with the leadership team. Framing and delivery stay separate, and the company keeps ownership of the decision.
