Questions to Ask a Web Developer Before You Hire

The best questions to ask a web developer are the ones that show how they work with you, not just what they can build. Ask to walk through a past project, ask what is in the price, ask who owns everything when the site is done, and ask who looks after it after launch. Clear, specific answers to those four things tell you more than any portfolio.

I’m Tommy Cosimano, and I build custom WordPress sites for small businesses, startups, nonprofits and agencies across the United States. Most of the people I talk to are not technical, and that is fine. You do not need to understand code to hire well. You need to know what to ask and what a good answer sounds like. This guide gives you both.

tcosi
Build a Website With Clear Communication
tcosi builds custom WordPress websites with a collaborative process that makes the technical side easier to understand.

Contact Me

TL;DR

  • Ask to see real past work and have the developer walk you through one project, including one that did not go as planned.
  • Get scope, timeline, price and what counts as an extra in writing before any work starts.
  • Confirm that you will own your domain, content, files and logins when the project is done.
  • Ask who handles updates, backups, security and fixes after launch, and what it costs per month.
  • Watch how they communicate during the first conversation. It is the best preview of the whole project.

Table of Contents

Start with experience and past projects

You are hiring a person or a small team, so begin with what they have actually done. HubSpot’s guide to hiring a development agency suggests asking what types of websites the developer has built and looking at past client work yourself instead of only hearing about it. The point is to match their projects to what you need.

Here are the questions I would ask:

  • What kinds of sites have you built, and which are most like mine? A local service business needs different things from a nonprofit with a donation form or a firm with dozens of service pages.
  • Can I click through a few live sites you built? Open them on your phone. See how they load and whether the menus are easy to use.
  • Which parts of that project did you do yourself? Some people sell a team’s work as their own. A direct answer here is a good sign.
  • Can I speak with a past client? The same HubSpot piece, as summarized in our research, points to talking with one or two past clients about whether the project stayed on scope and whether the site was easy to maintain after the developer left.

Ask about a project that went wrong

This is the most revealing question on the list. Web developer William Alexander recommends asking, “Tell me about a project that went wrong. What happened and what did you learn?” He says good answers name a specific situation, own the developer’s part in it, and describe a concrete lesson. Red flags are “all my projects go great” or blaming the client.

I agree with that. Every developer has had a launch that slipped, a plugin that broke something, or a misunderstanding about what was promised. What matters is whether they can talk about it plainly and what they changed afterward. I would trust someone who tells me about a rough project over someone who has never had one.

Ask about a project that went wrong

Pin down your goals, features and scope

A developer can only quote what they understand. Before you ask for a price, get clear on what the site needs to do. Martech.org’s list of 100+ website build questions covers the ground well: whether you have a domain, a logo and original artwork files, how many pages and wireframes you need, who writes the content, whether you need training, what actions visitors should take, which content management system you prefer, what your forms are for, which third-party tools need to connect, any accessibility needs, and your target time frame.

You do not have to answer all of that alone. A good developer asks you most of these questions. If they skip straight to a number, that is worth noticing.

Bring a short brief to the first call:

  1. The goal. More phone calls, booked appointments, online orders, donations, or a credible place to send people who hear about you.
  2. The pages. A rough list: home, services, about, contact, and anything else.
  3. The features. Contact forms, scheduling, a blog, a members area, a store.
  4. The tools you already use. Email marketing, a CRM, a booking system, payment processing. If your current site lives on a simple builder, it helps to know what Google Sites means for small business owners so you can describe what you want to keep or improve.
  5. The content. Who writes the text, who supplies photos, and whether your logo and brand colors exist yet.

If brand materials are missing, say so. A website style guide settles colors, fonts and button styles up front, which keeps design decisions from stalling the project later.

Ask about the process, step by step

Then ask the developer to describe how a project runs from start to finish. Good answers usually include a discovery conversation, a plan for page layouts, a design review, a build on a private staging site, testing, and launch. HubSpot’s guide also asks how you will be involved and whether you will see wireframes and prototypes along the way. Its author argues that even if you are not writing code, the site represents your brand, so you should expect regular status meetings and progress reports.

