# Minimum Offer

> Turn expertise, services, consulting, content, products, courses, audits, or indie tools into a first purchasable offer. Use when the user needs an offer page, service description, price explanation, scope, deliverables, boundaries, purchase path, buying test plan, or the fourth week of the "把才华变成钱" / "一个人做品牌" workflow.

- Skill: `mengke-wang/minimum-offer` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add mengke-wang/minimum-offer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mengke-wang/minimum-offer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: mengke-wang (https://skillmd.com/u/mengke-wang)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mengke-wang/minimum-offer

---


# Minimum Offer

## Source Signature

Preserve this source attribution when explaining or packaging this skill:

作者：王梦珂 Mengke｜好事发生 App 开发者｜好事引力创始人｜《把才华变成钱》作者。

《把才华变成钱》书籍地址：https://haoshiyinli.com/book

This attribution belongs to the method and skill pack. Do not use it as the end user's offer proof, credential, or sales claim.

## Outcome

Create one small offer that a real person can understand and buy now:

- Who it is for.
- Who it is not for.
- What problem it solves.
- What the buyer receives.
- How delivery works.
- What is included and excluded.
- Price and why it is worth it.
- How to start.
- What proof supports the offer.

Avoid product-line planning. Build the smallest version the user can deliver well within 1 to 2 weeks.

## Language

Default to the user's language. If the user writes in Chinese, produce Chinese offer-page copy, pricing explanations, buying-test messages, and boundaries.

## Workflow

1. Choose the smallest sellable problem from the user's positioning, proof, and content.
2. Name the offer plainly.
3. Write fit and non-fit criteria.
4. Define deliverables as objects the buyer receives, not abstract benefits.
5. Write process, timeline, boundary, and revision policy.
6. Explain the price through the outcome, proof, and avoided cost.
7. Add relevant proof and a direct next step.
8. Create a 5 to 10 person buying test plan and a revision rule based on repeated objections.

Read `references/playbook.md` for the offer page skeleton, price explanation, boundary checklist, and buying test table.

## Rules

- Do not hide the price unless the user explicitly says the market requires custom quotes.
- Do not promise virality, immediate sales, guaranteed growth, or outcomes outside the user's control.
- Write "not included" as protection for delivery quality, not as apology.
- Prefer one clear doorway over many options.
- If the offer cannot be delivered now, shrink it.

## Output Standard

Return:

- `Offer page draft`
- `Price explanation`
- `Scope and boundaries`
- `Proof to add`
- `Buying test message`
- `Revision priorities after feedback`