Questions to Ask Your Web Developer Before Hiring

Finding the right web developer can feel like a gamble. You're about to hand over money and trust them with your business's online presence - but how do you know they're any good?

We've put together the questions that actually matter. Not a lengthy guide (we've already written that one) - just the questions you should ask before signing anything, and why each one matters.

If you'd rather skip the vetting process entirely, see how we work - we answer all of these openly.

Experience and Portfolio Questions

"Can you show me 3-5 websites you've built for businesses similar to mine?"

You want evidence they understand your industry. A developer who's only built e-commerce sites might struggle with a service-based business, and vice versa. Look for examples that match your needs.

"How long have you been building websites professionally?"

Experience matters, but it's not everything. A developer with 3 years of focused experience can be better than someone who's been dabbling for 10. What you're really checking is whether they'll still be around next year.

"What happens to my website if you stop working or go out of business?"

This is crucial. If your developer disappears, you need to know whether you can access your site, who has the passwords, and whether another developer can take over. We've written about this nightmare scenario - what to do when your web developer disappears.

Technical Questions

"What platform or technology will you use, and why?"

They should be able to explain their choice in plain English. If the answer is full of jargon you don't understand, that's a warning sign - either they can't communicate clearly, or they're trying to impress rather than inform.

"Will my website work properly on mobile phones?"

Sounds obvious, but worth confirming. Over half of web traffic comes from mobile devices. Ask to see their mobile-responsive examples.

"How will you handle website security?"

Security isn't optional. They should mention SSL certificates, regular updates, secure hosting, and backups at minimum. If they look confused by the question, walk away.

"Do I own the website and can I take it elsewhere if needed?"

This varies depending on the type of build. With bespoke websites, you typically own the code. With platform-based solutions (including ours), you're often tied to that platform - similar to Squarespace or Wix. Neither is wrong, but you should know what you're getting.

Process Questions

"What do you need from me, and when?"

A good developer will be clear about what they need - content, images, branding, feedback. Vague answers like "we'll figure it out as we go" often lead to projects that drag on forever.

"How long will this take from start to finish?"

Get specific timelines. A simple business website shouldn't take months. If they can't give you a rough timeline, they either don't know their own capacity or haven't done this often enough.

"How will we communicate during the project?"

Email? Phone? Project management tool? Weekly calls? You need to know how to reach them and how quickly they typically respond. If they're hard to pin down before you've paid, they'll be worse after.

"What happens if I need changes after the website launches?"

Changes are inevitable. Understand the process and costs for updates after launch. Is support included? Is there an hourly rate? What's the turnaround time for small changes?

Pricing Questions

"What's included in your quote, and what costs extra?"

The initial quote is rarely the full picture. Ask specifically about:

• Domain registration
• Hosting
• Email setup
• SSL certificates
• Content writing
• Stock images
• Ongoing maintenance
• Future changes and updates

"Are there ongoing costs after the website is built?"

Hosting, maintenance, security updates - these don't stop when the site launches. Understand the full cost of ownership, not just the build cost.

"What are your payment terms?"

When do you pay? All upfront? 50/50? Monthly instalments? What happens if you're not happy with the work? Get this in writing before starting.

Red Flags to Watch For

These aren't questions - they're warning signs during your conversations:

• They can't show you their own website - If a web developer has a rubbish website (or none at all), that tells you something
• Vague answers about timelines and pricing - Professionals know their process
• Pushy sales tactics - Good developers have enough work; they don't need to pressure you
• No questions about your business - They should want to understand what you actually need
• Promises that sound too good - "We'll get you on page one of Google" without knowing anything about your business is nonsense
• Difficulty reaching them - If they're slow to respond now, imagine when you've already paid

The Questions They Should Ask You

A good developer will ask questions too. If they don't ask about your business goals, target customers, competitors, or what you want visitors to do on your site - they're probably just going to build something generic.

You want someone who's genuinely interested in solving your problem, not just taking your money and moving on.

What Good Answers Look Like

You don't need technical expertise to spot a good developer. Look for:

• Clear, jargon-free explanations - If they can't explain it simply, they don't understand it well enough
• Honest about limitations - "That's not my speciality" is better than "Sure, I can do everything"
• Asks clarifying questions - Shows they're thinking about your specific situation
• References or testimonials - Happy clients who'll vouch for them
• Written proposals - Professionals document what they'll deliver