When I work with a client, I want the process to be clear and collaborative, so you always know what is happening next and why. Whoever you hire, you should be able to say the same.

Ask for a realistic timeline

Ask how long each stage takes and what could slow it down. Honestly, the most common delay is not the developer. It is content that arrives late. A developer who says so and builds your review dates into the schedule is being realistic. If you want to see what typical schedules look like, I have laid out WordPress website timelines for small to complex sites you can compare against any quote.

Ask about platform, speed, search and accessibility

These questions sound technical, but you only need plain answers.

  • What platform will you use, and why is it right for me? For many small business sites, WordPress is a strong fit because you can edit your own content later. HubSpot’s list also asks whether you will be able to edit the site yourself. If you are choosing between platforms, Webflow vs WordPress walks through how each fits a business.
  • Will the site work well on phones? Most developers build responsive sites. Ask to see a past project on a phone, not a promise.
  • How will you set the site up for search? Ask about page titles, descriptions, clean URLs, and local search if you serve a specific area. Good answers are concrete. Vague ones sound like “we do SEO.” My WordPress SEO checklist shows the basics a developer should be able to talk through.
  • How will you keep the site fast? Ask what they do about image sizes and the number of plugins.
  • How do you handle accessibility? Martech’s list includes accessibility needs among the scope questions. A developer who has a ready answer about readable text, color contrast and keyboard navigation is thinking about all of your visitors.
  • Which plugins and tools will you install, and who maintains them? Every plugin is something that needs updating later.

If you want an SEO-optimized site from day one, make sure search setup is in the scope and not an afterthought. I list SEO Setup as its own line item at $375 so you can see it plainly.

Get price, payments and extras in writing

Price is where small misunderstandings turn into big arguments. HubSpot’s guide lists cost and estimated timeline among its core questions. Ask these:

  • What is the total price, and exactly what does it cover? Pages, design rounds, forms, search setup, training.
  • How are payments split? Many projects use a deposit up front and the balance at milestones or launch. Ask for the schedule in writing.
  • What counts as an extra? Extra pages, new features, a store added mid-project, stock photos, premium plugin licenses.
  • What happens when I want a change in the middle? Hon Tran recommends a defined scope-change process with a change log, and a new quote for big additions. That keeps both sides honest.
  • How many rounds of revisions are included? Number them. “Unlimited” and “as needed” both deserve a follow-up.
  • Are hosting, domain and plugin licenses in the price or separate? These are often yearly costs that nobody mentions at signing.

What published pricing looks like

I publish my project prices so you can compare before we talk. On my pricing page, website packages are Essentials at $1,200, Growth at $2,400 and Premium at $4,800, all one-time. There is also a Base Website at $875. Add-ons are priced separately: a Style Guide at $300, Wireframes at $175, SEO Setup at $375 and Custom Post Type Setup at $800.

You may not hire me, and that is your call, but you should expect any developer to explain their numbers this clearly. If a quote arrives as one lump sum, ask for it to be broken down by deliverable.

Ask who owns what

This is the question most owners forget, and it is the one that hurts most later. Before you sign, ask:

  • Will the domain be registered in my name? It should be. Ask for the registrar login or the account to be under your email.
  • Who owns the design, the content and the code when I have paid in full? The contract should say so in plain words.
  • Will I have administrator access to my own WordPress site? You should.
  • Who holds the hosting account, and can I move it? Ask how leaving works before you sign. E-3 Design suggests this question, and I think it is smart.
  • Do I receive files and logins at the end? Get a list of what is handed over.

I wrote a separate piece on this: developer handoff for websites, 5 checks owners must verify. Use it as a checklist for launch day.

Ask about communication and revisions

How someone communicates before you hire them is how they will communicate during the project. HubSpot says to establish how you will check in, ask questions, and hear about challenges that affect timeline or budget, and calls unwillingness to set up open communication a red flag.

