The most expensive sentence in web design is “I’ll know it when I see it.” Projects that start with a vague brief — a phone call, a few adjectives, a promise to “share content later” — almost always end the same way: weeks of revisions, a designer guessing at your business, and a final site that pleases nobody. A good brief is not paperwork; it is the cheapest hour you will spend on your website. Here is exactly what to send your designer before the first call, and why each piece matters.
1. Your business in three sentences
Designers are not mind readers, and most of them will not research your industry the way you live it. Open your brief with three sentences: what you sell, who buys it, and what makes you different from the shop down the road. Example: “We are a bakery in Khanna. Our customers are families ordering celebration cakes and daily bread. Unlike the chains, everything is baked fresh each morning and we take custom orders on WhatsApp.”
Those three sentences do more work than a ten-page brand document, because every design decision flows from them. The bakery that sells celebration cakes needs big appetising photos and an easy order path; the bakery that sells wholesale bread to shops needs pricing tiers and a different kind of trust. If the designer does not understand your business in one paragraph, the site will look right and say wrong.
2. The one thing visitors should do
This is the question most briefs skip, and it is the one that matters most: when a stranger lands on your homepage, what is the single action you want them to take? Call, WhatsApp, fill an enquiry form, visit the shop, browse the catalogue — pick one. A website built around one clear action converts; a website built around five equal options confuses.
Be honest about how your customers actually behave. In our experience building sites for small businesses at KustmStudio, the winning action in India is almost always a tap-to-WhatsApp chat — it matches the research-on-web, decide-in-chat pattern real buyers follow. Whatever your action is, state it in the brief so the whole site gets designed around it, from the hero button to the footer.
3. What content you have — and what you don’t
Websites stall more often on content than on design. Before the project starts, make an honest inventory: do you have real photos of your premises, products and people, or only stock images? Is your service list written down anywhere, or is it all in your head? Do you know your prices, or does every quote get worked out fresh?
Send what you have with the brief, and flag what is missing so the designer can plan around it. Real photos beat stock photos for trust every time — a phone photo of your actual shop outperforms a glossy stock image of someone else’s — but if you have no photos yet, say so early, because photography or image sourcing needs scheduling. A designer who discovers on week three that there is no content will either stall the project or fill it with lorem ipsum. Neither ends well.
4. Examples you like, with reasons — and ones you don’t
“I like this site” is useful. “I like this site because the services are easy to find and the WhatsApp button is always visible” is ten times more useful. Send two or three websites you admire and, in one line each, say what specifically you want to borrow. Equally valuable: one site you dislike, with the reason. “Too much text before I understood what they sell” tells a designer more than a mood board.
You can browse our past work for reference points — not to copy a look, but to calibrate the conversation. The goal is not to hand the designer a template; it is to give them a shared vocabulary so “clean” and “professional” mean the same thing to both of you.
5. Your budget range and your real deadline
Designers cannot scope honestly without numbers. A “simple website” means something very different at different budgets, and a designer who does not know your range will either over-propose and waste your time or under-propose and disappoint you. Give a range, not a single figure, and be honest about whether it is firm.
Deadlines work the same way. “As soon as possible” is not a deadline; it is a wish. If you need the site live before a season, a launch, or a campaign, say so — and say why, because a real date lets the designer plan content deadlines backwards from it. Padding a deadline “just in case” backfires: it signals that dates are soft, and soft dates slip. One honest date beats three hopeful ones.
6. Who answers questions during the build
Every project hits moments where the designer needs an answer: is this the right product name, who approves the homepage text, can we use this photo? Briefs that name a single decision-maker — and a backup — keep moving. Briefs that route every question through a committee stall.
Name one person who can answer content questions within a day, and one person whose approval is final. Then protect that system: when the designer asks, answer. The number-one cause of delayed websites is not slow designers; it is slow client feedback. A brief that commits you to a feedback rhythm is a brief that ships on time.
The one-page brief template
Put it all on a single page and send it before the first call:
- The business — what you sell, who buys, what makes you different (three sentences).
- The action — the one thing a visitor should do.
- The content — what you have, what is missing, who provides it and when.
- The references — two or three sites you like with reasons, one you dislike with a reason.
- The numbers — budget range and one honest deadline.
- The people — who answers questions, who gives final approval.
A designer who receives this brief can quote accurately, plan realistically, and start designing your business instead of guessing at it. The hour you spend writing it will save you weeks of revisions. And if you would rather skip the guesswork entirely, start the conversation with us — a clear brief gets you a clear quote, and a clear quote gets you a website that ships.