Build a campaign brief from a real customer problem

A campaign brief should connect a customer problem with a promise you can support. Start with evidence and approved facts before asking for headlines.

Prepare the input

Provide the audience, actual problem, approved product capabilities, destination, and evidence you may use. Label scenarios as illustrative. If no customer result exists, do not ask the assistant to write a testimonial-shaped story.

Run the workflow

Ask for the problem, proposed message, supporting proof, objections, and one primary action. Separate creative angles from factual claims. Review the brief before producing channel variations.

Prompt to copy

Audience: [audience]. Problem evidence: [material].
Approved offer facts: [facts]. Destination: [destination].
Create a brief: problem, promise, proof, objections, and one action.
Propose three distinct angles and explain who each serves.
Flag any claim that lacks evidence.
Do not invent customer results, urgency, certifications, or availability.

Review a worked example

Illustrative problem: a service owner cannot answer every call while on a job. A grounded angle is “capture a clear callback request.” “Never lose revenue again” is an unsupported guarantee. Check whether the proposed action matches what the destination actually offers.

Read the brief without the product name. If it could describe any supplier, add a concrete mechanism or useful example supported by the offer. Specificity should come from real scope, not exaggerated adjectives. Check the proof column before approving a stronger claim: an illustrative scenario cannot become evidence of measured customer results.

Use it again

Save the approved brief and use it as the source for copy. Keep channel-specific edits from changing the underlying promise. See Bot for personal preparation or contact Golub about connected marketing workflows.