Try these:

  • How will we communicate, and how fast do you reply? Email, phone, a shared project board? Hon Tran suggests asking for a named channel and cadence, such as a weekly check-in, a staging link and written updates.
  • Who is my point of contact? One person, not a rotating cast.
  • How do I give feedback? Consolidated notes on a staging site beat scattered emails. Agencies in particular may like this five-stage client feedback workflow.
  • What if I disagree with a design direction? Their answer shows how they handle conflict.

Responsive communication is something my clients mention often, and I treat it as part of the job, not a bonus.

Ask what happens after launch

A website is not finished on launch day. WordPress core, themes and plugins need updates, backups need to run and security needs watching. E-3 Design advises asking who handles updates, backups, security and support after launch, and how fast they respond.

Ask these before signing:

  • Is there a support window after launch, and what does it cover? Hon Tran recommends a defined post-launch window and a clear retainer or hourly rate afterward.
  • What does ongoing maintenance include and cost per month?
  • Who updates plugins and watches security? My notes on website security best practices for small businesses explain why this cannot be skipped.
  • Who makes content changes, like new hours, staff or prices?
  • If something breaks at 9 p.m., what happens?

My ongoing maintenance plan is $100 per month, and Content Updates and Plugin & Security Management are each also listed at $100 per month. If you want the full picture of what small businesses spend, see my breakdown of website maintenance costs. A developer who has no answer about the months after launch has not thought about your site as a long-term asset.

Green flags and red flags

Here is a quick way to read the answers you get.

Topic Good sign Warning sign
Past work Live sites, a walkthrough, a candid story about a project that went wrong Only screenshots, or “all my projects go great”
Scope Asks you questions before quoting Quotes a price in the first five minutes
Price Itemized, with extras named One lump sum, vague “as needed” language
Ownership Domain and accounts in your name, handoff list Hesitation about logins or files
Communication Named contact, regular check-ins, staging link Slow replies before you have even signed
After launch Clear support window and monthly rate “Call me if something breaks”

One more point from William Alexander: a developer who has built 20 varied sites and can explain why your project is unique may serve you better than one who has built 50 identical ones. Fit matters more than volume.

What we think: hire for clarity

We spend a lot of time with business owners who have been burned once. A site that was never handed over, a quote that doubled, a developer who stopped answering after launch. The fix is rarely a better developer in the abstract. It is a clearer process.

That is how we work: plain language, a collaborative process, and a site that is built to last, not patched with bandaids. We publish our project prices, we talk through what each stage involves, and we offer monthly support so the site is looked after once it is live.

Use the questions above with anyone you are considering, us included. A good developer will enjoy answering them.

Tommy Cosimano

If you want to talk it through

If you are a small business owner, startup or nonprofit looking for a custom WordPress site, I would be glad to answer every question in this article on a call. You will get a clear scope, published pricing and a plan for after launch. Start at tcosi.com or see the pricing page.

tcosi

Agencies looking for a build partner can also learn about white-label WordPress development, where I build under your brand.

FAQ

How many developers should I talk to before choosing?

Two or three is enough for most small business projects. Give each the same brief so the quotes and the questions they ask are comparable. Pay attention to who asks you good questions, not just who is cheapest.

What is the single most important question to ask a web developer?

Ask who will own the domain, content, files and logins when the project is complete. Then ask who looks after the site after launch. Ownership and support are the two things owners most often discover too late.

Should I ask a developer for references?

Yes. HubSpot’s guide suggests looking at past client work, and the research also points to talking with one or two past clients about scope and how easy the site was to maintain afterward. Ask them whether communication stayed clear from start to finish.

Do I need a technical background to ask these questions?

No. Every question here can be asked in plain language, and a good developer will answer in plain language too. If an answer is full of jargon and you cannot get a simple version, treat that as useful information about how the project would go.

Sources

Taking on new projects

Need Help With Your Website?

Tommy Cosimano is a New Jersey-based web designer and WordPress developer who helps businesses build, maintain, and improve websites that are fast, secure, and easy to manage. Through tcosi, he works with companies throughout New Jersey and beyond, providing website design, maintenance, SEO support, and ongoing website consulting.