Skip to content
Web Design

What to Prepare Before You Hire a Web Developer

Goals, examples, content and a budget range. The short list that gets you better quotes, fewer surprises and a faster project.

by 2 min read
A written strategy plan laid out on an office desk
Photo by Walls.io on Pexels.

01 / Why preparation matters

Vague briefs get vague quotes

Send three developers a one-line message saying you need a website and you will get three prices that differ by a factor of ten. None of them is wrong. Each one is guessing at a different project.

Half an hour of preparation turns those guesses into comparable quotes, and it is the half hour that most shortens the project afterwards.

02 / The goal

Write down what the site has to achieve

Not “look modern”. Something you could measure: more quote requests, fewer phone calls asking the same questions, online bookings instead of email back-and-forth, a place to send investors. One clear goal shapes every decision that follows, from the homepage layout to which pages exist at all.

03 / Examples

Three sites you like, and why

Find two or three websites, ideally outside your industry, and write one sentence on what you like about each. “Easy to find prices” is more useful than “clean design”. Add one site you dislike too. It tells a developer as much as the ones you like.

04 / Content

Know what you already have

  • Logo files, ideally as SVG or a large PNG.
  • Brand colours and fonts, if they exist.
  • Photos of your team, work or premises.
  • Existing copy you want to keep, and which pages need new words.
  • Testimonials, case studies, certifications and awards.

If you need help with copy or photography, say so up front. It changes the quote and the timeline.

05 / Features

List what it must do, not how

Booking, a shop, a members area, multiple languages, a CRM connection. Write the need in plain words and let the developer suggest the tool. “Customers need to pay a deposit when they book” leads to a better answer than “we need plugin X”.

06 / Budget

Share a range, even a rough one

Many clients hold back their budget, hoping for a lower price. It usually backfires. Without a range, a developer either designs the ideal version you cannot afford or the cheapest version you will outgrow. A range lets them tell you what is realistic, and what to leave for later.

07 / Ownership

Ask who will own what

Before you sign, confirm that the domain, hosting account and website files will be in your name. Ask how updates and backups work after launch. A good developer will be happy to answer. One who is vague here is telling you something.

Next step

Have most of this ready?

Share what you have, even if it is unfinished, and we will fill in the gaps with you. Send us your brief.