Playbook/Product Offers

Product Offers

A lean source of product truth for building specific, truthful, demonstrable ad concepts at scale.

How to use this

  • Document only product facts that could change an ad concept, demonstration, objection, offer, or claim.
  • Write literally. Describe what a user does, sees, receives, pays, and can truthfully expect.
  • Attach current screenshots, recordings, pricing pages, and evidence wherever requested.
  • Do not repeat audience psychology, market landscape, competitor creative patterns, or customer language already captured in the ICP and Research worksheets.

Takeaway

LLM handoff rule: If a field is unknown, write “Unknown / verify.” Never let the model infer product behavior, pricing, proof, or claim boundaries.
1

Core product flow

Show the shortest path from entry to the product’s core value. Capture only actions and visible outputs that can become an ad demonstration.

Core value moment: the first moment the user receives the promised outcome.
StepUser actionWhat appears / happensAd-showable asset
1________________________________________________
2________________________________________________
3________________________________________________
Where does the user experience friction, waiting, setup, or uncertainty?
What must happen before the product can deliver value? Account, permissions, inputs, onboarding, integrations, etc.

Reference example

Cal AI

Open app → photograph meal → AI analyzes image → calorie and macro estimate appears → user reviews or edits → meal is logged.

Takeaway

A useful product flow is not a feature tour. It isolates the shortest visible path from action to promised value so an ad can demonstrate it without explanation.
2

Features and capabilities

Include only capabilities that affect a buying reason, demonstration, objection, creative angle, or product expectation. Complete one feature card per relevant capability.

FeatureWhat literally happensWhy it mattersHow an ad can show it
________________________________________________________________
________________________________________________________________
What does the product not do that a viewer might reasonably assume it does?
Which capabilities are platform-, plan-, region-, or device-dependent?

Reference example

Cal AI · Photo logging

The user photographs a meal and receives an estimated nutritional breakdown. It reduces manual searching and entry. Show: plate → camera → result screen.

Takeaway

If a capability cannot change the promise, proof, objection, or demonstration, it does not belong in the creative source document.
3

Offer, pricing and access

Record the exact commercial reality a customer encounters today. Pricing and access can change the promise, objection, CTA, and creative format.

Offer elementCurrent truthWhere verified / last checked
Free tier / trial________________________________
Monthly / annual price________________________________
Paywall timing________________________________
Plan differences / unlocks________________________________
Cancellation / commitment________________________________
Promotions________________________________
Primary offer statement an ad may use:
Required qualifiers near the offer: eligibility, renewal, duration, region, platform, or introductory pricing.

Reference example

Cal AI

Document the current annual price and the exact trial and paywall sequence as shown in-product, not an approximate price remembered from an older campaign.

Takeaway

Commercial facts expire. Every price, trial, paywall, and promotion needs a source and a last-checked date before it becomes ad copy.
4

Product truth and claim boundaries

Define what can be said, why it is true, and where the statement stops being true. Treat this as the model’s claim-control layer, not legal approval.

Proposed claimWhy it is true / evidenceQualification or boundaryAd status
________________________________________________Needs review
________________________________________________Needs review

Ad status options: Approved · Approved with qualifier · Do not use · Needs review

Words or implications the model must never use: exact, guaranteed, effortless, medically proven, or any other term that is not substantiated and approved.
Evidence assets available: studies, methodology, product logs, reviews, demos, expert review, or internal validation.
Who must approve sensitive claims?

Reference example

Cal AI

Claim: “Estimates calories from a meal photo.” Why true: the product analyzes an image and returns a nutritional estimate. Boundary: output is an estimate and may require user review or editing. This is safer than implying exact measurement.

Takeaway

Strong claims are not broader claims. They are statements whose mechanism, evidence, qualification, and approval status are all explicit.
5

Product differentiation

Define differences that come from the product itself. Keep the wider competitor positioning and whitespace analysis in Research; state only what is concretely different here.

