Strategy consulting proposals fail when the scope is just "strategy." "Develop a growth strategy" or "help us think about the market" sounds like an objective, but it names no question and no output. Without a specific strategic question on the page, the engagement expands to cover whatever the client is worried about that week, and the deliverable never quite lands.
This is a different failure mode from a management consulting proposal, which usually diagnoses why something inside the organization is underperforming. A strategy proposal looks outward — should we enter this market, how do we position against this competitor, where should growth actually come from — and it needs its own structure to stay bounded.
What makes a strategy proposal different from a generic one
- Anchor to one named strategic question.Market entry, competitive positioning, or a growth-path decision are each a bounded question with a bounded deliverable. "Strategy" on its own is not — it invites the client to keep adding "can you also look at..." for as long as the engagement runs.
- Name your data dependencies.Market sizing, competitive intelligence, and customer interviews drive most strategy work, and you often need the client to provide access — customer lists, internal sales data, or introductions for interviews. State what you need from them and what you'll source from third-party data, with the confidence level that implies.
- The deliverable is a recommended direction, not a guaranteed outcome.You're proposing a decision framework with a recommendation and its trade-offs — not a promise that market entry succeeds or that the recommended positioning wins share. Execution and market response happen after you're gone, and the proposal should reflect that.
What to include
- Objective — the single strategic question being answered, stated as a decision to be made, not a topic to explore.
- Scope of work — concrete deliverables: a market-sizing analysis, a competitive landscape map, a set of customer interviews, a recommendation with named trade-offs.
- What's not included — implementation of the recommended direction, ongoing market monitoring, localization or execution planning beyond the initial recommendation.
- Timeline — phased if research and synthesis are separate steps, with dependencies on client-provided data or interview access called out.
- Pricing and payment terms — fixed project tied to the named question, priced for the research effort the question actually requires.
Worked example
Objective: Determine whether a project-management SaaS company should enter the Canadian SMB market, and if so, recommend an entry approach.
Scope of work: Market sizing (TAM/SAM) for Canadian SMB project-management software; competitive landscape map of the top 6 players with pricing and positioning; 8 customer and prospect interviews sourced from client introductions; go/no-go recommendation with two entry approach options (direct sales vs. channel partnership) and the trade-offs of each; findings presentation to leadership.
What's not included: Execution of the chosen entry approach; localization of product or marketing materials; ongoing competitive monitoring after the engagement ends.
Timeline: 6 weeks — 2 weeks market sizing and competitive mapping, 2 weeks customer interviews, 2 weeks synthesis, recommendation drafting, and leadership presentation.
Naming the question up front is also what makes the next engagement obvious — implementation support, or a follow-on strategy question, instead of an open-ended request to keep "thinking about strategy" together. The free Consulting Proposal Generator turns this structure into a formatted, ready-to-send document with a PDF download included.