42 Strategy Consulting Agents for Claude, Insight to Impact

Use when: You need a defensible size for the opportunity

Output: A sized market with top-down and bottom-up reconciliation

Use when: You need to see who competes and how they win

Output: A competitor map with positioning and likely moves

Use when: Decisions rest on assumptions about customers

Output: A customer insight synthesis of needs, drivers, and evidence

Use when: Leadership is debating symptoms, not the real problem

Output: A diagnosis of the core issue with an evidence-backed issue tree

Use when: Growth has stalled or lacks a clear source

Output: A ranked set of growth pathways with the case for each

Use when: Capital and attention are spread across too many bets

Output: A portfolio view with invest, hold, and exit calls

Use when: How the business creates and captures value must change

Output: A business model design across value creation and capture

Use when: The future is uncertain and one forecast is not enough

Output: Named scenarios on a two-axis matrix with signposts

Use when: The strategy needs sequencing into a credible path

Output: A phased roadmap with horizons, owners, and gates

Use when: One-size targeting is failing across different buyers

Output: Needs-based segments with size, value, and priority

Use when: The offer does not connect to what customers value

Output: A value proposition mapped to jobs, pains, and gains

Use when: Pricing power, packaging, or discounting is unclear

Output: A pricing recommendation with willingness-to-pay logic

Use when: An offer needs a coherent route to the customer

Output: A go-to-market plan across motion, funnel, and metrics

Use when: You must choose how to reach and serve buyers

Output: A channel mix with economics and coverage logic

Use when: Growth ambition needs concrete, sized initiatives

Output: A ranked initiative set with value and effort

Use when: Strategy has no clear way of getting done

Output: An operating model across process, people, and structure

Use when: The structure fights the strategy

Output: An org design with spans, layers, and accountabilities

Use when: You must know what the organization can actually do

Output: A capability map with maturity levels and gaps

Use when: Talent supply does not match the strategy's demands

Output: A workforce plan across build, buy, and borrow

Use when: Decisions stall because no one owns them

Output: A governance model with forums, cadence, and decision rights

Use when: A transformation needs a spine to run on

Output: A transformation office design with cadence and value tracking

Use when: The cost base must come down without breaking delivery

Output: A cost baseline with sized savings levers

Use when: A core process is slow, costly, or error-prone

Output: A redesigned process with waste removed and handoffs fixed

Use when: Metrics are noisy, lagging, or gamed

Output: A KPI tree of leading and lagging measures tied to decisions

Use when: Promised benefits must be proven, not assumed

Output: A benefits ledger tracking committed value to the P and L

Use when: A change could stall on people rather than plan

Output: A change plan with readiness, actions, and adoption measures

Use when: Digital investment lacks a value-linked plan

Output: A digital strategy tied to value pools and maturity

Use when: Data and AI ambition needs structure and focus

Output: A data and AI strategy across value, foundations, and governance

Use when: Technology work needs sequencing against dependencies

Output: A technology roadmap with sequencing and dependencies

Use when: Use-case ideas are everywhere and focus is missing

Output: A prioritized use-case portfolio with value and feasibility

Use when: Innovation spend lacks balance and a clear thesis

Output: An innovation portfolio balanced across horizons

Use when: Many workstreams and partners must stay aligned

Output: A workstream map with owners, interfaces, and dependencies

Use when: A programme needs a credible schedule to delivery

Output: A programme timeline with milestones and the critical path

Use when: Risks and cross-team dependencies threaten delivery

Output: A risk and dependency register with owners and mitigations

Use when: Client-facing deliverables must meet a consistent bar

Output: A QA checklist and review log for every deliverable

Use when: Too many initiatives compete for the same capacity

Output: A ranked roadmap with an explicit stop list

Use when: A decision needs economics, risks, and sensitivities

Output: A business case with costs, benefits, and payback

Use when: A decision must become sequenced, owned execution

Output: An implementation plan with phases, owners, and first 90 days

Use when: The recommendation must survive the room

Output: A stakeholder map with a pre-wiring engagement plan

Use when: Execution needs a regular, honest performance view

Output: A performance dashboard design with review cadence

Use when: Benefits must be captured after go-live, not assumed

Output: A value realization plan with owners and tracking to run rate

Use when: Capability must stay with the client after the team leaves

Output: A knowledge transfer plan with artifacts and capability handover