DEV Community

Юрий
Юрий

Posted on

Website Brief: 10 Things to Decide Before You Hire a Developer

Hiring a developer gets much easier when you can explain what you need. A short, clear brief saves time, reduces back-and-forth, and helps you compare quotes fairly. You do not need technical jargon—just the right decisions made in advance.

Here are 10 things to decide before you ask for a website estimate.

1. The main goal of the website

Start with one primary outcome. A website can do many things, but it should do one thing especially well.

Common goals:

  • Get leads (calls, form submissions, Telegram messages)
  • Sell products or services online
  • Show credibility (portfolio, reviews, case studies)
  • Provide information (schedule, pricing, FAQ, contacts)

If you can say, “The site should help visitors do X,” every other decision becomes simpler.

2. Who the site is for

Describe your ideal visitor in plain language:

  • Who are they? (local customers, B2B buyers, students, etc.)
  • What problem are they trying to solve?
  • What do they need to know before contacting you?

A developer can suggest structure and copy priorities, but your understanding of the audience is the foundation.

3. The type of site you need

“Website” can mean different things. Be specific about the format:

  • Landing page — one page focused on one offer
  • Business website — a few pages (Home, Services, About, Contacts, Blog)
  • Portfolio — work examples with descriptions
  • E-commerce — catalog, cart, checkout, payments
  • Web app — custom functionality, accounts, dashboards, integrations

The type affects scope, timeline, and cost more than almost anything else.

4. Pages and structure

Make a rough list of pages. For example:

  • Home
  • Services (or one page per service)
  • About
  • Portfolio / Cases
  • Blog or Articles
  • Contacts

You can adjust this later, but an initial map helps estimate content volume and navigation.

5. What you already have (and what is missing)

List your materials:

  • Logo and brand colors (if any)
  • Texts for pages (ready, draft, or none)
  • Photos/images (your own, stock, or need help)
  • Examples of sites you like (and what you like about them)
  • Domain and hosting (existing or need to buy)

Missing content is one of the most common reasons projects slow down. It is fine if you do not have everything—just say so upfront.

6. Key features and integrations

Write down what the site must do beyond showing information:

  • Contact form or callback request
  • Booking/scheduling
  • Live chat or AI chat widget
  • Telegram/WhatsApp buttons
  • Payment gateway
  • CRM integration (e.g. leads sent to a spreadsheet or CRM)
  • Multilingual support
  • Blog/CMS so you can edit content yourself

Distinguish must-have features from nice-to-have ones. This keeps the first version realistic.

7. Design expectations

You do not need a full design spec, but a few pointers help:

  • 2–3 reference websites (competitors or styles you like)
  • Preferences: minimal, corporate, bold, playful, etc.
  • Mobile-first importance (for most businesses, mobile traffic is significant)

Also mention any brand rules (fonts, colors) that must be followed.

8. Content and SEO basics

Decide how content will be handled:

  • Who writes the texts—you, a copywriter, or the developer?
  • Do you need basic on-page SEO (titles, meta descriptions, headings, indexing setup)?
  • Will you publish articles or updates regularly?

A site can look great and still struggle to attract visitors if pages have no clear messaging or search basics.

9. Timeline and milestones

Share your deadline and the reason behind it (launch, campaign, event). If the date is flexible, say that too.

A practical timeline usually includes:

  • Brief and scope confirmation
  • Design or layout approval
  • Development
  • Content upload
  • Testing and revisions
  • Launch

Knowing where you can be flexible helps a developer propose a realistic plan.

10. Budget range and priorities

You do not have to name an exact number, but a range helps. It lets the developer suggest the right approach—for example, a simple landing page now versus a larger site in phases.

If budget is limited, prioritize:

  1. The core goal (e.g. lead generation)
  2. Essential pages and features
  3. Improvements that can come later

A simple brief template

You can copy this and fill it in:

  • Business:
  • Goal:
  • Audience:
  • Site type: (landing / business site / portfolio / e-commerce / other)
  • Pages:
  • Must-have features:
  • Nice-to-have features:
  • Content ready: (texts / images / logo — yes/no/partial)
  • References: (links to sites you like)
  • Timeline:
  • Budget range:
  • Domain/hosting: (have / need)

Final tip

A good brief is not about writing a long document. It is about making key decisions clear. Even a one-page brief can lead to a faster quote, fewer surprises, and a website that actually supports your goals.

If you are unsure about some points, say so. An experienced developer can help you refine the scope—but starting with these 10 answers puts you in a much stronger position.

Top comments (0)