How to hire a web developer: questions to ask before you sign

You run a business and you are about to hire a web developer. You fear a contract that leaves you without the code, the logins or a finished site. To hire a web developer safely, write a short brief and check work you can open.

Quick answer: 6 steps

1. Write a one-page brief: the goal, the pages or features, the deadline and who updates the site later.
2. Choose the type of hire: a freelancer, an agency or an in-house developer.
3. Send the same brief to two or three candidates, so the answers are comparable.
4. Check work you can open: live sites, code, or a small paid test.
5. Ask the 10 questions below and get the answers in writing.
6. Sign only when the proposal names the scope, milestones, ownership and handover.

Write the brief first

I am on the receiving end of these briefs. I have worked in web development since 2013 and run my own practice since 2015. A clear brief is the fastest way to get quotes you can compare.

Put these items in the brief:

• The goal of the site and who will use it.
• The pages or features you must have at launch, and the ones that can wait.
• Who writes the content, and when it will be ready.
• Other systems the site must connect to, such as payments, a CRM or email.
• The deadline, and any date that cannot move.
• Who will update and maintain the site after launch.
• The accounts you already have, such as the domain and hosting, and whose name they are in.

Freelancer, agency or in-house

Each option fits a different situation. I am one independent developer, so read this table with that in mind.

Option	Fits when	Watch for
Freelancer	One clear project, and you want to talk to the person who writes the code	One person: ask who covers holidays or illness
Agency	You need design, content and development at the same time	Ask who writes the code, and how many people handle your project
In-house	You have continuous product work for years	Hiring time, salary and someone to manage the work

Where to find developers

Start with referrals from businesses you know. Then look at developer portfolio sites, agency case studies and freelance marketplaces. Wherever you find a candidate, send the same brief and use the same checks.

How to check skills

• Open live sites the candidate built. Use them on your phone and on a laptop.
• Ask for a code sample or a walkthrough of a repository, if someone on your side can read code.
• For a larger project, pay for a small test task with a clear output.
• Ask for one reference you can call.

For a Next.js project, see the screening checklist in hire a Next.js developer: what good looks like in 2026.

10 questions to ask before you sign

These questions cover scope, ownership and handover. Ask for the answers in writing, in the proposal or the contract.

#	Question	A good answer names
1	What is in the scope, and what is out of scope?	A list of pages or features, and a list of exclusions
2	What happens if I ask for something new during the project?	A change request with its own price and date
3	How many rounds of changes does each milestone include?	A number per milestone
4	Who owns the code, the design files and the content after I pay?	You, after each paid milestone or at final payment
5	Are the domain, hosting and other accounts in my name?	Yes, or a date when they move to you
6	Which paid themes, plugins or services does the site need?	Each item, its cost owner and whose name the licence is in
7	What do I receive at the end?	The code repository, all logins and short documentation
8	Who can update the site after launch, and how?	Your team, with a short guide or training
9	What support is included after launch, and for how long?	A period, what it covers and what it does not
10	How do we communicate, and how fast do you reply?	One channel and a reply time

Read the proposal and the milestones

A proposal should arrive before any code. I send a written plan with milestones and a quote before I write code. Use that as your test for any developer.

Check each milestone for three things:

• A result you can see, such as a page design or a working form.
• A date.
• A payment tied to that result.

The proposal should also list what is not included. For how fixed-price, hourly and retainer models compare, read what it costs to hire a Next.js developer.

Contract basics

I am not a lawyer. For a large contract, ask a lawyer to read it. These are the points to look for:

• Ownership: see question 4.
• Confidentiality: an NDA, if the project is sensitive. I can sign one for sensitive projects.
• Payment: amounts tied to milestones, not to dates alone.
• Stopping: what you receive if either side ends the project early.
• Bugs after launch: how long the developer fixes defects at no extra cost.

Red flags

• There is no written scope, only a call.
• You get a price before the developer has read your brief.
• The developer will not put the domain, hosting or code in your name.
• A large payment comes first, with no milestone behind it.
• The candidate cannot show work you can open.
• The candidate agrees to everything and asks no questions.

Questions about hiring a web developer

How much does it cost to hire a web developer?

The cost depends on the scope, the type of hire and the pricing model you agree on. A quote is only useful when it rests on a written brief, so compare quotes on one brief. This post gives no rates, but the cost post above covers pricing models and what changes a quote.

Should I hire a freelancer or an agency?

Hire a freelancer when you have one clear project and want to talk to the person who writes the code. Hire an agency when you need design, content and development at the same time from one team. In both cases, ask who writes the code, then compare the written answers to the same 10 questions.

What should I send a developer first?

Send a one-page brief with the goal, the must-have pages or features, the deadline and the site owner after launch. Add links to sites you like and a list of the accounts you already own, such as the domain. A good developer replies with questions about the brief before giving a price.

What to do next

If you have no brief yet, write one with the list above before you contact anyone. If you have quotes already, ask each developer the 10 questions and compare the written answers. If an answer on ownership or handover is vague, ask again before you pay a deposit. Then sign the proposal that answers all 10 clearly.

If you want me to read your brief, see my web development services or send it through the contact page. I reply within 24 hours and tell you plainly if I am the right fit.