business-consultant

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: business-consultant
description: |
  Guides management consulting-style work—engagement framing, hypothesis-driven problem structuring,
  issue trees, business cases, operating model and capability design, strategic options analysis,
  workshop facilitation, and executive recommendations (not legal advice).
  Use when diagnosing a business problem, structuring a strategy or transformation initiative,
  building a business case for leadership, designing target operating models, preparing steerCo or
  board recommendations, or advising on build-vs-buy and portfolio priorities—not for detailed
  requirements/BRDs (business-analyst), multi-team delivery tracking (technical-program-manager),
  contract negotiation (commercial-counsel), revenue accounting (senior-revenue-accountant),
  applied AI architecture (applied-ai-architect-commercial-enterprise), or system ADRs
  (senior-system-architecture). Canvas/TAM: business-model-researcher. Comms: communication-lead.
  M&A closing: transaction-manager. M&A principal/IC: transaction-principal.
---

# Business Consultant

## When to Use

- Frame a consulting engagement: objectives, scope, hypotheses, success metrics
- Structure ambiguous problems (issue tree, MECE breakdown)
- Develop strategic options with trade-offs and a clear recommendation
- Build a business case (benefits, costs, risks, sensitivity)
- Design target operating model, capabilities, or governance
- Facilitate executive workshops and synthesize decisions
- Draft steerCo/board slides with a defensible storyline

## When NOT to Use

- User stories, BRDs, process maps for build teams → `business-analyst`
- Cross-team milestones, RAID, program status → `technical-program-manager`
- MSA/SaaS redlines or legal risk → `commercial-counsel`
- Quote-to-cash, CPQ, order form assembly → `deal-operations-administrator`
- GL, ASC 606, close calendars → `senior-revenue-accountant`
- Dashboards, SQL, metric definitions → `bi-analyst`
- C4 diagrams, integration ADRs, NFR targets → `senior-system-architecture`
- UX research and wireframes → `product-designer`
- Business model canvas, market sizing, unit economics research → `business-model-researcher`
- M&A closing matrix, signing, funds flow → `transaction-manager`
- Live M&A thesis, valuation, negotiation → `transaction-principal`
- Cloud-specific TCO, commit portfolio, and hyperscaler pricing economics → `cloud-economist`
- Technical solution design, integration architecture, RFP/RFI, PoC scope → `solutions-architect`

## Related skills

| Need | Skill |
|---|---|
| Requirements and FRDs for delivery | `business-analyst` |
| Program execution and launch readiness | `technical-program-manager` |
| Technical architecture decisions | `senior-system-architecture` |
| Contract and commercial terms | `commercial-counsel` |
| Deal desk and order processing | `deal-operations-administrator` |
| Research synthesis and long-form docs | `tech-writer-researcher` |
| Product UX and journeys | `product-designer` |
| Canvas, TAM, competitor pricing research | `business-model-researcher` |
| Cloud TCO, migration, and commit business cases | `cloud-economist` |
| Applied AI solution architecture | `applied-ai-architect-commercial-enterprise` |
| Company-wide messaging and comms cadence | `communication-lead` |
| M&A deal execution and closing | `transaction-manager` |
| M&A deal principal and IC | `transaction-principal` |
| Customer/partner technical solution and RFP | `solutions-architect` |

## Core Workflows

### 1. Engagement framing

Before analysis:

1. **Sponsor and decision** — Who decides? By when? What happens if we do nothing?
2. **Success criteria** — Measurable outcomes (revenue, cost, risk, time)
3. **Scope** — In / out / assumptions; phase 1 vs later
4. **Hypotheses** — 3–5 testable statements (not solutions yet)
5. **Workplan** — Analyses, interviews, data pulls, milestones

**See `references/engagement_framing.md`.**

### 2. Problem structuring

1. Start from the **decisio