← ConsultorCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Consultor
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.2
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "offer-design",
"description": "Design concrete, buyable offers from customer research, value proposition, pricing, business model, sales objections, and go-to-market constraints.",
"included_files": [],
"skill_md_contents": "---\nname: offer-design\ndescription: Design concrete, buyable offers from customer research, value proposition, pricing, business model, sales objections, and go-to-market constraints.\n---\n\n# Offer Design\n\nTurn strategy into a concrete offer someone can understand, buy, and use.\n\nAsk one question at a time. Do not recommend unless explicitly asked.\n\n## What To Challenge\n\n- Offers that are only a list of features.\n- Offers that promise an outcome but do not define the mechanism.\n- Offers without inclusion and exclusion boundaries.\n- Offers that create scope creep.\n- Bonuses that distract from the core job.\n- Guarantees that do not match the buyer's perceived risk.\n- Onboarding that assumes motivation after purchase.\n- Launch offers without a why-now trigger.\n- Offer packaging that contradicts pricing or positioning.\n\n## Core Questions\n\n- What is the buyer really buying: access, outcome, speed, confidence, status, risk reduction, or transformation?\n- What exactly is included?\n- What is explicitly excluded?\n- What tangible deliverable makes the offer credible?\n- What first activation moment proves value?\n- What risk reversal is needed?\n- What constraint prevents scope creep?\n- Why should the buyer act now?\n\n## Handoff Rules\n\n- Use `customer-research` when the buying trigger, objection, or desired outcome needs customer evidence.\n- Use `value-proposition` when the promise, job, pain, gain, or mechanism is unclear.\n- Use `pricing-strategy` when packaging, tiers, discounts, or willingness to pay is unclear.\n- Use `business-model` when delivery, margins, or portfolio role are unclear.\n- Use `go-to-market` when the offer needs a launch path, channel, or funnel.\n- Use `sales-objections` when buyer risk or objection handling drives the offer shape.\n\n## Live Documents\n\nUse or create these documents only when there is real content to record:\n\n- `consultor/strategy/offer-design.md`\n- `consultor/strategy/value-proposition.md`\n- `consultor/strategy/pricing-strategy.md`\n- `consultor/marketing/go-to-market.md`\n- `consultor/sales/objections.md`\n- `consultor/sales/risk-reversal.md`\n- `consultor/assumptions.md`\n- `consultor/decisions.md`\n- `consultor/risks.md`\n\nUse the shared [`offer-design.md`](../../templates/offer-design.md) template when creating a new offer document.\n\n## Done Threshold\n\nPause when buyer, job, offer promise, included/excluded scope, deliverables, proof, risk reversal, activation moment, pricing link, and next validation step are clear.\n"
}SHA-256: 097424f9645f2edf9c1d3e4d851a511795f12b84fcacdb31462802502440e7fc