Questions to Ask Before Hiring a Web Developer

Sam Hemburyยท27 December 2024ยท8 min readยทBeginner

The essential questions to ask before committing to a web developer or agency. Avoid costly mistakes by knowing what to ask and what answers should concern you.

Key Takeaways

  • 1Ask about process, not just portfolio - how they work matters as much as what they've done
  • 2Understand what happens AFTER launch - websites need ongoing attention
  • 3Get specifics on timelines, deliverables, and what's included
  • 4Red flags include vague answers, guaranteed results, and reluctance to explain
  • 5Good developers welcome questions - it shows you're engaged

Hiring a web developer is one of the more important business decisions you'll make. A good choice can transform your online presence. A bad choice costs time, money, and opportunity.

Here are the questions that help you make the right choice.

๐ŸŽฏ
The right questions save you thousands
Most bad hires happen because clients focused on portfolio and price alone. The questions you ask โ€” about process, communication, and what happens after launch โ€” reveal far more about whether a developer will actually deliver.

Questions About Their Experience

"Can you show me similar projects you've completed?"

What you're looking for: Work relevant to your industry, size, or needs. Not just pretty portfolios, but sites that solve similar problems.

Red flag: No relevant examples, or examples that are years old.

Follow-up: "What was the challenge with this project, and how did you solve it?"

"How long have you been doing this?"

What you're looking for: Experience, but also context. A newer developer who specialises in your needs might beat a generalist with 20 years.

Red flag: Evasiveness or padding (listing years of "interest" rather than professional work).

Reality check: Years of experience matters less than relevant experience.

"What technologies do you work with?"

What you're looking for: Tools appropriate for your needs. WordPress for content-heavy sites, Shopify for e-commerce, modern frameworks for performance-critical sites.

Red flag: Pushing a specific technology regardless of your needs ("I only do WordPress" when WordPress might not fit).

Good answer: They recommend technology based on your requirements, not their preferences.

"Do you work alone or with a team?"

What you're looking for: Understanding of who actually does the work and what happens if that person is unavailable.

Red flag: Vague answers about "we" when it's clearly one person with no backup.

Reality: Solo developers can be excellent, but understand the implications.

๐Ÿ“‹
Relevant experience beats years of experience every time
Can they show work similar to what you need โ€” not just pretty sites?
Do they recommend technology based on your needs, or just what they prefer?
Can they talk through specific problems they solved, not just show end results?
If they're a solo developer, what's the backup plan if they're unavailable?

Questions About Their Process

"What does your typical project look like from start to finish?"

What you're looking for: A clear, structured process. Discovery, design, development, testing, launch, handover.

Red flag: No clear process, or "it depends" without explanation.

Good answer: They walk you through distinct phases with clear deliverables at each stage.

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

What you're looking for: Clear understanding of your involvement. Content, feedback, decisions, approvals.

Red flag: "We handle everything" (you should be involved) or no expectations (chaos awaits).

Good answer: Specific requests with timelines - "We'll need content by week 3, feedback on designs within 5 days."

"How do you handle feedback and revisions?"

What you're looking for: A structured revision process with clear limits.

Red flag: Unlimited revisions (unsustainable) or very limited revisions (inflexible).

Good answer: Defined revision rounds per phase, clear process for additional changes.

"What's your communication style during the project?"

What you're looking for: Compatibility with how you work. Regular updates, accessible contact, responsive communication.

Red flag: "We'll be in touch when we need something" (you deserve more visibility).

Good answer: Regular check-ins, project management tools, clear points of contact.

Questions About Timeline and Deliverables

"How long will this take?"

What you're looking for: Realistic timeline with phases explained.

Red flag: Suspiciously fast ("2 weeks for a custom e-commerce site") or no timeline at all.

Good answer: Broken down by phase - "4 weeks for design, 6 weeks for development, 2 weeks for testing and launch."

"What happens if the project runs over?"

What you're looking for: Clear policy on delays, whether caused by them or you.

Red flag: No contingency or blaming clients for all delays.

Good answer: Process for handling scope changes, delays, and how additional work is priced.

"What exactly will I receive?"

What you're looking for: Specific deliverables - files, access, documentation, training.

Red flag: Vague descriptions or lack of detail.

Good answer: Itemised list - "Live website, admin access, design files, training video, 30 days support."

"Do I own everything you create?"

What you're looking for: Clear ownership of the final product, including design files and code.

Red flag: "We retain ownership" or unclear IP terms.

Good answer: You own the custom work. They may retain rights to their reusable frameworks or templates (which is fair).

๐Ÿ“…
A custom website takes 10+ weeks โ€” anyone promising less is cutting corners
Weeks 1-2: Discovery Weeks 2-4: Design Weeks 4-8: Development Weeks 8-9: Testing Week 10: Launch
Anyone promising a custom business website in under 4 weeks is either cutting corners or hasn't scoped your project properly.

Questions About After Launch

