proposal-roi
Skill39 starsChanged 6 months agoMITView on GitHub
Builds the ROI projection and cost-of-inaction case. Invoked by /proposal roi <client>. Output: PROPOSAL-ROI-[Client].md.
In this repository14 other files it gives its agents.
- proposalSkill
- proposal-buildSkill
- proposal-casestudySkill
- proposal-compareSkill
- proposal-coverSkill
- proposal-followupSkill
- proposal-objectionsSkill
- proposal-pricingSkill
- proposal-quickSkill
- proposal-report-pdfSkill
- proposal-scopeSkill
- proposal-sowSkill
- proposal-summarySkill
- proposal-upsellSkill
The file
Files
Proposal ROI — Business Case & ROI Projection
Builds the ROI projection and cost-of-inaction case. Invoked by /proposal roi <client>. Output: PROPOSAL-ROI-[Client].md.
Steps
- Identify the value lever: service → metric → revenue (GEO/SEO → traffic → leads → revenue; reputation → rating → conversion → revenue; etc.). Use the client's business model.
- Quantify the cost of inaction: ongoing monthly/annual loss from the status quo, tied to audit weaknesses.
- Build a current-vs-projected table across conservative / moderate / aggressive, with annual value, investment, net ROI, ROI %.
- State every assumption with its basis.
Rules
Conservative case must still be positive ROI — if not, flag the scope/price. Transparent assumptions only. Use the client's own metrics where possible.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.