CtrlK
BlogDocsLog inGet started
Tessl Logo

executive-pitch

Crafts technical business cases with ROI justification, value pillars, and executive-ready framing. Trigger: "executive summary", "business case", "pitch the solution", "ROI".

SKILL.md
Quality
Evals
Security

Executive Pitch

Transforms technical analysis into executive-ready business cases that connect engineering decisions to business outcomes through structured value pillars and ROI frameworks.

Guiding Principle

"Executives do not buy technology. They buy outcomes. Frame every recommendation as a business result."

Procedure

Step 1 — Audience and Stakes Analysis

  1. Identify the decision-makers, their priorities, and their risk tolerance.
  2. Map the organizational pain points the recommendation addresses.
  3. Determine the decision timeline and competing initiatives.
  4. Establish the language and metrics that resonate with this audience.

Step 2 — Value Pillar Construction

  1. Define 3-5 value pillars that connect the technical solution to business outcomes.
  2. For each pillar, articulate the before/after state with measurable impact.
  3. Support each pillar with evidence: benchmarks, case studies, or proof-of-concept results.
  4. Prioritize pillars by audience relevance and defensibility.

Step 3 — ROI and Investment Framework

  1. Quantify the investment required (FTE-months, infrastructure, licensing).
  2. Project returns across multiple dimensions: revenue, cost savings, risk reduction.
  3. Calculate payback period and 3-year net value.
  4. Include a confidence assessment for each projection.

Step 4 — Narrative Assembly

  1. Open with a one-paragraph executive summary (problem, solution, impact).
  2. Present value pillars with supporting evidence.
  3. Include a visual investment/return timeline.
  4. Close with a clear ask and decision framework.

Quality Criteria

  • Executive summary is self-contained and under 200 words.
  • Every value claim has quantified impact and an evidence tag.
  • ROI projections include confidence levels and assumption disclosure.
  • The pitch answers "why now" and "why this approach" explicitly.

Anti-Patterns

  • Leading with technology features instead of business outcomes.
  • Presenting ROI without disclosing assumptions or confidence levels.
  • Using technical jargon that alienates the target audience.
  • Omitting the cost of inaction as a comparison baseline.
Repository
JaviMontano/mao-sovereign-architect
Last updated
First committed

Also appears in

JaviMontano/jm-adk
In sync

since Aug 28, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.