What to prepare before hiring a web developer

The best website projects aren't always the biggest. They're the ones where the business owner knew what they wanted before the first meeting. A little preparation gets you a more accurate quote, a faster project, and a website that actually does its job.

Here's what to think about before you contact a web developer.

1. Know what the website is for

Start with one sentence: "The website should help us ___." For example:

• "...get more enquiries from companies looking for office cleaning."
• "...sell our products online without confirming every payment by hand."
• "...let patients book appointments without calling."

This one sentence shapes every decision that follows: which pages you need, what goes at the top of the homepage, and which features are worth paying for. It also lets you judge later whether the website is working.

2. Know who it's for

Describe your typical customer in a few lines. Are they homeowners in Nairobi, procurement officers at large companies, or tourists planning a trip from abroad? Do they mostly use phones? What do they need to know before they contact you?

A website for busy procurement officers looks and reads very differently from one for young shoppers on Instagram.

3. List the pages you think you need

You don't need a perfect list, but a rough one helps. Most small business sites need:

• Home: who you are and what you do, in one screen.
• Services or products: what you offer, ideally with prices or starting prices.
• About: why customers should trust you.
• Work or gallery: proof that you've done this before.
• Contact: how to reach you, where you are, and your hours.

Then add anything specific to your business, such as a booking page, a shop or a blog.

4. Gather your content

Content is the text, photos, logos and product details that go on the site, and it's the most common reason website projects get delayed.

Before you start, gather what you can:

• Your logo, in the best quality you have.
• Photos of your work, products, premises and team.
• A list of your services or products, with prices if you'll show them.
• Your contact details, opening hours and location.
• Any testimonials from happy customers, with their permission.

If you don't have it all, that's fine, but say so early. Your developer can include content writing and branding in the quote, or plan the project around when your content will be ready.

5. Collect examples you like (and don't like)

Find three to five websites you like, and note exactly what you like about each: the layout, the colours, how easy it is to find prices, how the photos look. Websites you dislike are just as useful.

These examples turn vague words like "modern" and "clean" into something a designer can actually work with.

6. Decide on the features you need now

Be clear on what the website has to do on day one, and what can wait. Common features include:

• A contact or enquiry form
• A WhatsApp chat button
• Online booking
• Online payments with M-Pesa or card (see how M-Pesa payments work on a website)
• A product catalogue or full online store
• A blog

Starting with what you need now keeps the first version affordable, and a well-built site can grow later.

7. Set a realistic budget and timeline

Have a budget range in mind, even a rough one. It helps your developer suggest what's achievable instead of quoting for something you can't afford. Our article on what a website costs in Kenya explains the main price factors, and the cost estimator gives you a range for your project in about two minutes.

For timing, a focused business website typically takes one to two weeks once content is ready, and an online store three to four weeks. If you have a launch date, an event or a deadline, mention it at the start.

8. Know who will make decisions

Decide who approves the design and content on your side. Projects slow down when feedback has to pass through several people who disagree. One decision-maker, with others giving input to them, keeps things moving.

Questions to ask any web developer

Before you hire anyone, ask:

1. Can I see websites you've built that are live today?
2. Will I get a written proposal with a fixed scope, price and timeline?
3. Who will own the website, the code and the domain name?
4. How will we communicate during the project, and how often?
5. What happens if something breaks after launch?
6. Will I be able to update the content myself?

Clear answers to these questions are a good sign. Vague ones are a warning.

Ready to start?

If you've worked through this list, you're better prepared than most. Tell us about your project and we'll come back with a clear recommendation, or see how we work from first conversation to launch.