Skip to content

Questions to Ask a Web Developer Before Hiring One

WebDo24 Team 6 min read 1 view
Questions to Ask a Web Developer Before Hiring One

You do not need to understand code to tell a good developer from a bad one. Here is what to ask about strategy, ownership, money and time, and what you want to hear back.

Most small business owners only hire a web developer once or twice in their lives, so it's hard to know what a good one sounds like. They all seem friendly on the first call. They all say they do great work. So here are the questions to ask a web developer before hiring anyone, including us, along with what you want to hear back.

You don't need to understand code for any of this. These are business questions, and a decent developer will be glad you asked them.

The first questions to ask a web developer before hiring

"What would you need to know about my business before you could quote this?"

This is our favorite, and it tells you a lot. A good answer comes back as more questions: who are your customers, how do they find you, what happens after someone enquires, what isn't working today. Be careful with anybody who sends a firm price after two lines of email. They're quoting a website, not your problem.

"How will this website bring me customers?"

Listen for a real explanation. You want something like, "People searching for this will land on this page, they'll see these reviews, and here's how they'd book." If you just hear "modern design" and "responsive," you're being sold the look rather than the result.

"What would you leave out?"

Anyone can add features to a quote. It takes some honesty to say, "You don't need that app yet." If they agree with everything you suggest, they're either not thinking about it or they're happy to bill you for it.

Questions to ask a web developer about ownership

These are the boring ones that save you from the biggest headaches later, so don't skip them.

"Who owns the website when we're finished?"

Get this in writing. It's normal for some parts to stay with their makers, such as themes, plugins and stock photos, and for a developer to keep their own reusable tools. What matters is that you own what was made for you, or at least have clear rights to keep using it if you part ways. For reference, you can read the ownership section in our own terms.

"Whose name will the domain and hosting be in?"

Your domain should be in your name, or in an account you control. If a developer registers it in theirs and you fall out, or they vanish, you can find yourself locked out of your own address. It's one of the most painful mistakes an owner can make, and it's easy to avoid.

"If I leave, what do I get and how?"

A good developer won't be offended. Ask whether you'd get the files, the logins and the database, and how long that would take. You're hoping never to need this, but the answer tells you a lot about who you're dealing with.

Questions about the work itself

"Can you show me something similar you've built, and is it still live?"

Open it on your phone while you're talking. Is it quick? Can you work out how to contact the business? Pretty screenshots don't tell you much, but a working site does.

"Who will actually do the work?"

It's fine if they use a team, and plenty of good agencies do. You just want to know who you'll be talking to, and what happens if that person is off sick or leaves.

"Can I change things myself afterward?"

You shouldn't have to pay someone every time your opening hours change. Ask them to show you what editing a page looks like, ideally before you sign.

"How will you make sure Google can find it?"

You're not asking for a ranking promise. In fact, you should be wary of one. You just want to know the basics are covered, such as page titles, speed, mobile, redirects from your old site and Google Search Console. If you've ever launched a site that didn't show up on Google, you'll know why this matters.

Questions about money and time

"What exactly is included, and what would count as extra?"

Ask for it in writing. Copywriting, photos, extra pages and rounds of changes are the usual places where a small quote grows. Ask how many revision rounds you get, and what happens after that.

"How are payments split?"

Paying a deposit is normal, but paying everything upfront means you've got little leverage if things stall. Payments tied to milestones keep everyone honest. You pay as you see the work.

"What happens if I cancel halfway?"

Nobody likes this question, but a professional will have an answer ready. Here's our refund and cancellation policy, if you'd like an example to compare against.

"What will it cost me to keep it running each year?"

Think about hosting, domain renewal, licenses, backups and updates. Somebody has to look after all that. Find out who, and what it'll cost, before you commit.

Questions to ask yourself afterward

Once the call's over, ask yourself three things. Did they explain things so you understood them, or did you feel a bit silly? Did they ask about your customers, or just talk about technology? And did they ever tell you no? You're going to be working with this person for months, and you need someone who'll tell you when your idea's a bad one.

Red flags worth walking away from

A guaranteed first page on Google is the big one, because nobody outside Google controls that. So is pressure to sign today, or a price that's suddenly dropped if you commit this week. Watch out too for vague answers about ownership, and for developers who won't put anything in writing. And if the cheapest quote is a long way under the others, ask what's missing. There's usually a reason.

How we'd answer these

We wrote this list knowing you might ask us the same things, and we'd be happy if you did. At WebDo24, we explain our strategy before you sign anything. We'll tell you how your website would bring in customers, what we'd automate, and what you can skip. Payments go by milestone, the plan and price come in writing, and if the strategy doesn't make sense to you, we don't go ahead.

We mainly work with small businesses and startups, building websites and iOS and Android apps at prices that suit a small team. One example is a cleaning company in Australia whose website and apps remind each customer when their next clean is due. Send us your project and put these questions to us. We'd rather you hired us knowing exactly what you're getting.

Share

Need help putting this into practice?

Our team can do it for you — a clear plan and price within 24 hours, no obligation.

Get a Quote