bpo-roi-brief
Skill1 starsChanged 7 months agoNo licenceView on GitHub
Generate a high-fidelity 3-page Anyreach-style ROI brief PDF for any BPO pitching their end-client on outcomes-based AI + human pricing. The PDF matches the exact format proven on the Fabletics × Startek deal — page 1 (current state vs. outcomes-based future state), page 2 (outcome definitions + client-specific priorities), page 3 (lighthouse pilot proposal). Trigger whenever the user asks to build, generate, draft, or produce a 'BPO ROI brief', 'outcomes-based pricing brief', 'AI replacement ROI', 'partner pitch brief', or any 3-page ROI deliverable for a BPO partner pitching an enterprise/end-client. Also trigger when the user provides BPO brand guide + client current-state metrics and asks for a 'pitch deck', 'ROI doc', 'partner brief', or 'savings analysis brief'. Always use this skill instead of writing a brief from scratch — it contains the full template, brand-adaptive design system, ROI math model (containment, blended cost, phased pricing cascade, lighthouse pilot value), and PDF rendering pipeline.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- account-brief-generatorSkill
- ai-fluency-assessmentSkill
- anyreach-deck-pptxSkill
- anyreach-financial-reportSkill
- anyreach-funnel-analysisSkill
- anyreach-web-designSkill
- bpo-partner-pitch-deckSkill
- bpo-roi-internal-briefingSkill
- bpo-roi-modelSkill
- brand-style-extractorSkill
- callsSkill
- company-deep-researchSkill
- competitor-deep-diveSkill
- consumer-intelligence-xlsxSkill
- consumer-intel-reportSkill
- cx-intel-report-pdfSkill
- cx-intel-report-xlsxSkill
- demo-bot-usage-reportSkill
- deploy-intelSkill
- discovery-dashboardSkill
- discovery-to-proposalSkill
- gtm-audit-appSkill
- gtm-audit-pdfSkill
- gtm-stack-auditSkill
- legal-reviewSkill
- leverage-analysisSkill
- maturity-assessmentSkill
- meeting-recap-emailSkill
- narrative-deckSkill
- portfolio-cx-briefSkill
- product-site-frameworkSkill
- proposal-sow-generatorSkill
- remotion-best-practicesSkill
- reviews-vs-live-callsSkill
- richard-thought-leadershipSkill
- shadcn-deckSkill
- stakeholder-intelSkill
- status-deckSkill
- visual-briefSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

