To hire a freelance web developer without getting burned, do four things in order: write down what you need before you talk to anyone, check two or three of their live sites yourself, put the scope, price and ownership into a written agreement, and pay in stages tied to things you can see. Skip one of those four steps and you are relying on luck, however talented the developer is.
This guide walks through each step in plain words. You don't need to know how to code to follow any of it.
How do you hire a freelance web developer without getting burned?
You lower the risk by making the project clear before you hire, and by never paying for something you can't see or don't own.
Here is the order I'd follow if I were on your side of the table.
- 1
Prepare a one-page brief
Write your goal, the pages you need, your budget range and three websites you like. It takes an evening and it changes every quote you get.
- 2
Shortlist three developers
Ask people you trust, search for developers who have built your kind of site, and look at marketplaces last.
- 3
Check their live work
Open their past projects on your phone, test the speed, and ask what exactly they did on each one.
- 4
Have one real conversation
A 20 to 30 minute call. Listen for questions about your business, not only talk about their tools.
- 5
Agree it in writing
Scope, price, timeline, who owns the site, what counts as a change, and what happens after launch.
- 6
Pay in stages
A deposit to start, then payments when you approve the design and the working site. The last payment goes out when the site is live and the logins are yours.
A freelance web developer is one person who builds websites for clients directly, without an agency in between. That's the appeal: you talk to the person doing the work, and you usually pay less than an agency charges. It's also the risk. If that one person is disorganised, overbooked or dishonest, there's no account manager to step in. So your checks need to be a bit more careful than they would be with a larger firm.
What should you prepare before hiring a freelance developer?
Prepare six things: your goal, your page list, your content, your budget range, a few example sites, and a list of the accounts you already have. A developer can quote accurately only when they know what "done" looks like, and these six things tell them.
Here is what to prepare before hiring a freelance developer, in order of how much it helps.
1. The goal, in one sentence. "I want more enquiries from wedding couples." "I want people to order lunch online and pay by card." "I need a site my sales team can send to buyers." A developer who knows the goal will suggest different pages than one who only hears "I need a website". If you can't say the goal in one sentence yet, that's the first thing to work on.
2. The pages and features. List the pages you think you need (home, about, services, contact and so on) and anything the site must do: take payments, take bookings, show products, collect leads into a spreadsheet, show content in two languages. Mark each as "must have" or "nice to have". That split is what lets a developer fit the work to your budget.
3. Your content, or a plan for it. Text, photos, logo, prices, team details. Late content is a common reason a website misses its launch date. You don't need everything ready on day one, but decide who is writing it and by when. If you want the developer to arrange a copywriter or photographer, say so, because it changes the price.
4. A budget range. Many owners hide the budget because they fear the quote will rise to meet it. I understand the worry, but it tends to backfire. Without a number, one developer quotes a small template site and another quotes a custom build, and you can't compare them. Give a range and ask, "what can you do well inside this?" The answers tell you a lot about each developer.
5. Three websites you like, and why. Send links and a line on each: "I like how simple this menu is", "I like these product pages". Add one site you dislike as well. Ten minutes of examples saves days of design back-and-forth.
6. A list of what you already own. Your domain name (the address, like yourbusiness.com), hosting (the computer your site lives on), business email, Google Analytics, payment accounts. Write down where each one is registered and who has the password. If you don't know, find out now. It matters a lot later.
A BDC checklist of questions for website developers makes the same point from the other side: one of its ten questions is "What are my responsibilities as a client?", meaning the photos, logos and content you have to supply and who the developer's main contact will be.
If writing this down feels hard, my free Project Scope Generator turns a two-line idea into a list of pages and features ranked by priority. I've also written a longer guide on how to write a project scope for a website. Either gets you to a one-page brief that you can send to three developers and get three quotes for the same thing.
Send the same brief to everyone
If each developer gets a slightly different description, you can't compare the quotes. One page, same wording, same budget range, sent to all three.
How much does a freelance web developer cost?
A freelance web developer costs roughly $25 to $180 an hour depending on experience, and a small business website from a freelancer usually lands between $1,500 and $5,000 in the US or £1,500 and £3,000 in the UK. Rates in India are lower. The ranges are wide, so treat them as a way to spot a quote that is far too low or far too high.
These are published market figures, not my own prices. The India rows come from a rate calculator site that doesn't explain its method, so treat them as a rough guide.
| Where the developer is | Typical freelance hourly rate | Source |
|---|---|---|
| Any country, by experience | $25 to $45 for beginners, $50 to $90 mid-level, $100 to $180+ for senior developers | SoloHourly rate guide |
| United States | $60 to $150+ | SoloHourly rate guide |
| United Kingdom | £30 to £80 an hour, or £250 to £600 a day | Osdire UK rate guide |
| India, Indian clients | ₹500 to ₹2,500 for a developer with 3 to 5 years of experience | Freelance Rates India calculator |
| India, overseas clients | ₹1,500 to ₹4,000 for the same experience | Freelance Rates India calculator |
Most business owners buy a whole website for a fixed price instead of paying by the hour. Here is what published guides say a small site costs.
| Small business website (5 to 10 pages) | Freelancer | Agency | Source |
|---|---|---|---|
| United States | $1,500 to $5,000 | $5,000 to $15,000 | WPZOOM cost guide |
| United Kingdom (5-page brochure site) | £1,500 to £3,000 | £3,000 to £5,000 | Whito pricing research |
A brochure site is a simple site that describes your business and collects enquiries, with no online shop. Shops, booking systems and custom features cost more. The same Osdire guide puts UK e-commerce projects at £5,000 to £30,000 or more.
Four things move a quote up or down more than anything else:
- How many unique page designs there are. Twenty pages that share one layout cost far less than eight pages that each look different.
- What the site has to do. Payments, bookings, logins, product filters and links to other software (a CRM, an accounting tool) each add days.
- Who supplies design and content. A developer building from your finished design quotes less than one who has to design and write as well.
- How fast you need it. A rush job pushes other clients aside, and you pay for that.
One figure worth planning for: Whito's research suggests adding 30% to 50% to the quoted price for costs outside the quote, such as copywriting, photography, SEO setup, hosting and paid plugins. It doesn't show how that number was worked out, so read it as a rough warning. I'd still ask every developer, "what will I pay for in year one that isn't in this quote?"
A quote far below the market range isn't a bargain. It usually means a template with your logo dropped in, a beginner learning on your project, or a low starting price that grows through "extras". Any of those can be fine if you know that's what you're buying. The trouble starts when you think you're buying something else.
Where do you find a good freelance web developer?
The best source is a referral from a business owner whose website you like, followed by searching for developers who have already built your kind of site. Marketplaces work too, but they need more filtering.
| Where to look | Good for | Watch out for |
|---|---|---|
| Referrals from other business owners | You can see the finished site and ask how the project went | Your friend's needs may be different from yours |
| Google search for your exact need ("WooCommerce developer for restaurants") | Finding specialists who write about the work they do | Agencies posing as a single freelancer |
| The credit link in the footer of a site you admire | You already know you like the result | The developer may be booked up |
| Seeing real work history and shared contacts | Polished profiles with little work behind them | |
| Freelance marketplaces | Lots of choice at many price points, plus payment protection held by the platform | Very uneven quality, platform fees, and reviews that can be gamed |
Location matters less than it used to. I'm based in Gurugram, India, and I work with clients in India, the UK and the US. What matters more is overlap in working hours, clear written English (or whichever language you work in), and a way to pay each other that both sides trust. A developer two time zones away who replies within a day is easier to work with than one down the road who goes quiet for a week.
Shortlist three. One gives you nothing to compare, and six will eat a week of your time.
How do you check a freelance web developer portfolio?
Check a freelance web developer portfolio by opening the live websites yourself, on your phone, and asking what the developer personally did on each one. Screenshots prove nothing. A live site that loads fast and works on a phone proves quite a lot.
A portfolio is the collection of past work a developer shows to win new clients. Here is a 15-minute check anyone can do on a freelance web developer portfolio.
Open three projects on your phone. Many of your visitors will be on a phone. Does the menu work? Can you read the text without zooming? Do buttons do something when you tap them? Try the contact form or add a product to the basket.
Test the speed. Paste the address into Google PageSpeed Insights, a free Google tool. You don't need to understand every line. Look at one number, LCP, which is how long the main content takes to appear. Google's own guidance says it should happen within 2.5 seconds. If all three portfolio sites are slow, yours will probably be slow too.
Check the site is still live and still theirs. Old projects get redesigned by someone else. Ask, "is this still your build?" An honest developer will tell you which ones have changed since.
Ask what they did. This is the question that matters most. On many freelance web developer projects, one person did the design, another built it, and a third looked after it afterwards. "I built this from the client's Figma design" (Figma is a design tool) is a very different claim from "I designed and built this". Both are fine. You just need to know which one you're hiring.
Here is how that answer sounds on one of my own projects. Orilite is a website I built in 2023 for a BIS-certified AAC block and mortar brand. The design was the client's Figma design. My part was the build: custom PHP templates on Oxygen Builder, with Advanced Custom Fields for the product and marketing content. So if you asked me about it, the straight answer is "I built it, I did not design it".
Look for work like yours. A developer with ten beautiful portfolio sites and no online shop is a risky pick for your online shop. Look for the same type of problem: bookings, orders, lead forms, a product catalogue, a site in two currencies.
Read one project write-up. Good developers explain the problem, what they built and what happened next. If every project is a picture and a logo, you're learning about their taste and nothing about how they work.
Ask for one reference. A short call or email with one past client. Ask three things: did it finish on time, how were changes handled, and would you hire them again?
When you look at freelance web developer projects, the range matters less than the fit. I'd choose the developer with three projects just like mine over the one with thirty unrelated ones.
What if the developer can't show their past work?
Some good developers can't show everything, because they built it for an agency under a "white-label" deal, which means the agency puts its own name on the work. That's normal. In that case ask for a screen-share walkthrough, a reference from the agency, or a small paid test task. What isn't normal is having nothing at all to show and no one to vouch for them.
What questions should you ask a freelance web developer?
Ask about scope, ownership, changes, timeline and what happens after launch. The answers matter, and so does how easily they come. Someone who has done this many times won't need to think hard.
| Question to ask | What a good answer sounds like |
|---|---|
| What would you build first, and why? | A clear order of work tied to your goal, not a list of tools |
| What's not included in this price? | A specific list: content writing, stock photos, paid plugins, hosting |
| Who owns the site, the code and the design when we finish? | "You do, once the final payment clears, and it's in the agreement" |
| Whose name will the domain and hosting be in? | "Yours. I'll ask you to add me as a user" |
| What happens if I ask for a change halfway through? | A simple process: small tweaks are included, bigger ones are quoted first |
| What counts as a bug you fix for free? | A set period after launch, in writing |
| How many projects are you working on right now? | An honest number, and a start date they can keep |
| Will you do all the work yourself? | A straight answer about any partner or subcontractor, and who you'll talk to |
| How will I update the site myself? | A short handover or training session, plus notes or a video |
| What happens after launch? | A choice: a monthly care plan, pay-as-you-go, or a clean handover to someone else |
Several of these come from two lists I'd recommend reading in full: the BDC's top 10 questions for a website developer, which includes "How many other projects are you currently working on?" and "How much of the project will be outsourced?", and Twine's questions to ask before a build starts, which covers what is out of scope and how change requests are priced.
Notice the questions the developer asks you as well. Someone who asks about your customers, your current enquiries and what success looks like is thinking about your business. Someone who only asks "how many pages?" is thinking about the invoice.
What are the red flags when hiring a freelance web developer?
The biggest red flags are no live work, no written agreement, full payment upfront, and a developer who wants your domain and hosting in their own name. Any one of these is a reason to slow down. Two together is a reason to walk away.
| Red flag | Why it matters | What to do |
|---|---|---|
| Only screenshots, no live links | You can't test anything | Ask for live addresses, or a reference |
| Can't say what they did on a project | The work may be a team's, or someone else's | Ask, "which parts did you build?" |
| A quote within the hour, with no questions | They haven't understood the job, so the price will change | Pick the developer who asks questions first |
| 100% payment before any work | You have nothing to hold if the work stops | Offer a deposit and staged payments |
| "We don't need a contract" | Nothing defines done, changes or ownership | Insist on a short written agreement |
| Domain or hosting in their name | They control your address and your site | Register both yourself and add them as a user |
| Price far below every other quote | Template work, a beginner, or extras later | Ask exactly what's included |
| Promises "number one on Google" | Nobody controls Google's rankings | Ask what they'll actually do for search |
| Slow, vague replies before you've paid | Communication rarely gets better after the deposit | Treat the sales stage as a preview |
| No plan for after launch | Sites need updates and backups | Ask who looks after it and what that costs |
Two of these deserve a little more explanation.
The domain in their name. Your domain is registered to a "registrant", which is the person or company on record as holding it. ICANN, the body that oversees domain names, says the registrant takes sole responsibility for the registration and use of the domain name. If that registrant is your developer, the address your customers know is legally theirs to manage. I've written a separate guide on what to do if a developer has disappeared with your site, and almost every step in it would be unnecessary if the accounts had been in the owner's name from the start.
The instant quote. A fast reply is good. A fast price with no questions is a guess. When the guess turns out wrong, you either pay more or get less.
Related guide: Freelance web developer in Pune: rates and what to check
How should you pay a freelance web developer?
Pay in stages: a deposit to start, a payment when you approve the design, a payment when the working site is ready to review, and the last payment when it goes live and you hold the logins. Paying everything upfront removes the developer's reason to finish. Paying nothing until the end is unfair to them, and good developers will turn the job down.
A deposit is normal. A Contra guide to web design payment schedules says most designers ask for between 25% and 50% of the project cost upfront, with 50% deposits typical on projects under $5,000 and 25% to 33% on larger ones. IPSE, the UK body for the self-employed, gives freelancers the same advice in its example milestone plan: insist on a deposit and do not begin work without it. So a request for a deposit is a sign of someone who runs a proper business, not a warning.
The same Contra guide gives a typical four-stage split for a standard business website:
| Payment stage | Share of the price | What you should see before paying |
|---|---|---|
| Project kickoff | 25% to 50% | A signed agreement and a start date |
| Design approval | 20% to 30% | The design of the key pages, approved by you |
| Development complete | 20% to 30% | The working site on a private test address |
| Launch | 20% to 25% | The live site, plus every login and file handed over |
For a small job, two payments are enough: half to start and half at launch. For a large one, add stages so that no single payment is a big leap of faith for either side.
A few rules I'd stick to as a buyer:
- Tie each payment to something you can check. "Design approved" and "site working on the test link" are checkable. "50% complete" is an opinion.
- Review quickly. If you take three weeks to look at a design, the timeline slips and the developer's calendar fills with other work. Agree how long each review takes.
- Hold the last payment until handover. That means admin logins, the hosting and domain in your account, and a copy of the site files.
- Use a traceable method. A bank transfer or a card payment against a proper invoice. Avoid cash and avoid paying to a personal account in a different name from the one on the agreement.
- Get an invoice every time. It's your record of what was paid for.
If you hire through a marketplace, the platform usually holds your money and releases it at each stage. That protection is useful with someone you don't know, and it comes with platform fees, so check the current fee page before you agree a price.
Related guide: Freelance web designer vs web developer: who do you need?
What should the written agreement with a freelance web developer cover?
The agreement should cover what is being built, what it costs, when it's due, who owns it, how changes are handled and what happens after launch. Two pages in plain language is enough for most small sites. It doesn't need to be written by a lawyer to be useful, though for a large project it's worth having one read it.
Scope. The list of pages and features from your brief, plus what's excluded. "Up to 8 pages, contact form, blog, basic search setup. Not included: copywriting, logo design, paid plugin licences."
Price and payment stages. The total, the stages above, and what each stage is tied to.
Timeline. A start date, a launch date, and what you have to supply by when. If your content is late, the launch date moves. A fair agreement says so.
Ownership. This one surprises people. In the UK, the government's guidance on commissioned work says the first legal owner of copyright is the person or organisation that created the work, not the person who paid for it, unless a written agreement says otherwise. So paying for a website doesn't automatically make it yours. The rules differ from country to country, which is one more reason to write a single clear line into every agreement: on final payment, the site, its design and its code belong to you.
Accounts. Domain, hosting, email, analytics and payment accounts are opened in your name, with the developer added as a user.
Changes. What counts as a small tweak (included) and what counts as a new request (quoted separately, agreed in writing before work starts). This is where disputes tend to start. The owner thought something was obviously included. The developer thought it was obviously extra.
Bugs and support. How long after launch the developer fixes faults for free, and what ongoing care costs after that.
Ending early. If either side stops, you pay for work done up to that point and receive the files for it.
Is hourly or fixed price safer when you hire a freelance web developer?
Fixed price is safer for a website with a clear scope, and hourly is fairer for open-ended work like fixes, small updates and ongoing support. A fixed price puts the risk of underestimating on the developer. Hourly puts it on you.
If you go fixed, the scope has to be written down, or the price isn't really fixed. If you go hourly, ask for an estimate range before each task, a cap that needs your approval to pass, and a simple log of hours. Plenty of projects use both: a fixed price for the build, then hourly or a monthly plan afterwards.
Should you start with a small paid test project?
Yes, if the project is large or you found the developer cold. A small paid task, such as one landing page, a speed fix or a redesign of a single template, shows you how they communicate, whether they hit a date and how they handle feedback. That's more than any interview will show you.
Pay for it properly. Asking for free "sample work" drives away the experienced developers and leaves you with the ones who have time to spare. And keep the test real: pick something you need anyway, so the money isn't wasted whichever way it goes.
For a small brochure site this step is overkill. The staged payments already limit what you can lose.
How can I help you hire a freelance web developer with less risk?
I'm Mohit Goyal, a freelance senior web developer in Gurugram, India. In 4+ years I've shipped 100+ websites on WordPress, WooCommerce and Next.js, and I'd suggest you run every check in this post on me.
My case studies link to live sites you can open on your phone and test for speed. A few with different kinds of problem:
- The Ravens Ait venue website, a Thames island venue with 20+ event pages, Stripe bookings and HubSpot enquiry forms.
- Whitfield Service Station's online ordering, a WooCommerce store with a custom delivery radius plugin and automatic receipt printing.
- Nortek LED, a WooCommerce store built from the client's Figma design.
Ask me what I built on each one and what I didn't. Ravens Ait and Whitfield were delivered through a London agency, Aura Clips. Nortek was a direct client.
When a project needs design, a mobile app or Shopify, I bring in partners I trust and stay your single point of contact. Ask me who is doing which part. I also run monthly maintenance retainers, so "what happens after launch" has an answer.
I'm not the right fit for everything. If you need a ten-person team on site, or you want the cheapest possible template with no conversation, someone else will serve you better, and I'd rather say so on the first call.
What should you do next?
Spend one evening on the one-page brief: goal, pages, budget range, three example sites, and the list of accounts you own. Send the same page to three developers. Open their live work on your phone before you reply to any of them.
If you'd like me to be one of the three, send me your brief through the contact page. I'll start with questions about your goal, so that any scope and quote I send is for the right job and you can compare it against the others.
