Hiring guide
How to hire a web developer
Last reviewed , published by Gjethe
The short answer
To hire a web developer, first define what you need and your budget range, decide between a freelancer, agency or in-house hire, shortlist providers with relevant work, ask how they handle design, content, SEO and support, compare written quotes on scope rather than price, and make sure you will own the code, domain and accounts.
Hiring the wrong developer is expensive: missed deadlines, sites you can't edit, accounts you don't control and rebuilds within a year. Most of these problems can be avoided with a clear brief and a few good questions. This guide walks through the process step by step, whether you're hiring for a small business site or a larger web project.
The hiring process, step by step
- 01
Define the project
Goals, audience, pages or features, integrations, content and budget range.
- 02
Choose the type of provider
Freelancer, agency or in-house, depending on scope and how much you'll manage.
- 03
Shortlist
Look for relevant work, clear communication and a sensible process.
- 04
Compare proposals
Check scope, deliverables, exclusions, ownership and support.
- 05
Start with clarity
Agree milestones, communication and acceptance before work begins.
Freelancer, agency or in-house?
| Option | Strengths | Watch out for |
|---|---|---|
| Freelancer | Flexible and often affordable for small, clear projects | Single point of failure; you may manage design, content and SEO yourself |
| Agency or studio | Several skills, a process and continuity | Check who actually does the work and what's included |
| In-house developer | Full-time focus and deep product knowledge | Salary, recruitment and management overhead |
What to look for in a portfolio
- Live sites you can visit and test on a phone
- Projects similar in type or complexity to yours
- Fast loading pages
- Clear, accessible design
- Evidence of results, where clients allow sharing
- Consistent quality, not just one standout project
Questions to ask every candidate
| Question | Why it matters |
|---|---|
| Who will do the work? | Avoid surprises with subcontracting |
| What's included and excluded? | Content, SEO, hosting and licences vary widely |
| How do revisions work? | Prevents disputes about changes |
| Who owns the code, domain and accounts? | Protects you if you change provider |
| What happens after launch? | Support, maintenance and training |
| How will we communicate? | Sets expectations for updates and feedback |
Red flags
Be cautious if a provider can't explain their process, refuses to put scope in writing, keeps your domain or hosting in their own account, promises guaranteed rankings, or quotes far below everyone else without explaining why.
Very low quotes often mean templates with your logo added, missing essentials like SEO or accessibility, or a site you can't edit without paying the original developer for every change.
Make the brief do the work
The best way to get accurate, comparable quotes is a short written brief: what the site is for, who it serves, the pages and features you need, examples you like, integrations, content status and your budget range. It takes an hour to write and saves weeks of back-and-forth.
See our guide on how to write a project brief for a template.
How to run a fair comparison
Send the same brief to three or four providers and ask each for a written proposal with scope, deliverables, exclusions, milestones and price. Then compare like for like: does each proposal include content, SEO foundations, accessibility, hosting set-up, training and support?
Where proposals differ, ask why. Often the cheaper option leaves something out that you'd have to pay for later, or the more expensive option includes work you don't need.
What different quotes often include
| Item | Budget quote | Thorough quote |
|---|---|---|
| Design | Template with your logo | Custom design for your content |
| Content | You supply everything | Help with structure and copy |
| SEO | Not mentioned | Technical SEO and metadata included |
| Accessibility | Not mentioned | Designed to WCAG standards |
| Training | None | CMS training and documentation |
| Support | None | Defined support period after launch |
Working well once you've hired
Give the developer a single point of contact on your side, share content early, and give consolidated feedback at each milestone. Review work on real devices, not only on a desktop screen.
Most delays come from waiting for content and decisions, not from development itself.
After launch: support and ownership
Before signing, ask what happens after launch: how long support lasts, how bugs are handled, how much small changes cost and whether a maintenance plan is available. Also confirm that you'll receive admin access to everything.
A developer who plans the handover carefully is usually one who builds carefully too.
Technology choices in plain language
You don't need to be technical, but ask why a developer recommends a particular platform. Good answers connect the choice to your needs: who will edit the site, how much content you publish, which integrations you need and how fast it must be.
Be cautious if every client of a provider gets exactly the same platform regardless of their needs.
Frequently asked questions
Should I hire a freelancer or an agency?
A freelancer can suit small, clearly defined projects. An agency suits projects needing design, development, SEO and ongoing support together. See agency vs freelancer for a deeper comparison.
How do I compare quotes?
Compare scope line by line: pages or templates, content, integrations, revisions, SEO, support and ownership. Totals alone are misleading.
Should I pay upfront?
Milestone payments are common, for example a deposit and a final payment on delivery. Avoid paying everything before work starts.
Do I need a contract?
Yes. It should cover scope, payments, ownership, confidentiality and what happens if either side ends the project.
Can I hire a remote developer?
Yes. Remote work is common and effective with clear communication and overlapping working hours.
What should I own at the end?
Your domain, hosting account, analytics, code or CMS access and all design files.
How do I check references?
Ask for client contacts on similar projects and ask them about communication, quality and support after launch.
What if the developer disappears?
If you own your accounts and code, another developer can take over. That's why ownership matters from day one.
How many providers should I contact?
Three or four is usually enough to compare approaches and prices without spending weeks on evaluation.
Should I hire locally?
Not necessarily. Remote providers can be excellent; communication, overlapping hours and clear contracts matter more than location.
What if I don't like the design?
Revision rounds exist for this. Clear references at the start reduce the risk of a design that misses the mark.
Should the developer also host the site?
They can manage hosting for you, but the hosting account should be in your name.
Is a cheaper developer always riskier?
Not always, but very low prices often mean missing scope. Compare what's included before deciding.
Can I see work in progress?
You should. Ask for a staging link where you can review the site as it's built.
Related services
Website Development
Custom business websites on Next.js, React or WordPress.
Web Applications & SaaS
Portals, dashboards and subscription products.
Landing Pages
Single-purpose pages for ads, launches and lead capture.
Website Redesign
Rebuild an outdated site without losing traffic.
Website Maintenance & Support
Updates, backups, monitoring and fixes every month.
Keep reading
Talk it through with us.
Tell us what you need. You get an honest assessment, a clear plan and a written quote. The first consultation is always free.
- What happens next
- 1You tell us what you need
- 2We aim to reply within 24 hours with questions
- 3You get a written quote for your project