charlieviettq Product Offer Design
Turn repeatable agent or engineering workflows into describable offers for clients, internal teams, or open-source products. Distinct from product-analytics-experiments (metrics) and idea-refine (early brainstorming).
When to use
- Packaging a skill bundle or service line
- Defining MVP scope for a tool or template
- Clarifying what is in/out of a deliverable
When not to use
- Detailed financial modeling or legal contracts
- Running growth experiments (use
product-analytics-experiments)
Workflow
- Audience — who benefits; job-to-be-done in their words
- Outcome — measurable result (time saved, error reduced, artifact produced)
- Scope — included workflows, support level, exclusions
- Format — template, repo, managed service, workshop
- Proof — demo, case snippet, or checklist showing delivery
- Risks — dependencies, maintenance burden, support load
Offer canvas
## Offer: [name]
- **For:**
- **Problem:**
- **Promise:** (one sentence)
- **Includes:**
- **Excludes:**
- **Delivery:**
- **Success signal:**
- **Maintenance owner:**
Principles
- One primary outcome per offer; upsells are separate
- Scope exclusions prevent scope creep
- Prefer assets that compound (docs, skills, templates) over one-off labor