design-offers
Construct the purchasable offers - promised outcome, included scope and customer contribution, delivery status and path to first value, and any variant, entry offer, trial or guarantee with its purpose - and write the offer-catalogue candidate. Use when a revenue model exists or changed, when target opportunities or deliverable capabilities change, or when buyers do not understand or cannot adopt the current offer.
LeanOS-Technologies · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add LeanOS-Technologies/strategy --skill design-offers技能说明
name: design-offers description: Construct the purchasable offers - promised outcome, included scope and customer contribution, delivery status and path to first value, and any variant, entry offer, trial or guarantee with its purpose - and write the offer-catalogue candidate. Use when a revenue model exists or changed, when target opportunities or deliverable capabilities change, or when buyers do not understand or cannot adopt the current offer.
design-offers
Transformation: revenue-model × target opportunities × deliverable capabilities → offer-catalogue.
The document follows its contract and the group's document rules.
When to use it
- A revenue-model exchange exists and no offer implements it, or the exchange changed.
- A target opportunity or a delivery capability changed (a capability shipped, slipped or was withdrawn).
- Buyers stall between interest and purchase, or between purchase and first value.
Inputs and authority
| Input | Use | When missing |
|---|---|---|
revenue-model | The exchange each offer implements | Design the offer and mark the exchange it needs as an open dependency for design-revenue-model |
opportunities, target-segments | The outcome the buyer seeks and the buying situation | Reason from owner material; the outcome is a hypothesis |
documentation, roadmap, owner material | What can be delivered now and what later | Only what owner material or documentation shows as working counts as available |
differentiation | Why this offer beats the buyer's alternative | State the comparison as a hypothesis |
| Owner material naming commercial levels or units | Which levels the catalogue must cover | Cover the targets' needs; name the level question for the owner |
You propose offers, names, bundles and terms. They stay proposals until accepted. Governance approves legal wording; Product owns capability evidence.
Method
Record sources, exact owner quotes and calculation premises in the relevant table’s basis or source cells. Carry decision status in its status column and the document’s role; prose states choices and ambition directly.
1. Define the outcome and the scope to first value
For each target opportunity write: the outcome the buyer wants, the smallest scope that reaches first value, what the customer must supply, and what lies outside the purchase. Scope by meaningful need and delivery boundary (entitlement, delivery and economics §1): every included element is an obligation with a cost driver.
What to notice:
- The buyer's switching cost (their existing template, data, habits). Removing it can matter more than any feature.
- Setup effort before first value. A long setup needs a service, a guided start or a smaller first scope.
- Whether a capability the offer needs is available, committed or only possible.
2. Construct offers from real capability
Build offers from what the venture can deliver and what the target needs. Develop names and bundles with their rationale in the row’s basis cell and their proposed status in Status. Cover the commercial levels the venture source names, distinguishing available, proposed and future in the Status column. A complete future range is not a prerequisite for releasing the first useful offer.
Decision rules:
- Each promised element is deliverable now, or sold on a stated future condition (§2). A roadmap capability never enters the entitlement silently.
- Introduce variants or tiers only when needs, entitlements, purchasing conditions or delivery costs differ (price, packaging, response and friction §3). Otherwise one offer.
- A simple direct purchase is often right; never add subscriptions, tiers or guarantees by default.
3. Reduce purchase and adoption friction
Use the friction analysis in price, packaging, response and friction §4:
- A free standalone product delivers its stated outcome within its own boundaries. A demonstration, trial or entry component supports a stated evaluation or commercial purpose. Choose the form from the owner's policy and customer need; free pricing alone does not imply an upgrade path. State delivery costs and support boundaries for either form.
- Trial or pilot: when the decision-maker needs proof in use and setup cost is bearable for both sides.
- Guarantee: when fit is uncertain at purchase and the venture can bear refunds; not for delivered services. Each goes in Variants and conditions with its purpose and delivery condition.
4. Establish delivery readiness and terms
Fill Delivery and first value for every offer: delivery status, prerequisites, path to first value, customer contribution, support boundary and exclusions. Quantitative delivery claims ("converted in two days") need a basis; otherwise state the scope without the number. Proposed commercial conditions are written as proposals with Approval naming who approves them.
5. Compare with the buyer's alternative
For each offer, say why buying beats the buyer's actual alternative (from differentiation). If the offer does not beat it, change scope or path to value before pricing.
6. Connect
set-prices prices each offer's exact entitlement; Product and Customers fulfil it; Engagement sells within its scope. Name the capability dependencies that prioritize-bets must sequence.
Defects to detect and correct
| Defect | Correction |
|---|---|
| An offer includes a planned capability as available | Move it to a stated future condition, or set Status future |
| A tier or variant with no decision-relevant purpose | Remove it, or state the need it separates |
| An offer's scope or condit |