system-pitch

System pitch

A skill for writing a design system investment pitch that leads with a business problem, builds an honest ROI case, and addresses likely objections. Output is a pitch document that works for an audience who has never heard of a design system and does not need to.

Context

Design system pitches usually fail for one of two reasons. They lead with the design system — its components, its tokens, its Storybook — rather than with the business problem it solves. Or they oversell: promising a design system will solve problems it cannot solve, which creates scepticism or, worse, expectation debt that damages credibility when the system ships and the promised outcomes do not materialise.

The pitch that works leads with the cost of the current state. It makes the reader feel the friction of inconsistency, the waste of duplicated effort, the risk of inaccessible interfaces — before it introduces the design system as the solution. Then it is specific about what the investment costs, honest about the timeline, and precise about what success looks like.

Workflow overview

The system pitch workflow follows seven distinct steps:

1. Understand the context — Assess the situation and likely objections
2. Estimate the cost of the current state — Quantify the problem
3. Structure and write the pitch — Build the five-part template with business framing
4. Calculate and present ROI — Show the financial return
5. Address likely objections — Preempt the 5–7 most common objections
6. Frame by audience — Calibrate the pitch for different stakeholders
7. Review for clarity and quality — Ensure the pitch leads with problem, not solution

---

Step 1: Understand the context

Ask for or confirm:

• Is this a pitch for a new design system, or a pitch to continue investing in an existing one?
• What is the current state? (Multiple teams building the same things independently / an existing system with low adoption / no system at all)
• What is the organisation? (Size, product count, team structure)
• Who is the audience for this pitch? (Executive, product leadership, engineering leadership, combined)
• What is the likely objection? (Cost, timeline, team capacity, "we tried this before")
• Is there any existing data available? (Time spent on inconsistent work, accessibility incident history, customer complaints about inconsistency)