How to hire a web developer, in short: write a brief, shortlist three people or studios whose live work you have checked, and ask each the same twelve questions about ownership, process, cost and support. Compare the answers, not just the prices. A good developer answers clearly and in writing; vague answers about who owns the site or what happens after launch are the clearest warning you will get.
This guide gives the twelve questions, what a good answer sounds like, and our own answer to each, so you can see what we mean.
How to hire a web developer: start with a one-page brief
Write down:
- What the site is for and who it is for
- The pages you need and the features (forms, bookings, payments, a blog)
- Who will write the content
- Your budget range and your launch date
- Two or three sites you like, and why
Send the same brief to everyone. It makes the answers comparable. Our website RFP template is a fuller version if the project is large.
Ownership and accounts
1. Who owns the code, design and content when we finish?
A good answer: you do, once the invoice is paid, including the design files.
Ours: you own the code, the design files and the content after final payment.
2. Whose name are the hosting and domain registered in?
A good answer: yours. The developer can have access, but the accounts belong to you.
Ours: yours. We help you set them up and work with access you give us.
3. What will I need to run the site without you?
A good answer: the logins, a short guide to editing, and where the code lives.
Ours: admin logins, a short editing guide, and a copy of the code.
Process
4. How will I see progress?
A good answer: a design to approve before building starts, then a staging site you can click through. Our post on the web design process shows where each approval usually falls.
Ours: designs first, then a private staging link that updates as we build.
5. How many rounds of changes are included?
A good answer: a specific number, and what counts as a change versus new work.
Ours: we agree the rounds in the proposal. New pages or features outside the scope are quoted before we start them.
6. How do you test the site before launch?
A good answer: real phones and the main browsers, including Safari; forms and payments tested end to end; speed and accessibility checked.
Ours: Chrome, Safari and Firefox on desktop and phone, every form and checkout tested, and a Lighthouse check for speed, accessibility and SEO.
7. Who will I actually talk to?
A good answer: a named person who knows the project, with a stated response time.
Ours: the people building your site, by email and calls at times that suit your time zone.
Cost
8. What is included in the price, and what isn’t?
A good answer: a written list. Hosting, domain, paid plugins, copywriting and photography are the usual exclusions.
Ours: listed in the proposal. Hosting, the domain and paid apps are paid to their providers. Our ranges are on the pricing page.
9. How do you charge for changes after launch?
A good answer: a clear hourly rate, a fixed price per change, or a monthly plan.
Ours: small changes through website management at $50 to $150 a month, or a quote per change.
After launch
10. What happens if something breaks in the first month?
A good answer: bugs caused by the build are fixed free for a stated period.
Ours: we fix problems caused by our work after launch at no charge. The period is stated in the proposal.
11. Who keeps the site updated and secure?
A good answer: a clear plan: you, them on a monthly plan, or nobody needed because the platform needs little upkeep.
Ours: it depends on the platform. WordPress needs regular updates; a static Astro site needs very few. We say which in the proposal.
12. Can I see live sites you built, and talk to a past client?
A good answer: yes, live addresses you can open on your phone.
Ours: yes. Start with our own site and this blog, both built by us, and ask us for live client sites when we talk.
Red flags
- The developer registers the domain or hosting in their own name
- No written scope or a single total with no breakdown
- Pressure to sign quickly or pay most of the price up front
- No live work you can check, only screenshots
- They can’t explain what they will do in plain words
- “SEO guaranteed first page” or any guaranteed ranking
- Ownership of the code stays with them
How the answers differ by type of hire
Freelancer. Often one person who designs and builds, or builds only. Ask question 7 carefully: who covers when they are ill or busy? Ask about design if you don’t have one.
Studio or agency. Usually a fixed price for a defined scope. Ask who does the work, since some agencies pass it on to others.
In-house hire. Questions 1 to 3 don’t apply in the same way, but questions about testing and maintenance do. Budget well above the salary; see what it costs to hire a web developer.
Next step
Send your brief to three developers, ask all twelve questions, and compare the written answers side by side. If you’d like us to be one of the three, send us your brief and we’ll answer every question above for your project. Our hire a website developer page explains how we work with clients abroad.