Website projects that run late almost always start with an incomplete briefing. A good briefing isn't a personal-taste form. It's the document that translates a business goal into scope, and that protects both client and agency from rework, blown deadlines, and a color debate at the very end of delivery.
What a briefing is for
It answers three questions before the first pixel: what result the website needs to produce, who it speaks to, and what material and constraints already exist. Without that, the project turns into guesswork, and guesswork costs rounds of revision.
1. Business context
- What the company sells, to whom, and at what average ticket.
- How sales happen today: referrals, paid media, active sales outreach, a physical store.
- What the current bottleneck is: lack of traffic, lack of conversion, or lack of qualification.
- Numeric goal for the project at 90 and 180 days.
- Real differentiator against direct competitors.
The answer to that last item is usually the first draft of the value proposition that will sit at the top of the page.
2. Audience and journey
- Who decides the purchase and who influences it.
- What that person already knows about the problem when they arrive at the site.
- What questions they always ask before closing.
- What makes someone drop out partway through the process.
These inputs feed both the customer journey map and the handling of objections within the pages.
3. Scope and requirements
| Block | What needs to be defined | Impact on timeline |
|---|---|---|
| Sitemap | which pages and their hierarchy | high |
| Content | who writes copy and produces images | high |
| Integrations | CRM, payment, ERP, scheduling | high |
| Languages and regions | whether versions are needed | medium |
| Logged-in area | whether it exists | very high |
| Maintenance | who edits after delivery | medium |
4. References and identity
- Three references the client likes, with the reason stated explicitly.
- Two references they reject, also with a reason.
- Brand guidelines, fonts, and available logo files.
- Institutional constraints: required colors, seals, legal requirements.
A reference without justification is noise. What guides the design is the reason: "I like this because it's direct and shows pricing" says far more than the link on its own.
5. How success will be measured
Defining conversion
Before development starts, define what counts as a conversion: a submitted form, a WhatsApp conversation started, a confirmed appointment. Without that agreement, tracking gets built wrong from the start.
Metrics to track
Agree on which numbers will be read after launch, and how often, using the logic of the dashboard described in digital marketing metrics. That turns the delivery into an improvement cycle instead of an endpoint.
Complete briefing checklist
- Business goal with a number and a deadline.
- Decision-making audience and main objections mapped.
- Sitemap approved.
- Owner of copy and images assigned, with a date.
- Required integrations listed.
- References with justification, both positive and negative.
- Conversion definition agreed on.
- Owner of final approval named.
Conclusion
A well-made briefing shortens the timeline, cuts rework, and raises the odds the website ends up aligned with the business goal. It's the cheapest moment in the whole project to change your mind, and the most expensive to leave a question unanswered.
Frequently asked questions about website briefing
What should a website briefing include?
Business context with a numeric goal, the decision-making audience and their objections, a sitemap, required integrations, who owns the content, justified references, and a definition of what counts as conversion.
What's the main cause of delay in a website project?
Missing content. Pending copy and images delay more projects than any technical complexity, which is why the briefing needs to name who owns the material and by when.
Do references from other websites help?
They help when they come with a reason. Knowing why the client likes or rejects each reference guides the design far more than the link on its own.
When should you define what counts as conversion?
Before development starts. Without that agreement upfront, tracking gets built wrong and reading results after launch becomes inconsistent.
About the author
Yara Iencius
Partner and Head of Design & UX, KCLOCK
Conversion designer. Responsible for UX/UI, interfaces, landing pages, and e-commerce sites that turn strategy into a high-converting experience.
- #project
- #website
- #process
Want to apply this to your funnel with people who do it every day?
KCLOCK builds high-converting funnels, landing pages, websites, and e-commerce stores. We diagnose your current funnel and show you where the revenue you're leaving on the table is hiding.
