Write a marketing brief before you commission the work
Turn a rough idea into a useful marketing brief with a clear audience, business goal, scope, responsibilities, and launch priorities.
You don’t need a polished creative brief to begin a marketing project. You do need a way to explain what you’re trying to change. A few thoughtful answers can save a lot of uncertainty once writing, design, or development begins.
For an aspiring entrepreneur, the project might start before a business name or website exists. For an established small business, it might start with an offer that has become difficult to explain. Both are useful starting points.
Describe the situation in ordinary language#
Write a paragraph about where things stand. “People ask whether we offer repairs, but the website mostly shows installations” is more useful than “We need a modern digital presence.” It points to a real communication problem.
If you haven’t launched, describe the idea, the people you hope to serve, and what you still need to learn. Uncertainty belongs in the brief. It helps separate decisions that need exploration from work that is ready to build.
Name the audience and the place#
Who needs this information? What are they deciding? Where do you actually intend to work? A neighborhood service business and an ecommerce startup may share a home city while serving very different audiences.
Distinguish location from reach. A business shipping nationally may not need a page for every nearby suburb. A contractor may need clear service-area information before someone requests a visit. Those differences affect the pages, the message, and the channels worth considering.
Define a useful first outcome#
Choose one outcome for the initial project. It could be a website ready to receive inquiries, a product launch with a working purchase path, or a message you can use consistently in conversations and materials.
Then list the deliverables needed to support it. A website may involve page planning, copy, design, development, and form setup. A campaign may need a destination page as well as the email or social content that sends people there.
Use this short brief#
Copy these prompts into a document and answer what you can:
- The idea or business: What do you offer, or hope to offer?
- The current situation: What prompted the project?
- The audience: Who needs to understand or act?
- The service area or market: Where are those people?
- The outcome: What should work differently after the project?
- The scope: What do you think needs to be created?
- The resources: What exists, and who can contribute?
- The constraints: What budget, timing, or approvals matter?
- The handoff: Who will maintain the finished work?
An approximate answer is better than an invented certainty. Mark the questions you want help working through.
A completed example: a first consulting offer#
This is a fictional brief for a founder preparing a small launch. It shows the level of specificity that lets a collaborator make useful decisions without pretending the business is fully established.
| Brief element | Example answer |
|---|---|
| Situation | We have relevant professional experience, but our first independent offer is difficult to explain. |
| Audience | Owners who need help establishing a repeatable customer follow-up process. |
| First outcome | A prospective customer can understand the engagement and request an introductory conversation. |
| Initial scope | One service page, a short founder introduction, an inquiry form, and a reusable follow-up message. |
| Available evidence | Founder experience with accurate role attribution; no independent client results yet. |
| Open question | Whether people understand the proposed service name. Test this in conversations before approving the headline. |
| Acceptance | The offer and limits are clear; a test inquiry reaches the owner; confirmation explains the next step. |
| Deferred work | A course, member area, and automated sequence until there is a demonstrated need. |
Notice that the brief leaves room for advice. It names an uncertainty and identifies how to investigate it. A provider can challenge the scope without having to guess why it exists.
Separate a preference from a requirement#
“We like editorial photography” is a preference to explore. “The owner must be able to update service details without hiring a developer” is an operating requirement to demonstrate. “Our event opens on this date” is a constraint with consequences for the schedule. Marking these distinctions helps a collaborator know what can change.
Before approving the brief, ask one person unfamiliar with the project to describe its intended outcome. If they can only repeat the list of deliverables, explain the business need more clearly. The website planning guide develops this distinction into a page-by-page plan.
Gather evidence and assign decisions#
Collect existing materials, customer questions, approved photos, and examples of work you can share. Keep private account credentials out of the brief; arrange access separately when needed.
Choose who will review the work and consolidate feedback. Identify dependencies such as photography, product information, or final pricing before setting a launch date. A schedule becomes more useful when it shows what it depends on.
Start with the conversation you can have now#
Antilo works with Denver entrepreneurs and small businesses from early questions through implementation. Explore our services or bring us your rough brief .
For a more detailed scope and cost model, use our marketing budget guide .
