What is the most important question to ask before hiring a developer?

Ask whether you fully own the code, domain, hosting, and all accounts, in writing. This protects you most, because owners who skip it sometimes cannot move or even edit their own site when the relationship ends. A professional says yes without hesitation. Be wary of anyone who builds on a closed platform you cannot leave or registers your domain under their own name.

How do I know if a freelancer or developer is legit?

Ask to see live sites you can visit, not just mockups, and for one or two past clients you can contact directly. A confident professional shares both. Also ask who actually does the work, since some firms sell with one person and build with another. Watch how they communicate with you now, because slow, vague replies before you pay rarely improve after.

Should I ask about what happens after the website launches?

Absolutely, it is one of the most overlooked questions. Ask what the handover includes (all credentials, documentation, a walkthrough), whether there is a warranty period for free bug fixes, and how ongoing maintenance is handled. Silence or vagueness here is a serious red flag, because the post-launch phase is where neglected projects fall apart.

How should I compare quotes from different developers?

Insist on an itemized breakdown of what is and is not included: revisions, content, testing, deployment, and post-launch support. One big number with no detail makes comparison impossible. Also confirm the pricing model and how scope changes are estimated and billed, so you are never surprised by an invoice. Sanity-check any quote against realistic market ranges.

Is it rude to ask who actually does the work?

Not at all, it is a fair and important question. With some firms, the impressive person who sells the project is not the one who builds it, and the work quietly goes to a junior or an outsourced team. There is nothing wrong with a team, but you deserve to know who is responsible for your project. A professional answers directly and without defensiveness.

10 Questions to Ask Before Hiring a Developer or Freelancer

The 10 questions to ask before hiring a developer or freelancer, with good vs bad answers, so you can spot a pro, avoid getting locked out of your own site, and budget right.

Hiring a web developer is one of those decisions where the cost of choosing wrong is far higher than the price difference between candidates. I have rescued enough projects from the previous developer to know exactly which questions separate a professional from someone who will leave you stranded. The good news is you do not need to be technical to ask them. You just need to know what a good answer sounds like versus a bad one. Below are the 10 questions I would ask before handing anyone money, why each one matters, and the red flags to listen for.

Why the right questions matter before hiring a developer

Most project disasters I have seen did not come from bad code on day one. They came from things nobody asked about up front: who owns the code, what happens after launch, how changes are handled, and whether the person quoting the work is the person doing it. A thirty-minute conversation with the right questions will tell you more than any portfolio. Think of this as due diligence, the same way you would vet anyone you are about to trust with a meaningful chunk of your budget.

If you are still deciding between an individual and a firm before you even get to these questions, my comparison of a freelancer vs an agency for your website is the right place to start. Once you have a shortlist, run them through the list below.

The 10 questions, with good vs bad answers

Here is the full checklist at a glance, then I will expand on each one.

#	Question	Good answer	Red flag
1	Do I own all the code and accounts?	Yes, fully, in writing	Vague, or platform locks you in
2	What tech stack will you use and why?	A clear, mainstream reason	Obscure tech only they can maintain
3	What is the realistic timeline?	Phased dates with milestones	"A few weeks" with no detail
4	What happens after launch?	Defined handover and support	Silence or "we'll see"
5	How is ongoing maintenance handled?	Clear retainer or hourly terms	No plan at all
6	How and how often will we communicate?	Set cadence and one point of contact	Unclear or slow to reply now
7	Can I see real work and references?	Live sites plus contactable clients	Only mockups, no references
8	Who actually does the work?	Names the real people	Won't say, or quietly outsources
9	How do you handle scope changes?	A written change process	"We'll figure it out"
10	How do you price, and what is included?	Itemized, clear inclusions	One number, no breakdown

1. Do I own all the code and accounts?

This is the question that protects you most, so ask it first. You should own the code, the domain, the hosting account, and every login. I have met business owners who could not move their site or even update their hours because the developer held everything hostage. A professional says yes without hesitation and puts it in the agreement. Watch for anyone who builds on a closed platform you cannot leave, or who registers your domain under their own name.

2. What tech stack will you use, and why?

You do not need to understand the answer technically, but you need a reason that makes sense and a stack that other developers can maintain. Mainstream, well-supported tools mean you are never trapped with one person. A bad sign is an obscure framework or a homegrown system that only the original developer understands, which quietly locks you in. If you want context on the platform debate itself, I cover it in custom website vs WordPress.

3. What is the realistic timeline?

A pro gives you phases and milestones, not a vague "a few weeks." They should be able to say when design is due, when you will see a working version, and when it goes live, plus what they need from you to hit those dates. Beware both extremes: a wildly short promise usually means corners will be cut, and "it's done when it's done" means no accountability.

4. What happens after launch?

Launch is the start of the relationship, not the end. Ask what handover looks like: do you get all the credentials, documentation, and a walkthrough? Is there a warranty period where bugs are fixed for free? Silence here is a serious red flag, because the post-launch phase is where neglected projects fall apart.

5. How is ongoing maintenance handled?

Every live site needs updates, backups, security, and small changes. A professional offers clear options, a monthly retainer, an hourly rate, or a documented handoff if you will maintain it yourself. "You won't need any" is simply not true, and I explain why in detail in my guide to website and automation maintenance.

6. How and how often will we communicate?

Communication problems sink more projects than technical ones. Ask for a cadence, a weekly update or a shared board, and one clear point of contact. The best predictor is how they communicate with you right now: if replies are already slow and vague before you have paid, that will not improve after.

7. Can I see real work and references?

Ask for live sites you can visit, not just polished mockups, and for one or two past clients you can actually contact. A confident professional shares both. If everything is under NDA, or they can only show design files but no shipped, working sites, dig deeper before committing.

8. Who actually does the work?

This one surprises people. With some firms, the impressive person who sells you the project is not the person who builds it, and the work quietly gets passed to a junior or an outsourced team. Ask directly who writes your code. There is nothing wrong with a team, but you deserve to know who is actually responsible for your project.

9. How do you handle scope changes?

Scope always shifts mid-project. The question is whether there is a calm, written process for it. A pro explains how a new request is estimated, approved, and billed before work starts, so you are never surprised by an invoice. "We'll just figure it out as we go" is how budgets quietly double.

10. How do you price, and what is included?

Whether it is fixed-price or hourly, you want to know exactly what is and is not included: revisions, content, testing, deployment, post-launch support. One big number with no breakdown makes it impossible to compare quotes or know what you are buying. For realistic ranges to sanity-check any quote against, see how much a business website costs.

How to read the answers as a whole

No single answer makes or breaks a candidate, but the pattern does. The professionals are calm, specific, and happy to put things in writing. They volunteer the inconvenient details, ownership, maintenance, what could go wrong, before you ask. The ones to avoid get vague exactly where it matters: ownership, who does the work, and what happens after launch. Trust how someone handles these questions, because that is a preview of how they will handle your project when something goes wrong, and on a real project, something always does.

If you want a second opinion on a quote or a candidate, or you would just rather work with someone who answers all ten of these without flinching, book a call and tell me about your project. I am happy to walk you through what good looks like, even if you do not end up hiring me. You can also reach me through the contact form.