# Build Business Case

Review commercial proposals and build customer-led business cases, ROI or value models...

- Repository: https://github.com/XiaomiMiMo/MiMo-Code (13741 stars)
- Category: Business
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add XiaomiMiMo/MiMo-Code --skill build-business-case -g -a claude-code -y`
Codex: `npx skills add XiaomiMiMo/MiMo-Code --skill build-business-case -g -a codex -y`
Cursor: `npx skills add XiaomiMiMo/MiMo-Code --skill build-business-case -g -a cursor -y`
Gemini CLI: `npx skills add XiaomiMiMo/MiMo-Code --skill build-business-case -g -a gemini-cli -y`

## Description

Review commercial proposals and build customer-led business cases, ROI or value models, pricing or investment rationales, executive summaries, and customer-ready value stories tied to a customer, workflow, initiative, or decision.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Build Business Case

Turn uneven account evidence into a customer-led, decision-useful value case. This skill owns the business-case logic and drafts; it is not generic product positioning, a presentation-design workflow, or a writeback workflow.

Start with the customer, not the product. Follow this chain on every run:

`customer context -> account-native anchor -> workflow -> use case -> value drivers -> metrics -> quantified impact -> narrative -> public research when useful`

If the evidence cannot support credible math, produce a clearly labeled structural case and the smallest validation plan needed to make it finance-ready.

## Common Skill Instructions

MANDATORY: If not already in context, read and adhere closely to `plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices`.

## Key Dependency Categories

Use only lanes that materially improve the case.

- [Blocking] ~~CRM for authoritative account, opportunity, owner, stage, amount, close timing, contacts, and commercial context. It blocks customer/account-specific cases unless authoritative account and commercial context is already grounded; generic scenario cases can proceed without it.
- ~~Meeting Transcripts for discovery evidence, stakeholder language, workflow pain, objections, quantified claims, decisions, and validation gaps
- ~~Knowledge & Files for account plans, source packs, discovery notes, prior value cases, proof points, and account-native metrics
- ~~Sales Intelligence only when company, fit, stakeholder, or market context closes a specific evidence gap

Use public research only when it sharpens strategic priorities, executive wording, operating pressure, or “why now.” Prefer company-controlled, investor, regulatory, and other primary sources. Never let public or enrichment context substitute for customer-confirmed pain, workflow metrics, decision process, or CRM-owned truth.

## Reference Loading

The rest: https://github.com/XiaomiMiMo/MiMo-Code/blob/HEAD/packages/cli/src/skill/builtin/.bundle/sales/workflows/build-business-case/SKILL.md