Menu

Individual skill

roi-proof-generator

0upvotes

Use this skill when a renewal, QBR, or expansion conversation is coming and the user needs to prove what their AI agent actually delivered — "build the renewal deck," "show ROI for this account," "the buyer is asking what they got for the money." Turns raw agent activity into a renewal-ready value receipt: tasks completed, hours returned, cost avoided, and the ROI multiple, in the customer's own numbers. Built on Manny Medina's billing-first ROI approach: agents are cognitively invisible to the people paying for them, so their value has to be made explicit — continuously, not just at renewal.

skills/manny-medina/roi-proof-generator/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use when agent value must be proven to the people paying for it — before a renewal, at a QBR, or monthly as a standing receipt. Produces a value receipt: tasks completed, hours returned, cost avoided, ROI multiple.

## Get the right kind of metrics

Three reporting categories exist; only one closes renewals:

- **usage reporting** — tasks run, tokens consumed. Engineering metrics.
- **performance analytics** — uptime, error rate, latency. Reliability metrics.
- **ROI reporting** — time saved, cost avoided, revenue generated. Commercial metrics.

Enterprise renewals depend on the third category alone. If the input data is usage-shaped, convert it before writing anything.

## Establish the benchmark
Back to top