Hiring a web development consultant is a different job from buying a website package from an agency. With a package, you pick a tier and you know what you get.
With web development consulting, you are paying for someone's judgment and their hands-on work, and both are hard to see from the outside. Two consultants can quote the same price and leave you with very different websites a year later.
That is why the questions you ask before you hire matter so much. Many of the problems that come from a bad hire could have been caught in the first meeting.
The questions below are the ones that separate a good hire from a bad one. For each one, I will explain why it matters, what a good answer sounds like, and what should make you nervous.
Before you ask anything: know what you need
The best web development questions come after you have done a little homework on your own side. A consultant can only give you a clear answer if you give them a clear picture. Before your first call, write down a few things:
- What the website needs to do. Bring in phone calls? Take bookings? Sell products? Answer the same questions your staff answers all day?
- Who it is for. Homeowners in your town, other businesses, people across the country?
- What you have now. Your current site address (if you have one), where it is hosted, and who has the logins.
- Your budget range and your deadline. You do not have to share every number, but you should know them.
- A few websites you like, and one or two you do not like, with a short note on why.
This takes an hour and it saves you a lot of money.
When you are choosing a developer, the one who asks you follow-up questions about this list is usually the one who is thinking about your business as a whole.
If you are still deciding between building it yourself and hiring someone, our guide on Wix and Squarespace vs. hiring a professional walks through that choice first.
"Can you show me code you have written, not just finished sites?"
A finished site tells you what it looks like. It does not tell you how it was built.
Two websites can look the same in a screenshot while one is clean and easy to update and the other is a tangle that breaks every time someone touches it.
A consultant who is confident in their work will happily show you real code, or at least walk you through their approach in specific, technical terms.
You do not need to read code yourself to learn a lot from this conversation. Listen for how they talk about it.
What a good answer sounds like
A good consultant can explain, in plain words, how they organize a project and why.
They might show you a project on a code hosting site like GitHub, or share their screen and walk through how a page is put together. They can tell you what tools they use and what they avoid.
They can explain how another developer would pick up the project later if they were not around. That last part is important. You want a website that someone else can maintain, so you are never stuck with one person forever.
Red flags to watch for
- They only send you links to finished sites and change the subject when you ask how they were built.
- Every answer is marketing talk: "cutting edge", "best in class", "state of the art", with nothing specific behind it.
- They cannot name the tools or platform they would use for your site.
- They say nobody else could ever work on their code. That means you would be locked in with them.
If you want a second opinion on what you hear, it helps to know the basic choices. Our guide on WordPress vs. a custom-coded website explains the most common one in plain language, and custom web design vs. templates covers the other.
"What happens if I need changes after launch?"
Get this in writing before you start, not after. Almost every website needs changes after it goes live.
You will add a service, change your hours, swap in new photos, or realize a page is confusing once real customers start using it. None of that is unusual.
What causes fights is when nobody agreed ahead of time how those changes would be handled.
Ask these follow-up questions:
- Is a certain number of revision rounds included before launch? What counts as one round?
- Is there a period after launch where small fixes are included, like 30 days?
- What is the hourly rate for anything beyond that?
- Is there a monthly maintenance plan, and what exactly does it cover?
- How fast do they usually turn around a small change, like updating a phone number?
A consultant who cannot answer this clearly up front will not answer it clearly later either. Nobody can promise that every change is free forever and still run a business.
What you need is an answer that is clear, specific, and written down, so you both know where you stand.
An example of how this goes wrong
Say a landscaper in Berne hires a consultant for a new site. The quote says "website design, $2,500". It says nothing about changes.
Two weeks after launch, the owner asks to add a new page for snow removal. The consultant sends a bill for four more hours. The owner thought that was included.
The consultant thought it was obviously extra. Both of them feel cheated, and neither is really wrong, because nothing was written down. One paragraph in the agreement would have saved that relationship.
Our website maintenance services page shows the kind of ongoing care you should expect to see spelled out.
"How do you handle site speed and Core Web Vitals?"
This is a real, specific technical question, and the answer tells you a lot. Speed is one of the first things a visitor feels.
A slow page loses people before they read a word about your business, and Google measures how real visitors experience your pages as part of how it ranks websites.
Google's Core Web Vitals are three numbers that measure that experience. According to Google's own guidance, a good page:
- Shows its main content (Largest Contentful Paint, or LCP) within 2.5 seconds.
- Reacts to a tap or click (Interaction to Next Paint, or INP) in 200 milliseconds or less.
- Keeps its layout steady while it loads (Cumulative Layout Shift, or CLS), with a score of 0.1 or less.
A consultant who mentions actual practices, like image optimization, minimizing JavaScript, and server-side rendering, knows what they are doing. A consultant who just says "it'll be fast" without specifics may not have thought about it at all.
How to check their answer yourself
You do not have to take their word for it. Ask for links to two or three sites they built recently. Then open Google's free PageSpeed Insights tool, paste in each address, and look at the mobile results.
If their own recent work fails Core Web Vitals, yours probably will too. It takes five minutes and it is one of the most useful checks you can do when you hire a web developer.
Also ask how they handle images. Photos straight from a phone are usually much bigger than a web page needs.
A careful developer resizes and compresses every image, and sets its width and height so the page does not jump around while it loads.
Our guide on what makes a website fast explains each of these in more detail, and what is mobile-first web design covers why phone performance should be tested first.
"Who owns the domain, hosting account, and code when we are done?"
This should always be you, fully, with no exceptions. Some consultants set up hosting or domains under their own account "to make it easier", which can leave you locked out of your own website later if the relationship ends badly.
Insist on ownership in your name from day one.
This is the question I care about most on this list, because the damage is so hard to undo. Ownership covers three separate things, and you should ask about each one.
The domain name
Your domain is your address online. It should be registered in your business's name, with your email address on the account.
ICANN, the group that oversees domain names, says domain holders must provide accurate registration information and keep their registrar account data current. You cannot do that if the account belongs to someone else.
ICANN's rules also say domain holders must be able to transfer their domain between registrars. That right is much easier to use when the account is already yours.
You can check your current domain with ICANN's free Lookup tool at lookup.icann.org, which lets you look up the current registration data for a domain name.
Some details may be hidden for privacy, so the best check is simple: can you log in to the registrar account yourself?
The hosting account
Hosting is where your website lives. The account should be in your name, or at the very least you should have full admin access and the right to move the site whenever you want.
Ask what happens to your site if you stop paying the consultant. If the answer is "it goes offline and you start over", that is a problem.
The code and content
This one surprises a lot of people. Under U.S. copyright law, copyright in a work belongs at first to the person who created it.
The U.S. Copyright Office explains that an independent contractor stays the author of the work they create, and that ownership can only move to you through a signed, written agreement.
So paying for a website does not, on its own, mean you own the code. Your agreement should say, in writing, that the code, design, and content made for you become yours when the work is paid for.
(This is general information, not legal advice. If a lot of money is involved, have a lawyer read the contract.)
Also ask for a list of every login when the project ends: domain, hosting, website admin, analytics, and any paid plugins or tools. Keep them somewhere safe.
"What is your process if something breaks after launch?"
Sites break. Servers go down. A plugin update conflicts with something. Ask what happens when this happens: response time, who you contact, whether it costs extra. A consultant with a real answer has been through this before and has a real plan.
What a solid plan includes
Listen for specifics like these:
- Backups. How often is the site backed up, where are the backups kept, and have they ever actually restored one?
- Updates. Who updates the software and plugins, and how do they test that an update did not break anything?
- Monitoring. Will they know if the site goes down, or will they find out when you call them?
- Contact. Is there an email, a phone number, or a ticket system? What hours?
- Cost. Is emergency help part of a maintenance plan, or billed by the hour?
If the answer is "just email me if anything happens", ask how long a reply usually takes. A one-person shop can be a great fit. Plenty of excellent developers work alone.
You just want to know what happens if that one person is sick, busy, or on vacation the day your contact form stops working.
More web development questions worth asking
The five questions above are the big ones. These shorter questions fill in the rest of the picture, and a good consultant will answer them without any trouble:
- How do you set up the site for search engines from the start? Page titles, descriptions, headings, a sitemap, and clean page addresses should all be part of the build. Our SEO services page lists what that groundwork covers.
- If my business serves a local area, how will the site help me show up in local searches? (See our local SEO services for what that involves.)
- How do you make sure people with disabilities can use the site? Text contrast, image descriptions, and labeled form fields are basics. Our guide on website accessibility for small businesses explains what to look for.
- Will the site be secure, with an SSL certificate so browsers do not warn visitors?
- How long will the project take, and what do you need from me to keep it on schedule? Our guide to a website development timeline shows what a normal schedule looks like.
- Can I talk to one or two past clients?
- Who will actually do the work? You, or someone you pass it to?
Pay attention to how they answer, too. Do they explain things in words you understand? Do they ask about your business, or only talk about themselves? You will be working with this person for weeks, maybe years. Being able to talk easily matters.
How to compare quotes from different consultants
When you get two or three quotes, it is tempting to just pick the lowest number. I understand that. Nobody wants to overpay, especially a small business watching every dollar. The cheapest quote often leaves out the things that cost you later.
Put the quotes side by side and check whether each one covers the same things:
- The number of pages, and what goes on each one.
- Who writes the content and supplies the photos.
- Mobile design and speed testing.
- Basic SEO setup.
- Revision rounds before launch.
- Fixes and support after launch, and for how long.
- Hosting cost per month, and who owns the account.
- Ownership of the domain, hosting, and code, in writing.
A quote that looks cheap because it leaves out half this list is not really cheaper.
Our guide on how much a small business website costs in 2026 breaks down what different price levels usually include, and affordable web design without overpaying covers how to keep costs down without cutting the wrong corners.
The high cost of cheap SEO explains the same trap on the search side.
Common mistakes when hiring a web developer
These are some of the most common mistakes business owners make when hiring a developer:
- Choosing on price alone, then paying again a year later to fix or rebuild the site.
- Starting work on a handshake, with no written scope, no revision terms, and nothing about ownership.
- Letting the developer register the domain "for convenience".
- Never asking for logins, then losing access when the developer moves on.
- Skipping the speed check on the consultant's past work.
- Handing over nothing, then being unhappy with generic content. A developer can only show your business well if you give them real details, real photos, and your best reviews.
- Waiting until launch day to look at the site on a phone.
Every one of these is easy to avoid if you know about it ahead of time. Our article on how to choose a web design company covers more of the warning signs.
A quick checklist for your first meeting
Print this out or keep it open on your phone during the call:
- Ask to see real code or a walk-through of how they build a site.
- Get the terms for changes and revisions in writing.
- Ask how they handle speed and Core Web Vitals, then test two of their sites in PageSpeed Insights.
- Confirm that the domain, hosting, and code will be in your name, with a written agreement for the code.
- Ask what happens when something breaks, including backups, response time, and cost.
- Ask about SEO setup, accessibility, and security.
- Ask for one or two past clients you can talk to.
- Compare quotes item by item, not by the total.
If a consultant answers all of this clearly, with specifics, you have probably found a good one. If they get annoyed at the questions, that tells you something too.
The bottom line
A good web development consultant answers all of these clearly, with specifics, not vague reassurance. Good web development consulting should leave you with a fast website you fully own, clear terms for changes, and a plan for when things go wrong.
If you would rather skip the consultant search entirely, BuzFind's Site Builder builds fast, custom-coded sites with transparent, fixed pricing and no guessing required.
Our websites start at $599 for a Web Presence site (2 pages), and go to $1,299 for a Business Website, $1,799 for a Blog Website, and $3,499 for E-Commerce (a full store with a cart and Stripe checkout).
Each is a one-time price, plus $19 a month if we host the site. See our full web design and development services for details.
And if you already have a site and want to know where it stands before you hire anyone, start with a free SEO audit.