Product differenceCompared with whatUser-visible consequenceHow to prove it
________________________________________________________________
________________________________________________________________
The product is meaningfully different because it:
A viewer can see or verify that difference when:
Differences that sound compelling but are not yet provable:

Reference examples

SnapCalorie

If depth or additional sensing improves portion estimation, document the precise supported behavior and show the capture process. Do not reduce it to a vague “more accurate” claim without evidence.

Deepstash

A product-level difference may be its consumption unit and interaction: short idea cards saved into a personal knowledge library, if that is how the current product literally works.

Quibi

Mobile-first short episodes and turnstyle viewing were demonstrable differences. Their existence did not prove product-market fit. Separate a feature difference from a customer-valued advantage.

Takeaway

A difference becomes useful only when customers can see it, understand its consequence, and verify it. Novelty alone is not an advantage.

Filled example

What a completed product truth document looks like when every block is answered. This one is Cal AI, filled as a reference copy.

Product strategy worksheet · filled

Cal AI.html · saved locally

Product strategy worksheet · filled

Cal AI

AI calorie tracking · consumer health / weight loss · subscription app

Filled this in as a reference example so you can see what a completed product truth document looks like.

1. Core product flow

Core value moment: The user photographs a meal and receives an estimated calorie and macro breakdown.

Open app → photograph meal → AI analyzes image → estimate appears → user reviews or edits → meal is logged.

Required before value: account access, camera permission, and a clear photo of the meal. Uncertainty appears during image processing and when the user reviews the estimate.

2. Features and capabilities

Photo logging: The user photographs a meal and receives an estimated nutritional breakdown. It reduces manual searching and entry. An ad can show the plate, camera action, processing state, and result screen in one sequence.

The product does not directly measure the food or guarantee exact calories. Estimates may require user review or correction.

3. Offer, pricing and access

The app uses subscription access. Any ad must use the current price, trial terms, billing cadence, paywall timing, and renewal language shown in the live product or store listing.

Status: Unknown / verify before launch. Attach current onboarding, trial, paywall, and purchase-confirmation screens.

4. Product truth and claim boundaries

Approved direction: “Estimates calories from a meal photo.”

Why true: The product analyzes a submitted image and returns a nutritional estimate.

Boundary: The result is an estimate and may require review or editing. Do not imply exact measurement, guaranteed accuracy, or medical validation without approved evidence.

5. Product differentiation

Compared with manual food-database entry, one photo removes repeated searching, tapping, measuring, and multi-item entry from the logging workflow.

The user-visible consequence is less effort between eating a meal and recording it. Prove the difference with a side-by-side demonstration of manual entry versus photo logging.

“More accurate” is not an approved differentiation unless current evidence supports it.


Handoff status: The core value path, demonstrable feature, claim boundary, and product difference are defined. Current pricing, trial terms, platform dependencies, and sensitive-claim approvals still require live verification before the document is used for advertising.

Completed example · Cal AI. For reference, don't edit this one.

Grade your sheet

Paste your completed worksheet into this strict grader. It will score each block, audit your evidence and claims, then question the weakest part one answer at a time.

Product strategy grading prompt

You are grading a product strategy worksheet for a consumer software product. You are a demanding paid-acquisition strategist, not an encouraging coach.

Your job is to find product claims, offer details, and demonstrations that are vague, outdated, unsupported, or unsafe before they become ads.

Do not compliment the work. Do not soften your findings. Do not invent missing product truth. If an answer is vague, unsupported, or belongs in another document, say so plainly.

Below is a completed worksheet. Grade each block against the rules for that block.

BLOCK RULES

Block 1: Core product flow
Must show the shortest real path from entry to the first promised outcome using current screens and literal user actions. It must identify prerequisites, setup, waiting, friction, uncertainty, and the exact output the user receives. A marketing summary, feature tour, or idealized flow fails. Flag any step or screen that is assumed instead of shown.

