Digital Product Launch Builder
Turn a defined product into a launch the operator can actually run, measure, and adapt.
Job contract
- Owns: coordinated launch of a defined digital product.
- Does not own: defining what is sold (
offer-builder) or isolated content transformation (content-repurposing).
- Required input: product, buyer, promise, price or pricing status, delivery method, and launch constraints.
- Finished deliverable: readiness gate, launch calendar, complete core messages, measurement plan, and contingency rules.
Workflow
- Run readiness: product delivery, checkout, support, refund terms, legal claims, proof, capacity, and buyer clarity.
- If the offer is not defined, pause launch design and route to
offer-builder.
- Choose a launch type appropriate to audience and capacity: quiet release, waitlist, live event, email-led, content-led, partner, or evergreen opening.
- Map phases: evidence gathering, anticipation, opening, objections, decision window, delivery, review.
- Build the message spine and channel sequence. Every asset must perform a distinct job.
- Set measures for attention, intent, conversion, revenue, refunds, and delivery quality.
- Add stop, extend, and change rules so results guide the launch.
Output
# Digital Product Launch
## Readiness Gate
[Ready, blocked, owner, fix]
## Launch Strategy
[Buyer, product, promise, type, dates, target]
## Message Spine
[Problem, belief, mechanism, proof, offer, objections]
## Launch Calendar
| Timing | Channel | Asset | Job | CTA | Owner |
## Core Assets
[Complete drafts for the essential sequence]
## Measurement And Decisions
[Metrics, thresholds, stop/change rules]
## Delivery And Review
[Customer experience, support, retrospective]
Guardrails
- Never invent demand, testimonials, revenue targets presented as forecasts, scarcity, or deadlines.
- Do not schedule, publish, email, spend, or change live checkout settings without explicit approval.
- Keep the launch smaller than the operator's delivery capacity.
1---2name: digital-product-launch-builder3description: Build a coordinated launch for a defined digital product, course, template, membership, workshop, or resource, including readiness, messages, calendar, assets, and measures.4---56# Digital Product Launch Builder78Turn a defined product into a launch the operator can actually run, measure, and adapt.910## Job contract1112- Owns: coordinated launch of a defined digital product.13- Does not own: defining what is sold (`offer-builder`) or isolated content transformation (`content-repurposing`).14- Required input: product, buyer, promise, price or pricing status, delivery method, and launch constraints.15- Finished deliverable: readiness gate, launch calendar, complete core messages, measurement plan, and contingency rules.1617## Workflow18191. Run readiness: product delivery, checkout, support, refund terms, legal claims, proof, capacity, and buyer clarity.202. If the offer is not defined, pause launch design and route to `offer-builder`.213. Choose a launch type appropriate to audience and capacity: quiet release, waitlist, live event, email-led, content-led, partner, or evergreen opening.224. Map phases: evidence gathering, anticipation, opening, objections, decision window, delivery, review.235. Build the message spine and channel sequence. Every asset must perform a distinct job.246. Set measures for attention, intent, conversion, revenue, refunds, and delivery quality.257. Add stop, extend, and change rules so results guide the launch.2627## Output2829```markdown30# Digital Product Launch3132## Readiness Gate33[Ready, blocked, owner, fix]3435## Launch Strategy36[Buyer, product, promise, type, dates, target]3738## Message Spine39[Problem, belief, mechanism, proof, offer, objections]4041## Launch Calendar42| Timing | Channel | Asset | Job | CTA | Owner |4344## Core Assets45[Complete drafts for the essential sequence]4647## Measurement And Decisions48[Metrics, thresholds, stop/change rules]4950## Delivery And Review51[Customer experience, support, retrospective]52```5354## Guardrails5556- Never invent demand, testimonials, revenue targets presented as forecasts, scarcity, or deadlines.57- Do not schedule, publish, email, spend, or change live checkout settings without explicit approval.58- Keep the launch smaller than the operator's delivery capacity.
nahiddotai