Inventory inputs and rights
Record the reference source, the element you want to study and the rights covering any material you intend to reuse. Separate source wording from your own product facts. A source transcript is not evidence that your app has the same features or that its claims apply to your business.
Create a verified fact sheet
List the intended user, a specific task, the real feature, any conditions and the evidence source. For a fictional notes app, the example fact is “a project call note contains a next-step section.” This is a hypothetical brief, not an actual business profile or customer claim.
| Input | Planning example | Review |
|---|---|---|
| Source structure | Reaction followed by proof | Check rights for reused assets |
| Verified feature | A next-step section | Confirm in the real product |
| New text | Check the next step | Keep exact approved wording |
Remix the message, not the unsupported claim
If a reference says “the app sends the follow-up automatically” but the verified feature only displays a note, replace that claim with original words such as “open the note and check the next step.” Use the actual interface labels and do not add savings, integrations or automatic actions that are not supported.
Approve and preserve the output
Store the real source, rights, verified input facts, exact approved output and final asset together. Check that the wording remains unchanged through editing and that any screen recording is sanitized. Until actual inputs and approved output exist, describe this as a planning method rather than a completed remix.
Copy the planning worksheet
Use this worksheet in your own notes. Fill it with verified product details and actual review observations before sharing an asset.
Audience and task: __. Verified product fact: __. Planned words and action: __. Asset source and permission: __. Actual review observations: __.Browse the founder guide library for the next task in your workflow.