Use this offer design worksheet to turn expertise, a product, or a service idea into something a specific customer can evaluate and buy.
The worksheet separates the customer outcome from the delivery mechanism. It also makes exclusions, dependencies, and customer responsibilities visible before they create scope disputes. Use the complete offer creation guide when the underlying strategy needs more work.
The Components of a Complete Offer
A complete offer identifies who it is for, the situation that creates demand, the useful result, the included deliverables, the customer’s role, exclusions, timing, evidence, price, terms, risk allocation, and a clear next action.
The offer should promise what the business can influence. Results that depend on customer implementation, market response, regulation, third parties, or future behavior need explicit assumptions and boundaries.
When to Use This Worksheet
- Before launching a new service, product, package, or subscription.
- When every proposal is custom and difficult to price.
- When prospects repeatedly misunderstand what is included.
- When delivery produces change requests, delays, or unplanned support.
- When an existing offer receives attention but few purchase decisions.
Evidence to Gather First
Bring customer language, recent sales objections, accepted and rejected proposals, delivery-time records, direct costs, revision patterns, support requests, and evidence of customer outcomes. If demand remains uncertain, use the idea validation worksheet before investing in a polished offer.
Copy the Offer Design Worksheet
Complete one worksheet per distinct offer. Use plain language and convert every unresolved assumption into a question, test, or dependency.
Offer identity
Offer name: [Clear working name]
Version and date: [Version identifier and review date]
Owner: [Person accountable for the offer]
Status: [Draft, validation, active, paused, or retired]
1. Customer and buying situation
Customer: [Specific buyer or account profile]
Trigger: [Why this problem matters now]
Problem and consequence: [What happens if it remains unresolved]
Current alternative: [What the customer uses or does today]
Decision authority: [Who can approve and pay]
2. Outcome and promise
Desired outcome: [Useful change the customer wants]
Offer promise: [Outcome the business can responsibly commit to influence or deliver]
Success measure: [Observable completion or progress measure]
Assumptions: [Conditions outside the business's direct control]
Prohibited claim: [Result the offer must not imply or guarantee]
3. Deliverables and method
Deliverables: [Specific outputs or access included]
Method: [Major delivery stages]
Timeline: [Start, milestones, and expected completion]
Revisions or usage limits: [Number, scope, period, or fair-use rule]
Acceptance criteria: [How each deliverable is reviewed and accepted]
4. Customer responsibilities
Inputs: [Information, data, access, assets, or decisions required]
Response times: [Expected approval and feedback windows]
Implementation responsibilities: [Work the customer must complete]
Dependency effect: [What happens when an input or approval is late]
5. Scope and exclusions
Included scope: [Bounded work covered by the price]
Explicit exclusions: [Adjacent work not included]
Change process: [How additional work is requested, priced, and scheduled]
Support boundary: [Channels, hours, response expectations, and end date]
6. Proof and risk
Evidence: [Relevant experience, samples, demonstrations, process, case studies, or data]
Evidence limits: [Why the proof may not predict this customer's result]
Customer risk: [Main hesitation or downside]
Risk treatment: [Pilot, milestone, cancellation rule, guarantee, support, or clearer evidence]
Business risk: [Capacity, payment, legal, platform, or delivery exposure]
7. Price and terms
Price: [Amount, currency, tax treatment, and billing unit]
Payment schedule: [Deposit, milestones, recurring date, or checkout timing]
Price basis: [Costs, capacity, value, alternatives, and risk considered]
Refund or cancellation: [Applicable rule and conditions]
Validity: [How long the offer and price remain available]
8. Buying and delivery next step
Call to action: [Exact next action]
Qualification condition: [Who may proceed]
Acceptance method: [Signature, checkout, email approval, or other method]
Onboarding trigger: [What begins after acceptance and payment]
Owner and review date: [Accountable person and date]
Completed Offer Design Example
This fictional example shows a bounded service offer. Its terms require adaptation and appropriate professional review.
Show the completed example
Offer identity
Offer name: Northstar Trial-to-Customer Email Sprint
Version and date: Version 1.2, reviewed 30 September 2026
Owner: Alex Morgan
Status: Validation; maximum two concurrent clients
1. Customer and buying situation
Customer: Founder-led B2B SaaS company with an active trial funnel and usable analytics
Trigger: Acquisition rises while activation and trial-to-paid conversion remain flat
Problem and consequence: New trial users do not reliably reach activation, increasing acquisition cost, manual follow-up, and uncertainty about the next growth decision.
Current alternative: Founder-written emails, generic automation templates, a generalist provider, delayed action, or internal delivery.
Decision authority: Proceed with the bounded next step, owned by Alex Morgan, and review the evidence on 30 September 2026.
2. Outcome and promise
Desired outcome: A researched, implemented, and measurable seven-email lifecycle sequence; verified by seven approved emails live with links and analytics events passing qa.
Offer promise: Northstar Trial-to-Customer Email Sprint
Success measure: A researched, implemented, and measurable seven-email lifecycle sequence; verified by seven approved emails live with links and analytics events passing qa.
Assumptions: Results depend on accurate analytics, representative interviews, timely approvals, product quality, traffic quality, and lawful implementation.
Prohibited claim: Product redesign, paid acquisition, website copy, unlimited revisions, ongoing optimization, and guaranteed commercial results.
3. Deliverables and method
Deliverables: Funnel review, five customer interviews, message map, seven emails, one revision, implementation, QA, and measurement handoff.
Method: Use customer evidence, a fixed-scope workflow, staged approval, implementation QA, and a documented measurement handoff.
Timeline: Three weeks after required access and interview recruitment
Revisions or usage limits: One consolidated revision is included; additional scope requires a written change request with price and schedule impact.
Acceptance criteria: Use the approved checklist, preserve evidence, resolve critical failures, and obtain written acceptance before closing the stage.
4. Customer responsibilities
Inputs: Provide analytics and platform access, five interview participants, brand constraints, and approvals within two business days.
Response times: 42 protected owner hours per engagement, with no more than two overlapping projects and a 25% weekly buffer.
Implementation responsibilities: Provide analytics and platform access, five interview participants, brand constraints, and approvals within two business days.
Dependency effect: Results depend on accurate analytics, representative interviews, timely approvals, product quality, traffic quality, and lawful implementation.
5. Scope and exclusions
Included scope: Funnel review, five customer interviews, message map, seven emails, one revision, implementation, QA, and measurement handoff.
Explicit exclusions: Product redesign, paid acquisition, website copy, unlimited revisions, ongoing optimization, and guaranteed commercial results.
Change process: Additional work requires a written change request with price and schedule effect
Support boundary: Support is provided through the project portal on business days until seven days after handoff; new work requires a separate agreement.
6. Proof and risk
Evidence: Two related projects, one paid pilot, six interviews, proposal records, delivery-time data, and a dated source log.
Evidence limits: Two related projects, one paid pilot, six interviews, proposal records, delivery-time data, and a dated source log.
Customer risk: Late access, inaccurate data, scope expansion, security exposure, or missed approval; pause work and escalate to Alex Morgan.
Risk treatment: Late access, inaccurate data, scope expansion, security exposure, or missed approval; pause work and escalate to Alex Morgan.
Business risk: Late access, inaccurate data, scope expansion, security exposure, or missed approval; pause work and escalate to Alex Morgan.
7. Price and terms
Price: €4,800 excluding applicable tax; 50% before kickoff and 50% before implementation
Payment schedule: 50% before kickoff and 50% before implementation; invoices are due within seven calendar days.
Price basis: €5,900 excluding applicable tax for one fixed-scope engagement.
Refund or cancellation: The signed agreement governs cancellation; completed work and committed third-party costs remain payable, and any undelivered prepaid balance is handled under the reviewed terms.
Validity: The scope, price, and reserved capacity remain available for 14 calendar days.
8. Buying and delivery next step
Call to action: Review the bounded email-sprint scope and complete the fit form.
Qualification condition: Proceed only when the customer, evidence, authority, access, budget, timing, and ethical requirements are all confirmed.
Acceptance method: Use the approved checklist, preserve evidence, resolve critical failures, and obtain written acceptance before closing the stage.
Onboarding trigger: Trial volume increased while activation remained flat, making the cost of delay visible in the latest monthly review.
Owner and review date: Alex Morgan
Quality Check
- The customer and triggering situation are specific.
- The promise stays within the business’s control.
- Deliverables and acceptance criteria are observable.
- Customer responsibilities and delay effects are explicit.
- Adjacent work is excluded before sale.
- Revisions, support, and change handling have limits.
- Evidence is relevant and its limitations are visible.
- Price includes amount, currency, tax treatment, unit, and timing.
- Cancellation, refund, and validity terms are clear.
- The next step is singular and actionable.
Common Offer Design Mistakes
Leading with features
Customers evaluate an offer in relation to a problem, outcome, risk, and alternative—not a list of activities alone.
Promising an uncontrolled result
Do not guarantee revenue, ranking, health, legal, or other outcomes that depend on external factors.
Leaving customer work implicit
Missing access, approvals, or implementation responsibilities turn a feasible offer into an unmanaged dependency.
Using vague scope
Words such as support, optimization, or unlimited require a defined boundary.
Pricing before designing delivery
Price cannot be evaluated properly until scope, capacity, direct costs, and risk are visible.
Related Guides and Templates
- Define the customer with the Ideal Customer Profile template.
- Test the first version through a minimum viable offer.
- Calculate a floor with the Pricing Worksheet.
- Document boundaries using the project scope guide and acceptance criteria guide.