Offer Builder
Build something a specific buyer can understand, value, and decide on.
Job contract
- Owns: what is sold, to whom, for what outcome, under what terms.
- Does not own: choosing between unrelated strategies (
llm-council), improving an existing page (landing-page-cro), or running a launch (digital-product-launch-builder).
- Finished deliverable: offer card, full package, objections, and a low-risk validation test.
Workflow
- Establish the buyer, urgent situation, desired outcome, current alternative, and evidence available.
- Choose one primary outcome. Remove promises the delivery cannot support.
- Define the mechanism, included work, exclusions, time to value, and buyer effort.
- Build the package and price logic. Label assumptions when there is no sales evidence.
- Add proof only when supplied. Convert missing proof into a collection plan.
- Name the three strongest objections and answer them without fake guarantees.
- Create the smallest test that can produce a real buying or commitment signal.
Output
# Offer
## Offer Card
- For: [specific buyer and situation]
- Outcome: [credible transformation]
- Mechanism: [how it works]
- Includes: [scope]
- Does not include: [boundaries]
- Time to value: [credible timing]
- Price and terms: [with reasoning]
- Proof: [real evidence or gap]
## Positioning
[One-sentence version and short pitch]
## Objections
[Objection, answer, proof needed]
## Delivery Check
[What must be true to fulfil the promise]
## Validation Test
[Audience, message, ask, success threshold, learning window]
Guardrails
- Never invent demand, testimonials, scarcity, savings, or results.
- Do not turn an unclear offer into a larger bundle by default.
- When price evidence is weak, present a testable starting hypothesis.
1---2name: offer-builder3description: Create, clarify, package, price, or improve an offer with a defined buyer, credible promise, scope, proof, price logic, boundaries, and validation test.4---56# Offer Builder78Build something a specific buyer can understand, value, and decide on.910## Job contract1112- Owns: what is sold, to whom, for what outcome, under what terms.13- Does not own: choosing between unrelated strategies (`llm-council`), improving an existing page (`landing-page-cro`), or running a launch (`digital-product-launch-builder`).14- Finished deliverable: offer card, full package, objections, and a low-risk validation test.1516## Workflow17181. Establish the buyer, urgent situation, desired outcome, current alternative, and evidence available.192. Choose one primary outcome. Remove promises the delivery cannot support.203. Define the mechanism, included work, exclusions, time to value, and buyer effort.214. Build the package and price logic. Label assumptions when there is no sales evidence.225. Add proof only when supplied. Convert missing proof into a collection plan.236. Name the three strongest objections and answer them without fake guarantees.247. Create the smallest test that can produce a real buying or commitment signal.2526## Output2728```markdown29# Offer3031## Offer Card32- For: [specific buyer and situation]33- Outcome: [credible transformation]34- Mechanism: [how it works]35- Includes: [scope]36- Does not include: [boundaries]37- Time to value: [credible timing]38- Price and terms: [with reasoning]39- Proof: [real evidence or gap]4041## Positioning42[One-sentence version and short pitch]4344## Objections45[Objection, answer, proof needed]4647## Delivery Check48[What must be true to fulfil the promise]4950## Validation Test51[Audience, message, ask, success threshold, learning window]52```5354## Guardrails5556- Never invent demand, testimonials, scarcity, savings, or results.57- Do not turn an unclear offer into a larger bundle by default.58- When price evidence is weak, present a testable starting hypothesis.
nahiddotai