mengke-wang 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
- Choose the smallest sellable problem from the user's positioning, proof, and content.
- Name the offer plainly.
- Write fit and non-fit criteria.
- Define deliverables as objects the buyer receives, not abstract benefits.
- Write process, timeline, boundary, and revision policy.
- Explain the price through the outcome, proof, and avoided cost.
- Add relevant proof and a direct next step.
- 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 draftPrice explanationScope and boundariesProof to addBuying test messageRevision priorities after feedback