agentleFS
jacobtop-tcgjacobtop-tcg/sales-engineering-skills/skills/proof-of-value-plan/SKILL.md

proof-of-value-plan

Skill0 starsChanged 13 days agoMITView on GitHub

Plans a Proof of Value for a B2B software deal, from agreed business outcomes through success criteria, the go or no-go before technical validation, the pilot agreement check and the readout. Use when a sales engineer is about to scope a proof of concept, pilot, trial or evaluation, or needs to check whether a planned proof will answer the customer's business question.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Do the terms limit disclosing results or comparisons?

    line 28
  2. Distinctive:

    Keep the buyer's decision date separate from the pilot's end date.

    line 31
  3. Distinctive:

    Put the customer's steps toward the decision, each with an owner and a date, into the mutual action plan.

    line 32
  4. Distinctive:

    After the customer decides, the value presentation and the success criteria become part of the customer's success plan.

    line 34
  5. Distinctive:

    If the pilot end date is the only date in the plan, the decision date is missing.

    line 54
  6. Distinctive:

    If the team reports on its proofs, keep technical wins apart from deals won.

    line 55

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

Proof of Value plan

A Proof of Concept tests whether the product works in the customer's environment. A Proof of Value tests whether the product delivers the business outcomes the economic buyer has agreed to, and that agreement comes before the proof starts.

Ask for these inputs

  1. The deal, the product being evaluated and the economic buyer.
  2. The business outcomes the customer has stated, in their words, and who said each.
  3. The capabilities and use cases the team plans to test, and who at the customer will judge the result.
  4. The pilot, trial or evaluation agreement, plus any completed order form, schedule or project plan.
  5. The customer's decision date and the pilot's planned end date.

Steps

  1. Agree the outcomes first. Record two to four business outcomes in the customer's own words, agreed by the economic buyer. If the team started from product capabilities, flag it: that route can produce an impressive evaluation that never answers the customer's business question.
  2. Work back to the test. With the customer, list the minimum capabilities needed to reach each outcome, the use cases that demonstrate them, and the criteria for judging the result. Ask about the work itself: for faster invoice approval, where invoices wait today, which exceptions cause delays and who must act on them. Those findings decide which parts of the customer's work belong in the proof.
  3. Write the success criteria with the people who will judge the result. For each, state what the result is compared with and what evidence the proof can reasonably produce. Mark any effect that depends on wider implementation or on changes to the customer's process before anyone promises to demonstrate it.
  4. Hold the go or no-go. Before technical validation, the account executive and the sales engineer confirm the outcomes, the timeline and the next step with the economic buyer. If nobody can agree what the proof is meant to establish, go back to discovery. A Business Value Assessment can help when the answer needs conversations with several of the customer's people. More time in a test environment will not settle a business decision nobody has made.
  5. Make the step after a successful proof explicit. The customer may still need to compare commercial terms, get another approval or plan the implementation.
  6. Check the agreement:
    • Does access end at the close of the period, or does a subscription start automatically? For an automatic transition, is there a right to stop it and a notice deadline?
    • What happens to the customer's data at the end?
    • Do the terms limit disclosing results or comparisons? Check before results go into a report that leaves the company.
    • On the buyer's own proof of concept paper, which ticked policies bind the proof itself?
    • Where are the success result, the decision-maker and the decision date written? Common Paper's published pilot terms, for example, do not say. Check the completed order form, schedule or project plan before treating them as missing.
  7. Keep the buyer's decision date separate from the pilot's end date. If continued access is needed, letting the pilot end before the decision may leave a gap.
  8. Put the customer's steps toward the decision, each with an owner and a date, into the mutual action plan.
  9. Plan one readout for three readers. The economic buyer needs the business case for the agreed outcomes and the investment. The deal champion needs to judge whether the right tool is being put in place and to carry the decision internally. The technical champion needs to understand how the product works, including limitations that matter in their environment. Keep gaps visible: a failed capability or a result that depends on a change still to be made belongs in the decision whether to proceed.
  10. After the customer decides, the value presentation and the success criteria become part of the customer's success plan. Customer Success and the sales engineer prepare that handover together.

Output

SectionContent
Business outcomes (2 to 4)Customer's words, who said it, economic buyer agreement and date
Capabilities and use casesEach linked to an outcome and to the part of the customer's work it covers
Success criteriaCriterion, compared with what, evidence the proof can produce, who judges it
DependenciesEffects that need wider implementation or process change
Go or no-goDate; outcomes, timeline and step after a successful proof confirmed with the economic buyer
Agreement checkEnd mechanism, notice deadline, data at end, limits on results, buyer policies
DatesPilot end and buyer's decision date, separately
Readout and handoverNeeds of each of the three readers; Customer Success owner

Checks

  • An outcome phrased as a product feature, or in the vendor's words, is weak. Send it back.
  • An outcome the economic buyer has not agreed is a hypothesis. Do not start technical validation on it.
  • Criteria count when the people who will judge the result have agreed them.
  • If the pilot end date is the only date in the plan, the decision date is missing.
  • If the team reports on its proofs, keep technical wins apart from deals won.

A browser version of the same check, for people without an agent: Proof of Value plan checker.

Based on: What is a Proof of Value, and what does it need to prove? and Proof of concept vs pilot: what the agreement leaves out

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.