"What happens after the site goes live?"

What you're looking for: Clear handover process and understanding of ongoing needs.

Red flag: "You're on your own" or no discussion of post-launch reality.

Good answer: Support period, training, documentation, ongoing maintenance options.

"How do I make updates myself?"

What you're looking for: Training and/or user-friendly content management.

Red flag: "You'll need to contact us for everything" (unless that's your preference).

Good answer: CMS with training, clear instructions, self-service capability for routine changes.

"What about hosting and maintenance?"

What you're looking for: Clear options and pricing for ongoing services.

Red flag: Unclear or suspiciously expensive ongoing fees.

Good answer: Options ranging from self-managed to fully managed, with transparent pricing.

"What if something breaks?"

What you're looking for: Support arrangements and response expectations.

Red flag: No support or "best effort" with no commitments.

Good answer: Defined support period, response times, and ongoing options.

Questions About Money

"What's included in this price?"

What you're looking for: Detailed breakdown, not just a total.

Red flag: Lump sum with no detail or "it depends."

Good answer: Itemised scope showing what's in and what's out.

"What's NOT included?"

What you're looking for: Clarity on boundaries to avoid surprise costs.

Red flag: Reluctance to answer or "nothing extra needed."

Good answer: Clear exclusions - stock photos, content writing, specific integrations - and how those are priced.

"How do you handle changes to scope?"

What you're looking for: Clear process for handling additions and changes.

Red flag: No process or "we'll figure it out."

Good answer: Change request process with pricing approach (hourly, quoted per item).

"What's your payment structure?"

What you're looking for: Reasonable milestone-based payments.

Red flag: 100% upfront or suspiciously back-weighted (sign of cash flow problems).

Good answer: Typically 25-50% upfront, 25-50% at milestones, remainder at launch.

๐Ÿ’ท
A fair payment structure protects both sides
25-50% deposit at project start โ€” secures commitment from both parties
25-50% at a milestone like design approval โ€” ties payment to progress
Remainder at launch โ€” ensures you're happy before final payment
100% upfront is high risk for you. 100% on completion is rare. Something in between is fair.

Red Flag Answers

Be cautious if you hear:

"We guarantee page 1 Google rankings" - No one can guarantee this. SEO is influenced by many factors outside developer control.

"You don't need to worry about the details" - You're investing significant money. You should understand what you're getting.

"Our process is proprietary/secret" - Web development isn't secret. Legitimate developers explain their approach.

"Everyone else is overcharging you" - Cheap rarely means good value. Be suspicious of unusually low quotes.

"We need a decision today" - Pressure tactics suggest desperation, not confidence.

"We'll sort out the contract later" - Professional relationships need clear agreements upfront.

Good Signs

Look for:

Clear communication - They explain things simply and answer questions directly.

Relevant questions about your business - They want to understand your goals, not just your specs.

Honest about limitations - They tell you what they can't do or what might be difficult.

Examples of problem-solving - They share how they've handled challenges.

Realistic timelines and prices - Neither suspiciously low nor inexplicably high.

Structured process - They have a way of working that's proven.

After You Ask

Compare answers - Different developers will have different strengths. Some excel at design, others at technical complexity.

Check references - Ask for and contact past clients. Ask about communication, delivery, and post-launch support.

Trust your judgment - If something feels wrong, it probably is. If you feel comfortable and confident, that matters.

Get it in writing - Whatever's discussed should be in the proposal and contract. Verbal promises don't count.

The Bottom Line

Good developers welcome questions. They understand you're making an important decision and investing significant resources. If someone's annoyed by your questions or rushes you, that tells you something.

Take the time to ask, listen carefully to the answers, and choose someone who:

  • Understands your needs
  • Communicates clearly
  • Has relevant experience
  • Offers fair, transparent pricing
  • You feel comfortable working with

The questions you ask now prevent the problems you'd pay for later.

Frequently Asked Questions

How many developers should I talk to?
At least 3 for comparison. This helps you understand the range of approaches, prices, and personalities. But don't get stuck in endless research - once you've found someone competent who you trust and can afford, that's often enough.
What if I don't understand their answers?
That's actually useful information. Good developers explain things in plain English. If they can't communicate clearly during the sales process, imagine working with them during a project. Don't blame yourself for 'not being technical' - translation is their job.
Should I choose the cheapest quote?
Rarely. The cheapest quote often becomes the most expensive project. Understand what makes one quote higher than another. Sometimes it's margin; sometimes it's scope, quality, or experience. Ask them to explain their pricing.
What about gut feeling?
It matters. You'll work closely with this person for weeks or months. If something feels off - poor communication, arrogance, pressure tactics - trust that instinct. Professional relationships need trust and compatibility.

Sources & References

Tagged with:

HiringWeb DevelopmentAgency SelectionDue DiligenceQuestions
Share this article

Need Help Implementing This?

Pink Frog Studio builds fast, secure websites that actually get found. Let's chat about your project.