customer-commitment-validation
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.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- customer-commitment-validation
- license
- MIT
- metadata
- { "tags": "customer-discovery,sales,validation,startups,commitment", "version": "0.1.3", "category": "Marketing", "displayName": "Customer Commitment Validation" }
- description
- 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.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 2
- 参考文档agents/openai.yaml238 B
- 参考文档workflows/classify-meeting-outcome.md1.4 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.