agentleFS
anotbanotb/forward-deployed/skills/value-case/SKILL.md

value-case

Skill1 starsChanged 33 days agoMITView on GitHub

Build and test the business case, ROI and economics of an enterprise AI investment or service. Use for revenue, decision quality, expert capacity, delivery economics, and expansion choices where the architecture and changed work determine the return.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the capability to an operating or customer result.

    line 12
  2. Distinctive:

    Keep a useful operating measure when monetary conversion is weak.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Value case

Build the economic argument for the decision at hand: investigate, deploy, redesign, price, or expand. Compare the proposed capability with what the organization would otherwise do over the relevant horizon. Make a recommendation and calculate the assumptions that could reverse it.

Establish how value is created

Follow the capability to an operating or customer result. Use the mechanisms that fit:

  • Revenue and new services: who buys what, adoption or conversion, price, retention, time to revenue, and incremental contribution after fulfillment costs. Include cannibalization where the service replaces existing revenue.
  • Decision quality: which decision changes and how that affects an outcome. Evaluate better choices, useful discoveries, or avoided losses against comparable work.
  • Capacity and coverage: which scarce expertise is released, what work it will take on, and whether the receiving operation can use it.
  • Service performance: what earlier, broader, or more reliable work makes possible, such as reaching customers previously uneconomic to serve.
  • Cash savings: which purchased service, overtime, hiring, or other expenditure changes and when.

Keep a useful operating measure when monetary conversion is weak. For a new service, test demand through use, a commercial offer, or paid delivery. Build the case around the population the funded scope can reach.

Cost the delivered outcome

Choose a unit that carries value through the workflow: a completed implementation, resolved investigation, accepted customer deliverable, or retained subscriber. Keep acceptance and timing consistent across alternatives. Include abandoned and unresolved work in the entered population.

Model the materially different paths, including retries, review, correction, fallback, and subsequent completion. For mutually exclusive paths:

expected cost per entered case = Σ path share × full path cost
delivery cost per accepted outcome = total delivery cost / accepted outcomes
human demand = entered volume × Σ path share × human time

Charge both attempts when assistance fails and a person completes the work. Connect machine consumption to the workflow: investigation depth, tool use, refresh frequency, and reused work. A cheaper model can cost more overall if it creates expensive recovery.

Separate build cost, fixed operation, usage costs, and human delivery effort. Include integration, evaluation, support, transition, and maintenance where they affect the choice. Use current prices and measured consumption when available.

Make volume and capacity agree

Compare human demand with productive time available after existing obligations. Include ongoing customer support and supervision, as well as individual case handling. Averages establish capacity arithmetic; delivery deadlines may require arrival and handling distributions or a queue simulation.

Model the effects of expansion. More complex cases can increase price, investigation effort, and review together. Wider coverage can lower conversion and create downstream work. A second deployment may reuse context and tools while adding local policies, integration, and support costs.

Released salary time is capacity until the operating plan converts it into avoided expenditure or additional output. Do not add a labor-equivalent benefit to revenue earned with the same hours, count avoided hiring and staffing reductions twice, or repeat shared benefits across several workflows.

Price the commitment and test the return

Use period cash flows when build cost, adoption ramp, benefit lag, or useful life matters. For a paid service, show contribution per customer, service margin, onboarding effort, and the continuing obligation at the proposed price. For investment appraisal, state the horizon and any discount rate; positive unit margin alone does not recover a build.

Find the thresholds that matter: paid demand needed to cover fixed cost, accepted volume needed for payback, human effort compatible with capacity, or price needed to sustain the service. Read the new-service economics example for a worked model linking all four.

Recommend the commitment that the evidence supports. Where uncertainty dominates, price the next test and specify which investment decision its result will resolve. Reconcile realized value against comparable case mix, participation, accepted outcomes, total cost, and the use of released capacity. Deliver an editable model and a short explanation of the recommendation, including the assumption that most threatens it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.