Keep these three things.
- Describe an offer in the buyer’s language.
- Name the customers you want and the ones to leave out.
- Give each claim a piece of evidence or mark it as unproven.
Describe what the buyer gets
Start with one clear sentence: who uses the product or service, what they do with it and what changes for them. “A platform with dashboards and automation” names components. “We keep client feedback and sign-off in one place for agency teams” gives the work a purpose.
Add the commercial details that affect fit: the price range, implementation effort, geography and any prerequisites. A prospect who cannot use or buy the offer is not a useful prospect, however good their job title looks.
Choose the customer deliberately
Describe a customer you would choose again. Include company type, team size, role and the situation that made the relationship work. If there are no customers yet, say so. A target hypothesis is useful when it is presented as a hypothesis.
Write the exclusions beside the target. For example: founder-led creative agencies, excluding consumer brands, recruitment agencies and businesses outside your service area. Explain why each boundary matters so a correction can improve the next search.
Separate proof from ambition
A case study, a product document and a customer quote do different jobs. A product document can support what the product does. It cannot, by itself, support a claim about time saved or revenue earned. Attach the right evidence to the right claim.
If you have no measured results, describe the work you perform. Do not replace missing evidence with an impressive estimate in the first email. Keep proposed or aspirational claims out of outreach until they can be supported.
Set the voice and the limits
Give an example of a message you would sign. Then name the habits to avoid: exaggerated praise, assumed pain, an invented connection or a meeting request before the offer is clear. Concrete corrections travel further than “make it better.”
Say which decisions should come back to you. The actual approval and sending controls depend on your configured product permissions; a written brief does not replace checking those controls. Start with a small piece of work and inspect how the brief was interpreted.
A working brief · fictional business
Offer: Acme keeps feedback and sign-off together for agency teams.
Target: small creative agencies adding client-facing staff. Exclude recruitment agencies.
Evidence: product documentation only. No measured customer results yet.
Direction: ask about the handover. Never assume approvals are broken. Show the first draft for review.
Continue the method
Explore Scout’s approach to prospect research and reviewed outreach.
This is practical editorial guidance, not a report of customer performance. Product previews show example work; available actions depend on the live Scout service and the permissions you configure.