Hiring a web developeriring a web developer often happens when you are already in a hurry. A website may be down, a previous provider may have disappeared, or a needed change may be overdue.
That first conversation matters. The questions you ask can reveal how the developer works, who controls your website, and what happens when something goes wrong.
Price and timeline are worth discussing, but they only tell part of the story. Here are questions that can help you understand the working relationship before you commit.
Ask how the work gets done
“Who will actually work on my website?”
You may speak with one person during the sales call, then discover someone else is doing the work. That arrangement can be perfectly reasonable, but you should know about it first.
A good answer identifies the people or roles involved and explains how you will communicate with them. If the developer uses subcontractors, ask who manages the work and who is responsible for the result.
You are not asking to inspect an organization chart. You are making sure you know who has access to your site and who can answer your questions.
“What will you need from me, and when?”
A website project often needs your content, images, business details, and feedback. Delays can happen when the developer is waiting for something you did not know you needed to provide.
A helpful answer explains what materials are needed, when they are due, and how approvals will work. They should also be willing to help clarify what you need to prepare.
For example, a service page may require a description of your work, contact details, and a photo. Knowing that early makes the project easier for everyone.
“What would you change about my current site, and why?”
This question reveals whether the developer has looked closely at your website. A useful answer points to a specific issue and explains how it affects visitors or your business.
Perhaps a contact form is hard to find, or important information is difficult to read on a phone. A thoughtful developer should explain the concern without making you feel foolish about the site you already have.
Be cautious if every answer is simply, “You need a complete rebuild.” Ask what can be improved, what should stay, and why.
Ask who controls the important things
“Who owns the website files, domain, and hosting account?”
Your domain is your web address. Hosting is the service where your website lives. The website files and content are separate pieces, too.
Ask whose name and account details appear on the domain registration and hosting account. Ideally, your business controls these accounts, while the developer receives appropriate access to do their work.
A clear answer should also explain how you can sign in, recover access, and see renewal notices. For more background, read Do YOU own your website? and Who owns your domain?.
“Could I move the site to another host or developer?”
You may stay with the same developer for years. Still, you should understand your options if your needs change or the relationship ends.
A reassuring answer describes what can be transferred, what files or access you would receive, and whether any software or services require separate licences. Some website platforms have limits, so ask about those before signing up.
The answer should not make leaving sound like a punishment. If you want to understand the process, see what moving your website to a new host involves.
“Can I talk to two current clients?”
References can help you learn how the developer communicates after the contract is signed. Ask for clients whose projects resemble yours, if possible.
A good developer should explain whether references are available and respect their clients’ privacy. If you speak with someone, ask whether the work matched expectations and how problems or extra costs were handled.
Client references are not the only way to judge a provider. But a real conversation can tell you more than a polished sales page.
Ask what support and pricing really mean
“How do I reach you if the site is down at 8 a.m. on a Saturday?”
This question is not a demand for round-the-clock service. It asks how support works and what the developer considers urgent.
A useful answer explains the available contact methods, normal business hours, and how urgent problems are handled. Ask what counts as an emergency. A broken payment or appointment form may matter more than a minor spacing issue.
The developer should not promise instant help unless they can explain what that commitment includes. Clear expectations now are much better than guessing during an outage.
“What is included in the monthly or hourly rate?”
A monthly fee might cover hosting, updates, backups, support, or a set amount of maintenance. An hourly rate might apply only when you request changes.
Ask what is included, what costs extra, and whether third-party services have separate charges. Request examples, such as adding a staff photo or fixing a contact form.
A good answer separates routine service from additional work. It should also explain how you will approve extra costs before the work begins.
“How do you bill for small jobs?”
A small edit can take less time than a full hour. Ask whether the developer bills by the minute, in partial hours, or with a minimum charge.
A clear response explains the billing unit and how work is recorded. If there is a minimum fee, ask when it applies.
You do not need to haggle over every small change. You do need to understand how the invoice is calculated. The older developer checklist also discusses billing practices.
“Are backups and software updates part of the arrangement?”
Ask what gets backed up, where copies are kept, and who can access them. Find out whether backups include both the website files and its database.
Also ask who handles updates and what happens if an update causes a problem. A good answer describes the routine and explains how restoration works.
A backup is more useful when it can be restored. Learn more in what website backups cover, and what they do not. For ongoing care, see a website maintenance routine you will actually keep.
Notice how they answer
A red flag is not always proof of bad intent. It is a reason to pause and ask for a clearer explanation.
Be cautious if a developer:
- Refuses to put the domain or hosting account in your business’s name.
- Will not provide a written scope or quote.
- Has no phone number or clear way to reach a real person.
- Pressures you to sign a long contract before answering basic questions.
- Gives vague answers about who will do the work.
- Says, “We’ll handle all that,” but will not explain what that means.
- Offers a price far below other proposals without explaining what is included.
A very low price may leave out important work, support, or maintenance. Compare what each proposal actually covers, not just the total.
Make the conversation easier to compare
Before calling, write a one-page brief. Include what your business does, what you want the website to accomplish, what is currently frustrating, and any important features.
Talk to two or three developers and ask each the same questions. That makes it easier to compare their answers, not just their personalities or prices.
Then ask for the scope and price in writing. The scope should explain what the developer will do, what you need to provide, and what costs extra. Keep the written agreement somewhere you can find it later.
You can also begin with one small paid job before handing over the whole site. For instance, ask the developer to review a form or make a specific update. Notice how they communicate, explain the work, and handle billing.
If you are replacing someone, do not cancel the old arrangement immediately. First, make sure the new person has the needed files and domain access. Confirm that a backup exists and has been tested. Otherwise, you could lose access before the transition is ready.
Choose someone whose answers you can rely on
The goal is not to find the cheapest developer or the fastest promise. It is to find someone whose answers you can hold them to later.
Good questions do not make you difficult. They help both sides understand the work and avoid preventable surprises. A developer who welcomes these questions is usually the right kind.



European Union General Data Protection Regulation Compliant