From f1952ea1c0ffca5bbbf9107d2af0996b20503678 Mon Sep 17 00:00:00 2001 From: Anot Date: Fri, 20 Mar 2026 10:09:34 -0400 Subject: [PATCH 1/3] feat: Add management consulting plugin: strategy & analysis skills Plugin scaffolding + five skills covering the front half of consulting work: strategic analysis, financial modeling, proposal development, engagement setup, and engagement pricing. Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude-plugin/marketplace.json | 26 +- .../.claude-plugin/plugin.json | 10 + management-consulting/CLAUDE.md | 26 + management-consulting/README.md | 69 ++ .../skills/engagement-pricing/SKILL.md | 430 ++++++++++ .../skills/engagement-setup/SKILL.md | 650 +++++++++++++++ .../skills/financial-modeling/SKILL.md | 553 +++++++++++++ .../skills/proposal-development/SKILL.md | 775 ++++++++++++++++++ .../skills/strategic-analysis/SKILL.md | 727 ++++++++++++++++ 9 files changed, 3257 insertions(+), 9 deletions(-) create mode 100644 management-consulting/.claude-plugin/plugin.json create mode 100644 management-consulting/CLAUDE.md create mode 100644 management-consulting/README.md create mode 100644 management-consulting/skills/engagement-pricing/SKILL.md create mode 100644 management-consulting/skills/engagement-setup/SKILL.md create mode 100644 management-consulting/skills/financial-modeling/SKILL.md create mode 100644 management-consulting/skills/proposal-development/SKILL.md create mode 100644 management-consulting/skills/strategic-analysis/SKILL.md diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 3fc11f6a..d42fa658 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -65,7 +65,7 @@ { "name": "apollo", "source": "./partner-built/apollo", - "description": "Prospect, enrich leads, and load outreach sequences with Apollo.io — one-click MCP server integration for Claude Code and Cowork.", + "description": "Prospect, enrich leads, and load outreach sequences with Apollo.io \u2014 one-click MCP server integration for Claude Code and Cowork.", "author": { "name": "Apollo.io" } @@ -81,22 +81,22 @@ { "name": "engineering", "source": "./engineering", - "description": "Streamline engineering workflows — standups, code review, architecture decisions, incident response, and technical documentation. Works with your existing tools or standalone." + "description": "Streamline engineering workflows \u2014 standups, code review, architecture decisions, incident response, and technical documentation. Works with your existing tools or standalone." }, { "name": "human-resources", "source": "./human-resources", - "description": "Streamline people operations — recruiting, onboarding, performance reviews, compensation analysis, and policy guidance. Maintain compliance and keep your team running smoothly." + "description": "Streamline people operations \u2014 recruiting, onboarding, performance reviews, compensation analysis, and policy guidance. Maintain compliance and keep your team running smoothly." }, { "name": "design", "source": "./design", - "description": "Accelerate design workflows — critique, design system management, UX writing, accessibility audits, research synthesis, and dev handoff. From exploration to pixel-perfect specs." + "description": "Accelerate design workflows \u2014 critique, design system management, UX writing, accessibility audits, research synthesis, and dev handoff. From exploration to pixel-perfect specs." }, { "name": "operations", "source": "./operations", - "description": "Optimize business operations — vendor management, process documentation, change management, capacity planning, and compliance tracking. Keep your organization running efficiently." + "description": "Optimize business operations \u2014 vendor management, process documentation, change management, capacity planning, and compliance tracking. Keep your organization running efficiently." }, { "name": "brand-voice", @@ -200,7 +200,7 @@ }, { "name": "cockroachdb", - "description": "CockroachDB plugin for Claude Code — explore schemas, write optimized SQL, debug queries, and manage distributed database clusters directly from your AI coding agent.", + "description": "CockroachDB plugin for Claude Code \u2014 explore schemas, write optimized SQL, debug queries, and manage distributed database clusters directly from your AI coding agent.", "source": { "source": "url", "url": "https://github.com/cockroachdb/claude-plugin.git", @@ -240,7 +240,7 @@ }, { "name": "nimble", - "description": "Nimble web data toolkit — search, extract, map, crawl the web and work with structured data agents", + "description": "Nimble web data toolkit \u2014 search, extract, map, crawl the web and work with structured data agents", "source": { "source": "url", "url": "https://github.com/Nimbleway/agent-skills.git", @@ -260,7 +260,7 @@ }, { "name": "searchfit-seo", - "description": "Free AI-powered SEO toolkit — audit websites, plan content strategy, optimize pages, generate schema markup, cluster keywords, and track AI visibility. Works with any website or codebase.", + "description": "Free AI-powered SEO toolkit \u2014 audit websites, plan content strategy, optimize pages, generate schema markup, cluster keywords, and track AI visibility. Works with any website or codebase.", "source": { "source": "url", "url": "https://github.com/searchfit/searchfit-seo.git", @@ -292,7 +292,7 @@ }, { "name": "product-tracking-skills", - "description": "AI agent skills that make SaaS products data-ready for product analytics — from codebase scan to tracking plan to working instrumentation code.", + "description": "AI agent skills that make SaaS products data-ready for product analytics \u2014 from codebase scan to tracking plan to working instrumentation code.", "source": { "source": "url", "url": "https://github.com/Accoil/product-tracking-skills.git", @@ -319,6 +319,14 @@ "url": "https://github.com/figma/mcp-server-guide.git" }, "homepage": "https://github.com/figma/mcp-server-guide" + }, + { + "name": "management-consulting", + "source": "./management-consulting", + "description": "Strategic problem solving, framework analysis, and engagement delivery for management consulting. Covers the full lifecycle from scoping and proposals through implementation and closeout.", + "author": { + "name": "Anot" + } } ] } diff --git a/management-consulting/.claude-plugin/plugin.json b/management-consulting/.claude-plugin/plugin.json new file mode 100644 index 00000000..bb954d41 --- /dev/null +++ b/management-consulting/.claude-plugin/plugin.json @@ -0,0 +1,10 @@ +{ + "name": "management-consulting", + "version": "1.0.0", + "description": "Strategic problem solving, framework analysis, and engagement delivery for management consulting", + "author": { + "name": "Anot" + }, + "repository": "https://github.com/anotb/management-consulting-plugin", + "license": "Apache-2.0" +} diff --git a/management-consulting/CLAUDE.md b/management-consulting/CLAUDE.md new file mode 100644 index 00000000..f5d5bc22 --- /dev/null +++ b/management-consulting/CLAUDE.md @@ -0,0 +1,26 @@ +# Management Consulting Plugin + +Skills for consulting-grade deliverables. These rules apply to all of them. + +## Writing Style + +Write like a senior consultant, not like an AI describing what a senior consultant would write. + +- No em-dashes. Use parentheses or periods instead. +- Vary sentence length. Short sentences land points. Longer ones handle nuance. +- State opinions directly. "This approach failed because..." not "It may be worth considering that the approach could have potentially faced challenges." +- No "not just X, but Y" constructions. Say what it IS. +- Quantify when possible. "Revenue dropped 12%" not "Revenue experienced a significant decline." +- When uncertain, say so plainly: "We don't have enough data to call this yet." +- Go deep where insight lives, light where routine. Not every section deserves equal airtime. +- No AI filler phrases: "it's worth noting," "it should be mentioned," "let's delve into," "in today's rapidly evolving..." + +## Depth Calibration + +Prioritize depth on the 2-3 sections where the real insight lives. Don't give every section equal airtime. If the problem is clearly in one area, go deep there and sketch the rest. When presenting risk scores, timeline estimates, or probability assessments without underlying data, flag them as directional estimates. + +## Content Integrity + +- Ask for information rather than fabricating it. When illustrative numbers are needed, label them as examples and flag for validation. +- Present benchmarks as illustrative, not authoritative. Always note the source and context. +- Never fabricate engagement experience or specific dollar figures. Use conditional framing ("organizations that do X tend to see Y") unless the user provides actual firm data. diff --git a/management-consulting/README.md b/management-consulting/README.md new file mode 100644 index 00000000..82e8a8a9 --- /dev/null +++ b/management-consulting/README.md @@ -0,0 +1,69 @@ +# Management Consulting Plugin + +A management consulting plugin primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application — though it also works in Claude Code. Covers the full engagement lifecycle from problem definition through implementation and closeout. Helps with hypothesis-driven analysis, business cases, client deliverables, change management, and project governance. Works with any consulting team — standalone with your input, supercharged when you connect your project tracker, knowledge base, and other tools. + +## Installation + +```bash +claude plugins add knowledge-work-plugins/management-consulting +``` + +## Skills + +Domain knowledge Claude draws on automatically when your work touches consulting topics: + +| Skill | Description | +|---|---| +| `strategic-analysis` | Hypothesis-driven decomposition, issue trees, MECE analysis, and named framework application (Five Forces, PESTLE, 7S, VRIO, etc.) | +| `financial-modeling` | Business case math, ROI/NPV/IRR, sensitivity analysis | +| `client-deliverables` | Consulting reports, executive presentations, top-down structured communication, storylining, data visualization | +| `change-management` | Transformation planning, resistance management, adoption tracking | +| `due-diligence` | Commercial, operational, and strategic assessment | +| `engagement-setup` | Kickoff planning, discovery phase, stakeholder mapping | +| `implementation-planning` | Options evaluation, business cases, roadmaps, implementation plans | +| `org-design` | Operating model and organizational structure design | +| `engagement-pricing` | Pricing consulting engagements: fee structures, rate cards, commercial terms | +| `process-excellence` | DMAIC, value stream mapping, process improvement | +| `project-closeout` | Deliverable handover, lessons learned, transition planning | +| `project-governance` | RACI, steering committees, stage gates, status reporting, risk tracking | +| `proposal-development` | RFP analysis, proposal writing, SOW creation, pitch decks | +| `thought-leadership` | POVs, white papers, case studies, research content | +| `workshop-facilitation` | Workshop design, facilitation techniques, participant engagement | + +## Example Workflows + +### Scoping a new engagement + +Start with the problem. Describe the client situation and what they're asking for: + +``` +A mid-market SaaS company is losing enterprise deals to a competitor. +They want to understand why and what to do about it. +Help me structure the engagement. +``` + +The `strategic-analysis` skill kicks in to build an issue tree and hypotheses. `engagement-setup` helps plan the discovery phase and stakeholder mapping. `proposal-development` can then turn that into a scoped SOW with workstreams, timeline, and pricing. + +### Building a strategic recommendation + +You've done the analysis and need to pull it together: + +``` +We've completed our market analysis for the client's expansion into Southeast Asia. +Here are our findings: [paste or upload data]. +Help me build the recommendation deck. +``` + +`strategic-analysis` structures the analysis (market attractiveness, competitive positioning). `financial-modeling` builds the business case with scenarios. `client-deliverables` shapes the storyline, slide structure, and detailed appendix. + +### Running a transformation programme + +The client has approved the strategy and you're into implementation: + +``` +We're restructuring the client's supply chain operations across 3 regions. +12-month programme, 4 workstreams, steering committee meets monthly. +Help me set up the governance and tracking. +``` + +`project-governance` builds the RACI, stage gates, and reporting cadence. `change-management` maps stakeholder impact and resistance risks. `implementation-planning` lays out the roadmap with dependencies. `workshop-facilitation` helps design the kickoff sessions with regional teams. diff --git a/management-consulting/skills/engagement-pricing/SKILL.md b/management-consulting/skills/engagement-pricing/SKILL.md new file mode 100644 index 00000000..edcf7812 --- /dev/null +++ b/management-consulting/skills/engagement-pricing/SKILL.md @@ -0,0 +1,430 @@ +--- +name: engagement-pricing +description: Price consulting engagements and structure commercial terms. Use when structuring fees (fixed, T&M, value-based, retainer, outcome-based), building rate cards, modeling engagement economics, setting payment terms, analyzing margins, planning discount strategy, or preparing commercial terms for proposals and SOWs. This is about pricing your own consulting work, not helping clients with their product/service pricing strategy. +--- + +# Engagement Pricing + +Structure pricing models, rate cards, engagement economics, and commercial terms for consulting engagements. Balance the firm's margin requirements with competitive positioning and client value delivery. + +## Before You Begin + +Do not build a pricing model with illustrative rates if the user can provide their actual rates. Ask first. If they say they don't have a rate card, help them build one from their cost structure (see Step 2). Only use illustrative ranges as a last resort, and label every number clearly as illustrative. + +Pricing depends entirely on firm-specific economics. Before structuring anything, get real inputs: +- **Rate card**: What is the firm's actual rate card by level? If they don't have one, what are their fully loaded costs per level? (This is the starting point for building one.) At minimum, establish the tier: MBB, Big Four, boutique, independent. +- **Target margins**: What are the target margins for this type of engagement? +- **Competitive context**: Sole source, beauty parade, incumbent relationship? +- **Don't skip this step.** A pricing model built on generic rates looks professional but is functionally useless. The gap between "here's a framework" and "here's your pricing" is the rate card. Get it first. + +--- + +## The Pricing Process + +### Step 1: Assess Engagement Characteristics + +The right pricing model depends on the engagement, not on preference. Understand what you're pricing before deciding how to price it. + +**Engagement factors that drive model selection:** + +| Factor | Assessment Range | Pricing Implication | +|---|---|---| +| Scope clarity | Defined / Fuzzy / Evolving | Clear scope enables fixed fee; fuzzy scope needs T&M or retainer | +| Duration | Weeks / Months / Ongoing | Longer engagements favor retainers or phased fixed fees | +| Deliverables | Tangible / Advisory / Implementation | Tangible deliverables support fixed fee; advisory work suits retainer | +| Risk level | Low / Medium / High | Higher risk warrants premium or risk-sharing model | +| Client relationship | New / Existing / Strategic | Strategic accounts may warrant investment pricing | +| Outcome measurability | Measurable / Partially / Not measurable | Measurable outcomes enable value-based or outcome-based pricing | + +The engagement characteristics above determine which pricing model fits. A clearly scoped, deliverable-driven engagement points toward fixed fee; an evolving advisory relationship points toward retainer or T&M. The table below maps each model to its conditions and risk profile. + +**Pricing model options:** + +| Model | How It Works | Best When | Risk Profile | +|---|---|---|---| +| Time & Materials (T&M) | Bill hours/days at agreed rates | Scope is undefined or evolving; discovery phases; staff augmentation | Low risk to consultant, high to client | +| Fixed Fee | Agreed price for defined scope | Scope is clear and stable; deliverables are concrete; you've done similar work before | High risk to consultant (scope creep), low to client | +| Retainer | Monthly fee for access and availability | Ongoing advisory relationships; predictable recurring needs; strategic accounts | Medium to both sides | +| Value-Based | Fee linked to value delivered | Client outcomes are quantifiable; ROI is clear and large; you can credibly claim attribution | Low risk to consultant if structured well | +| Outcome-Based | Fee tied to achieving specific results | Clear metrics exist; you have significant control over outcomes; client trusts measurement | Shared risk; high upside potential | +| Risk/Reward | Base fee plus performance bonus | Client wants skin in the game; results are measurable; relationship supports transparency | Shared risk; aligns incentives | +| Hybrid | Combine models (e.g., T&M with a cap, fixed fee + success bonus) | Complex engagements with both defined and undefined components | Tailored risk sharing | + +**Model selection logic:** + +Can you define the scope precisely? If yes, lean toward fixed fee. If no, lean toward T&M or retainer. + +Can you measure the value you'll create? If yes, consider value-based or outcome-based pricing, especially if the value is large relative to fees. + +Is this an ongoing relationship? If yes, retainer or hybrid models create stability for both sides. + +### Step 2: Develop the Rate Structure + +Rates are the foundation of every pricing model, even when you don't show them to the client. + +**Rate card development:** + +These ranges vary significantly by firm tier, geography, and specialization. Use them as orientation, not gospel. + +| Level | Daily Rate Range (US Market) | What Drives the Rate | +|---|---|---| +| Partner/Director | $8,000-15,000/day | Client relationship, deal origination, quality assurance, experience premium | +| Principal/Associate Director | $5,500-10,000/day | Workstream leadership, client management, senior problem-solving | +| Manager/Engagement Manager | $3,500-6,500/day | Day-to-day delivery, team management, analysis oversight | +| Senior Consultant | $2,500-4,500/day | Core analytical work, deliverable production, client interaction | +| Consultant | $1,800-3,200/day | Analytical support, research, deliverable drafting | +| Analyst | $1,200-2,200/day | Data gathering, modeling support, research | + +MBB firms (McKinsey, Bain, BCG) price at the top of these ranges or above. Big Four consulting practices sit in the middle. Boutique and specialized firms span the full range depending on niche premium. Independent consultants typically price 20-40% below firm rates but keep a much higher share. + +Offshore/nearshore delivery typically runs 40-60% of onshore rates for equivalent levels. Blending onshore leadership with offshore execution is a common margin play. + +Once the rate card is established, calibrate it against these factors. Rates aren't set in isolation; they shift based on context, competition, and the specific engagement. + +**Rate determination factors:** + +| Factor | Direction | Rationale | +|---|---|---| +| Market rates | Benchmark | What competitors charge for comparable work | +| Specialization premium | Up | Scarce expertise commands higher rates | +| Relationship/volume | Down | Strategic accounts and large commitments earn discounts | +| Scope certainty | Up for uncertain | Risk premium for poorly defined work | +| Urgency | Up | Timeline pressure warrants premium | +| Location/delivery model | Variable | On-site typically higher than remote; offshore lower | +| Competitive pressure | Down | If the client has alternatives, rates may flex | + +**Team composition and leverage:** + +The team mix drives both cost and perceived value. Higher partner/principal involvement signals seniority but raises fees. Higher analyst/consultant leverage reduces fees but may concern clients about junior staffing. + +Illustrative leverage ratios for firms with a Partner/Manager/Consultant tier structure. Team composition should be driven by the engagement's specific needs. + +| Engagement Type | Partner:Manager:Consultant Ratio | Rationale | +|---|---|---| +| Strategy | 1:1:2 | High-judgment work, senior-heavy | +| Operations improvement | 1:2:4 | Process work, more execution-heavy | +| Implementation | 1:3:6 | Execution-intensive, more junior resource | +| Due diligence | 1:1:3 | Time-pressured, analytical | +| Advisory retainer | 1:1:1 | Senior-focused, relationship-driven | + +### Pricing by Engagement Type + +Different engagement types carry different economics. Use these as starting orientation. + +| Engagement Type | Typical Fee Range | Typical Duration | Pricing Model | Key Consideration | +|---|---|---|---|---| +| Commercial due diligence (CDD) | $150K-$500K | 3-6 weeks | Fixed fee | Compressed timeline = premium pricing. No room for overruns; price in contingency. Scope is relatively standardized. | +| Strategy review | $300K-$1.5M | 6-12 weeks | Fixed fee or T&M with cap | Senior-heavy team drives cost. Value is in judgment, not volume. | +| Operational improvement | $500K-$3M | 12-26 weeks | Phased fixed fee or hybrid | Phase 1 diagnostic creates Phase 2 implementation scope. Land-and-expand economics apply. | +| Implementation / transformation | $1M-$10M+ | 6-18 months | T&M or fixed fee per workstream | Long duration creates rate pressure from procurement. Lock in rates for the program term. | +| Expert advisory / second opinion | $50K-$200K | 1-4 weeks | Fixed fee or day rate | Partner-only delivery. Price the expertise, not the hours. | + +**CDD-specific note**: PE firms buying CDD on compressed timelines (2-4 weeks) will pay a premium, but they also expect standardized outputs. Build a reusable CDD template to reduce delivery cost and protect margin. Repeat CDD clients (PE firms doing 5-10 deals/year) expect volume discounts of 10-15% in exchange for deal flow. + +### Step 3: Model Engagement Economics + +Build the cost model to understand your margins before you price. + +**Direct costs:** + +| Category | What to Include | +|---|---| +| Personnel | Fully loaded cost of team time (salary + benefits + overhead, not billing rate) | +| Travel | Flights, hotels, meals, ground transport (if on-site) | +| Third-party costs | Licensed data, specialist subcontractors, tools, software | +| Materials | Printing, production costs for deliverables | + +**Indirect costs and overhead:** + +These ranges vary significantly by firm size, geography, and operating model. Use your firm's actual cost data. + +| Category | Illustrative Range | +|---|---| +| Firm overhead allocation | 15-30% of direct personnel cost | +| Business development cost | 5-10% (the cost of winning the work) | +| Risk contingency | 5-15% depending on scope certainty | + +**Margin analysis:** + +| Metric | What It Tells You | +|---|---| +| Gross margin (fee minus direct cost) | Whether the engagement covers its direct costs with room to spare | +| Contribution margin (fee minus all allocated costs) | Whether the engagement contributes to firm profitability | +| Realization rate (actual fee / standard rate card value) | How much of your rate card you're actually capturing | +| Effective daily rate (total fee / total days worked) | What you're actually earning per day across the team | + +Margins vary significantly by firm size, market, and service type. Establish your firm's target range based on your cost structure. As a starting point for discussion (not benchmarks): +- Gross margin below 40% is often a warning sign (illustrative) +- Gross margin of 50-65% is healthy for many consulting firms (illustrative) +- Gross margin above 70% may suggest underinvestment in the engagement (illustrative) + +### Step 4: Structure Commercial Terms + +Commercial terms are where pricing meets contracting. Get these wrong and a well-priced engagement still loses money. + +**Payment structure options:** + +| Structure | When to Use | +|---|---| +| Monthly invoicing | T&M engagements; straightforward, predictable | +| Milestone-based | Fixed fee engagements; ties payment to deliverable acceptance | +| Upfront + milestones | New clients or large engagements; reduces payment risk | +| Monthly retainer | Retainer models; predictable for both sides | +| Outcome-triggered | Value/outcome-based; payment when results are achieved | + +**Payment schedule design:** + +For fixed-fee or milestone-based engagements, front-load payments to match your cost profile. You incur most costs early (team ramp-up, research, analysis); your payment schedule should reflect that. + +An illustrative schedule: +- 20-30% at contract signature or kickoff +- 30-40% at interim milestones (spread across 1-2 milestones) +- 30-40% at final deliverable acceptance + +Consider limiting final acceptance payments to manage cash flow risk. The appropriate split depends on engagement duration, client creditworthiness, and contractual norms. + +**Standard commercial terms:** + +| Term | Standard Position | Negotiation Notes | +|---|---|---| +| Payment terms | Net 30 | Push back on Net 60+; it's a financing cost you're absorbing | +| Expense policy | Reimbursed at cost, pre-approved | Cap expenses as a % of fees if the client insists | +| Intellectual property | Client owns client-specific work product; firm retains methodologies and tools | Non-negotiable on methodology; flexible on work product | +| Confidentiality | Mutual NDA | Standard; rarely contentious | +| Liability cap | Capped at a multiple of fees (varies by jurisdiction and client type; consult legal counsel) | Don't accept unlimited liability | +| Termination | 30-day notice; payment for work completed | Protect against sudden termination; include kill fee for fixed-fee work | +| Scope changes | Written change order process with pricing | Essential for fixed-fee; protects against scope creep | + +**IP and licensing considerations:** + +For engagements involving proprietary tools, models, or software: +- License vs. transfer: License your tools for use; don't transfer ownership +- Usage rights: Define whether the client can use deliverables internally only or share with affiliates +- Derivative works: Clarify who owns improvements built on your methodology +- Pricing IP access: License fees can be structured as one-time (typically 15-30% of engagement fee), annual subscription (5-15% of engagement fee per year), or per-user/per-use +- Platform or tool access bundled with advisory: price the advisory work normally and add the tool access as a separate line item with its own renewal terms + +### Step 5: Discount and Negotiation Strategy + +Every engagement involves negotiation. Have a strategy before you enter the room. + +**Discount types and when to use them:** + +These are directional. Your discount strategy should reflect your margin analysis and competitive position. Read the discount ranges below in context of your walk-away margin; a 15% volume discount is sensible if you're starting from 60% gross margin but dangerous if you're at 42%. + +| Discount Type | Illustrative Range | Justification | +|---|---|---| +| Volume | 5-15% | Multiple engagements or large scope commitment | +| Relationship/strategic | 5-10% | Long-term partnership, reference client, marquee logo | +| Early payment | 2-5% | Payment within 10-15 days (a genuine financing benefit to you) | +| Competitive | 5-10% | When you need to win and the client has credible alternatives | +| Pilot/land-and-expand | 10-20% | First engagement priced to win, with expansion opportunity | + +**Negotiation principles:** + +- **Know your walk-away point** before you start. Calculate the minimum fee that delivers acceptable margin. Below that, you're buying the work, not winning it. +- **Never discount without getting something back.** Longer commitment, faster payment, case study rights, reference-ability, expanded scope. +- **Discount the total, not the rates.** Cutting your rate card devalues your people. Instead, reduce hours, adjust team composition, narrow scope, or provide a lump-sum discount. Protect the rate card. +- **Show value first, price second.** If the client is focused on fee before they understand value, you're in a cost negotiation, not a value conversation. +- **Use anchoring.** Present your recommended option alongside a higher-priced premium option and a stripped-down economy option. The middle option looks reasonable by comparison. + +**Navigating procurement:** + +Fortune 500 procurement teams are professional negotiators. They are not your buyer; they are the gatekeeper between you and your buyer. Different game, different tactics. + +| Procurement Tactic | What They're Doing | How to Respond | +|---|---|---| +| Rate benchmarking | Comparing your rates against their database (often outdated or mismatched by scope) | Shift the conversation from rates to total cost of engagement and outcomes. "Our rate is $X but the engagement is 8 weeks, not 12, because we've done this 15 times." | +| Demand for rate card | Want line-item visibility to negotiate each level down | Provide a rate card but price the engagement as a fixed fee or blended rate. Protect individual rates. | +| Three-bid requirement | Need competitive quotes to justify selection | Help your sponsor write the requirements in a way that plays to your strengths. Offer to respond to a directed RFP. | +| Preferred vendor panel | Only buy from approved vendors; getting on takes 3-6 months | Start the panel process early (before you need it). Use a small initial engagement to get in the door. | +| Payment terms push (Net 60/90) | Standard policy; they do it to everyone | Price it in. Net 90 costs you roughly 2-3% in financing. Either add that to the fee or negotiate payment milestones that front-load cash flow. | +| Scope unbundling | Break the engagement into pieces to commoditize and bid separately | Resist unless the pieces genuinely can stand alone. Explain integration risk and coordination cost of splitting. | +| Year-end budget pressure | "We need to spend by December 31 or lose the budget" | Accommodate timing but don't discount for urgency that benefits the client. This is leverage, not a concession. | + +Key principle with procurement: maintain a direct relationship with the business sponsor throughout. Procurement can negotiate terms, but the sponsor controls the decision. If procurement is negotiating without sponsor involvement, you're in trouble. + +### Beauty Parade Strategy (Competitive Bake-Offs) + +When a client is comparing 4-5 firms simultaneously (common for large transformations and strategy reviews), pricing is only one dimension of differentiation. + +**What the client is actually evaluating**: team quality and chemistry, understanding of their specific situation, credibility of approach, and price. In that order. Most firms lose beauty parades on the first two, not the last one. + +**Pricing tactics for beauty parades**: +- **Don't bid lowest.** Clients rarely pick the cheapest option in a beauty parade. Being cheapest signals you're not in the same tier. Being most expensive is risky unless your brand justifies it. Target the middle-to-upper range. +- **Differentiate on structure, not rate.** Offer a pricing model the others won't (outcome-based component, phased commitment, skin-in-the-game element). Structural creativity is more memorable than a 5% rate difference. +- **Include an "only we can do this" element.** Proprietary data, a named expert, a relevant case study with results. Something that makes an apples-to-apples comparison impossible. +- **Show the math on value.** If your fee is $1.2M and the projected benefit is $15M, the fee conversation is academic. Make the ROI case explicitly in the proposal. +- **Address the team question directly.** "The team that pitches is the team that delivers." Say it, mean it, put the names in the contract. + +**Post-presentation follow-up**: Within 24 hours, send a concise note addressing the 2-3 questions where you felt your answer was weakest. This demonstrates self-awareness and follow-through, traits clients value in an advisory relationship. + +### Public Sector Pricing + +Government and public sector engagements operate under fundamentally different rules. Ignoring these leads to disqualification, not just lost deals. + +**Key constraints**: + +| Constraint | Implication | +|---|---| +| Published rate ceilings (GSA schedule, Crown Commercial Service frameworks) | Your commercial rates may exceed allowable maximums. Build a public sector rate card. | +| Cost-plus or labor-hour contracts | Margin is capped (typically 10-15% for cost-plus). Volume and utilization become the margin levers, not rate. | +| Competitive bidding requirements | Sole-source is the exception. Proposals are scored on published criteria. Price is typically 20-30% of the evaluation weight. | +| LPTA (Lowest Price Technically Acceptable) | Some procurements select the cheapest bid that meets minimum requirements. If LPTA applies, either bid aggressively or don't bid. There is no middle ground. | +| Period of performance and option years | Base year + option years is standard. Price option years with modest escalation (2-3%). Aggressive option-year pricing can win the base year but erode margin later. | +| Subcontracting requirements | Small business subcontracting goals (often 20-30% of contract value) are mandatory on large contracts. Build these into the cost model. | +| Audit rights | Government contracts include audit provisions. Your cost structure must be defensible under DCAA or equivalent audit standards. | + +**Practical guidance**: If public sector is a meaningful revenue stream, invest in a contracts and pricing function that understands FAR/DFARS (US), Cabinet Office guidelines (UK), or equivalent local regulations. Getting this wrong creates legal risk, not just commercial risk. + +**Pricing sensitivity analysis:** + +Before presenting any fee, model the economics under three scenarios. This isn't academic; it's your preparation for the negotiation. Know in advance what each concession costs you. + +| Scenario | Assumptions | Fee | Margin | +|---|---|---|---| +| Base case | Scope as defined, standard team, no complications | Target fee | Target margin | +| Upside | Scope expands, additional phases, premium positioning | Higher fee | Higher margin | +| Downside | Scope narrows, competitive pressure, discount applied | Floor fee | Minimum acceptable margin | + +### Step 6: Build the Value Case + +For any engagement above commodity rates, you need a value story. Clients buy outcomes, not inputs. + +**Value quantification framework:** + +| Value Driver | How to Measure | Example | +|---|---|---| +| Cost reduction | Current cost minus future cost | Process improvement saves $2M/year in labor | +| Revenue increase | Incremental revenue attributable to engagement | Pricing optimization adds $5M in annual revenue | +| Risk reduction | Expected loss avoided or probability reduced | Compliance program reduces expected regulatory fines | +| Speed to market | Value of time saved | Launching 3 months earlier captures $3M in first-mover revenue | +| Capability building | Cost of alternative capability development | Building internal team would cost $4M and take 18 months | + +Once the value drivers are quantified, decide how to share that value with the client. The model you choose signals your confidence in the value estimate and shapes the fee conversation. + +**Value-sharing models:** + +| Approach | Structure | When It Works | +|---|---|---| +| Percentage of value | Fee = X% of quantified benefit | Value is large, measurable, and clearly attributable | +| Tiered sharing | Lower % on first tranche, higher on upside | Aligns incentives as value grows | +| Base + bonus | Fixed base fee plus bonus for exceeding targets | Client wants cost certainty with performance alignment | +| Gainsharing | Fee funded from realized savings | Cost reduction engagements with measurable baseline | + +**ROI presentation:** + +Present the client's investment case clearly: +- Their investment (your fee) +- Expected return (quantified benefits) +- ROI ratio (benefits / fee) +- Payback period (when benefits exceed fees) +- Confidence level (how certain are the estimates) + +### Step 7: Proposal Fee Presentation + +How you present pricing in the proposal matters as much as the pricing itself. Poorly presented fees create objections that well-structured fees avoid. + +**Fee presentation structure:** + +1. **Value context first**: Before any numbers appear, restate the business case. "This engagement will deliver $8-12M in annual run-rate savings" sets the frame before "$1.2M in fees" appears. + +2. **Options table**: Present 2-3 options, not one take-it-or-leave-it number. + +| Element | Option A (Recommended) | Option B (Comprehensive) | Option C (Focused) | +|---|---|---|---| +| Scope | Core transformation + pilot | Core + full rollout + capability building | Diagnostic + recommendations only | +| Duration | 16 weeks | 24 weeks | 8 weeks | +| Team | 4 FTE | 6 FTE | 2 FTE | +| Fee | $1.2M | $1.8M | $480K | +| Expected ROI | 7-10x | 8-12x | N/A (diagnostic) | + +Option A is always the one you want them to buy. Option B makes A look reasonable. Option C exists so they don't feel cornered, but it should be clearly inferior on ROI. + +3. **Fee breakdown**: Show enough detail to demonstrate rigor without inviting line-item negotiation. By phase or workstream, not by person-by-person rate card. + +4. **What's included / excluded**: Be explicit. Travel, expenses, third-party data, licensing fees. Ambiguity here creates post-sale conflict. + +5. **Investment framing**: "Total investment of $1.2M" not "Our fees are $1.2M." Small language choice, meaningful difference in how it lands. + +--- + +## Multi-Workstream and Program Pricing + +Large engagements spanning multiple workstreams or running as multi-phase programs need pricing structures beyond single-engagement models. + +**Program pricing considerations:** + +| Element | Single Engagement | Multi-Workstream Program | +|---|---|---| +| Pricing unit | One fee for one scope | Master agreement with workstream-level SOWs | +| Discounting | Engagement-level | Program-level volume discount (typically 10-20% on aggregate) | +| Team continuity | Priced per engagement | Premium for guaranteed team continuity across phases | +| Governance overhead | Included in fee | Price program management separately (typically 8-12% of total program cost) | +| Risk | Scope-specific | Portfolio risk; some workstreams may subsidize others | + +**Master Service Agreement (MSA) + SOW model:** + +For programs expected to run 6+ months with multiple workstreams: +- Negotiate the MSA once (rates, terms, IP, liability) +- Issue individual SOWs per workstream or phase +- Apply volume discounts at the MSA level based on aggregate commitment +- Include a "ramp-down" provision: if the client cuts scope mid-program, rates adjust upward to account for lost volume discount + +**Phased engagement economics (land-and-expand):** + +Phase 1 (diagnostic or pilot) is often priced at or below target margin to win the work. The economics only work if Phase 2+ materializes. + +| Phase | Typical Pricing Approach | Margin Target | Purpose | +|---|---|---|---| +| Phase 1: Diagnostic / Assessment | Fixed fee, often discounted 15-25% | 35-45% (below normal) | Prove value, build trust, shape Phase 2 scope | +| Phase 2: Design / Pilot | Fixed fee or hybrid | 50-60% (target) | Deliver core value, demonstrate results | +| Phase 3: Implementation / Rollout | T&M or fixed fee per workstream | 55-65% (above target) | Scale what works, capture full value | + +Rules for land-and-expand pricing: +- Phase 1 must generate findings that create urgency for Phase 2. If the diagnostic could conclude "everything's fine," don't discount it. +- Price Phase 1 so you'd still break even if Phase 2 never happens. Don't bet the engagement economics on expansion. +- Include a "Phase 2 pricing framework" in the Phase 1 proposal so the client knows what to expect and procurement doesn't reset the negotiation. +- Track your land-and-expand conversion rate. If less than 60% of Phase 1s convert to Phase 2, your Phase 1 pricing is too aggressive or your Phase 1 delivery isn't compelling enough. + +--- + +## Retainer Structures + +Retainers deserve specific attention because they're the most relationship-dependent model. + +**Retainer design:** + +| Element | What to Define | +|---|---| +| Monthly fee | Fixed amount, usually based on expected hours x blended rate | +| Hours included | Specify a range or minimum/maximum | +| Rollover policy | Do unused hours carry forward? (Usually no, or capped) | +| Overage rate | Rate for hours beyond the included amount | +| Scope boundaries | What's in-scope vs. what triggers a separate engagement | +| Review period | When to reassess the retainer level (quarterly is typical) | +| Termination notice | Usually 30-60 days | + +**Tier structures:** + +| Tier | Positioning | Typical Includes | +|---|---|---| +| Advisory | Senior access, strategic guidance | Partner/principal hours, limited deliverables | +| Standard | Ongoing project support | Mixed team, regular deliverables, monthly check-ins | +| Embedded | Team augmentation, continuous delivery | Dedicated resources, sprint-based delivery, daily interaction | + +--- + +## Key Principles + +- Price for value, not for cost. Your cost structure informs your floor, not your ceiling. +- Protect your rate card. Discount the deal, not the rates. Once rates drop, they rarely recover. +- Understand the client's buying process. Know who approves, what budget exists, what alternatives they're considering, and what procurement will challenge. +- Every pricing decision is a margin decision. Model the economics before you quote. +- Document all assumptions. Pricing disputes almost always trace back to unstated assumptions about scope, effort, or deliverables. +- Build in scope change mechanisms. Fixed-fee engagements without change order processes are blank checks. +- Know your walk-away point. Not every engagement is worth winning. Unprofitable work is worse than no work. +- Align payment timing with cost timing. Don't finance the engagement for the client. +- The best pricing strategy is one the client feels good about. If they feel squeezed, the relationship suffers even if you win the deal. +- Retainers only work with trust. Don't propose retainers to new clients who haven't seen your work yet. +- Procurement is a process, not a person. Understand the system and work within it, but never lose your direct line to the business sponsor. diff --git a/management-consulting/skills/engagement-setup/SKILL.md b/management-consulting/skills/engagement-setup/SKILL.md new file mode 100644 index 00000000..a13a54d1 --- /dev/null +++ b/management-consulting/skills/engagement-setup/SKILL.md @@ -0,0 +1,650 @@ +--- +name: engagement-setup +description: Guide the first weeks of a consulting engagement from contract signature through a running project. Covers sales-to-delivery transition, kickoff workshop design, discovery phase planning, stakeholder mapping, and standing up workstreams and cadences. Use when launching a new engagement, onboarding a new client, or resetting a stalled project. +--- + +# Engagement Setup + +Take a consulting engagement from "we just won this work" to "the engagement is running." This covers five things that happen roughly in sequence but overlap in practice: transitioning from sales to delivery, planning the kickoff, mapping stakeholders, designing discovery, and establishing the operating rhythm. + +The goal is shared understanding and momentum, not a stack of templates. Every artifact here should earn its place by driving alignment or unblocking work. + +## Before You Begin + +This skill naturally prompts for information at each phase, but confirm these basics early: +- What was the scope sold (SOW or proposal available)? +- Who is the client sponsor and key stakeholders? +- What is the timeline and team composition? +- Don't generate stakeholder names, political dynamics, or engagement history. Ask the user for these details rather than guessing. + +## Phase 0: Sales-to-Delivery Transition + +The gap between "we won" and "we start" is where engagements get scoped wrong. Before you do anything else, understand what was sold. + +### What Did the Partner Promise? + +Interview the sales lead (partner, BD lead, whoever ran the pursuit). Ask: + +1. What did the client hear that isn't in the SOW? (There is always something.) +2. What concerns did the client raise during the sales process that we need to address early? +3. Who was the real champion? Who was skeptical? +4. Were there scope items the client wanted that we pushed out? They'll bring them back. +5. Is there a political dynamic we should know about? (Reorgs, competing initiatives, executive changes.) +6. What's the client's emotional state? Excited, nervous, resigned, skeptical? + +### SOW Reality Check + +Read the SOW. Read the proposal. Compare them. Common gaps: + +- Proposal describes a broader vision; SOW scopes a narrower engagement. Client may expect the vision. +- Timeline in the SOW assumes immediate start and full client availability. Neither is guaranteed. +- Team composition in the proposal may not match who's actually available for staffing. +- Deliverables described at different levels of specificity in each document. + +Flag any gaps and resolve with the partner before kickoff. Do not discover these gaps in front of the client. + +### Day 1 Checklist + +The 10 things you do on literal Day 1 after winning the work. Day 1 is chaotic and things get missed. + +1. Confirm the project sponsor and get their direct contact info +2. Set up the engagement code, billing structure, and time tracking +3. Create the shared drive / workspace with a folder structure +4. Draft the data request (don't wait until after kickoff) +5. Schedule the kickoff (aim for within 5-7 business days of contract signature) +6. Pull all prior work your firm has done with this client +7. Review the SOW and proposal side-by-side (see above) +8. Identify and brief your core team +9. Draft the stakeholder list from what you know; plan to complete it +10. Send the client a "we're excited to get started" note with kickoff logistics and pre-read materials + +### Practical Logistics + +The stuff that feels administrative but will block real work if you don't handle it early. Start all of this on Day 1; some items take weeks to come through. + +**Physical and system access:** + +| Item | Who to Ask | Typical Lead Time | Workaround if Delayed | +|------|-----------|-------------------|----------------------| +| Building badges / site access | Client facilities or security office | 1-5 days | Have your client lead escort you; get a visitor badge process established | +| Laptops / client devices | Client IT | 1-4 weeks (this is the killer) | Bring your own equipment; work from your firm's systems until client devices arrive | +| VPN / remote access | Client IT | 1-2 weeks | Work on-site; request temporary guest Wi-Fi access | +| System credentials (ERP, BI tools, data warehouses) | Client IT + data owner approval | 1-3 weeks per system | Ask the data owner to pull exports for you while access is pending | +| Email / distribution lists | Client IT | 1-2 weeks | Use your firm email; ask your client lead to forward relevant threads | + +**IT access blocking is extremely common.** Client IT departments have their own priorities and your consulting engagement is not one of them. Assume it will take 2-3x longer than anyone promises. Mitigations: + +- Submit all access requests on Day 1, even before you know exactly what you need. It's easier to cancel a request than to start one late. +- Get your client sponsor to send the IT request (or cc them). A request from a VP moves faster than one from an unknown contractor. +- Identify one person in client IT who actually processes requests and build a relationship with them directly. +- Have a "no-access" plan for the first two weeks. What can the team accomplish using only exported data, interviews, and your own tools? + +**Client document management:** + +Every client has a different system (SharePoint, Google Drive, Box, Confluence, shared drives on a server from 2008). Find out: +- Where do they store project documents? (Not where they say they do... where do they actually look for things?) +- What's the naming convention? (Match theirs, don't impose yours.) +- Who controls permissions? (This person is your new best friend.) +- Is there a document that everyone references but nobody can find? (There always is. Find it early.) + +**Figuring out who actually answers emails:** + +The org chart tells you who has authority. You need to know who has responsiveness. In the first week, identify: +- The EA or admin who controls the sponsor's calendar +- The client project lead's preferred communication channel (some people live in Teams, some in email, some need a phone call) +- Who on the client side actually follows up on action items (this is rarely the most senior person) +- Which client stakeholders are reliably unavailable and need to be worked around + +## Phase 1: Stakeholder Mapping + +Build the stakeholder picture before the kickoff. You need it for invitation lists, interview scheduling, and knowing who can actually make decisions. + +### Stakeholder Identification + +**Internal stakeholders** (client side): + +| Name/Role | Function | Relationship to Initiative | Current Stance | +|-----------|----------|---------------------------|----------------| +| | C-suite / VP / Director / Manager | Sponsor / Decision-maker / Contributor / Affected | Champion / Supporter / Neutral / Skeptic / Opponent | + +**External stakeholders** (partners, regulators, vendors — only if relevant to the engagement): + +| Name/Role | Organization | Relationship | Priority | +|-----------|-------------|--------------|----------| +| | | Client / Regulator / Partner / Vendor | High/Med/Low | + +### Influence-Interest Analysis + +Map everyone on the power-interest grid. This determines your engagement strategy for each person. + +``` + HIGH INTEREST + | + +--------------------+--------------------+ + | | | + | KEEP SATISFIED | MANAGE CLOSELY | + | | | + | Regular updates | Active engagement| + | Address concerns | Co-creation | + | | Regular 1:1s | +HIGH+--------------------+--------------------+ +POWER | + | | | + | MONITOR | KEEP INFORMED | + | | | + | Periodic check | Regular comms | + | Watch for shifts | Feedback loops | + | | Town halls | + +--------------------+--------------------+ + LOW INTEREST +``` + +Score each stakeholder: + +| Stakeholder | Power (1-5) | Interest (1-5) | Quadrant | Strategy | +|-------------|-------------|----------------|----------|----------| +| | | | Manage Closely / Keep Satisfied / Keep Informed / Monitor | | + +### Alignment and Resistance Assessment + +Before kickoff, get a read on where people actually stand versus where you need them. Consolidate stance, resistance type, and influence into one view: + +| Stakeholder | Current Position | Desired Position | Resistance Type | Root Cause | Influenced By | Mitigation | +|-------------|-----------------|------------------|----------------|------------|---------------|------------| +| | Opponent / Skeptic / Neutral / Supporter / Champion | | Rational / Emotional / Political / None | Why they resist | Who sways them | Approach | + +Resistance types matter because they require different responses: +- **Rational**: They have a logical objection. Address it with data and evidence. +- **Emotional**: They fear change, loss of status, or uncertainty. Address with empathy, involvement, and early wins. +- **Political**: The initiative threatens their power base or allies. Address through coalition building and sponsor engagement. + +Map influence networks. Who listens to whom? Where are the informal power centers? The org chart lies about this. + +### Kickoff Materials + +Prepare and share 24-48 hours before the kickoff: + +1. **Agenda** with time blocks and objectives for each section +2. **Project charter template** (to be completed collaboratively, not presented as fait accompli) +3. **Stakeholder map** (sanitized version appropriate for the audience) +4. **Working arrangements draft** for discussion +5. **Expectations document** covering what you need from the client +6. **Initial communication plan** + +## Phase 2: Kickoff Workshop + +The kickoff is about alignment, not information transfer. If people leave with different understandings of the problem, scope, or how you'll work together, the kickoff failed. + +### Agenda Structure + +``` +Part 1: Introduction (15 min) +- Introductions (not just names... roles, what each person cares about) +- Project purpose and background +- Meeting objectives + +Part 2: Problem and Scope (30 min) +- Problem statement (get agreement before moving on) +- Scope boundaries (in-scope and out-of-scope, explicitly) +- Success criteria +- Key constraints + +Part 3: Approach and Plan (30 min) +- Methodology (how you'll work, not a sales pitch) +- Phase structure and milestones +- Timeline overview +- Dependencies and assumptions + +Part 4: Governance (20 min) +- Team roles and decision rights +- Steering committee composition +- Meeting cadence +- Escalation paths + +Part 5: Working Arrangements (15 min) +- Communication protocols +- Document sharing and version control +- Access requirements +- Working styles and norms + +Part 6: Next Steps (10 min) +- Action items with owners and dates +- Next meeting scheduled before anyone leaves +- Open questions parking lot +``` + +**For virtual or hybrid kickoffs:** Plan 25% more time. Use breakout rooms for the Problem and Scope discussion (small groups surface more honest input). Schedule informal 1:1 video calls with key stakeholders in the days following. And for the love of all that is holy, do not run a 2-hour kickoff as a one-way slide presentation over Zoom. + +### Facilitation Principles + +- Set a collaborative tone from the start. You're working with them, not presenting to them. +- Align on the problem before jumping to approach. If you skip this, you'll pay for it later. +- Confirm scope boundaries explicitly. Verbal assumptions become scope disputes. +- Exchange expectations in both directions. What do you need from the client (access, decisions, resources, availability)? What can they expect from you? +- Establish decision rights clearly. Who can approve scope changes? Who resolves disagreements? +- Build personal connections. Engagement success tracks relationship quality more than methodology quality. +- Surface risks early. The kickoff is the safest time to name uncomfortable truths. +- Ensure all decision-makers are present or represented. If the sponsor doesn't show up, you have a problem. + +### Handling Kickoff Misalignment + +Sometimes the kickoff reveals that stakeholders have fundamentally different expectations. The sponsor thinks this is a cost-cutting exercise; the VP of Operations thinks it's a technology modernization. The SOW says one thing; the room says another. + +This is a blocker, not a risk. Do not proceed past Part 2 of the kickoff agenda until alignment exists. Options: + +1. **Pause and align in the room** if the sponsor has authority and willingness to resolve it live +2. **Park it and schedule a resolution meeting** within 48 hours with only the disagreeing parties and the sponsor +3. **Escalate to the partner** if the misalignment implies the SOW needs rework + +The worst thing you can do is proceed as if alignment exists when it doesn't. You'll build the wrong thing and discover it in Week 6. + +### Project Charter + +Complete this collaboratively during the kickoff. It's the contract between the team on what you're doing and how. + +``` +Project Charter: [Project Name] + +1. PROJECT OVERVIEW + +Background: +[Why this project exists] + +Problem Statement: +[What problem you're solving] + +Objectives: +| Objective | Success Metric | +|-----------|----------------| +| | How you'll measure it | + +2. SCOPE + +In Scope: +- [Deliverable or activity] + +Out of Scope: +- [Explicit exclusion] + +3. TIMELINE + +| Milestone | Target Date | +|-----------|-------------| +| Kickoff | | +| Discovery complete | | +| Analysis complete | | +| Recommendations | | +| Final delivery | | + +4. GOVERNANCE + +Core Team: +| Role | Name | Organization | +|------|------|--------------| +| Project Sponsor | | Client | +| Project Lead | | Client | +| Engagement Manager | | Firm | + +Steering Committee: +| Member | Role | Responsibility | +|--------|------|----------------| +| | | Strategic decisions | + +Meeting Cadence: +| Meeting | Frequency | Attendees | +|---------|-----------|-----------| +| Steering Committee | Monthly | Sponsor, Partner | +| Project Team | Weekly | Core team | +| Status Update | Bi-weekly | Extended team | + +5. RISKS AND DEPENDENCIES + +| Risk | Impact | Mitigation | +|------|--------|------------| +| | H/M/L | | + +Dependencies: +- [Dependency] + +6. COMMUNICATION PLAN + +| Audience | What | How | When | +|----------|------|-----|------| +| Steering Committee | Status, decisions | Meeting + email | Monthly | +| Extended Team | Updates | Email | Weekly | +| Working Team | Day-to-day | Slack/Teams | Daily | + +7. SIGN-OFF + +| Role | Name | Date | +|------|------|------| +| Client Sponsor | | | +| Firm Partner | | | +| Engagement Manager | | | +``` + +## Phase 3: Discovery Design + +Discovery starts immediately after kickoff (often in the same week). The goal is understanding the current state deeply enough to form hypotheses worth testing. + +### Hypothesis-Driven Discovery + +Don't go into discovery with a blank slate. Enter with 2-3 initial hypotheses about what you'll find and what the answer might be. These come from the proposal, the sales process, industry pattern matching, and your experience. + +``` +Hypothesis 1: [Statement of what you believe is true] +Confidence: [Low / Medium / High] +Key test: [What evidence would confirm or disconfirm this?] +If wrong: [How does this change the engagement direction?] + +Hypothesis 2: [...] +``` + +The point is NOT to confirm your hypotheses. It's to have a structure for listening. Hypotheses give you a framework to be surprised against. If every interview confirms what you already thought, you weren't listening — you were auditing. + +### Discovery Plan + +Design the approach based on what you need to learn: + +| Method | Purpose | Participants | Timing | +|--------|---------|--------------|--------| +| Executive interviews | Strategic context, priorities, political landscape | C-suite, senior leaders | Week 1 | +| Working sessions | Detailed requirements, process understanding | Middle management, subject matter experts | Week 1-2 | +| Data review | Quantitative baseline, trend analysis | N/A (analyst work) | Week 1-2 | +| Process observation | See how work actually happens (not how people describe it) | Operations, front-line staff | Week 2 | +| Survey | Broad feedback, validate interview themes at scale | Organization-wide | Week 2 | + +### Interview Guides + +#### Executive Interviews (45 min) + +**Opening (5 min)** +- Thank participant, explain purpose +- Confirm confidentiality (what will and won't be attributed) + +**Strategic Context (15 min)** +1. What is your vision for [area] over the next [X] years? +2. What are the biggest challenges preventing you from achieving this? +3. How does this initiative fit into your strategic priorities? +4. What does success look like for you personally? + +**Current State (15 min)** +5. How would you describe the current state of [area]? +6. What works well that we should preserve? +7. What are the most significant pain points? +8. What has been tried before? What worked and what didn't? + +**Stakeholders and Organization (10 min)** +9. Who are the key people we need to engage? +10. What organizational changes might be needed? +11. What concerns or resistance should we anticipate? +12. What questions should we be asking that we haven't? +13. Anyone else we should speak with? Documents we should review? + +#### Process Interviews (45 min) + +**Process Overview** +1. Walk me through how [process] works today, start to finish +2. What are the key steps and hand-offs? +3. Who is involved at each stage? + +**Pain Points** +4. Where does the most time get spent? +5. Where do errors or rework happen most often? +6. What constraints or bottlenecks exist? + +**Requirements** +7. What would the ideal process look like? +8. What capabilities are must-haves versus nice-to-haves? +9. What systems or tools are critical? + +**Volume and Metrics** +10. How many [transactions/cases/units] per period? +11. What are current cycle times? +12. What metrics are tracked today? Which ones actually drive behavior? + +### Data Request + +Structure your ask clearly. Vague data requests produce vague data. + +| Category | Data Needed | Format | Owner | Due Date | +|----------|-------------|--------|-------|----------| +| Financial | Revenue by segment, cost breakdown | Spreadsheet | CFO office | | +| Operational | Process volumes, cycle times, error rates | Spreadsheet | Ops lead | | +| Organizational | Org chart, headcount by function, role descriptions | Any | HR | | +| Technology | System inventory, integration map | Any | CTO office | | +| External | Market data, competitive benchmarks | Report | Strategy team | | + +If client data is messy or incomplete, provide templates. Don't assume they'll know what format you need. + +### Red Flags During Discovery + +Signs that something is wrong at the structural level, not just the analytical level. These require escalation, not just documentation. + +**Signs the engagement is scoped wrong:** +- Every interviewee describes a different problem than what's in the SOW +- The real problem is upstream or downstream of what you've been asked to look at +- The scope is either far too broad (no way to deliver in the timeline) or too narrow (solving a symptom, not a cause) + +**Signs the real problem isn't what the client thinks:** +- Interviewees at the working level describe a completely different reality than leadership +- The stated problem is actually a solution ("we need a new CRM") masking the real issue ("we have no idea why we're losing customers") +- Data contradicts the narrative. The problem everyone talks about accounts for 5% of the impact + +**Signs the client isn't ready for recommendations:** +- Leadership hasn't agreed on what success looks like +- There's an active reorg or leadership transition that will reset priorities +- The sponsor is leaving, retiring, or being moved to a different role +- Previous consulting engagements produced recommendations that were never implemented + +**Signs discovery is being blocked:** +- Data requests go unfulfilled for more than two weeks +- Key stakeholders are "unavailable" for interviews +- You're being steered away from certain topics or people +- Your client lead is filtering all access + +When you see these, escalate to the engagement manager and partner. These aren't things you fix by working harder. + +### Synthesizing Discovery + +After interviews and data collection, synthesize into findings that drive the next phase: + +``` +Discovery Summary: [Project Name] + +EXECUTIVE SUMMARY +[2-3 paragraphs: what you learned, what it means, what to do next] + +CURRENT STATE ASSESSMENT + +Strengths (preserve these): +- [What works well] + +Pain Points (with root causes, not just symptoms): +- [Pain point: impact and underlying cause] + +Opportunities: +- [Opportunity with estimated impact] + +KEY FINDINGS + +Finding 1: [Title] +Evidence: [Interview quotes, data points] +Implication: [What this means for the engagement] + +QUANTITATIVE HIGHLIGHTS + +| Metric | Current | Benchmark | Gap | +|--------|---------|-----------|-----| +| | | | | + +HYPOTHESIS CHECK + +| Hypothesis | Status | Evidence | Implication | +|-----------|--------|----------|-------------| +| [H1 from pre-discovery] | Confirmed / Partially confirmed / Disconfirmed | [What we found] | [How this changes direction] | + +RISKS IDENTIFIED + +| Risk | Likelihood | Impact | Mitigation | +|------|------------|--------|------------| +| | H/M/L | H/M/L | | + +RECOMMENDATIONS FOR NEXT PHASE +[Where to focus analysis and why] +``` + +**Triangulation discipline:** One person's perspective is an anecdote. Two is interesting. Three perspectives on the same theme is a finding. Note the evidence strength for each finding. + +### Discovery Readout + +The discovery readout is the first major client-facing moment after kickoff. It's where you present what you found, test your hypotheses with the client, and set direction for the next phase. + +**Structure (aim for 45-60 minutes, not 90):** + +``` +1. Recap: What we set out to learn (5 min) +2. What we found: Key findings, organized by theme (20 min) +3. What the data says: Quantitative highlights (10 min) +4. What this means: Implications and initial hypotheses (10 min) +5. Where we go next: Recommended focus areas for analysis (5 min) +6. Discussion (10+ min) +``` + +**Handling findings the client won't want to hear:** +- Lead with findings they'll agree with. Build credibility before delivering hard news +- Use data and direct quotes (anonymized). "We heard from multiple stakeholders that..." is harder to dismiss than "we think..." +- Frame problems as opportunities. "The current process creates a $2M annual rework cost" is more useful than "your process is broken" +- Separate findings from recommendations. Let the findings land before jumping to "here's what you should do" +- If the sponsor previews the readout (which they should), there should be no surprises in the room. Walk the sponsor through difficult findings 24-48 hours before the group readout + +## Phase 4: Standing Up the Engagement + +With kickoff done and discovery underway, establish the operating rhythm that will carry the engagement. + +### Workstream Structure + +For engagements with multiple workstreams, define clearly: + +| Workstream | Lead | Scope | Key Deliverables | Dependencies | +|------------|------|-------|------------------|--------------| +| | | What this workstream covers | What it produces | What it needs from other workstreams | + +### Engagement Cadences + +Set up recurring rhythms immediately. Don't wait for "things to settle." + +| Cadence | Purpose | Frequency | Attendees | Duration | Owner | +|---------|---------|-----------|-----------|----------|-------| +| Daily standup | Coordination, blockers | Daily | Working team | 15 min | Engagement manager | +| Workstream sync | Progress, cross-cutting issues | Weekly | Workstream leads | 30 min | Engagement manager | +| Client status | Progress, decisions needed | Weekly or bi-weekly | Core team + client lead | 45 min | Engagement manager | +| Steering committee | Strategic decisions, escalations | Monthly or milestone-based | Sponsors, partners | 60 min | Partner | +| Team retrospective | Working effectiveness | Bi-weekly or end of phase | Consulting team | 30 min | Team lead | + +**For virtual/hybrid engagements:** Add informal 1:1 check-ins (15 min, weekly) with your key client counterpart. Relationships that build naturally in an office require deliberate effort when remote. Also: agree on camera-on norms, default meeting platform, and "core hours" for real-time collaboration across time zones. + +### Working Arrangements + +Capture the operational details that prevent friction: + +``` +Communication: +- Primary channel: [Slack/Teams/Email] +- Expected response time: [X hours during business hours] +- Status updates: [Format and frequency] +- Escalation: [How and to whom] + +Document Sharing: +- Platform: [SharePoint/Google Drive/Box] +- Folder structure: [Link or description] +- Naming convention: [Convention] +- Version control: [Approach] + +Meetings: +- Default time zone: [TZ] +- Recording policy: [Yes/No/Ask first] +- Notes responsibility: [Who, where stored] +- Decision log: [Where decisions are captured] + +Access Requirements: +- [System/tool needed, who to request from] +- [Building/VPN access] +- [Data access permissions] +``` + +### Engagement Strategy by Stakeholder + +Now that you've mapped stakeholders and run the kickoff, set the ongoing engagement approach: + +| Stakeholder | Objective | Key Messages | Channel | Frequency | Owner | +|-------------|-----------|-------------|---------|-----------|-------| +| | What you need from them | Tailored to their concerns | 1:1 / Meeting / Email | Weekly / Biweekly / Monthly | Team member responsible | + +### Coalition Building + +Identify and activate your champions early: + +| Champion | Sphere of Influence | How to Engage | Support They Need | +|----------|-------------------|---------------|-------------------| +| | Who they can mobilize | Activation approach | Resources / air cover / information | + +Plan quick wins that build credibility: + +| Quick Win | Target Stakeholder | Expected Impact | Timeline | +|-----------|-------------------|-----------------|----------| +| | Who benefits | Credibility / Trust / Proof of value | | + +### Escalation Triggers + +Define what signals trouble and what to do about it: + +| Signal | What It Means | Response | Escalate To | +|--------|--------------|----------|-------------| +| Client sponsor cancels two status meetings | Engagement losing priority | Request 1:1 with sponsor | Partner | +| Data requests unfulfilled after two weeks | Access or willingness problem | Escalate through client lead | Engagement manager | +| Stakeholder actively undermining in meetings | Political resistance | 1:1 conversation to understand concerns | Partner | +| Team members reassigned without notice | Client organization shifting priorities | Assess impact on deliverables; raise in steering committee | Partner | +| Scope discussions in every status meeting | SOW ambiguity or client expectations misaligned | Document scope interpretation; trigger change control if needed | Engagement manager | + +## Principles + +These aren't platitudes. They're the things that separate engagements that work from ones that don't. + +**On the sales-to-delivery transition:** +- Read the SOW before you do anything else. Then read the proposal. Then talk to whoever sold it. In that order. +- The client heard things during the sales process that aren't in any document. Find out what they are before kickoff. +- If the SOW and the client's expectations don't match, fix it now. Week 6 is too late. + +**On kickoffs:** +- Kickoff is about alignment, not information transfer. If you're presenting for 90 minutes, you're doing it wrong. +- Get agreement on the problem before discussing the approach. Skipping this is the most common engagement mistake. +- Confirm your expectations of the client explicitly. Access, decision timelines, team availability. Don't be polite about this. +- Document assumptions. Every undocumented assumption is a future scope dispute. +- Schedule the next meeting before closing. Momentum dies in the gap. +- If the kickoff reveals fundamental disagreement on scope, stop. This is a blocker, not a risk. Resolve it before proceeding. + +**On discovery:** +- Enter with hypotheses. Test them, don't confirm them. If your findings perfectly match your initial hypothesis, you weren't listening. +- Interview more people than you think you need to. Breadth catches what depth misses. +- Cross-validate everything. One person's perspective is an anecdote. Three perspectives with the same theme is a finding. +- Follow up, don't rapid-fire. One thoughtful question followed by genuine listening beats ten questions read from a guide. +- Focus on root causes. Ask "why" until you get past symptoms. Pain points without root causes produce recommendations that don't stick. +- Flag data gaps early. Don't wait until analysis to discover you're missing critical information. +- When discovery is blocked, that's a finding in itself. Escalate it. + +**On stakeholders:** +- Informal influence often matters more than formal authority. The org chart lies. +- Stakeholder positions shift. Revisit the map regularly. +- Build coalitions of supporters before tackling resistors. Champions create social proof. +- One-on-one conversations move difficult stakeholders more than group presentations. +- Stakeholder mapping is confidential. Handle with care. +- Listen before you advocate. Understanding someone's concerns is a prerequisite to addressing them. +- Early engagement prevents late-stage resistance. The cost of inclusion is always lower than the cost of opposition. + +**On standing up the engagement:** +- Set cadences immediately. "We'll figure out the rhythm as we go" means no rhythm. +- Working arrangements feel bureaucratic until the first miscommunication. Then they feel essential. +- Quick wins in the first two weeks buy goodwill that carries you through the hard middle of the engagement. +- For hybrid engagements, relationships require deliberate effort. Schedule the informal conversations that would happen naturally in person. + diff --git a/management-consulting/skills/financial-modeling/SKILL.md b/management-consulting/skills/financial-modeling/SKILL.md new file mode 100644 index 00000000..2ab1bcac --- /dev/null +++ b/management-consulting/skills/financial-modeling/SKILL.md @@ -0,0 +1,553 @@ +--- +name: financial-modeling +description: Build financial models for business cases including ROI, NPV, IRR, DCF, scenario analysis, and total cost of ownership. Use for investment recommendations, comparing strategic options, quantifying initiatives, building business cases, or company valuations. +--- + +# Financial Modeling + +Build business cases, calculate investment returns, and structure financial analyses to support strategic recommendations. Every output should be table-heavy, assumption-explicit, and end with a clear decision recommendation. + +## Before You Begin + +Financial models are only as good as their inputs. Ask for actual data rather than fabricating figures: +- What are the actual cost figures (labor costs, infrastructure spend, operating costs)? +- What revenue or benefit figures should the model use? +- What is the organization's discount rate, WACC, or hurdle rate? +- When using numbers the user didn't provide, flag every one explicitly: "I'm assuming $22M annual labor cost based on [300 FTEs at $73K average loaded cost]. This is a placeholder... validate with actual payroll data." Never present fabricated financial inputs as if they were the user's real numbers. + +--- + +## Behavioral Principles + +1. **Document every assumption.** State the source, basis, and confidence level for each assumption. Undocumented assumptions are the #1 cause of flawed business cases. +2. **Be conservative by default.** Use realistic, not optimistic, assumptions. Stretch goals are not baseline projections. If a client pushes for aggressive numbers, flag the risk explicitly. +3. **Sensitivity over precision.** A precise but wrong number is worse than an approximate range. Always identify which 2-3 variables drive 80% of the outcome and test them. +4. **Show alternatives.** Never present a single option. Always show a "do nothing" baseline (quantified, not just mentioned) and one alternative to the recommended path. +5. **Separate facts from forecasts.** Clearly distinguish historical data from projected values. Label assumptions as "verified," "estimated," or "placeholder." +6. **Make it auditable.** Structure analyses so a third party can trace any output back to its source assumptions in under 5 minutes. +7. **The number supports the decision.** The business case exists to support a decision, not to generate a number. If the financial analysis doesn't lead to a clear recommendation, the framing is wrong. + +--- + +## Analysis Type Selection + +| Analysis Type | Use Case | Key Outputs | +|---|---|---| +| ROI Analysis | Quick investment assessment | Return %, payback period | +| Business Case | Comprehensive investment case | NPV, IRR, payback | +| DCF Valuation | Company or business unit valuation | Enterprise value, equity value | +| Scenario Analysis | Risk assessment | Best/base/worst case, probability-weighted NPV | +| Break-even Analysis | Volume or revenue threshold | Break-even point, margin of safety | +| TCO Comparison | Comparing competing solutions | Annualized cost, cost per user | +| EVA | Cross-unit performance comparison | Value creation vs. capital cost | + +--- + +## Interpreting Client Inputs + +When clients provide financial parameters, clarify before modeling: + +- **Percentage improvements**: "Reduce costs by 30%" ... 30% of what? Get the absolute base number. $22M labor bill at 30% = $6.6M. $8M labor bill at 30% = $2.4M. The percentage is meaningless without the base. +- **Rate vs. cost vs. outcome**: "15% quality improvement" could mean defect rate drops 15% (3.2% to 2.7%), cost of poor quality drops 15% ($4.5M to $3.8M), or yield improves 15% (85% to 97.8%). Each has very different financial impact. State your interpretation explicitly and flag it for validation. +- **When the base isn't provided**: State your assumption, show the math, and mark it as a placeholder. "Assuming $22M annual labor cost based on 300 FTEs at $73K average loaded cost [placeholder ... validate with client payroll data]." + +--- + +## Capex vs. Opex Distinction + +This matters for financial statement impact and CFO evaluation. Always classify costs. + +| Dimension | Capex | Opex | +|---|---|---| +| P&L impact | Depreciated over useful life | Expensed in period | +| Cash flow | Large upfront outflow | Spread over time | +| Balance sheet | Increases asset base | No asset impact | +| CFO preference | Varies by company; some prefer capex (asset build), others prefer opex (flexibility) | +| Tax treatment | Depreciation shield over years | Immediate deduction | + +When relevant (cloud migration, build vs. buy, lease vs. purchase, M&A purchase price allocation): show the same investment under both capex and opex treatment. Cloud migrations are often justified partly on the capex-to-opex shift. For M&A, classify the purchase price into goodwill, identifiable intangibles (amortized), and tangible assets (depreciated). The amortization schedule affects reported earnings and tax shields, which matters for PE exit multiples and earnout calculations. + +--- + +## Do-Nothing Baseline (Required) + +Every business case must quantify the cost of inaction. "Do nothing" is never free. Include: + +- **Ongoing costs**: Current run-rate, fully loaded +- **Cost escalation**: Aging infrastructure maintenance, rising labor costs, technical debt accumulation. Use 5-10% annual escalation for aging systems unless client provides actuals +- **Risk costs**: Probability x impact for known risks (outages, compliance, security) +- **Opportunity costs**: Revenue foregone, competitive disadvantage, inability to execute strategic initiatives + +Example: A $50M/year on-prem environment isn't a $150M 3-year baseline. With aging hardware requiring $8-12M refresh, 8% cost growth, and $2M annual outage risk, the real 3-year baseline is $170-180M. + +--- + +## ROI Analysis + +For quick investment assessment, structure the analysis as: + +**Investment Summary**: Initial investment, ongoing investment per year, project life. Classify each cost as capex or opex. + +**Benefits Projection**: For each benefit category, project Year 1 through end of project life with totals. Show ramp-up (Year 1 benefits are rarely at full run-rate). + +**Return Metrics**: + +| Metric | Value | Benchmark | Assessment | +|---|---|---|---| +| Simple ROI (%) | [calc] | >50% | Exceeds / Meets / Below | +| Payback period | [calc] | <3 years | Exceeds / Meets / Below | +| NPV (at WACC) | [calc] | >$0 | Positive / Negative | +| IRR | [calc] | >WACC | Exceeds / Below | + +**Sensitivity**: Identify the 2-3 variables that drive the outcome and show NPV impact at +/- 10% and +/- 20% variation. + +--- + +## Business Case Development + +For comprehensive investment cases, structure as: + +**Executive Summary**: 2-3 sentences stating the investment, the recommendation (Go/No-Go/Conditional), and the headline number (NPV or ROI). + +**Problem Statement**: What problem does this investment solve? Size the problem in dollars. + +**Do-Nothing Baseline**: Quantified cost of inaction over the analysis period (see Do-Nothing Baseline section). + +**Financial Summary**: + +| Metric | Value | +|---|---| +| Total Investment | $[X]M | +| NPV (Base Case) | $[X]M | +| IRR | [X]% | +| Payback Period | [X] months | +| 3-Year ROI | [X]% | + +**Investment Details**: Cost categories (capital, implementation, ongoing opex) projected across the analysis period. Use a year-by-year table. + +**Benefit Projections**: Revenue growth, cost reduction, risk mitigation projected across the analysis period. Include a confidence column (High/Medium/Low) for each benefit line. + +**Cash Flow Analysis**: Annual cash flows with discount factors and present values. Show cumulative PV building to the NPV. + +| | Year 0 | Year 1 | Year 2 | Year 3 | +|---|---|---|---|---| +| Total Benefits | - | $[X]M | $[X]M | $[X]M | +| Total Costs (incremental) | ($[X]M) | ($[X]M) | ($[X]M) | ($[X]M) | +| Net Cash Flow | ($[X]M) | $[X]M | $[X]M | $[X]M | +| Discount Factor | 1.000 | 0.[X] | 0.[X] | 0.[X] | +| PV of Cash Flow | ($[X]M) | $[X]M | $[X]M | $[X]M | +| Cumulative PV | ($[X]M) | ($[X]M) | $[X]M | $[X]M | + +**Assumptions**: List every assumption in a table with columns: #, Assumption, Value, Basis, Status (verified/estimated/placeholder). + +**Sensitivity Analysis**: Show NPV, IRR, and assessment under upside, base, and downside scenarios. Also show a tornado-style table: the 3-5 key variables with NPV impact at +/-10%. + +**Risks and Mitigations**: Each risk with quantified impact ($), likelihood (H/M/L), and specific mitigation action. + +**Alternatives**: At least two alternatives to the recommended option (including "do nothing"), each with NPV and key trade-offs. + +**Recommendation**: See Recommendation Template below. + +--- + +## Phased Investment Structure + +For investments >$5M or with significant execution risk, structure as a staged commitment: + +**Phase 1 (Pilot)**: Smallest investment that tests the critical assumption. +- Scope: What's included, what's excluded +- Investment: Typically 20-35% of full program +- Duration: 3-6 months +- Success criteria: Specific, measurable thresholds (e.g., "achieve >25% labor cost reduction on Line 1") + +**Gate Decision**: Explicit go/no-go with defined metrics. +- Metrics that trigger "proceed": [thresholds] +- Metrics that trigger "stop": [thresholds] +- Metrics that trigger "modify and re-evaluate": [thresholds] + +**Phase 2 (Scale)**: Full investment, contingent on Phase 1 results. +- Incremental investment beyond Phase 1 +- Updated projections incorporating Phase 1 actuals + +Show NPV for three scenarios: +1. Phase 1 only (worst case: we learn it doesn't work; cost = Phase 1 investment) +2. Full program (expected case) +3. Expanded program (upside: Phase 1 exceeds expectations, justifying broader scope) + +This approach reduces downside risk. If a $15M investment has a worst-case NPV of ($3.8M), but a phased approach limits Phase 1 to $5.5M, the worst case drops to ($1.2M). + +--- + +## DCF Valuation + +For business or company valuation: + +**Revenue Projections**: Revenue, growth rate, gross profit, gross margin, EBITDA, and EBITDA margin for current year through Year 5. Model growth rate deceleration explicitly (high-growth companies at $30M revenue typically decelerate 3-4 percentage points per year). + +Revenue projection methodology depends on business maturity: +- **Mature businesses**: Apply growth rate decay. Start from the current growth rate and decelerate toward GDP growth or industry average over the projection period. A 10% grower at $500M revenue is not growing 10% in Year 5. +- **Subscription/SaaS businesses**: Use cohort-based projections. Model existing customer revenue (base revenue x net retention rate) separately from new customer revenue (new logos x average ACV x ramp). This exposes the real growth engine and avoids masking churn behind gross bookings. +- **Early-stage/high-growth**: Use a top-down reasonableness check (implied market share in Year 5) alongside the bottom-up build to catch hockey-stick projections that imply implausible market capture. + +**Unlevered Free Cash Flow (UFCF)**: Build from EBITDA: +- EBITDA +- Less: taxes on EBIT (EBIT x tax rate). Use the marginal tax rate, not the effective rate, for incremental cash flow analysis. +- Less: capex (or capitalized development costs). Distinguish maintenance capex (required to sustain current operations) from growth capex (investment in new capacity or capabilities). +- Less: change in net working capital. Model each component (receivables, inventory, payables) as a percentage of revenue or COGS. Watch for businesses where working capital is a significant cash drag during growth. +- Equals: Unlevered Free Cash Flow + +**Terminal Value**: Terminal value often represents 60-80% of total enterprise value, so the methodology choice matters. + +- **Exit Multiple method**: Year 5 EBITDA (or revenue for high-growth/pre-profit businesses) x an appropriate comparable multiple. Use when market comparables exist and the business will likely be sold or valued on a multiples basis. Select the multiple from comparable transactions, not from current trading multiples (which fluctuate with market sentiment). +- **Gordon Growth Model**: Year 5 FCF x (1 + g) / (WACC - g). More conservative; appropriate when the business is expected to reach steady state. The terminal growth rate (g) should not exceed long-term GDP growth (2-3% nominal) for most businesses. Using a higher g implies the business will eventually become larger than the economy. +- **When to weight each**: Use exit multiple as primary for businesses with clear comparable sets and likely M&A or IPO exit paths. Use Gordon Growth as a floor or sanity check. When the two methods diverge significantly, explain why (usually because the exit multiple embeds growth expectations above the terminal growth rate) and state which you're using as primary. + +**WACC Calculation**: Build up from components: + +| Component | Value | Basis | +|---|---|---| +| Risk-free rate | [X]% | 10-year Treasury | +| Equity risk premium | [X]% | Damodaran estimate | +| Beta (levered) | [X] | Industry median | +| Cost of equity (CAPM) | [X]% | Rf + Beta x ERP | +| Size premium | [X]% | If sub-$500M EV | +| Cost of debt (after-tax) | [X]% | If applicable | +| Debt/equity weights | [X]/[X] | Target structure | +| **WACC** | **[X]%** | | + +**Valuation Summary**: PV of projected FCFs + PV of terminal value = enterprise value. Show implied multiples (EV/Revenue, EV/EBITDA) as sanity check against comparable transactions. + +**Valuation Sensitivity**: Show enterprise value in a matrix of WACC (+/- 1%) vs. terminal value driver (exit multiple or growth rate). + +--- + +## SaaS Valuation Metrics + +For SaaS and subscription businesses, supplement DCF with these metrics. They drive multiples and investor perception. + +| Metric | Definition | Healthy Benchmark | Red Flag | +|---|---|---|---| +| Net Revenue Retention (NRR) | Revenue from existing customers this year / same cohort last year | >110% (>120% = premium) | <100% (shrinking base) | +| LTV/CAC | Customer lifetime value / cost to acquire | >3x | <1x (destroying value) | +| CAC Payback | Months to recover acquisition cost from gross profit | <18 months | >24 months | +| Rule of 40 | Revenue growth % + EBITDA margin % | >40 (good), >60 (elite) | <20 | +| Gross Margin by Type | Subscription vs. services vs. usage | Subscription >75% | Blended <60% | +| Logo Churn vs. Revenue Churn | Customer count loss vs. dollar loss | Revenue churn < logo churn (expansion offsets) | Revenue churn > logo churn | +| ARR per Employee | Annual recurring revenue / headcount | $150K-250K+ | <$100K | + +**How these affect valuation**: +- NRR >120%: supports 8-12x ARR multiples. NRR <100%: compresses to 3-5x. +- Rule of 40 >40: "good" SaaS company. Each point above 40 adds ~0.5x to ARR multiple. +- Always request NRR by cohort and vintage. Blended NRR can mask deteriorating cohorts. +- Only subscription gross margin should drive the revenue multiple. Services revenue should be valued at 1-2x at most. +- For M&A business cases involving SaaS targets, always calculate LTV/CAC with explicit inputs shown (not just assumed). Request cohort retention data by vintage and model value per cohort. If the target can't provide cohort-level data, flag as a data quality concern that affects valuation confidence. + +--- + +## Scenario Analysis + +For risk assessment: + +**Scenario Definitions**: Upside, base, and downside with description and probability weighting (must sum to 100%). + +**Scenario Comparison**: Revenue, costs, NPV, IRR, and payback under each scenario. + +**Probability-Weighted NPV**: Each scenario's NPV times its probability, summed to expected NPV. + +Example: (0.20 x $12.8M) + (0.50 x $7.5M) + (0.25 x $1.2M) + (0.05 x ($3.8M)) = $6.4M expected NPV. + +**Break-even Analysis**: Break-even revenue, break-even volume, and margin of safety vs. base case. + +--- + +## Monte Carlo Thinking + +For major investments, three-point scenarios (best/base/worst) understate the range of outcomes. When appropriate, describe the simulation design: + +- **Identify variable distributions**: Which assumptions should be modeled as ranges rather than point estimates? (e.g., "labor savings: triangular distribution, min 15%, mode 30%, max 40%") +- **Specify correlations**: Which variables move together? (e.g., higher adoption speed correlates with higher training costs) +- **Define outputs to track**: Probability of positive NPV, expected NPV, 5th/95th percentile range, maximum loss +- **Identify variance drivers**: Which input assumptions contribute most to output variance? (This is often the most actionable insight) + +This provides a richer risk picture than three scenarios and identifies which assumptions to spend time validating. + +--- + +## Economic Value Added (EVA) + +**Formula**: EVA = NOPAT - (Capital Charge) + +Where Capital Charge = WACC x Capital Employed. + +**Building the Components**: + +| Component | Calculation | Notes | +|---|---|---| +| NOPAT | EBIT x (1 - tax rate) | Use operating income, exclude financing costs and non-recurring items. Adjust for operating leases if material. | +| Capital Employed | Total Assets - Current Liabilities | Or equivalently: Net Fixed Assets + Net Working Capital. For asset-light businesses, include capitalized R&D and intangibles. | +| Capital Charge | WACC x Capital Employed | Use the same WACC as DCF analysis; adjust for division-specific risk if comparing business units. | + +**Interpretation**: + +| EVA Result | Meaning | Action | +|---|---|---| +| Positive, growing | Creating and increasing value | Invest more capital if returns hold | +| Positive, shrinking | Still creating value, but declining | Investigate: margin erosion? Capital inefficiency? | +| Near zero | Earning approximately cost of capital | Business is a "rent payer" ... covering capital costs but not creating surplus value | +| Negative | Destroying shareholder value | Restructure, divest, or fundamentally change the business model | + +**EVA for Cross-Unit Comparison**: + +This is EVA's primary advantage over ROI or ROIC: it expresses value creation in absolute dollars, making units of different sizes directly comparable. + +| Business Unit | NOPAT ($M) | Capital Employed ($M) | WACC | Capital Charge ($M) | EVA ($M) | +|---|---|---|---|---|---| +| Unit A | 25.0 | 150.0 | 10% | 15.0 | +10.0 | +| Unit B | 8.0 | 30.0 | 10% | 3.0 | +5.0 | +| Unit C | 12.0 | 140.0 | 10% | 14.0 | -2.0 | + +Unit A has the highest absolute EVA, but Unit B has the highest EVA/Capital ratio (16.7% vs. 6.7%). Unit C is destroying value despite being profitable on a NOPAT basis. + +**EVA-Based Performance Targets**: + +Set targets as EVA improvement (delta EVA), not absolute EVA. This avoids penalizing units that inherited large capital bases. Decompose EVA improvement into three levers: +1. **Increase NOPAT** without proportional capital increase (operational efficiency) +2. **Reduce capital employed** without proportional NOPAT decline (asset efficiency, working capital management) +3. **Invest new capital** at returns above WACC (value-creating growth) + +**When to Use EVA**: +- Comparing performance across divisions of different sizes (EVA's sweet spot) +- Evaluating whether growth is actually creating value (a division can grow revenue and NOPAT while destroying value if capital grows faster) +- Setting management incentive targets that align with shareholder value creation +- Assessing acquisition targets: is the target generating returns above its cost of capital? If EVA is negative, the acquisition price must account for the turnaround investment needed to get EVA positive +- Capital allocation decisions: direct incremental capital to units with the highest marginal EVA per dollar invested + +--- + +## Discount Rate Selection + +### Factors + +| Factor | Consideration | Impact on Rate | +|---|---|---| +| Cost of capital | Company's WACC | Baseline | +| Risk level | Project risk vs. company average | +/- adjustment | +| Industry | Industry average returns | Benchmark | +| Inflation | Expected inflation rate | Include | +| Market conditions | Current interest rates | Adjust | +| Technology risk | AI/technology implementation uncertainty | + adjustment | + +### Typical Ranges by Risk Level + +These ranges are illustrative and depend on the prevailing interest rate environment, geography, and company-specific cost of capital. Always anchor to the organization's actual WACC or hurdle rate. + +| Risk Level | Discount Rate Range | Examples | +|---|---|---| +| Low risk | 5-8% | Core operations, efficiency improvements | +| Medium risk | 8-12% | Growth initiatives | +| High risk | 12-20% | New market entry | +| Very high risk | 20%+ | New ventures, R&D | +| Platform/AI | 15-25% | Digital transformation, AI investments | + +### Guidance + +- When in doubt, use a higher discount rate. Better to reject a good project than to accept a bad one. +- If a project looks attractive only at a low discount rate, flag it as sensitive to cost-of-capital assumptions. +- Always show NPV at multiple discount rates (e.g., WACC, WACC+2%, WACC+5%). + +--- + +## Real vs. Nominal Cash Flows + +A common modeling error: mixing real and nominal values in the same analysis. Pick one convention and apply it consistently. + +| Convention | Cash Flows | Discount Rate | When to Use | +|---|---|---|---| +| **Nominal** | Include expected inflation in revenue growth, cost escalation, etc. | Use nominal WACC (includes inflation expectations) | Default for most business cases. Easier to tie to budgets, contracts, and reported financials. | +| **Real** | Strip out inflation; express all values in today's purchasing power | Use real WACC (nominal WACC - expected inflation) | Long-horizon analyses (10+ years) where inflation compounds significantly. Infrastructure, energy, real estate. | + +**The rule**: nominal cash flows with nominal discount rate, or real cash flows with real discount rate. Never cross them. Mixing nominal cash flows with a real discount rate overstates NPV; mixing real cash flows with a nominal rate understates it. + +**Practical guidance**: +- For 3-5 year business cases, use nominal. The inflation distortion is small and nominal is easier for stakeholders to follow. +- For 10+ year analyses, consider real. It keeps the focus on whether the project creates genuine value above inflation. +- When inflation rates differ significantly across cost and revenue lines (e.g., labor inflating at 4% but software costs deflating at 2%), model each line's escalation explicitly in nominal terms rather than applying a blanket inflation rate. +- Always state the assumed inflation rate and its source. A seemingly small difference (2% vs. 4%) compounds dramatically over long horizons. + +--- + +## Foreign Currency Considerations + +For multi-country business cases, currency effects can materially alter the economics. Address these explicitly. + +**Step 1: Identify Currency Exposure** + +Map each cash flow line to its currency denomination: + +| Cash Flow Item | Currency | Exposure Type | +|---|---|---| +| Revenue from US customers | USD | Revenue exposure | +| European subsidiary costs | EUR | Cost exposure | +| Manufacturing in China | CNY | Cost exposure | +| Debt service | USD | Financing exposure | + +**Step 2: Choose a Modeling Approach** + +| Approach | Method | When to Use | +|---|---|---| +| **Constant exchange rate** | Use today's spot rate for all future periods | Simplest. Acceptable for short-horizon cases (1-2 years) or when FX exposure is <10% of total cash flows. Label clearly: "at constant exchange rates." | +| **Forward rates** | Use market forward rates for each future period | Better for 3-5 year cases. Forward rates embed market expectations of currency movements. Source from Bloomberg or central bank data. | +| **Scenario-based** | Model base/upside/downside exchange rate paths | Best for material FX exposure. Show NPV sensitivity to +/-10% and +/-20% currency moves on the dominant exposure. | + +**Step 3: Address Key Risks** + +- **Translation risk**: Reporting currency impact when consolidating foreign subsidiary results. Affects reported earnings but not necessarily cash flow. +- **Transaction risk**: Actual cash flow impact when revenues and costs are in different currencies. This is the one that matters for business case economics. +- **Natural hedging**: Does the business have offsetting exposures? (e.g., EUR revenues and EUR costs in Europe net out.) Quantify the net exposure after natural offsets. +- **Hedging costs**: If the business hedges FX risk, include the cost (typically 1-3% annually for major currency pairs). Note that hedging removes volatility but not the long-term trend. + +**In the analysis**: Show the base case NPV at current exchange rates, then show NPV sensitivity to the top 1-2 currency exposures. Flag if any scenario flips the recommendation from Go to No-Go. + +--- + +## Total Cost of Ownership (TCO) + +### Cost Categories + +**Direct Costs** (by year): Acquisition, implementation, operation, maintenance, upgrade/replacement. Classify each as capex or opex. + +**Indirect Costs**: Training, productivity loss during implementation, support overhead, compliance/certification. + +**Hidden Costs** (often missed): +- Data migration and integration +- Dual-running during transition +- Vendor lock-in switching costs +- Technical debt accumulation +- Opportunity cost of internal resources + +**TCO Summary**: Total TCO, annualized TCO, cost per user/year, and comparison vs. alternatives. + +### When to Use TCO vs. Simple ROI + +- **Use TCO** when comparing competing solutions (build vs. buy, vendor A vs. vendor B) +- **Use ROI** when evaluating a single investment against a do-nothing baseline +- **Use both** when the decision involves both "should we do it?" and "how should we do it?" + +--- + +## Advanced Valuation Concepts + +### Modified IRR (MIRR) + +Standard IRR assumes reinvestment at the IRR rate, which is often unrealistic. MIRR corrects this by specifying: +- **Financing rate**: Cost to fund the project (typically WACC) +- **Reinvestment rate**: Rate earned on interim cash flows (typically cost of capital or a conservative market rate) + +Use MIRR when the project has non-standard cash flows (multiple sign changes) or when IRR produces multiple solutions. + +### Real-Options Valuation + +Traditional NPV undervalues projects with embedded flexibility. Real-options thinking adds value for: +- **Option to expand**: Invest small now, scale up if successful +- **Option to abandon**: Cut losses if early results are poor +- **Option to defer**: Wait for better information before committing +- **Option to switch**: Change inputs, outputs, or technology mid-project + +Apply real-options thinking when: +- Investments are staged (especially R&D, pilot programs) +- High-uncertainty environments where flexibility has tangible value +- Platform investments where future use cases are uncertain +- Traditional NPV is negative but "close" and flexibility may tip the balance + +Connect to the Phased Investment Structure: a phased approach is how you capture option value in practice. + +--- + +## AI and Technology Investment Modeling + +Technology and AI investments have cost and benefit structures that differ from traditional capital projects. + +### Cost Patterns +- **Cloud infrastructure**: Operating expense, scales with usage (not fixed capital) +- **Data costs**: Acquisition, cleaning, labeling, storage... often underestimated +- **AI/ML talent**: Scarce and expensive; model as ongoing cost, not one-time +- **Technical debt**: Accumulates if not managed; include remediation budget + +### Benefit Patterns +- **Automation savings**: High confidence, easy to quantify +- **Prediction/decision quality**: Medium confidence, model as error-rate reduction +- **Personalization uplift**: Measurable via A/B testing, but adoption curve matters +- **Platform/network effects**: Hard to model precisely; use scenario analysis + +### Modeling Guidance +- Separate "proven" benefits (automation) from "speculative" benefits (network effects) +- Use higher discount rates for speculative benefits +- Model adoption curves. AI benefits rarely arrive at full scale in Year 1 +- Include a "technology pivot" scenario where the chosen approach needs to change + +--- + +## Forecasting Approach + +- **Driver-based forecasting**: Build from operational drivers (units, prices, headcount) rather than top-down growth rates. More transparent and auditable. +- **Growth deceleration**: For high-growth businesses, model explicit deceleration. A 25% growth company at $30M revenue typically decelerates 3-4 percentage points per year as the base grows. +- **Scenario generation**: Consider additional scenarios based on historical variance, not just optimistic/pessimistic. + +--- + +## Recommendation Template + +Every financial analysis must end with a recommendation. Use this structure: + +**Decision**: Go / No-Go / Conditional Go + +**Rationale**: 2-3 sentences tying the recommendation directly to the financial analysis. Lead with the strongest number. + +**Conditions** (if conditional): +- What must be true for the recommendation to hold +- Specific thresholds that would change the decision + +**Immediate Next Steps**: First 30-90 day actions. + +**Decision Reversibility**: What's the cost if we change course after committing? (Sunk cost at each decision point.) This informs whether speed or caution is warranted. + +**Timeline/Urgency**: When does the decision need to be made? What triggers urgency (e.g., hardware refresh deadline, competitive window, contract expiration)? + +--- + +## Worked Example: 3-Year Business Case (Abbreviated) + +**Prompt**: "Build a business case for a $15M factory automation investment. Expected to reduce labor costs by 30% and improve quality by 15%." + +**Interpretation of inputs**: "30% labor cost reduction" interpreted as 30% of $22M annual labor bill = $6.6M/year at run-rate. "15% quality improvement" interpreted as 15% reduction in cost of poor quality ($4.5M COPQ) = $0.68M/year. [Both flagged as placeholder ... validate base figures with client.] + +**Financial Summary**: Investment $15.5M (including $0.5M Year 0 setup), NPV $7.5M, IRR 29%, payback 2.5 years. + +**Cash flow build**: + +| | Year 0 | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | +|---|---|---|---|---|---|---| +| Labor savings | - | $3.3M | $6.6M | $6.6M | $6.6M | $6.6M | +| Quality savings | - | $0.34M | $0.68M | $0.68M | $0.68M | $0.68M | +| Other benefits | - | $0.2M | $1.2M | $2.1M | $2.1M | $2.1M | +| Investment + ongoing costs | ($15.5M) | ($1.8M) | ($1.8M) | ($1.8M) | ($1.8M) | ($1.8M) | +| **Net cash flow** | **($15.5M)** | **$2.04M** | **$6.68M** | **$7.58M** | **$7.58M** | **$7.58M** | +| PV (10% WACC) | ($15.5M) | $1.85M | $5.52M | $5.69M | $5.18M | $4.71M | +| Cumulative PV | ($15.5M) | ($13.65M) | ($8.13M) | ($2.44M) | $2.74M | $7.45M | + +Year 1 labor savings at 50% of run-rate due to phased rollout. Full run-rate from Year 2. + +**Key sensitivity**: Labor savings drive ~80% of the NPV. At 20% reduction instead of 30%, NPV drops to $2.6M but remains positive. Quality improvement is valuable but not material to the go/no-go decision. + +**Recommendation**: Conditional Go. Invest $5.5M in Phase 1 (one production line). If Phase 1 achieves >25% labor cost reduction over 6 months, commit remaining $9.5M for Lines 2-3. This limits downside to ($1.2M) while preserving full upside. + +--- + +## Key Principles + +- The "number" is never the point. The business case supports a decision. +- Finance and strategy must work together. Numbers without story lack impact. +- Sensitivity analysis is more important than precise projections. +- Always stress-test the business case with realistic downside scenarios. +- Present financial outputs in tables, not prose. Tables are auditable; paragraphs of numbers are not. +- Be prepared to explain every assumption. diff --git a/management-consulting/skills/proposal-development/SKILL.md b/management-consulting/skills/proposal-development/SKILL.md new file mode 100644 index 00000000..4fe8b2eb --- /dev/null +++ b/management-consulting/skills/proposal-development/SKILL.md @@ -0,0 +1,775 @@ +--- +name: proposal-development +description: Develop consulting proposals and manage the business development lifecycle. Use when analyzing RFPs, writing proposals, creating Statements of Work, building pitch decks, or articulating value propositions for client pursuits. Covers everything from initial opportunity assessment through proposal submission, oral defense, and post-pursuit debrief. +--- + +# Proposal Development + +Manage the full business development lifecycle for consulting engagements: assess opportunities, develop proposals, draft SOWs, build pitch decks, prepare oral defenses, and articulate value propositions. + +## Before You Begin + +Proposals built on guesses lose deals. Ask for the inputs that shape the response: +- What is the opportunity (RFP, inbound request, or proactive pursuit)? Is the source document available? +- What is the firm's relevant experience and which case studies can be referenced? +- What is the competitive landscape (who else is bidding, what's the client's selection process)? +- Don't fabricate case study results, client names, or team credentials. Use placeholders where the user needs to supply firm-specific content: "[Insert relevant case study with quantified results]." + +Determine which stage of the BD lifecycle the user needs, then execute accordingly. A full pursuit flows through these stages in order, but the user may enter at any point. + +### Stage 1: Opportunity Assessment + +Analyze an RFP, inbound request, or proactive pursuit to decide whether and how to respond. + +#### 1a. Parse the Opportunity + +Accept and parse the source material (RFP document, client conversation notes, or opportunity brief). Identify: + +- **Client organization** and background +- **Problem statement** — what challenge are they trying to solve? +- **Scope of work** — what are they asking for? +- **Deliverables** — what will be required? +- **Timeline** — key dates and deadlines +- **Budget** — if disclosed (flag as risk if not) +- **Evaluation criteria** — how will responses be scored? +- **Submission requirements** — format, length, required sections + +For proactive pursuits where there's no RFP, work with what's available: client conversations, news, strategic context, known pain points. + +#### 1b. Score the Opportunity + +Assess fit before investing effort: + +``` +## Opportunity Assessment + +- **Fit score**: [High / Medium / Low] +- **Estimated value**: [Range if available] +- **Win probability**: [Initial assessment with rationale] +- **Resource requirement**: [High / Medium / Low] +- **Strategic value**: [Does this open a new account, practice area, or market?] +``` + +**Go/No-Go signals:** +- Do we have the right people and relevant experience? +- Is the timeline realistic? +- Are there signs of a preferred vendor? (unusual or overly specific requirements, insider language) +- Does the economics work at our rate card? +- Is this strategically important beyond this single engagement? + +#### 1c. Analyze Evaluation Criteria + +For RFPs with explicit criteria, break down the evaluation framework: + +| Criterion | Weight | Interpretation | Our Strength | +|-----------|--------|----------------|---------------| +| [Criterion] | X% | [What they really want] | [High/Med/Low] | + +Key questions: +- What matters most? (highest weight) +- What is differentiated vs. table stakes? +- What are they explicitly vs. implicitly evaluating? +- What does the weight distribution signal about the client? (heavy methodology weight often means they've been burned by "winging it"; heavy price weight means procurement is driving the process) + +Note whether weightings are explicit or inferred. For informal pursuits, identify the implicit evaluation criteria from client conversations and context. + +**Evaluation-driven response strategy:** Let the weights dictate where you invest effort. If methodology is 40% and price is 20%, your methodology section should be 3x more developed than your pricing section. Don't allocate proposal effort equally across unequally weighted criteria. + +#### 1d. Assess Competitive Position + +Map the competitive landscape: + +- **Known competitors**: Who is likely bidding? +- **Our advantages**: Where do we win against each? +- **Our vulnerabilities**: Where do we need to mitigate? +- **Gaps**: What do we need to address? + +If multiple stakeholders are involved, note different evaluation perspectives (technical vs. commercial vs. strategic). + +**Losing position recovery:** If you're not the frontrunner (no existing relationship, weak references, competitor is incumbent): +- Reframe evaluation criteria to favor your strengths through how you structure the response +- Consider proposing alternative scope that changes the competitive dynamic +- Use pricing structure (performance-based, phased with off-ramps) to de-risk the client's decision +- Plan to use the oral presentation to overcome a weaker written score + +#### 1e. Identify Win Themes + +Develop 3-5 win themes locked to what the client is actually evaluating. Each theme needs a "why" (not just a "what"), evidence, and explicit alignment to evaluation criteria: + +``` +### Theme: [Name] +- **Why it wins**: [Client pain point] is their priority — this addresses it directly +- **Evidence**: [Quantifiable case study or track record with measurable outcomes] +- **Alignment**: [Maps to evaluation criterion X] +``` + +Win themes carry forward into every subsequent stage. They're the backbone of the proposal narrative. + +### Stage 2: Value Proposition + +Articulate the differentiated value that underpins the pursuit. This work feeds into the proposal, pitch deck, and client conversations. + +#### 2a. Define Value Drivers + +Structure value: + +**What value do we create?** +- Primary value: cost reduction, revenue growth, risk mitigation, capability building +- Quantified impact: specific numbers, percentages, timeframes + +**Why does this matter to THEM?** +- Connect value to their specific priorities, not your capabilities +- Use their language and terminology +- Address their biggest fear or aspiration + +**Why should they believe us?** +- Methodology with track record +- Relevant experience with named outcomes +- Credentials, certifications, or third-party validation + +Evidence hierarchy (strongest to weakest): quantified case study with named client > quantified case study (anonymized) > named reference willing to take a call > methodology certification or award > team credentials and tenure > assertion without evidence. Never rely on the bottom of this hierarchy when you can reach higher. + +**What makes us different?** +- Differentiators that only we can claim +- Why those differentiators are sustainable +- Why competitors cannot easily replicate them + +**How do we deliver and prove it?** +- Delivery model +- Track record with quantified results from similar engagements +- How we de-risk the engagement for the client + +#### 2b. Validate the Messaging + +Run the value proposition through four tests: + +- **Clarity**: Can someone explain it in 30 seconds? Is the benefit immediately obvious? +- **Relevance**: Does it address their specific pain? Would they care? +- **Differentiation**: Could a competitor make this same claim? Is it specific? +- **Belief**: Is it credible? Do we have proof points? + +If any test fails: +- Clarity fails: simplify, remove jargon, cut to one core benefit +- Relevance fails: you may be solving the wrong problem — re-examine client needs +- Differentiation fails: dig into methodology, team, or IP. Examine potential differentiators: proprietary tools, team composition, delivery model, commercial structure, geographic depth, industry track record. Replace generic claims with specifics only you can claim +- Belief fails: move up the evidence hierarchy. Quantified case studies beat assertions. Named references beat anonymous ones. If you can't find strong evidence, the claim probably isn't true enough to make + +#### 2c. Develop Stakeholder-Level Messages + +Tailor messaging for different decision-makers when the pursuit involves a complex buying group: + +| Audience | Care About | Lead With | Prove With | +|----------|-----------|-----------|-----------| +| C-Suite | Enterprise value, competitive advantage | Strategic impact | Board-level metrics | +| Functional Leaders | Capability, team effectiveness | Operational improvement | KPIs, benchmarks | +| Practitioners | Methodology, tools, daily work | How their work improves | Practical examples, peer references | +| Procurement | Compliance, value for money, risk | Competitive positioning | References, certifications | + +This is supplementary to the core value proposition, not a replacement. Only develop stakeholder-level messages when the pursuit has multiple distinct audiences evaluating the response. + +### Stage 2d: Consortium and Joint-Venture Proposals + +Increasingly common for large public sector work, multi-capability programs, or when the client requires coverage you can't provide alone. Partnering changes the pursuit dynamics fundamentally. + +**When to consider a consortium bid:** +- The RFP requires capabilities your firm doesn't have (e.g., technology implementation + management consulting) +- Geographic coverage requirements exceed your footprint +- The client explicitly encourages or requires consortium bids +- The contract is too large for one firm to resource or too risky to bear alone + +**Partner selection criteria:** + +| Factor | What to Assess | +|--------|---------------| +| Complementarity | Do they fill a genuine gap, or are they a competitor you're sharing margin with? | +| Track record together | Have you worked with them before? Cold partnerships rarely survive the stress of delivery | +| Cultural compatibility | Compatible working styles, quality standards, and client management approaches | +| Commercial alignment | Agreement on rate cards, margin sharing, and who bills what | +| Reputation risk | Would their brand strengthen or weaken your proposal? What's their delivery track record? | + +**Structuring the consortium:** + +- **Lead partner**: One firm must lead. This firm owns the client relationship, manages the contract, and bears primary delivery risk. Decide this first. If you can't agree on who leads, don't bid together. +- **Teaming agreement**: Formal agreement covering scope split, pricing, IP, liability, exclusivity, and what happens if you win and one partner underperforms. Get this signed before you start writing. +- **Unified proposal voice**: The proposal must read as one team, not two firms stapled together. Assign one editor with authority to rewrite any section. Evaluators can always tell when Section 3 was written by a different firm than Section 5. +- **Single governance model**: Present one project governance structure to the client, not "our governance + their governance." Joint steering, single escalation path. + +**Common consortium pitfalls:** +- Spending more time negotiating with your partner than writing the proposal +- Misaligned pricing (one firm's day rates are 40% higher than the other's) +- "We'll figure out the scope split during delivery" (you won't; figure it out now) +- Unclear IP ownership for jointly developed deliverables + +### Stage 2e: Timeline-Driven Proposal Strategy + +How much time you have to respond changes what you can do. Most proposal guidance assumes you have ample time. In practice, you often don't. + +**2 weeks or less (emergency response):** +- Skip the full opportunity assessment. Make a rapid go/no-go call in the first 2 hours based on fit, availability, and win probability +- Assign a single proposal lead with decision authority (no committee reviews) +- Reuse aggressively: pull the closest prior proposal and adapt. Customize only the executive summary, Understanding Your Challenges, team, and pricing +- Skip the red team. Instead, have one senior person (partner or director) do a single critical read 24 hours before submission +- Allocate effort by evaluation weight. If methodology is 40%, spend 40% of your time there +- Accept that the result will be imperfect. A good-enough proposal submitted on time beats a perfect one submitted late + +**3-4 weeks (standard response):** +- Full process as described in Stages 1-3, but compress: opportunity assessment and win themes in Week 1, drafting in Week 2, internal review and revision in Week 3, final polish and submission in Week 4 +- One red team review (not two). Schedule it at end of Week 2 so there's time to act on findings +- Develop 2-3 case studies maximum. Don't spend time finding the perfect six + +**6+ weeks (full pursuit):** +- Full process with time for client engagement: Q&A submissions, clarification meetings, reference calls +- Multiple red team reviews (after first draft, after revision) +- Time to develop custom case studies or conduct preliminary analysis that demonstrates insight +- Potential for a pre-submission meeting or draft review with the client (if the process allows) +- Use the extra time for differentiation, not padding. The risk with long timelines is producing a bloated, committee-written proposal instead of a sharp one + +**Regardless of timeline:** decide early what you're NOT going to do. The biggest time sink is trying to do everything and doing nothing well. + +### Stage 3: Proposal Development + +Write the full proposal document. Carry forward win themes and value proposition work from earlier stages. If entering at this stage without earlier work, develop win themes and value drivers first. + +#### 3a. Gather Context + +Confirm or gather: + +1. **Client background**: Industry, market position, recent initiatives, current challenges +2. **Engagement scope**: Problem statement, desired outcomes, scope boundaries, timeline +3. **Decision process**: Who decides, timeline, evaluation criteria +4. **Our positioning**: Win themes, value proposition, differentiation + +#### 3b. Structure the Proposal + +Lead with their challenges, not your credentials: + +``` +1. Executive Summary +2. Understanding Your Challenges +3. Our Recommended Approach +4. What This Delivers +5. Why [Our Firm] +6. Team +7. Client References +8. Investment +9. Next Steps +``` + +For RFP responses, restructure to match the required format while preserving this narrative flow within each section. + +**Customization vs. reuse:** Every proposal has a mix. Know which is which. + +Must be customized every time: +- Executive summary, Understanding Your Challenges, Team (roles on this engagement), Investment, Next Steps + +Can be adapted from prior proposals: +- Methodology descriptions, firm credentials, case study write-ups + +Should never be boilerplate: +- Anything referencing the client's specific situation, any claim about "understanding your needs" + +Common tells that scream boilerplate to an evaluator: wrong client name (obviously), generic industry language that doesn't match the client's terminology, methodology descriptions that don't connect to the stated problem, team bios that don't explain relevance to this engagement. + +#### 3c. Develop Each Section + +**Executive Summary (1 page max)** + +Write this LAST but position it FIRST. It must stand alone — it may be the only thing read. Lead with client outcomes: + +``` +[Client Name] seeks to [objective]. We propose [approach] that will deliver [quantified outcome]. + +The Outcome You'll Achieve +- [Primary outcome with metric] +- [Secondary outcome with metric] + +Why [Our Firm] +[Differentiator 1], [differentiator 2], and [differentiator 3]. + +Our Approach +[Methodology] over [timeline], structured in [number] phases. + +Investment +[Range or structure] + +Next Steps +[One clear, low-friction action] +``` + +**Understanding Your Challenges** + +Demonstrate client knowledge. Reference their specific challenges, use their terminology, acknowledge their constraints. This section earns the right to propose a solution. + +**Our Recommended Approach** + +Present methodology as the solution to their specific challenges: + +``` +Phase 1: [Name] — [Duration] +Objective: [What we achieve] +Key Activities: [Activities] +Deliverables: [Deliverables] + +Phase 2: [Name] — [Duration] +[...] + +Critical Success Factors +- [Factor 1] +- [Factor 2] +``` + +**What This Delivers** + +Quantified outcomes, ROI, impact — tied directly to their stated priorities. Show how each outcome maps back to a challenge they raised. + +**Why [Our Firm]** + +Specific, not generic. Industry depth with relevant statistics. Methodology differentiators. Case studies with quantified results. + +**Team** + +Key team members with role on this engagement, relevant experience (2-3 bullets each), and notable credentials. Include an org chart for larger teams. + +**Client References** + +Relevant case studies structured as Challenge → Approach → Results (quantified). Select cases that mirror the client's situation. + +**Investment** + +Present pricing clearly: + +| Phase | Fee | Timing | +|-------|-----|--------| +| Phase 1 | $XX | [Date] | +| Phase 2 | $XX | [Date] | +| Total | $XX | | + +Include what's covered, what's excluded, and key assumptions. Make payment terms align with deliverable milestones. + +**Next Steps** + +One clear, low-friction action. Not a menu of options. + +#### 3d. Pricing Strategy + +How you price is as strategic as what you propose. Match the pricing model to the engagement type and evaluation context. + +**Pricing models and when to use them:** + +| Model | Best For | Risk Profile | Client Perception | +|-------|----------|-------------|-------------------| +| Fixed fee | Well-defined scope, clear deliverables | Firm bears scope risk | Client prefers budget certainty | +| Time & Materials (T&M) | Ambiguous scope, discovery-heavy work | Client bears scope risk | Flexibility, but less cost certainty | +| Blended / Capped T&M | Moderate scope clarity with some unknowns | Shared risk | Balances certainty with flexibility | +| Performance-based | Measurable outcomes, confident in results | Firm bears delivery risk | Strong differentiator; demonstrates confidence | +| Phased with gates | Large or uncertain programs | Decision points reduce commitment | Lowers initial commitment barrier | + +**Evaluation-weight-driven pricing strategy:** +- Price weight < 25%: optimize for value, not cost. Justify the investment with ROI. A higher fee with superior methodology wins +- Price weight 25-35%: be competitive but not cheapest. Emphasize value per dollar +- Price weight > 35%: procurement is driving. You need to be within 10-15% of the lowest credible bid or have a compelling value story +- Price weight > 50%: this is a commodity procurement. Either win on cost or propose an alternative scope that changes the evaluation + +**When budget is not disclosed:** +- Ask directly in the Q&A period (if allowed) +- Size the engagement based on comparable work and propose a range +- Offer a phased approach where Phase 1 is a smaller commitment with a defined decision point +- Include an "investment options" section showing two or three scope/price combinations +- Never submit a proposal without some price indication; "to be discussed" signals that you're either expensive or unserious + +**Rate card construction:** +- Blended day rate = weighted average across team composition +- Show per-phase economics if team mix varies across phases +- For T&M, specify rate card by role level and any volume or duration discounts +- Include expense policy: what's included in fees, what's billed separately, caps if applicable + +#### 3e. Red Team Review + +Before submission, score your own proposal. Real pursuit teams do this; it catches problems that the writing team is too close to see. + +**Compliance check:** +- Did you answer every required question? +- Does the format match submission requirements (page limits, font, section numbering)? +- Are all required attachments included? + +**Strength assessment against evaluation criteria:** + +| Criterion | Weight | Our Section Strength (1-5) | Gap | Action | +|-----------|--------|--------------------------|-----|--------| +| [Criterion] | X% | [Score] | [Weakness] | [How to fix before submission] | + +**Cross-section consistency:** +- Does the team described in the methodology section match the team section? +- Do the deliverables in the approach match the deliverables in pricing? +- Is the timeline consistent across all sections? + +**Executive summary standalone test:** Give the executive summary to someone who hasn't read the full proposal. Can they explain what you're proposing, why you're the right firm, and what it costs? If not, rewrite it. + +**Evaluator experience test:** Read the proposal as if you're the evaluator with 5 other proposals on your desk. Where would you lose interest? Where would you get confused? Where would you question a claim? + +#### 3f. Persuasion Principles + +Throughout the proposal: +- Lead with outcomes in every section (what this delivers for them) +- Use specificity over generality (client names, data, quantified results) +- Evidence-based credibility (case studies with measurable impact, not just credentials) +- Every section connects back to their stated objectives +- Compliance + responsiveness + persuasion + credibility, in that order + +### Stage 4: Statement of Work + +Draft the SOW that formalizes scope, deliverables, timeline, governance, and commercial terms. The SOW protects both parties. Vague SOWs create scope creep and disputes. + +#### 4a. Define Project Context + +Gather or confirm: + +- **Background**: Business context, rationale, strategic importance +- **Objectives**: Primary objective (what success looks like), secondary objectives, success metrics +- **Scope**: What's IN scope, what's explicitly OUT of scope, key assumptions + +#### 4b. SOW Structure + +``` +1. Engagement Overview +2. Objectives & Success Criteria +3. Scope of Work +4. Approach & Methodology +5. Deliverables +6. Timeline & Milestones +7. Team & Roles +8. Client Responsibilities +9. Governance +10. Assumptions & Dependencies +11. Commercial Terms +12. Acceptance Criteria +``` + +#### 4c. Critical SOW Sections + +**Scope of Work — In and Out** + +Be exhaustive. The out-of-scope list is as important as the in-scope list: + +``` +In Scope +- [Activity or deliverable] +- [Activity or deliverable] + +Out of Scope — Explicitly Excluded +- [Activity the client might assume is included] +- [Activity the client might assume is included] + +Assumptions +- [Assumption about client resources, access, or decisions] + +Dependencies +- [External dependency — client action required] +- [External dependency — third-party action required] +``` + +**Deliverables** + +Specify each deliverable precisely with description, format, and timing: + +| Deliverable | Description | Format | Timing | +|-------------|-------------|--------|--------| +| D1.1 | [Name] | [Format] | [When] | + +**Success Criteria** + +Measurable, not aspirational: + +| # | Criterion | Measurement | Target | +|---|-----------|-------------|--------| +| 1 | [Criterion] | [How measured] | [Target] | + +**Client Responsibilities** + +This section prevents the most common source of engagement failure: unmet client obligations. Be explicit. + +| Responsibility | Description | Timeline / SLA | Consequence if Not Met | +|---------------|-------------|----------------|----------------------| +| Data access | Provide access to [systems/data] per data request | Within 5 business days of request | Timeline extension of equivalent duration | +| Decision authority | Designated decision-maker available for approval of [deliverables/phase gates] | Within 3 business days of submission | Timeline extension; fees for rework if direction changes after delay | +| Resource commitment | [Named roles] available at [X]% dedication for working sessions and reviews | Per project schedule | Scope may need to be adjusted; change control process applies | +| Workspace/access | Physical workspace, VPN access, system credentials for team of [X] | Prior to engagement start | Engagement start date shifts | +| Subject matter experts | SMEs available for [X] hours per week of interviews and working sessions | Per discovery/analysis schedule | Findings limited to available input; risk flagged in deliverables | + +Don't be polite about this section. Engagements fail when client obligations are assumed rather than documented. The consequence column is what gives the section teeth. + +**Governance** + +Match the governance structure to the engagement's complexity and the client's organization: + +| Forum | Frequency | Attendees | Purpose | +|-------|-----------|-----------|---------| +| Steering Committee | [Bi-weekly/Monthly] | [C-suite], Partner | Strategic decisions | +| Working Sessions | [Weekly] | Team leads | Work progress | +| Status Reviews | [Bi-weekly] | Manager, Client lead | Status, issues | + +Include escalation paths by issue type (technical, commercial, strategic) and decision rights. + +**Commercial Terms** + +Fee structure (fixed, T&M, or blended), payment schedule aligned to milestones, expense policy, and change control process: + +| Milestone | Payment | Timing | +|-----------|---------|--------| +| Contract signature | 20% | [Date] | +| Milestone 2 complete | 30% | [Date] | +| Milestone 4 complete | 30% | [Date] | +| Final delivery | 20% | [Date] | + +**Acceptance Criteria** + +Define specific, measurable acceptance criteria for each deliverable. Include: +- What "done" looks like for each deliverable +- Review period (X business days) +- Acceptance process (delivery → review → accept or feedback → revision) +- Grounds for rejection (failure to meet criteria, material scope deviation, factual errors) +- Deemed acceptance if no feedback within the review period + +**Team & Roles** + +Both sides. Consulting team with role, name, level, and commitment percentage. Client team with role and responsibilities. + +#### 4d. Change Control + +Include a process for scope modifications. Any change to scope, timeline, or cost requires: +1. Written change request describing the modification +2. Impact assessment (scope, timeline, cost) +3. Approval from designated decision makers on both sides +4. Amendment to the SOW + +### Stage 5: Pitch Deck + +Build a persuasive deck for client presentations. Decks complement written proposals; they're the vehicle for oral delivery and discussion. + +#### 5a. Determine Deck Objectives + +Clarify before building: + +- **Audience**: C-suite, board, working team (each gets different treatment) +- **Occasion**: Initial pitch, follow-up, final presentation, oral defense +- **Time available**: Drives slide count and depth +- **Key messages**: What do we want them to remember? +- **Desired action**: What do we want them to do? + +#### 5b. Standard Structure (15-20 slides) + +``` +Opening (1-2 slides) + 1. Title + +The Challenge (2-3 slides) + 2. Context and situation + 3. The problem / opportunity + 4. Why now? + +Our Solution (4-6 slides) + 5. Our approach + 6. Methodology + 7. Key differentiators + 8. What makes us unique + +Results & Credentials (3-4 slides) + 9. Relevant case study 1 + 10. Relevant case study 2 + 11. Team experience + +The Deal (2-3 slides) + 12. Scope and approach + 13. Investment + 14. Timeline + 15. Next steps + +Closing (1-2 slides) + 16. Summary + 17. Q&A +``` + +Adjust length for context. A 30-minute slot with discussion gets 10-12 slides. A detailed capabilities presentation may need 25+. + +#### 5c. Slide Development + +**The Challenge section** creates tension. Show you understand their world: +- Context: industry trends, market forces, current position +- The problem: current state vs. desired state (make the gap visceral) +- Why now: market timing, competitive pressure, cost of inaction + +**Our Solution section** resolves the tension: +- Approach: phased methodology framed as the answer to their challenge +- Differentiators: what makes us different, presented as evidence not assertion + +| Capability | Our Difference | Proof | +|-----------|----------------|-------| +| [Area] | [What makes us different] | [Evidence] | + +**Results & Credentials section** builds belief: +- Case studies: Challenge → Approach → Results (quantified). Include client testimonials if available +- Team: relevant experience, combined track record + +**The Deal section** makes it concrete: +- Scope (in and out), investment by phase, timeline with milestones, clear next steps + +#### 5d. Storytelling Principles + +1. **One message per slide** — anchor every element to the slide's thesis +2. **Start with why** — create urgency before presenting the solution +3. **Quantify everything** — facts build credibility +4. **Create tension** — problem → solution → result narrative arc +5. **End with action** — specific, time-bound next steps +6. **Stay on the storyline** — if a slide doesn't advance the argument, cut it +7. **Answer first** — lead with recommendations, support with analysis +8. **Design for the room** — white space, clarity over density, visuals over text walls + +### Stage 6: Oral Presentation and Defense + +For RFPs with an oral defense stage, or any client presentation of the proposal. The written proposal gets you to the shortlist; the oral presentation wins the work. + +#### 6a. Presentation Design by Time Slot + +| Time Slot | Presentation | Q&A | Slide Count | Depth | +|-----------|-------------|-----|-------------|-------| +| 30 min | 15-18 min | 12-15 min | 8-10 | Hit the 3 win themes only | +| 45 min | 25-28 min | 17-20 min | 12-15 | Win themes + methodology detail | +| 60 min | 35-40 min | 20-25 min | 15-20 | Full proposal narrative | +| 90 min | 50-55 min | 35-40 min | 20-25 | Deep methodology + case studies + team intros | + +Never fill the full time with presentation. Evaluators learn more from Q&A than from your slides, and so do you. + +#### 6b. Who Presents What + +| Section | Presenter | Why | +|---------|-----------|-----| +| Opening / relationship | Partner / Principal | Sets seniority and commitment | +| Understanding the challenge | Manager / engagement lead | Demonstrates the working team's grasp | +| Methodology | Subject matter expert | Credibility on approach | +| Case studies | Person who did the work | Authenticity over polish | +| Team | Each person, briefly | Let them see who they'll work with | +| Commercial / next steps | Partner | Decision-level conversation | + +Don't let the partner present everything. Evaluators want to see the team that will actually do the work. + +#### 6c. Q&A Preparation + +Prepare for the questions you'll get. Most fall into predictable categories: + +- **Risk / mitigation**: "What happens if this doesn't work?" "What's the biggest risk?" +- **Team commitment**: "Will the people presenting be the ones doing the work?" "What's the partner's time commitment?" +- **Methodology depth**: "Walk us through exactly how you'd handle [specific scenario]" +- **References**: "Can we speak to a client where this didn't go as planned?" +- **Pricing**: "Can you do this for less?" "What's the value per dollar?" +- **Scope**: "Can you include [thing that's out of scope]?" + +**Q&A team roles:** +- One person fields each question (don't have three people answer the same question) +- Designated person captures questions that need follow-up ("parking lot") +- If you don't know, say so and commit to a follow-up timeline + +#### 6d. Rehearsal + +Rehearse at least once with someone playing the evaluator. Focus on: +- Transitions between presenters (these are where presentations fall apart) +- Timing (cut content rather than rush) +- Q&A simulation with adversarial questions +- The first 90 seconds (if the opening is weak, you're fighting uphill) + +### Stage 6e: Best and Final Offer (BAFO) + +Some procurements (especially public sector and large enterprise) include a BAFO round after shortlisting. You've submitted your proposal, possibly presented orally, and now you're asked to submit a "best and final offer." This is a negotiation, not a revision. + +**What BAFO actually means:** +- The client has shortlisted 2-3 firms and wants to drive final competition on price, scope, or both +- Your original proposal is the baseline. BAFO is your chance to sharpen the offer, not rewrite it +- The client may share feedback on your proposal (weaknesses to address) or simply ask you to "submit your best terms" + +**BAFO strategy:** + +*When the client gives feedback:* +- Address every piece of feedback explicitly. Map your BAFO response to their concerns point by point +- Strengthen weak areas without undermining strong ones. Don't cut the methodology section to fund a price reduction +- If they flagged a team concern, consider upgrading a team member or adding a subject matter expert + +*When the client just says "submit your best and final":* +- Don't assume "best and final" means "lowest price." It means your most competitive overall offer +- Consider what you can add (value) rather than only what you can cut (price). An additional deliverable, accelerated timeline, or performance guarantee may differentiate more than a 5% discount +- If you reduce price, tie it to something: reduced scope, longer timeline, volume commitment, or multi-phase relationship. Never reduce price without a stated reason; it signals your original price had margin to burn + +**Tactical moves:** +- **Sharpen, don't slash.** A 5-10% price adjustment signals competitiveness. A 25% cut signals you were overpriced originally or you're about to cut corners +- **Restructure, don't just discount.** Move from fixed-fee to phased with gates, or offer a performance-based component. This changes the comparison framework +- **Add a conditional sweetener.** "If awarded by [date], we can guarantee [named partner] will lead the engagement" or "We will include a complimentary [half-day workshop / diagnostic] during Phase 1" +- **Hold your floor.** Know your walk-away price before the BAFO round starts. Calculate the minimum engagement economics (cost to deliver + acceptable margin) and don't go below it + +**What not to do in BAFO:** +- Don't change your core approach. The client shortlisted you based on your methodology. Swapping it now signals desperation +- Don't remove team members who were highlighted in the oral defense +- Don't submit a BAFO that contradicts your original proposal without explanation +- Don't treat it as optional. If you're asked for a BAFO and don't submit one, you've withdrawn + +### Stage 7: Post-Pursuit + +Whether you win or lose, close the loop. + +#### 7a. Win + +- Send confirmation and transition plan within 24 hours +- Introduce delivery team to client team +- Cross-reference the engagement-setup skill for kickoff planning +- Archive proposal materials for reuse on future pursuits + +#### 7b. Loss + +- Request a debrief from the client (most will agree if asked promptly) +- Ask specific questions: What was the deciding factor? Where did we score well/poorly? What would have changed the outcome? +- Document learnings: pricing feedback, methodology gaps, team perception, competitive intelligence +- Update win/loss records for pipeline analytics +- Thank the client and keep the relationship warm. Today's loss is next year's opportunity + +#### 7c. Debrief (Win or Lose) + +Internal debrief with the pursuit team: +- What worked in our process? +- What would we do differently? +- What did we learn about the client, the market, or our competitors? +- What content or materials should be templated for reuse? + +## Output Format + +Output depends on the stage requested. Each stage generates its primary artifact: + +**Opportunity Assessment** → Analysis document with fit score, evaluation breakdown, competitive landscape, win themes, and go/no-go recommendation + +**Value Proposition** → Core value proposition, stakeholder-level messages (if needed), validation results + +**Proposal** → Complete proposal document with cover page, executive summary, all sections, and appendices + +**Statement of Work** → Complete SOW with cover page, all sections, signature block, and appendices + +**Pitch Deck** → Slide-by-slide content with titles, bullets, visual suggestions, and optional speaker notes + +**Oral Presentation** → Presentation plan with timing, presenter assignments, Q&A preparation, and rehearsal notes + +After generating any artifact, offer relevant next steps: +- Move to the next stage in the lifecycle +- Adjust tone, emphasis, or scope +- Add specific case studies or credentials +- Create alternative versions (e.g., shorter deck, T&M vs. fixed-fee SOW) +- Red team review the output against evaluation criteria + +## Notes + +- Win themes developed in Stage 1 should thread through every subsequent artifact +- The executive summary may be the only thing read. Make it standalone +- Quantify results wherever possible. Specific numbers beat vague promises +- Out-of-scope lists prevent more disputes than in-scope lists +- Payment terms should align with deliverable milestones +- Design decks for the audience. C-suite gets strategic framing; working teams get operational detail +- Test value propositions against the validation criteria before committing to positioning +- For complex RFPs, recommend breaking response development into sections with review gates +- Always note if evaluation criteria weightings are explicit or inferred +- If budget is not disclosed, flag it as a risk factor and use the pricing strategy guidance to address it +- Flag any unusual requirements that may indicate a preferred vendor +- Cross-reference the engagement-setup skill when transitioning from proposal win to delivery diff --git a/management-consulting/skills/strategic-analysis/SKILL.md b/management-consulting/skills/strategic-analysis/SKILL.md new file mode 100644 index 00000000..e04aa15e --- /dev/null +++ b/management-consulting/skills/strategic-analysis/SKILL.md @@ -0,0 +1,727 @@ +--- +name: strategic-analysis +description: Hypothesis-driven problem solving with strategic framework application. Use for MECE decomposition, issue trees, hypothesis development, analytical workplans, root cause analysis, and framework-based strategic analysis (Five Forces, PESTLE, VRIO, SWOT, 7S, Ansoff, BCG Growth-Share, Value Chain, Business Model Canvas, Strategy Canvas, Blue Ocean, competitive positioning). Covers the full arc from problem definition through structured decomposition, prioritization, hypothesis testing, framework application, cross-framework synthesis, and actionable recommendations. +--- + +# Strategic Analysis + +Hypothesis-driven methodology for structuring complex business problems combined with established strategic frameworks as the analytical toolkit. The problem-solving process is the backbone; frameworks are the tools applied within it. + +## Before You Begin + +Good analysis starts with understanding the actual problem, not assuming one. Before structuring or applying frameworks: + +- **Ask clarifying questions.** What exactly is happening? Since when? How is it measured? What is the company, its industry, and approximate scale (revenue, headcount, geography)? +- **Seize on contradictions.** "Costs are rising but headcount is flat" or "NPS is up but revenue is down" are signals, not just facts to accept. Name the tension explicitly and make it a primary hypothesis driver. The most valuable problems to solve are often hiding in the gap between two things that shouldn't both be true. +- **Establish the data landscape.** What data is available vs. what needs to be gathered? Don't fabricate baseline metrics, financial figures, or market data. When illustrating a structure with example numbers, flag them clearly: "Using $X as an illustrative figure to show the math. Replace with actuals." +- **When working without confirmed data**, flag every estimate with its basis and confidence level. Present market sizes, share figures, and growth rates as directional estimates to be validated, not as established facts. + +### Two Modes of Operation + +- **Structuring mode** (no data provided): Build the issue tree, form hypotheses, select frameworks, design the analytical workplan, and specify what data would prove or disprove each hypothesis. The output is a roadmap for the analysis. +- **Analysis mode** (data provided): Apply frameworks, run the analysis, test hypotheses against the data, synthesize findings, and deliver recommendations. The output is answers. + +Default to structuring mode unless the user provides data to analyze. When operating in structuring mode, open with an explicit statement: "Operating in structuring mode since no data has been provided. The output will be a roadmap: issue tree, hypotheses, framework selection, and an analytical workplan specifying what data to collect and how to test each hypothesis." This sets expectations that the deliverable is a plan, not answers. + +--- + +## The Problem-Solving Process + +### Step 1: Define the Problem + +Before any analysis, rigorously define the problem. Get outcome clarity and constraints upfront. + +A good problem definition covers: + +- **The Question**: What exactly are we trying to solve? State in one sentence. +- **The Context**: Industry dynamics, company position, timeframe, technology landscape. +- **Quantification**: Size the problem. What is the financial impact of the status quo? What is the value of solving it? Anchor all subsequent prioritization to these numbers. If exact figures aren't available, estimate the order of magnitude. +- **Success Criteria**: What does a successful solution look like? How will we measure it? What are the constraints? What is the decision timeline? +- **Out of Scope**: What are we NOT solving for? What boundaries exist? + +**Look for contradictions and tensions in the problem statement.** "Market share declined despite increased marketing spend" contains a tension (more spend should equal more share). "Customer satisfaction scores are high but churn is rising" is another. Name the tension explicitly and make it a primary hypothesis driver. + +**Validate the premise before proceeding:** + +- Is the data behind this problem statement reliable? How was it measured? +- Is the comparison fair? (Apples-to-apples scope, same definitions, same time periods) +- Is the stated problem actually a problem, or is it a solution looking for justification? +- Are we solving symptoms or root causes? +- What would happen if we did nothing? + +### Step 2: Structure the Problem + +Apply MECE decomposition (Mutually Exclusive, Collectively Exhaustive) to break the problem into non-overlapping, complete branches. + +**Issue tree templates by problem type:** + +| Problem Type | Recommended Structure | +|---|---| +| Profitability decline | Revenue (price x volume) + Cost structure | +| Market entry | Market size x Achievable share + Entry requirements | +| Operational inefficiency | Throughput x Yield + Cycle time | +| Customer churn | Acquisition x Retention x Lifetime value | +| Growth strategy | Core business + Adjacent opportunities + Transformational bets | +| Digital transformation | Current state + Capability gaps + Technology options | +| Cost reduction | MECE cost waterfall by value chain stage + overhead | +| Build vs. buy | Strategic fit + Economics (TCO) + Execution risk | +| Pricing strategy | Value to customer + Cost to serve + Competitive positioning | +| Org effectiveness | Structure + Processes + People + Technology | +| M&A evaluation | Strategic rationale + Valuation + Integration feasibility | + +**MECE in practice:** + +NOT MECE (overlapping): +- North America, Europe, Emerging markets, Developed markets + +MECE: +- North America, Europe, Asia-Pacific, Latin America, Middle East & Africa + +NOT MECE (inconsistent categories): +- Product revenue, Service revenue, License revenue, Software + +MECE: +- Product revenue, Service revenue, License revenue, Other revenue + +For digital businesses, consider alternative MECE cuts: +- Recurring revenue (subscriptions, SaaS), Transaction revenue (usage-based, marketplace), Professional services, Ecosystem/partner revenue + +#### Which Tree Do You Need? + +This is the most common point of confusion in structured problem solving. The diagnostic is simple: + +**Ask: "Am I choosing between competing explanations, or breaking a known problem into its parts?"** + +| Signal | You Need a... | Why | +|---|---|---| +| "Why is X happening?" with multiple plausible causes | **Hypothesis tree** | You're testing competing theories. The branches are mutually exclusive explanations, and the goal is to eliminate wrong answers. | +| "How do we improve X?" or "What drives X?" | **Logic tree** | You're decomposing a system into its component drivers. The branches coexist (they're all real), and the goal is to find the biggest lever. | +| "Revenue dropped 20% last quarter" | **Hypothesis tree** | Something changed. You need to figure out *what*. Was it pricing? Volume? Mix? Churn? These compete as explanations. | +| "How do we grow revenue by 20%?" | **Logic tree** | You need to map all the ways revenue can grow (price, volume, mix, new products, new segments) and size each lever. | +| You could be wrong about the cause | **Hypothesis tree** | The value is in disproving wrong theories fast. | +| The causes are known; the question is relative magnitude | **Logic tree** | The value is in comprehensive decomposition and prioritization. | + +**The mistake**: Using a logic tree when you should be using a hypothesis tree. This happens when someone decomposes "revenue declined" into "price x volume" (logic tree) instead of asking "why did revenue decline?" and generating competing hypotheses (pricing error vs. competitive loss vs. customer churn vs. macro downturn). The logic tree maps the math; the hypothesis tree maps the possible causes. You often need both: the logic tree tells you *where* the problem is (volume dropped), and the hypothesis tree tells you *why* (competing theories about volume loss). + +**Hypothesis Tree** + +Use when you have competing theories about what's happening. The branches are alternative explanations, and the goal is to eliminate wrong answers quickly. + +``` + [Ultimate Question] + + ┌───────────────┼───────────────┐ + ▼ ▼ ▼ + [Hypothesis 1] [Hypothesis 2] [Hypothesis 3] + │ │ │ + ┌────┴────┐ ┌────┴────┐ ┌────┴────┐ + ▼ ▼ ▼ ▼ ▼ ▼ + [Proof 1] [Proof 2] [Proof 1] [Proof 2] [Proof 1] [Proof 2] + │ │ │ + [Quick Test] [Quick Test] [Quick Test] +``` + +Start with the ultimate question. Branch into competing hypotheses. Under each hypothesis, identify the proof points needed and the quickest way to test them. The key discipline: design a quick test for each hypothesis that could *disprove* it, not just confirm it. + +**Logic Tree** + +Use when you need to decompose a problem into its component drivers. The branches coexist (they're all real parts of the system), and the goal is to find the biggest lever. + +``` + [Problem Statement] + + ┌───────────────┼───────────────┐ + ▼ ▼ ▼ + [Driver A] [Driver B] [Driver C] + │ │ + ┌────┴────┐ ┌────┴────┐ + ▼ ▼ ▼ ▼ + [Factor 1] [Factor 2] [Factor 3] [Factor 4] + │ │ + [Root Cause] [Root Cause] +``` + +Decompose the problem into its causal drivers. Keep branching until you reach actionable root causes. The key discipline: ensure MECE at every level (no overlaps, no gaps). + +### Step 3: Prioritize Issues + +Not all branches deserve equal attention. Rank branches by estimated impact and data availability. + +Use a 2x2 prioritization: + +| | High Data Availability | Low Data Availability | +|---|---|---| +| **High Expected Impact** | Analyze first | Design data collection, analyze in parallel | +| **Low Expected Impact** | Quick scan, move on | Deprioritize | + +Decision criteria: +- Where is the biggest lever? (Quantify: "This branch represents ~$Xm of the gap") +- Where is the data available? +- What can we test quickly with minimum viable analysis? +- What is the time sensitivity? + +### Step 4: Select Frameworks and Develop Hypotheses + +Once the problem is structured, select the right analytical frameworks and form testable hypotheses. Frameworks provide the lens; hypotheses focus the analysis. + +#### Framework Selection + +Match frameworks to the question being asked. Always apply at least 2 frameworks to any strategic question. + +| Question | Primary Framework | Complementary Pairing | Avoid | +|---|---|---|---| +| How attractive is our industry? | Five Forces Analysis | PESTLE, Value Chain | SWOT (not designed for industry-level analysis) | +| How should we compete? | Competitive Positioning | Strategy Canvas, VRIO | Ansoff (growth strategy, not competitive strategy) | +| How is our organization aligned? | 7S Framework | Balanced Scorecard | Five Forces (external, not internal) | +| What is our competitive advantage? | VRIO | Value Chain, Five Forces | SWOT (too generic for advantage analysis) | +| How should we grow? | Ansoff Matrix | Growth-Share Matrix, Three Horizons | VRIO (diagnostic, not prescriptive for growth) | +| What external factors affect us? | PESTLE | Five Forces, SWOT | 7S (internal only) | +| What are our strengths and weaknesses? | SWOT Analysis | PESTLE (external), VRIO (internal) | Growth-Share Matrix (portfolio, not capability) | +| How should we enter a new market? | Market Entry Framework | Five Forces, PESTLE | Balanced Scorecard (performance tracking, not entry) | +| What is our business model? | Business Model Canvas | Value Chain, Platform Strategy | Five Forces (industry, not firm model) | +| How do we create value? | Value Chain | Business Model Canvas, Competitive Positioning | Ansoff (growth paths, not value creation) | +| How do we measure performance? | Balanced Scorecard | 7S Framework | Strategy Canvas (competitive, not performance) | +| How should we allocate resources? | Growth-Share Matrix | Nine-Box, Three Horizons | PESTLE (external context, not allocation) | +| What are our strategic options? | Strategy Canvas | Three Horizons, Ansoff Matrix | Balanced Scorecard (tracking, not option generation) | +| How do we build a platform? | Platform Strategy | Business Model Canvas, Five Forces | 7S (org alignment, not platform design) | + +**Redirect framework requests when appropriate.** Clients often request a specific framework by name ("do a SWOT") when a different framework would better answer their actual question. When this happens: (a) acknowledge the request, (b) apply the requested framework, but (c) flag the better-fit framework and explain why. Never refuse the requested framework outright; instead, use it as one of the two required frameworks and pair it with the one that better fits the question. + +#### Day 1 Answer + +Before any analysis, state your best guess at the final answer based on available information. This is not a commitment. It is a focusing device. + +The Day 1 answer should be: +- A complete sentence answering the original question +- Your current confidence level (low/medium/high) +- The 1-2 analyses that would most change your mind + +This forces intellectual honesty. If you can't form even a tentative answer, you don't understand the problem well enough. + +#### Hypothesis Development + +A good hypothesis: +- Is specific and concrete +- Is testable with available data +- Implies a recommended action if proven true +- States "we believe X because Y" +- Has a quick validation path + +For each hypothesis, define: +- **Current belief**: What we think is true +- **Evidence needed**: What would prove or disprove it +- **Data source**: Where to find the evidence +- **Quick test**: Fastest way to validate or invalidate +- **If true, then**: What we'd recommend + +### Step 5: Conduct Analysis + +Structure analysis to test hypotheses, not to generate data for its own sake. Apply selected frameworks to the prioritized branches. + +For each analysis workstream, define: +- Which hypothesis it tests +- The analytical method (including which framework) +- Data inputs required +- Expected output and what it tells us + +Analytical approaches by situation: + +| Situation | Recommended Analysis | +|---|---| +| Profit driver identification | Bridge analysis, variance analysis | +| Market sizing | Top-down, bottom-up, triangulated | +| Competitive assessment | Five Forces, Strategy Canvas, relative positioning | +| Internal capability | VRIO, Value Chain, 7S | +| External environment | PESTLE, Five Forces | +| Financial projections | Scenario modeling, sensitivity analysis | +| Process optimization | Root cause analysis, process mining, time studies | +| Customer insights | Segmentation, cohort analysis, journey mapping | +| Cost gap analysis | Cost bridge/waterfall decomposition | +| Growth strategy | Ansoff Matrix, Three Horizons, Growth-Share | +| Business model | Business Model Canvas, Platform Strategy | + +For each analysis, document assumptions, check sensitivity (which inputs matter most), and actively seek disconfirming evidence. + +#### Data Confidence Markers + +When working without access to proprietary client data or real-time market data: +- Flag estimates with confidence level: "~$30B (industry estimate, +/- 15%)" +- Distinguish between directionally certain and precisely uncertain: "Fee compression is directionally certain; the rate (estimate: 3-5% annually) requires validation" +- Identify the 2-3 data points that, if validated, would most change the recommendations +- Recommend specific data sources the client should validate against (industry reports, internal data, customer research) + +### Step 6: Synthesize Findings + +Synthesis is NOT summary. Summary says "we found X." Synthesis says "X means Y, which changes our recommendation to Z." + +**Lead with the answer (Pyramid Principle):** + +1. **The Answer** (1 sentence): Direct response to the original question +2. **Three supporting arguments**: The key reasons behind the answer, ordered by importance +3. **Evidence for each argument**: The specific data that proves each point + +#### Cross-Framework Synthesis + +When multiple frameworks have been applied, synthesize across them. Individual frameworks provide structure, but the connections between them drive insight. + +**External Landscape** +- Industry attractiveness (Five Forces assessment, overall profit potential) +- Key external trends (PESTLE top 3 trends with timeline and impact) +- Competitive dynamics (where is power shifting?) + +**Internal Position** +- Organizational alignment (7S assessment, where are the gaps?) +- Competitive advantage (VRIO assessment, what's truly sustainable?) +- Value creation (Value Chain insights, where do we win?) + +**Growth Options** +- Current portfolio (Growth-Share assessment) +- Growth strategy (Ansoff recommendation with risk-adjusted view) +- Future pipeline (Three Horizons view, are we investing enough in H2/H3?) + +**Cross-Framework Findings** +- **Converging findings**: Where 2+ frameworks agree (high confidence insights) +- **Contradictions**: Where frameworks disagree (requires judgment call, often reveals the most important insight) +- **Blind spots**: What none of the frameworks capture (qualitative factors, culture, timing) +- **Highest-leverage insight**: The single most important finding across all analyses + +Look for the non-obvious connection. The most valuable insight from multi-framework analysis is usually where two frameworks, applied independently, point to a conclusion neither would reach alone. State this explicitly: "Five Forces shows X, VRIO shows Y, and together they suggest Z." If cross-framework synthesis only restates what each framework already said, you haven't synthesized... you've summarized. + +#### End Each Framework Section with a "So What?" + +One to two sentences stating the single most important implication of that framework for the client's decision. Not a summary of findings, but the actionable takeaway. + +**Anti-patterns to avoid:** +- "We found many interesting things" (no hierarchy, no answer) +- Restating findings without interpretation +- Burying the answer at the end +- Presenting analysis in the order it was conducted rather than the order that supports the argument +- Confusing "thorough" with "useful" (every finding must connect to the answer) + +**Test your synthesis:** Can someone read only the first paragraph and understand the answer and why? If not, restructure. + +### Step 7: Develop Recommendations + +Translate findings into action. Each recommendation needs: +- **Rationale**: Why this addresses the problem +- **Impact**: Expected outcome, quantified +- **Effort**: Resources required +- **Timing**: When to act (quick wins vs. structural changes) +- **Implementation approach**: How to execute +- **Risks**: What could go wrong and how to mitigate + +**Key Risks** + +| Risk | Likelihood (H/M/L) | Impact (H/M/L) | Mitigation | +|---|---|---|---| +| [Risk 1] | | | [Action] | +| [Risk 2] | | | [Action] | +| [Risk 3] | | | [Action] | + +Identify the "single point of failure": the one risk that could invalidate the entire strategy. + +**Implementation Priorities** +- Phase 1 (0-6 months): Quick wins that build momentum and prove the thesis +- Phase 2 (6-18 months): Medium-term capability building +- Phase 3 (18+ months): Long-term strategic positioning + +--- + +## Behavioral Principles + +1. **Always apply at least 2 frameworks** to any strategic question. Single-framework analysis is incomplete. +2. **Provide substantive analysis, not empty templates.** For each cell, give 2-3 sentences of reasoning with evidence. +3. **Quantify wherever possible.** Use specific numbers, not vague ratings: + - Market share: "Competitor A holds ~35% share, representing ~$X.XB revenue" + - Risk: "Regulatory change probability: ~40%, estimated revenue impact: $XM-$XM" + - Timing: "Expected market entry window: Q3 2026-Q1 2027 based on [trigger]" + - Investment: "Required investment: $XM-$XM with X-X year payback period" +4. **Synthesize across frameworks.** Call out where frameworks agree (high confidence), disagree (needs judgment), and what none of them capture (blind spots). +5. **End with prioritized recommendations.** Analysis without action items is incomplete. +6. **State key assumptions explicitly.** When client context is incomplete, list 3-5 assumptions at the top of the analysis. Flag which assumptions most affect the conclusions. Example: "Assumes client revenue is $200-400M (sensitivity: if <$100M, organic build becomes infeasible and acquisition is the only viable entry mode)." +7. **Validate data early.** Before deep analysis, flag the 2-3 data points that most affect the conclusions and recommend the client validate them. Structure as: "Data validation priorities: (1) [data point] ... if this is wrong, [which conclusion] changes. (2) [data point] ... needed to confirm [which recommendation]." + +### Output Calibration + +Calibrate depth to the use case. Default to working analysis unless the user specifies otherwise. + +- **Executive summary** (500-800 words): Key findings from 2-3 frameworks applied briefly. Prioritized recommendations with sizing. No detailed tables. +- **Working analysis** (2,000-4,000 words): Full framework application with tables, cross-framework synthesis, and prioritized recommendations. This is the default. +- **Deep dive** (4,000-8,000 words): Comprehensive multi-framework analysis with detailed evidence per factor, scenario analysis, implementation roadmap, and risk register. + +--- + +## Framework Reference + +### External Analysis + +#### Five Forces Analysis + +**Purpose**: Assess industry attractiveness and competitive intensity. + +For each of the five forces (New Entrants, Buyer Power, Supplier Power, Substitutes, Competitive Rivalry): +- Rate the force as High/Medium/Low with a 1-2 sentence justification +- Create a table with columns: Factor | Assessment | Implication +- Include 4-6 factors per force, including digital/platform dimensions (network effects as entry barrier, digital switching costs, platform supplier power, digital substitutes, winner-takes-all dynamics) +- After all five forces, provide an Industry Attractiveness Summary (overall profit potential) and Strategic Implications (how to compete, where to position, how to mitigate unfavorable forces) + +**So What?** End with: "This industry is [attractive/unattractive/mixed] for [client] because [specific reason]. The dominant force shaping profitability is [X], which means [strategic implication]." + +#### PESTLE Analysis + +**Purpose**: Analyze external macro-environmental factors. + +For each dimension (Political, Economic, Social, Technological, Legal, Environmental): +- Create a table with columns: Factor | Trend | Impact (H/M/L) | Timeframe (S/M/L) | Strategic Response +- Include 2-4 factors per dimension +- Conclude with Key Trends Summary: the top 3 most significant trends ranked by strategic impact + +**So What?** End with: "The external environment is [favorable/hostile/shifting] on a [timeframe]. The single trend most likely to reshape the competitive landscape is [X], requiring [response] within [timeframe]." + +#### SWOT Analysis + +**Purpose**: Assess strategic position through internal strengths/weaknesses and external opportunities/threats. + +Create four tables (Strengths, Weaknesses, Opportunities, Threats) with columns: Factor | Evidence | Strategic Significance (H/M/L). Include 3-5 factors per quadrant, grounded in evidence rather than generic claims. After the four quadrants, generate a Cross-Quadrant Strategy Matrix: +- **SO strategies**: Use strengths to capture opportunities +- **WO strategies**: Address weaknesses to capture opportunities +- **ST strategies**: Use strengths to counter threats +- **WT strategies**: Mitigate weaknesses against threats + +Conclude with the 2-3 highest-priority strategic actions. + +**So What?** End with: "The strategic position is [strong/vulnerable/mixed]. The highest-leverage move is [SO/WO/ST/WT strategy] because [reason]." + +### Internal Analysis + +#### 7S Framework + +**Purpose**: Assess organizational alignment and capability. + +Create two summary tables: +- Hard Elements (Strategy, Structure, Systems) with columns: Element | Current State | Target State | Gap | Priority +- Soft Elements (Shared Values, Style, Staff, Skills) with the same columns + +For each of the 7 elements, provide 2-3 current-state observations and key gaps identified. + +Conclude with: +- **Alignment Assessment**: Which elements are aligned, which have gaps, implications of misalignment +- **Recommendations**: 3-5 prioritized actions to close gaps + +**So What?** End with: "The organization is [aligned/misaligned] on [X]. The most critical gap is [element], which is blocking [strategic objective]." + +#### VRIO Framework + +**Purpose**: Assess competitive advantage and resource sustainability. + +Create a VRIO table with columns: Resource/Capability | Valuable? | Rare? | Costly to Imitate? | Organized to Capture? | Competitive Implication. + +Map implications: +- Not Valuable = Competitive Disadvantage +- V only = Competitive Parity +- V+R = Temporary Advantage +- V+R+I+O = Sustained Advantage + +Conclude with which resources provide sustained advantage, which need development, and what the imitation barriers are. + +**So What?** End with: "[Client] has [N] sources of sustained advantage. The most defensible is [X] because [imitation barrier]. The critical gap is [resource that is V+R but not I or O]." + +#### Balanced Scorecard + +**Purpose**: Translate strategy into measurable objectives across four perspectives. + +For each perspective (Financial, Customer, Internal Process, Learning & Growth), create a table with columns: Objective | Measure | Target | Initiative | Status. Include 3-4 objectives per perspective. Ensure objectives cascade logically: Learning & Growth capabilities enable Internal Process excellence, which drives Customer outcomes, which deliver Financial results. + +Conclude with a Strategy Map narrative showing cause-effect linkages and identifying any broken links in the strategy logic. + +**So What?** End with: "The strategy logic [holds/breaks] at [perspective]. The broken link is [X], meaning [investment/objective] won't deliver the expected [outcome] without [fix]." + +#### Value Chain Analysis + +**Purpose**: Understand how value is created in the business. + +Create two tables: +- Primary Activities (Inbound Logistics, Operations, Outbound Logistics, Marketing & Sales, Service) with columns: Activity | Description | Value Created | Cost | Competitive Advantage (H/M/L) +- Support Activities (Procurement, Technology, HR, Infrastructure) with the same columns + +Conclude with Value Chain Linkages (how activities reinforce each other), Cost Analysis, and Differentiation Sources. + +**So What?** End with: "Value creation is concentrated in [activity]. The strongest linkage is between [X] and [Y]. The cost/differentiation trade-off suggests [strategic action]." + +### Strategy Formulation + +#### Growth-Share Matrix + +**Purpose**: Analyze business portfolio and resource allocation. + +Create a portfolio table with columns: Business Unit | Market Growth Rate (%) | Relative Market Share | Quadrant (Star/Question Mark/Cash Cow/Dog) | Strategy (Invest/Hold/Harvest/Divest). + +Conclude with Portfolio Implications (cash flow dynamics, investment requirements, rebalancing needs) and 3-4 prioritized recommendations. + +**So What?** End with: "The portfolio is [balanced/unbalanced]. Cash cows generate ~$XM to fund [Stars/Question Marks]. The critical decision is [invest/divest] on [specific unit]." + +#### Ansoff Matrix + +**Purpose**: Analyze growth strategies across four paths. + +Start with the current position (products, markets, revenue). Then create a summary table with columns: Strategy | Risk Level | Opportunity | Key Consideration. + +For each of the four strategies (Market Penetration, Product Development, Market Development, Diversification), assess: approach, opportunity size, risk level, and investment required. + +Conclude with Recommended Strategy: primary choice with rationale, secondary option, and investment requirements. + +**So What?** End with: "The recommended growth path is [strategy] because [reason], representing ~$XM opportunity at [risk level]. Avoid [strategy] because [reason]." + +#### Nine-Box Matrix + +**Purpose**: Multi-business portfolio prioritization. + +Plot business units on a 3x3 matrix (Market Attractiveness vs. Competitive Position). Create a table with columns: Business Unit | Market Attractiveness (H/M/L) | Competitive Position (H/M/L) | Strategy (Invest/Select/Harvest/Divest). Conclude with investment allocation implications. + +#### Three Horizons Model + +**Purpose**: Balance short-term and long-term growth. + +For each horizon, create an initiative table: +- **H1 (0-12 months)**: Defend and grow core. Columns: Initiative | Impact | Investment | Timeline +- **H2 (1-3 years)**: Nurture emerging businesses. Columns: Initiative | Market Size | Investment | Timeline +- **H3 (3-7+ years)**: Create future options. Columns: Option | Potential | Risk | Investment + +Conclude with Investment Allocation (% split across horizons) and Key Risks per horizon. + +**So What?** End with: "The current investment split is [X/Y/Z%] across horizons. The portfolio is [over-invested in H1/under-invested in H2-H3]. The most promising H2/H3 bet is [X]." + +### Competitive Strategy + +#### Competitive Positioning + +**Purpose**: Define competitive positioning. + +Assess current position across three dimensions (Target Scope, Cost Advantage, Differentiation). Then evaluate each generic strategy (Cost Leadership, Differentiation, Focus) covering: suitability conditions, required capabilities, and key risks. + +Conclude with Recommended Strategy: chosen position, rationale, how to achieve, and how to defend. + +**So What?** End with: "The winning position is [strategy] because [reason]. The single capability that must be built is [X]. The key risk is [stuck in the middle / competitor imitation / focus trap]." + +#### Strategy Canvas + +**Purpose**: Visualize competitive differentiation by comparing value curves across key factors. + +Identify 6-10 factors the industry competes on (price, quality, features, service, brand, convenience, etc.). Create a table with columns: Competing Factor | Our Company (1-5) | Competitor A (1-5) | Competitor B (1-5) | Industry Average (1-5). + +Identify where your curve diverges from competitors (differentiation) and where it converges (parity). + +Then create an ERRC (Eliminate-Reduce-Raise-Create) table to define the target value curve: + +| Action | Factor | Rationale | +|---|---|---| +| **Eliminate** | [factors to remove entirely] | [why: cost savings, irrelevant to target segment] | +| **Reduce** | [factors to reduce below industry average] | [why: over-served, diminishing returns] | +| **Raise** | [factors to raise above industry average] | [why: underserved need, willingness to pay] | +| **Create** | [new factors not currently competed on] | [why: unmet need, new value source] | + +Conclude with Differentiation Assessment and a recommended Target Value Curve. + +**So What?** End with: "The blue ocean opportunity is [create/raise X while eliminating/reducing Y], which redefines competition from [current basis] to [new basis]." + +### Business Model and Platform + +#### Business Model Canvas + +**Purpose**: Map and evaluate the complete business model. + +Analyze all nine building blocks in a table with columns: Block | Current State | Strengths | Vulnerabilities. The blocks: Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, Cost Structure. + +Assess how the blocks reinforce each other. Conclude with: +- **Model Coherence**: Where blocks align vs. conflict +- **Sustainability**: Which blocks are hardest for competitors to replicate +- **Evolution Opportunities**: Where shifts could transform the model + +**So What?** End with: "The business model is [coherent/fragmented]. The most vulnerable block is [X] because [reason]. The highest-leverage evolution is [shift]." + +#### Market Entry Framework + +**Purpose**: Evaluate and select market entry strategies for new geographies or segments. + +Assess market attractiveness in a table with columns: Factor | Assessment | Data Source | Implication (covering market size, growth rate, competitive intensity, regulatory barriers, cultural factors). + +Evaluate entry modes (organic build, acquisition, joint venture, partnership, licensing, export) in a table with columns: Entry Mode | Investment Required | Risk Level | Speed to Market | Control Level | Recommendation. + +Conclude with Recommended Entry Strategy, sequencing, and key success factors. + +**So What?** End with: "Enter [market] via [mode] because [reason]. Investment: ~$XM. Break-even: [timeframe]. The go/no-go decision hinges on [single factor]." + +#### Platform Strategy + +**Purpose**: Assess and design platform-based business models. + +**Step 1: Platform Classification** + +Identify the platform type. This determines the economics and strategic playbook. + +| Platform Type | Core Mechanism | Key Metric | Examples | +|---|---|---|---| +| Marketplace | Matches buyers and sellers | Liquidity (match rate, time-to-match) | Airbnb, Uber, eBay | +| Innovation platform | Enables third-party development | Developer adoption, API calls, app count | iOS, AWS, Salesforce | +| Social platform | Facilitates user interactions | DAU/MAU ratio, engagement, content creation rate | Facebook, Reddit, Discord | +| Data platform | Aggregates data to generate insights | Data volume, data freshness, unique data assets | Bloomberg, Palantir | +| Hybrid | Combines 2+ of the above | Varies by dominant mechanism | Amazon (marketplace + innovation), Google (data + innovation) | + +**Step 2: Ecosystem Mapping** + +Map participants in a table with columns: Participant Type | Role | Value Created | Value Captured | Incentive to Join | Switching Costs. + +**Step 3: Network Effects Analysis** + +Network effects are the primary source of platform defensibility. Assess each type: + +| Network Effect Type | Description | Strength Assessment | Defensibility | +|---|---|---|---| +| **Same-side (direct)** | More users on one side attract more users on the same side | Strong if users actively recruit others; weak if value doesn't scale with user count | High if strong (hard to leave when your network is there) | +| **Cross-side (indirect)** | More users on one side attract more users on the other side | Strong if both sides see measurable value from the other's growth; weak if one side is indifferent | Medium to high (depends on multi-homing) | +| **Data network effects** | More usage generates more data, which improves the product, which attracts more users | Strong if data genuinely improves the core value prop; weak if improvements plateau | High if the improvement curve hasn't flattened | +| **Content/inventory** | More content/listings attract more consumers, whose demand attracts more content | Strong if supply is fragmented and hard to aggregate elsewhere; weak if supply is concentrated | Medium (content can be multi-homed) | + +For each applicable network effect, assess: +- **Current strength**: Is the flywheel actually spinning, or is it theoretical? +- **Inflection point**: At what scale does the network effect become self-sustaining? +- **Diminishing returns**: At what point does adding more users/data stop improving the experience? + +**Step 4: Multi-Homing Risk** + +Multi-homing (users participating on competing platforms simultaneously) is the single biggest threat to platform economics. Assess: + +| Factor | Low Multi-Homing Risk | High Multi-Homing Risk | +|---|---|---| +| Switching costs | High (data, reputation, integrations locked in) | Low (no data portability barriers, easy to join) | +| User investment | Users build profiles, reputations, content | Users are anonymous or transactional | +| Differentiated supply | Exclusive or hard-to-replicate supply | Commodity supply available everywhere | +| Pricing | Users penalized for splitting activity (volume discounts, loyalty rewards) | No cost to participating on multiple platforms | +| Integration depth | Deep workflow/API integrations | Standalone, shallow usage | + +If multi-homing risk is high, the platform must compete on execution every transaction, not on lock-in. Strategy shifts from network effects to operational excellence, curation, and trust. + +**Step 5: Platform Economics** + +Assess the unit economics and monetization model: + +- **Subsidized side vs. monetized side**: Which side do you subsidize to build critical mass? What's the subsidy cost and how long until the platform is self-sustaining? +- **Take rate / monetization**: What percentage of value does the platform capture? Sustainable range depends on the platform's value-add (5-15% for distribution; 20-30% for trust, payments, insurance; >30% risks disintermediation). +- **Winner-takes-all dynamics**: Does this market tend toward one dominant platform or can multiple coexist? +- **Margin structure**: Platform businesses often have high gross margins (60-80%+) but require significant investment in growth before profitability. Model the path to contribution margin breakeven by cohort or geography. + +**Step 6: Conclusion** + +Conclude with: +- **Platform Design**: Governance model (open vs. curated), openness strategy (API access, data sharing), monetization approach +- **Growth Strategy**: How to solve the chicken-and-egg problem (single-player mode, seeding supply, concentrating geographically, marquee partnerships). What is the minimum viable liquidity? +- **Defensibility Assessment**: Which network effects are real vs. theoretical? What is the multi-homing risk? How deep are switching costs? + +**So What?** End with: "The platform's defensibility rests on [network effect type]. The critical mass threshold is [X users/transactions]. The biggest risk is [multi-homing/disintermediation/regulation]." + +### Market and Competitive Analysis + +When conducting market analysis, structure the work in layers: + +**Market Sizing** +- Use TAM (Total Addressable Market), SAM (Serviceable Addressable Market), SOM (Serviceable Obtainable Market) +- Triangulate using both top-down and bottom-up approaches +- Distinguish between market size and addressable opportunity +- Document growth rates (historical CAGR and forecast) with drivers +- Apply data confidence markers to all estimates + +**Competitive Landscape** +- Map competitors by market share, revenue, growth rate, and positioning +- Profile key competitors on strengths, weaknesses, strategy, and threats +- Assess competitive positioning across dimensions that matter to customers (price, quality, reach, innovation) +- Look for emerging competitors and adjacent-market entrants, not just established players + +--- + +## Common Pitfalls + +| Pitfall | Why It's Problematic | Solution | +|---|---|---| +| Defining the problem too broadly | Diffuses analysis, no clear success criteria | Narrow scope iteratively, quantify the problem | +| Skipping the Day 1 answer | Analysis drifts without a point of view | Force a tentative answer before analysis begins | +| Jumping to solutions | Misses root causes | Follow the process: define, structure, hypothesize, then solve | +| Collecting all data | Wastes time on low-value analysis | Prioritize by hypothesis, apply 80/20 | +| Confirming existing beliefs | Biases analysis | Actively seek disconfirming evidence | +| Summarizing instead of synthesizing | No actionable insight | Lead with the answer, then support it | +| Presenting findings without recommendations | Leaves client without action | Always translate findings to actions | +| Applying frameworks mechanically | Empty templates, no insight | Provide substantive reasoning per cell, end each with "So What?" | +| Using one framework alone | Incomplete picture, overfit to one lens | Always pair frameworks, synthesize across them | +| Wrong framework for the question | Misaligned analysis, wasted effort | Use the framework selection guide, redirect when appropriate | + +--- + +## Worked Example + +**Prompt**: "Our SaaS company's enterprise churn rate jumped from 8% to 14% last quarter. Help me structure an analysis to understand why and what we should do about it." + +### Step 1: Define the Problem + +- **Question**: Why did enterprise churn increase from 8% to 14% last quarter, and what can we do to reverse it? +- **Quantification**: A 6-point jump in one quarter is acute (not gradual drift), suggesting a triggering event. At 14% annualized, if average enterprise ACV is $200K and we have 300 enterprise accounts, we're losing ~$8.4M ARR/year vs. ~$4.8M at baseline. The incremental exposure is ~$3.6M ARR. +- **Premise check**: Is 14% calculated consistently with the prior 8%? Same denominator (beginning-of-period accounts)? Same definition of "churn" (logo vs. revenue, gross vs. net)? +- **Success criteria**: Identify the 2-3 root drivers, quantify their contribution, and develop interventions to return churn to <10% within 2 quarters. +- **Out of scope**: SMB/mid-market churn, new logo acquisition, pricing overhaul (unless directly implicated). + +### Step 2: Structure (MECE) + +This is a "why is X happening?" question with competing plausible causes, so we need a **hypothesis tree** (not a logic tree). Something changed; we need to figure out what. + +Three branches (mutually exclusive, collectively exhaustive... every churn event is driven by one of these): + +1. **We caused it** (Product/service failures): Feature regressions, support quality decline, CSM turnover +2. **Competitors caused it** (Market shift): New entrant, price undercut, feature parity shift +3. **Customer circumstances changed** (External): Budget cuts, M&A, leadership turnover + +### Step 3: Prioritize + +| Branch | Expected Impact | Data Availability | Priority | +|---|---|---|---| +| Product/Service | HIGH (most common SaaS churn driver) | HIGH (usage data, tickets, NPS) | Analyze first | +| Competitive | MEDIUM | MEDIUM (win/loss, exit surveys) | Parallel track | +| Customer-side | MEDIUM | LOW (requires outreach) | Quick scan of top 10 churned accounts | + +### Step 4: Framework Selection, Day 1 Answer & Hypotheses + +**Framework selection**: This is primarily a diagnostic problem (why did churn spike?), but it has a strategic component (how do we compete to retain?). Primary analysis: hypothesis-driven root cause. Complementary framework: **Five Forces** on the competitive dynamics (is buyer power or rivalry shifting?) and **VRIO** on retention capabilities (do we have defensible advantages that should prevent churn?). + +**Day 1 answer**: "Enterprise churn spiked because a Q3 product release degraded the enterprise experience, compounded by CSM turnover that left accounts without a relationship anchor during the disruption." Confidence: Medium. The analysis that would most change my mind: usage data overlay with churn timing. + +**Hypotheses:** + +H1: A product release degraded the enterprise experience. +- Quick test: Overlay churn dates with release dates. Compare support ticket volume in churned vs. retained accounts. + +H2: A competitor made a significant move. +- Quick test: Pull exit survey verbatims, count competitor mentions. Apply Five Forces lens: has buyer power shifted? + +H3: CSM changes left accounts unanchored. +- Quick test: Compare churn rate for accounts with CSM reassignment vs. stable CSM coverage. Apply VRIO lens: is our CSM capability Valuable and Rare, or is it at parity? + +H4: Enterprise customers are cutting vendor spend due to macro pressure. +- Quick test: Check top 10 churned accounts for public signals (layoffs, earnings warnings). PESTLE scan on macro conditions. + +### Step 5: Analytical Workplan + +| Workstream | Tests | Method | Framework | Timeline | +|---|---|---|---|---| +| Churn cohort analysis | H1-H4 | Segment churned accounts by tenure, size, industry, usage | Root cause decomposition | Week 1 | +| Product usage analysis | H1 | Usage metrics (DAU, feature adoption) in churned vs. retained, 90 days pre-churn | Variance analysis | Week 1 | +| Competitive assessment | H2 | Exit survey verbatims, 5-8 win-back interviews, competitive positioning map | Five Forces, Strategy Canvas | Week 1-2 | +| CSM coverage analysis | H3 | Churn rate by CSM tenure, reassignment events | VRIO on retention capabilities | Week 1 | +| External signal scan | H4 | Cross-reference churned accounts with public filings, layoff news | PESTLE (abbreviated) | Week 1 | + +### Step 6: Synthesis (structure, not yet populated) + +"Enterprise churn spiked from 8% to 14% because [root cause], accounting for [X%] of the incremental churn. [Secondary driver] contributed [Y%]. We recommend [top 3 actions] to return churn to <10% by [quarter]." + +Three supporting arguments would follow, each backed by specific data from the workstreams above. + +**Cross-framework synthesis would address:** +- **Converging**: Do Five Forces and VRIO agree on whether the churn is structural (industry shifting) or operational (fixable)? +- **Contradiction**: If VRIO says we have defensible advantages but churn is spiking anyway, the "O" (Organized to Capture) is the weak link. +- **Blind spot**: Neither framework captures relationship/trust dynamics well. The CSM analysis fills this gap. From bc3cb49093e9f5a62a575a11bb3dc04f7692b957 Mon Sep 17 00:00:00 2001 From: Anot Date: Fri, 20 Mar 2026 10:42:04 -0400 Subject: [PATCH 2/3] refactor: Relax two-framework rule and add skill boundary clarity strategic-analysis: No longer mandates "always apply at least two frameworks." For broad/high-stakes questions, two+ are still recommended. For specific, well-defined questions, one applied rigorously is preferred over two applied superficially. proposal-development: Add cross-reference to client-deliverables for engagement deliverables vs pre-engagement proposals. engagement-setup: Add cross-reference to workshop-facilitation for standalone facilitated sessions vs engagement launch. Co-Authored-By: Claude Opus 4.6 (1M context) --- management-consulting/skills/engagement-setup/SKILL.md | 2 +- management-consulting/skills/proposal-development/SKILL.md | 2 +- management-consulting/skills/strategic-analysis/SKILL.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/management-consulting/skills/engagement-setup/SKILL.md b/management-consulting/skills/engagement-setup/SKILL.md index a13a54d1..cd0ec2dc 100644 --- a/management-consulting/skills/engagement-setup/SKILL.md +++ b/management-consulting/skills/engagement-setup/SKILL.md @@ -5,7 +5,7 @@ description: Guide the first weeks of a consulting engagement from contract sign # Engagement Setup -Take a consulting engagement from "we just won this work" to "the engagement is running." This covers five things that happen roughly in sequence but overlap in practice: transitioning from sales to delivery, planning the kickoff, mapping stakeholders, designing discovery, and establishing the operating rhythm. +Take a consulting engagement from "we just won this work" to "the engagement is running." This covers the first weeks of a consulting engagement: transitioning from sales to delivery, planning the kickoff, mapping stakeholders, designing discovery, and establishing the operating rhythm. For designing standalone facilitated sessions later in the engagement (strategy offsites, innovation sprints), see workshop-facilitation. The goal is shared understanding and momentum, not a stack of templates. Every artifact here should earn its place by driving alignment or unblocking work. diff --git a/management-consulting/skills/proposal-development/SKILL.md b/management-consulting/skills/proposal-development/SKILL.md index 4fe8b2eb..427dd435 100644 --- a/management-consulting/skills/proposal-development/SKILL.md +++ b/management-consulting/skills/proposal-development/SKILL.md @@ -5,7 +5,7 @@ description: Develop consulting proposals and manage the business development li # Proposal Development -Manage the full business development lifecycle for consulting engagements: assess opportunities, develop proposals, draft SOWs, build pitch decks, prepare oral defenses, and articulate value propositions. +Manage the full business development lifecycle for consulting engagements: assess opportunities, develop proposals, draft SOWs, build pitch decks, prepare oral defenses, and articulate value propositions. This covers the business development lifecycle from opportunity assessment through proposal submission. For creating deliverables during an engagement (steering committee decks, final reports), see client-deliverables. ## Before You Begin diff --git a/management-consulting/skills/strategic-analysis/SKILL.md b/management-consulting/skills/strategic-analysis/SKILL.md index e04aa15e..3036552a 100644 --- a/management-consulting/skills/strategic-analysis/SKILL.md +++ b/management-consulting/skills/strategic-analysis/SKILL.md @@ -166,7 +166,7 @@ Once the problem is structured, select the right analytical frameworks and form #### Framework Selection -Match frameworks to the question being asked. Always apply at least 2 frameworks to any strategic question. +Match frameworks to the question being asked. For broad or high-stakes strategic questions, apply two or more frameworks and synthesize across them. For specific, well-defined questions, one framework applied rigorously is better than two applied superficially. | Question | Primary Framework | Complementary Pairing | Avoid | |---|---|---|---| @@ -329,7 +329,7 @@ Identify the "single point of failure": the one risk that could invalidate the e ## Behavioral Principles -1. **Always apply at least 2 frameworks** to any strategic question. Single-framework analysis is incomplete. +1. **For broad or high-stakes strategic questions, apply at least 2 frameworks** and synthesize across them. For specific, well-defined questions, one framework applied rigorously is better than two applied superficially. 2. **Provide substantive analysis, not empty templates.** For each cell, give 2-3 sentences of reasoning with evidence. 3. **Quantify wherever possible.** Use specific numbers, not vague ratings: - Market share: "Competitor A holds ~35% share, representing ~$X.XB revenue" From 46fdb3cb68d02ffa471afad5d487c1b3606cd233 Mon Sep 17 00:00:00 2001 From: Anot Date: Fri, 20 Mar 2026 14:16:08 -0400 Subject: [PATCH 3/3] fix: Align financial-modeling description with consulting context Replaced "company valuations" (investment banking framing) with "valuing a business unit for strategic decisions." Added full coverage list. Updated due-diligence and financial-modeling README entries to match. Co-Authored-By: Claude Opus 4.6 (1M context) --- management-consulting/README.md | 4 ++-- management-consulting/skills/financial-modeling/SKILL.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/management-consulting/README.md b/management-consulting/README.md index 82e8a8a9..61ada895 100644 --- a/management-consulting/README.md +++ b/management-consulting/README.md @@ -15,10 +15,10 @@ Domain knowledge Claude draws on automatically when your work touches consulting | Skill | Description | |---|---| | `strategic-analysis` | Hypothesis-driven decomposition, issue trees, MECE analysis, and named framework application (Five Forces, PESTLE, 7S, VRIO, etc.) | -| `financial-modeling` | Business case math, ROI/NPV/IRR, sensitivity analysis | +| `financial-modeling` | Business cases, cost-benefit analysis, ROI/NPV/IRR, sensitivity analysis, scenario modeling | | `client-deliverables` | Consulting reports, executive presentations, top-down structured communication, storylining, data visualization | | `change-management` | Transformation planning, resistance management, adoption tracking | -| `due-diligence` | Commercial, operational, and strategic assessment | +| `due-diligence` | Commercial, operational, financial, strategic, and technology assessment, integration planning | | `engagement-setup` | Kickoff planning, discovery phase, stakeholder mapping | | `implementation-planning` | Options evaluation, business cases, roadmaps, implementation plans | | `org-design` | Operating model and organizational structure design | diff --git a/management-consulting/skills/financial-modeling/SKILL.md b/management-consulting/skills/financial-modeling/SKILL.md index 2ab1bcac..0ac076a7 100644 --- a/management-consulting/skills/financial-modeling/SKILL.md +++ b/management-consulting/skills/financial-modeling/SKILL.md @@ -1,6 +1,6 @@ --- name: financial-modeling -description: Build financial models for business cases including ROI, NPV, IRR, DCF, scenario analysis, and total cost of ownership. Use for investment recommendations, comparing strategic options, quantifying initiatives, building business cases, or company valuations. +description: Build financial models for business cases including ROI, NPV, IRR, scenario analysis, and total cost of ownership. Use when developing investment recommendations, comparing strategic options, quantifying the value of initiatives, building business cases, performing cost-benefit analysis, or valuing a business unit for strategic decisions. Covers standard financial analysis workflows (ROI, business case, cash flow projections, break-even, DCF) and advanced techniques (EVA, MIRR, real options, Monte Carlo thinking, discount rate selection). --- # Financial Modeling