Short answer: choose a web developer who can show you work similar to what you need, explains their process in plain English, gives you a written scope and price before starting, and makes sure you own your website, domain and content. The ten questions below help you check all of that in one conversation.
A website is a long-term asset, and the developer you choose shapes how fast it loads, how easily customers find you on Google, and how simple it is to update for years. Here is what to ask before you sign anything.
10 questions to ask a web developer
1. Can I see work similar to my project?
Look for live sites, not just screenshots. Open them on your phone, check how quickly they load and how easy they are to use. Similar does not have to mean the same industry, but it should mean similar size and features.
2. Who will actually design and build my site?
Some agencies sell the project and pass it to someone else. Knowing who does the work, and whether design and development happen in the same team, avoids a lot of lost detail between hand-offs.
3. What is your process, step by step?
A good answer covers discovery, wireframes or design, development, testing, launch and support. If the process is vague, the timeline and the result usually are too.
4. What exactly is included in the price?
Ask for a written scope: the pages, features, number of design revisions, content entry, hosting set-up and training. A clear scope protects both of you and makes quotes easy to compare.
5. Will I own the website, domain and content?
You should own your domain name, your content and your site’s files, with admin access in your own name. Avoid arrangements where leaving means losing your website.
6. How will the site perform on phones and in Google?
Most visitors arrive on a phone. Ask how the developer handles page speed, mobile layouts, page titles and descriptions, structured data and sitemaps. These foundations decide whether search engines can understand your site.
7. How do you handle security and backups?
Ask how the site is kept updated, where backups are stored and how quickly it can be restored if something goes wrong.
8. Can I update the content myself?
You should be able to change text, images and blog posts without calling a developer for every small edit. Ask for a short walkthrough at launch.
9. What happens after launch?
Find out what support is included, how changes are charged and how quickly they reply. A website improves over time, so ongoing support matters as much as the launch.
10. How will we know the website is working?
Agree what success means before you start: more enquiries, more bookings, better visibility for certain searches. Then make sure the site is set up so you can measure it, for example with Google Search Console.
Red flags to watch for
- No portfolio of live sites you can test yourself.
- No written scope, only a single price with no detail.
- The developer keeps ownership of your domain or hosting account.
- Promises of guaranteed first place on Google. Nobody can honestly guarantee rankings.
- No plan for updates, security or backups after launch.
Frequently asked questions
How long does it take to build a business website?
It depends on the size and features. A clear scope at the start, with agreed content deadlines, is the best way to get an accurate timeline.
Should my web developer also do the design?
Not always, but having design and development in the same hands means the design you approve is exactly what gets built, with no detail lost between separate teams.
Do I need a developer in London?
Not necessarily. Most projects run well by video call, email and shared designs. A local developer can help if you want to meet in person or need local search knowledge.
Work with me
I am Rahijan, a London-based UX/UI designer and web developer. I design and build fast, search-ready websites, and I handle both the design and the development, so nothing is lost in a hand-off.
Planning a new website or a redesign? Tell me about your project in three quick steps and I will reply within one working day.