Claude is exceptionally strong at problems that don't have a simple answer — where multiple factors interact, trade-offs exist, and the "right" answer depends on context and values. It builds structured reasoning frameworks that make the complexity navigable.
Strategy consultants, executives, product managers, researchers, and anyone tackling high-stakes decisions
Describe the situation, the decision to be made, the stakeholders involved, the constraints, and what a good outcome looks like.
Claude identifies the key dimensions of the problem, the most important uncertainties, and a structured approach to working through them.
Each dimension is analyzed in depth, with evidence weighed, trade-offs quantified where possible, and key dependencies identified.
A clear recommendation is given alongside 2-3 scenarios (best/base/worst case) that show how the recommendation changes under different key assumptions.
Deciding where to invest limited resources
We have $500K to grow our SaaS product. Options: hire 2 sales reps, invest in paid acquisition, build a key missing feature, or expand to Europe. What framework should we use to decide, and what is your recommendation?
Structuring a growing engineering team
We're growing from 8 to 25 engineers. Should we organize by product area, technical layer, or customer segment? Analyze the trade-offs for our specific situation: 3 products, 2 customer segments, high feature velocity needed.
Choosing between architectural approaches
Evaluate microservices vs modular monolith for our current stage: 15-person engineering team, $2M ARR, complex domain, 3-year plan to 10x scale. Give me a reasoned recommendation with risk analysis for each path.
The more you share — team size, budget, timeline, past decisions — the more accurate the framework. Claude can't ask for what you don't provide.
"What would a smart person who disagreed with your recommendation argue?" prevents anchoring on the first conclusion and strengthens your thinking.
"How does your recommendation change if the market grows 50% slower?" or "if we lose our lead engineer?" tests the robustness of any strategic decision.
"Format this as a board-ready decision memo: problem statement, options, recommendation, risks, and next steps." Instantly turns analysis into a shareable document.