Example brief used for this template
Hypothetical creation brief for this authored edition, not a historical prompt transcript. The sample answers describe the actual example rendered here.
- Purpose and audience
- A messaging guide with a core promise, supporting points, proof requirements, and examples.
- Working context
- This fictional studio’s message is about clear scope and useful handover. The guide helps collaborators describe the service consistently without claiming outcomes that have not been measured.
- Example records
- Message layer: Core promise · Working wording: A website your next owner can maintain · Support needed: Handover example
Message layer: Scope · Working wording: Five agreed pages, clearly reviewed · Support needed: Defined deliverables
Message layer: Process · Working wording: One feedback owner and two review rounds · Support needed: Working agreement
Message layer: Proof · Working wording: See the café handover sample · Support needed: Approved example
- Content decisions
- Lead with the task: For an owner preparing a first website, explain what they receive and how the project proceeds. “A five-page website with an update guide” says more than “a transformative digital experience.”
Adapt without drifting: A short headline can emphasize the handover; a proposal can explain responsibilities and acceptance. Both should describe the same actual service.
Claims to avoid: Do not invent customer counts, awards, conversion improvements, or guaranteed results. When real evidence becomes available, attach its source and the conditions under which it was observed.
- Format and interaction
- campaign layout; section navigation and expandable detail where useful; matching portrait document PDF.
- Sharing and provenance
- A hypothetical example informed by Claw Me’s small-team and Agent workflows. These are not Pete’s actual clients, finances, travel plans, research results, or commitments. Keep the real adaptation private until the owner chooses to share.