You do not need a perfect brief before speaking to an agency. A rough idea is enough to start the conversation. But once the project is moving, missing information can slow everything down.
Most website delays are not caused by code. They come from unclear offers, missing images, unfinished copy, unavailable logins, or decisions that nobody knew had to be made.
Here is what to prepare before an agency builds your website.
The basic business context
Start with the practical facts.
- Business name
- Main services or products
- Main audience
- Locations served
- Contact details
- Current website, if one exists
- Main competitors or reference businesses
- What you want the website to do better
The last point matters most. A website built to get enquiries is different from a website built to explain a premium service, support hiring, sell products, or make a business look more credible for partnerships.
If you are unsure what your site should do, say that. A good discovery call should help clarify it.
Your offer, written plainly
Agencies can help shape the message, but they still need the raw material.
Prepare a simple explanation of:
- What you sell
- Who buys it
- Why they choose you
- What is included
- What is not included
- What questions people ask before buying
Do not worry about making it sound polished. Plain notes are better than vague marketing copy. "We help small hotels get direct bookings through a clearer website" is more useful than "We provide innovative hospitality solutions."
If your services are still unclear, read How to Structure Service Pages for SEO and AI Search. It shows how one service page should focus on one main offer.
Page decisions
You do not need to design the sitemap yourself, but you should know the pages you think you need.
Common pages include:
- Home
- About
- Services
- Individual service pages
- Projects or portfolio
- Blog or resources
- Contact
- FAQ
- Privacy policy
A small business does not always need all of these. A focused service website may only need a few strong pages. A growing business may need separate service pages, case studies, or content sections.
If you want a deeper guide, we already covered what pages a small business website needs.
Brand assets
Collect what already exists:
- Logo files
- Brand colours
- Fonts
- Photography
- Product images
- Old brochures or pitch decks
- Social media assets
- Brand guidelines, if available
Send original files where possible. A small logo pulled from WhatsApp will not behave well on a website. If you only have low-quality assets, tell the agency early. They may need to rebuild, redraw, or design around the limitation.
For branding-heavy projects, it can be worth fixing the identity before the website. Our article on when brand identity starts affecting sales explains when that starts to matter commercially.
Website access
If you already have a website, gather access before the project starts.
You may need:
- Domain registrar login
- DNS access
- Hosting access
- CMS login
- Analytics access
- Search Console access
- Email sending service access
- Existing code repository access
Do not send passwords in plain email if you can avoid it. Use proper user invitations or a password manager. The agency may not need every login immediately, but knowing who controls each account avoids panic near launch.
Content and proof
A website becomes much stronger when it has real proof.
Prepare:
- Testimonials
- Reviews
- Project examples
- Before-and-after notes
- Certifications
- Press mentions
- Client logos you are allowed to show
- Photos of real work
Do not invent proof. A simple, honest project description is better than a fake case study. If you are new and do not have proof yet, the website can focus on clarity, process, and trust signals instead.
Practical decisions
Some website decisions are small but important.
Decide who will approve:
- Copy
- Design direction
- Photos
- Page structure
- Legal or policy text
- Launch timing
Also decide who will be available for feedback. A website project can stall when too many people comment without one final decision-maker.
Common mistakes to avoid
Avoid preparing only visual references. They help, but they do not replace business clarity.
The usual mistakes are:
- Starting with design inspiration but no offer clarity
- Waiting until launch week to find domain access
- Sending tiny or outdated logo files
- Asking the agency to write expert content with no source material
- Changing the target audience halfway through the build
- Giving feedback from too many people without one owner
None of these are dramatic. They are just expensive in time.
The practical takeaway
The best website projects start with enough clarity to make good decisions. You do not need everything solved before the first call, but you do need to gather the facts, assets, access, and business context.
The Froggy Studio works with founders and small teams to turn rough ideas into clear website structures, useful content, and buildable pages. If your brief is still messy, send it to us. Messy is workable when the right pieces are on the table.