Choose a web developer by asking for live sites you can visit, confirming you will own the domain, hosting, and code, and getting a written scope that says what is included and what is not. Then ask who writes the content, how the site is maintained after launch, and what happens if you part ways.
We are a development studio, so read this with that in mind. We have also rebuilt sites that someone else built first, and seen which questions would have saved the owner trouble if they had been asked at the start.
One client came to us with a one page site and no copy of its source code. Nothing about that was a technical failure. It was a question nobody asked. The ten below take about half an hour to go through, and a developer worth hiring will be glad you asked them.
What should you ask a web developer before hiring?
Before hiring a web developer, ask ten questions covering five subjects: proof of live work, ownership of the domain, hosting, and code, the written scope, who writes the content, and what happens after launch. Each question below comes with what a good answer sounds like.
- Can I see sites you built that are live right now? A good answer is a list of addresses you can open on your phone, not screenshots. Ask what the developer did on each one.
- Whose name will the domain and hosting be in? A good answer is "yours". The developer should be a user on your accounts, not the owner of them.
- Will I get the source code? A good answer is yes, with a description of the form: a repository or a complete export.
- What exactly is included, and what is not? A good answer is written down and names page types, features, and rounds of revision. The "not included" list matters as much as the other one.
- Who writes the text and supplies the photos? A good answer is specific. Either you do, or they do and it is in the price. Vague answers here cause most delays.
- What will you build it on, and why that? A good answer starts from your needs: who edits the site, how many pages, what it must connect to. Be wary of one tool recommended for everything.
- What does the site need after launch, and who does it? A good answer lists tasks: updates, backups, monitoring. It also says what it costs if they do it and whether you could do it yourself.
- How will people find the site in search? A good answer talks about pages that answer real searches, page titles, speed, and structured data. A promise of a specific ranking is a bad answer.
- How do I ask for changes during the build and afterwards? A good answer describes one channel and a normal response time, and explains how extra requests are priced.
- If we stop working together, what do I walk away with? A good answer is "everything": accounts, code, content, and a short handover note.
How do you check a developer's past work?
Check a developer's past work by opening their live sites yourself. Load them on a phone, click through the menu, submit nothing but read the forms, and look for specifics: real photos, real addresses, verifiable details. A portfolio of images tells you about design. Live sites tell you about delivery.
Things you can verify in a few minutes without technical knowledge:
- Does every menu link lead to a finished page?
- Does the site load quickly on mobile data?
- Is the content specific to the business, or could it describe anyone?
- Does the business behind the site actually exist at that address?
Our own work is listed with live addresses on the work page. The One Stop Bail Bonds site, for example, is 271 pages with a jail finder covering all fifteen Arizona counties, and anyone can open it and try the finder. The Vortech site shows license numbers a visitor can look up. That is the kind of proof to ask any developer for.
What does a good answer about ownership sound like?
A good answer about ownership is short and unconditional: the domain is registered to you, the hosting account is yours, and you receive the code. A developer who needs to explain why holding your accounts is simpler for everyone is describing what is simpler for them.
There are honest reasons a developer might host your site in their own account, such as a shared platform they manage. In that case the good answer includes how you would leave: what gets exported, in what format, and how long it takes.
We explain the three parts and how to check each in who owns your website.
What are the warning signs when hiring a web developer?
The warning signs when hiring a web developer are guaranteed rankings, no live examples, a quote with no written scope, pressure to sign quickly, accounts kept in the developer's name, and a monthly fee with no list of what it covers. Any one is worth a follow-up question.
| What you hear | What it often means | What to ask next |
|---|---|---|
| "We guarantee page one" | Nobody controls search results | "Which searches, and what do you do if it does not happen?" |
| "We handle all the hosting for you" | The account may not be yours | "Can the account be in my name with you as a user?" |
| "It includes everything" | Scope is undefined | "Can you list what is not included?" |
| "We will sort out content later" | Content is not in the price | "Who writes each page, and by when?" |
| "It is a proprietary system" | The site cannot be moved | "What do I get if I leave?" |
Should you hire a freelancer, an agency, or a studio?
Hire based on the size of the job and how much continuity you need. A freelancer suits a small, well-defined site. An agency suits a business that wants marketing services bundled together. A small studio suits projects that need custom code and the same people from start to finish.
No category is better across the board. A good freelancer will outdo a careless agency on a small site and cost less. The ten questions apply equally to all three, and the answers matter more than the label.
Price follows scope more than it follows the type of firm. If you are comparing quotes, how much a small business website costs explains what moves the number.
What should you prepare before contacting a developer?
Prepare a short description of your business, the services you sell, the places you serve, any existing site and its logins, examples of sites you like, your deadline, and a budget range. A developer can give a useful answer from those seven items in one conversation.
You do not need a formal document. A few sentences on each point is enough. Knowing what you have also shortens the project, as we explain in how long it takes to build a website.
Frequently asked questions
Should I hire a local web developer?
Local helps if you want to meet in person or if the developer knows your market. It is not required. What matters more is whether they answer promptly, show live work, and understand the kind of business you run.
How many quotes should I get?
Two or three is enough to see the range. More than that and you spend your time in sales calls. Give each developer the same description so the quotes can be compared, and ask each for a written list of what is included.
Is the cheapest quote a bad sign?
Not by itself. It may reflect a smaller scope, a simpler platform, or content left to you. Ask what was left out. A low quote with a clear scope is fine. A low quote with no scope is a guess.
Do I need a written contract for a small website?
A written agreement protects both sides, even a short one. It should state the scope, the price, the payment schedule, and who owns the result. Contract terms are a legal question, so have your own attorney look at anything you are unsure of.
How do I know if a developer writes their own code?
Ask them to explain how one of their live sites was built and what they would do differently. Someone who built it can answer in detail.
If you want to put these questions to us, get in touch. We will answer all ten in writing.