Customer Commitment Validation
Use this skill after a product, sales, partnership, investor, or customer
conversation where the team needs to decide whether the meeting created real
progress. The core test is what the other person gave up: time, reputation, or
money.
Source Traceability
Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 5 and 8.
Guidance is paraphrased for this MIT repo; authoring notes used converted EPUB
lines 2365-2790 and 3613-4108.
Commitment Currencies
| Currency |
Examples |
Signal Strength |
| Time |
Scheduled next meeting with goals, trial setup work, real feedback session |
Medium |
| Reputation |
Intro to a decision maker, internal championing, public case study |
Medium to high |
| Money |
Deposit, preorder, paid pilot, purchase order, signed letter of intent |
High |
Compliments, vague "keep me posted" replies, and future-tense buying promises
are not commitments.
An advancement must move the real-world funnel to a specific next decision or
action. A next step without an owner, date, or customer-side effort is usually
weak interest.
Review Workflow
- Restate the meeting context and what the team hoped would happen next.
- Classify the outcome as commitment, advancement, rejection, weak interest, or
bad data.
- Identify what the other person gave up, if anything.
- If the outcome is fuzzy, propose a concrete next ask that creates a decision.
- If there was rejection, preserve the learning and decide whether it changes
the product, segment, positioning, or sales path.
- If there was commitment, define the owner, date, success criteria, and follow
up.
Outcome Classification
| Outcome |
Meaning |
Action |
| Commitment |
They gave up time, reputation, or money |
Track and follow through |
| Advancement |
They moved the real-world funnel forward |
Confirm next step details |
| Rejection |
They declined a concrete ask |
Learn and update assumptions |
| Weak interest |
They were friendly but gave up nothing |
Ask for a concrete next step or stop counting it |
| Bad data |
Outcome is only compliments or future hypotheticals |
Return to evidence or commitment |
Output Format
# Commitment Review
## Meeting
- Person/company:
- Context:
- Stage:
## Outcome
- Classification, evidence, currency given up:
## Interpretation
- What this proves / does not prove:
- Risks, missing decision makers, approval path:
## Next Ask
[A concrete ask that creates advancement or rejection.]
## Follow-Up
- Owner, deadline, success criteria:
Workflow
Use workflows/classify-meeting-outcome.md when the user provides notes,
transcripts, CRM entries, or a narrative of how a meeting ended.
Quality Bar
- Do not call a meeting successful because it felt positive.
- Do not count a lead as real until they had a chance to reject a concrete ask.
- Do not overvalue free trials that cost the customer nothing.
- Do not ignore missing decision makers or approval paths.
- Treat rejection as useful evidence, not as failure.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/customer-commitment-validation/SKILL.md
1---2name: customer-commitment-validation3description: Evaluate whether customer, sales, investor, partner, or product meetings produced real commitment and advancement instead of polite interest. Use when interpreting meeting outcomes, stalled leads, trial requests, letters of intent, preorders, warm intros, case-study offers, unclear next steps, or compliments after a pitch.4---5
6
7# Customer Commitment Validation
8
9Use this skill after a product, sales, partnership, investor, or customer
10conversation where the team needs to decide whether the meeting created real
11progress. The core test is what the other person gave up: time, reputation, or
12money.
13
14## Source Traceability
15
16Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 5 and 8.
17Guidance is paraphrased for this MIT repo; authoring notes used converted EPUB
18lines 2365-2790 and 3613-4108.
19
20## Commitment Currencies
21
22| Currency | Examples | Signal Strength |
23|----------|----------|-----------------|
24| Time | Scheduled next meeting with goals, trial setup work, real feedback session | Medium |
25| Reputation | Intro to a decision maker, internal championing, public case study | Medium to high |
26| Money | Deposit, preorder, paid pilot, purchase order, signed letter of intent | High |
27
28Compliments, vague "keep me posted" replies, and future-tense buying promises
29are not commitments.
30
31An advancement must move the real-world funnel to a specific next decision or
32action. A next step without an owner, date, or customer-side effort is usually
33weak interest.
34
35## Review Workflow
36
371. Restate the meeting context and what the team hoped would happen next.
382. Classify the outcome as commitment, advancement, rejection, weak interest, or
39 bad data.
403. Identify what the other person gave up, if anything.
414. If the outcome is fuzzy, propose a concrete next ask that creates a decision.
425. If there was rejection, preserve the learning and decide whether it changes
43 the product, segment, positioning, or sales path.
446. If there was commitment, define the owner, date, success criteria, and follow
45 up.
46
47## Outcome Classification
48
49| Outcome | Meaning | Action |
50|---------|---------|--------|
51| Commitment | They gave up time, reputation, or money | Track and follow through |
52| Advancement | They moved the real-world funnel forward | Confirm next step details |
53| Rejection | They declined a concrete ask | Learn and update assumptions |
54| Weak interest | They were friendly but gave up nothing | Ask for a concrete next step or stop counting it |
55| Bad data | Outcome is only compliments or future hypotheticals | Return to evidence or commitment |
56
57## Output Format
58
59```markdown
60# Commitment Review
61
62## Meeting
63- Person/company:
64- Context:
65- Stage:
66
67## Outcome
68- Classification, evidence, currency given up:
69
70## Interpretation
71- What this proves / does not prove:
72- Risks, missing decision makers, approval path:
73
74## Next Ask
75[A concrete ask that creates advancement or rejection.]
76
77## Follow-Up
78- Owner, deadline, success criteria:
79```
80
81## Workflow
82
83Use `workflows/classify-meeting-outcome.md` when the user provides notes,
84transcripts, CRM entries, or a narrative of how a meeting ended.
85
86## Quality Bar
87
88- Do not call a meeting successful because it felt positive.
89- Do not count a lead as real until they had a chance to reject a concrete ask.
90- Do not overvalue free trials that cost the customer nothing.
91- Do not ignore missing decision makers or approval paths.
92- Treat rejection as useful evidence, not as failure.
93
94---
95
96**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/customer-commitment-validation/SKILL.md`
hashgraph-online