What to prepare before hiring a web developer

A practical checklist of what to gather before you contact a web developer, so you get an accurate quote, a smoother project and a site that fits your business.

Why preparation matters

The quality of a quote depends on what the developer knows. A vague request gets a vague estimate, and vague estimates are where surprise costs come from. A little preparation gives you a more accurate price, a faster project and a site that fits your business.

You don’t need everything finished. You just need to know what you have and what you want.

1. Know what the website is for

Write one or two sentences about what the site should achieve. For example: get more enquiries for kitchen fitting, sell personalised gifts online, or let members renew and register for events.

This is the most useful thing you can give a developer. Every decision about design, pages and features follows from it.

2. Describe your customers

Who are they, what do they need to know before they buy, and what questions do they usually ask you? The answers shape the pages, the wording and the order things appear in.

3. List the pages you think you need

A rough list is enough, such as home, services, a page for each service, work examples, about and contact. A developer can suggest changes, but your list shows the size of the project.

4. Note any features

Features change the price more than anything else, so mention them early:

  • Contact or quote forms
  • Booking or appointments
  • An online shop or payments
  • Member logins or customer accounts
  • A blog or news section
  • Integrations with tools you already use

5. Gather your content

Check what you already have: text for each page, photos of your work, your team or premises, a logo, brand colours and any testimonials you have permission to use.

If some of it isn’t ready, say so. It is better to agree up front who writes or sources it than to discover halfway through that it is missing.

6. Collect a few examples

Find two or three websites you like, and note why: the layout, the colours, how easy it is to find things, how it feels on a phone. Examples of sites you don’t like are useful too.

7. Decide on budget and timing

Think about what you can spend, and when you need the site to be live. If there is a fixed date, such as a launch or event, say so at the start.

8. Check the practical details

  • Do you already own a domain name, and do you have the login?
  • Is there an existing website, and who has access to it?
  • Who will update the site after launch?
  • Who makes the final decisions on your side?

What to expect back

A good developer should reply with questions, then a written scope that lists the pages, features, timeline and price, what you need to supply, and what happens after launch. Compare quotes by what they include, not just the total.

How Crashielab can help

Crashielab works by email, so you can send this information whenever it suits you, with no calls to arrange. Every project starts with a free email conversation and a written scope, whether it is a full website, a landing page or a web app.

Questions

Do I need my content ready before I contact a developer?
No, but it helps to know what is ready and what isn’t. A developer can plan around missing content once they know about it.
Should I set a budget before asking for a quote?
It helps. Even a rough range lets a developer suggest what is realistic and what to leave for later.
What should a web developer’s quote include?
A written scope listing the pages, features, timeline and price, plus what you need to supply and what happens after launch.

Related services

  • Small business websites: A complete, fast website for your small business, designed around your customers and easy for you to update. Quoted per project after a free email chat.
  • Landing page design: One focused, fast landing page to launch a product, event or idea, designed to turn visitors into enquiries. Usually ready in about a week.
  • Custom web app development: Custom web apps for small businesses and growing teams, from member areas and booking tools to dashboards, designed and built by one developer.

Have a project in mind?Start a project