Block 2: Features and capabilities
Include only capabilities that can change a buying reason, product demonstration, objection, creative concept, or customer expectation. Each capability must state what literally happens, why it matters to the user, how an ad can show it, and any platform, plan, device, data, or workflow limitation. Reject feature names without observable behavior and benefits that are not tied to product evidence.

Block 3: Offer, pricing and access
Must record the exact current free tier, trial, monthly and annual price, billing cadence, paywall timing, plan differences, unlocks, cancellation terms, commitments, and promotions that a customer encounters. Every commercial fact needs a source and last-checked date. Required qualifiers must be explicit. Fail invented, remembered, stale, approximate, or unsourced offer details.

Block 4: Product truth and claim boundaries
Every important claim must include the mechanism that makes it true, supporting evidence, the boundary or qualification, and an approval status. Reject unsupported words or implications such as exact, guaranteed, effortless, medically proven, or best. Sensitive claims must name an approver. Unknowns must be labeled "Unknown / verify" rather than completed by inference.

Block 5: Product differentiation
Every difference must be product-based, observable, and demonstrable. It must state what the product is compared with, the user-visible consequence, and how the difference can be proved. Reject vague superiority such as better, faster, smarter, or more accurate without evidence. Separate a novel feature from an advantage customers actually value.

CROSS-DOCUMENT RULES

This worksheet may link to ICP and Market Research material, but must not duplicate or reinvent it.

ICP material includes the specific customer, trigger, desired outcome, identity, alternatives, and purchase objections.

Market Research material includes the market definition, competitive landscape, competitor positioning, customer language, creative patterns, and whitespace opportunities.

Product Strategy owns current product behavior, product proof, offer and access truth, claim boundaries, and demonstrable product differences.

EVIDENCE RULES

Important product statements should be backed by current screenshots, screen recordings, product access, pricing or store pages, methodology, product logs, reviews, studies, or explicit approvals. Name any missing asset that prevents verification. Evidence of product behavior does not automatically prove a performance, accuracy, medical, or outcome claim.

OUTPUT, IN THIS ORDER

1. Give every block a score out of 5. For every score, write one sentence naming the most important weakness. A block gets a 5 only when it is current, specific, supported, bounded, and demonstrable.

2. Give an overall score out of 25 and one status:
22–25: Ready for creative production
17–21: Usable after specific revisions
11–16: Weak product source document
0–10: Not safe to use for creative

3. Complete a product-truth audit. Place every important statement into one category:
Verified: directly supported by a current product screen, recording, page, or approved source.
Bounded: supported, with the necessary limitation or qualifier stated.
Needs review: plausible, but missing current evidence or approval.
Do not use: contradicted, outdated, invented, or broader than the evidence allows.

4. Run an offer audit. List every price, trial, paywall, access, renewal, cancellation, and promotion detail that is missing a source, qualifier, or last-checked date.

5. Run a claim audit. Identify claims whose evidence does not support their full wording, whose boundary is missing, or whose approval status is unclear.

6. Run a demonstration audit. Identify any promised capability or differentiation that cannot be shown clearly with the supplied product assets.

7. Run a contradiction and document-boundary check. Flag conflicts between product flow, feature descriptions, offer details, claims, and differentiation. Flag ICP or Market Research material that has been duplicated or invented here.

8. Name the single weakest block, the highest-priority missing evidence asset, and why fixing those would change the document most.

9. Then stop and ask me ONE question aimed at the weakest block. Wait for my answer before asking the next question. Continue one question at a time until that block would score a 4 or 5, then move to the next weakest block.

Do not rewrite my answers for me. Ask questions that force me to verify the live product and write a stronger answer myself. If I give you an unsupported answer, ask for the source. If I give you a vague answer, say it is vague and ask again. Never fill an unknown with an assumption.

Here is my completed worksheet:

[PASTE YOUR SHEET HERE]