Blog

Questions to Ask Before Hiring a Website Developer

A pre-call checklist that saves you from a bad contract

Before you book a single discovery call, run the developer through these questions — the answers will tell you more than any portfolio.

May 15, 2026

Most website projects don't go wrong during the build. They go wrong in the first phone call, when nobody asked the question that mattered.

If you want the longer version of this — how to actually evaluate and shortlist agencies — read How to Choose a Web Design Agency in Dubai. This post is the short, scannable version: the specific questions to bring into your first call, in order, with what a good answer sounds like.

Table of Contents

  • Why a checklist beats a gut feeling
  • Ownership and access questions
  • Pricing and scope questions
  • Platform and technical questions
  • Timeline and process questions
  • Support and aftercare questions
  • Red flags to listen for
  • How to score the answers afterward
  • What to do if you don't like the answers

Why a checklist beats a gut feeling

A sales call is designed to make you feel good. That's not a criticism — it's the job of the call. Your job is to come in with questions that cut through the pitch and get to facts: who owns what, what's included, and what happens when something breaks.

Write these down. Ask them in order. Take notes on the actual wording of the answers, not just the vibe.

Ownership and access questions

This is the single most important category, and the one most people skip.

  1. "Will I own the code, the CMS, and the hosting account — or will they be under your company's accounts?"
  2. "If we part ways in a year, what exactly do I walk away with?"
  3. "Can I get admin-level access to everything from day one, not just after final payment?"

If the answer involves "our platform," "our proprietary system," or hosting that stays under the agency's name indefinitely, you're looking at a vendor lock-in setup. We wrote a full breakdown of how this trap works in Website Vendor Lock-In, Explained — worth reading before you sign anything.

Pricing and scope questions

  1. "Is this a fixed price, or will I get change orders as we go?"
  2. "What's explicitly NOT included in this price?"
  3. "What happens if I want one more page, or one more revision round, after we start?"

Vague pricing isn't always a scam — sometimes it's just an agency that hasn't scoped properly. Either way, it becomes your problem. Ask for the quote in writing, itemized, before you commit. For context on why so many agencies dodge this question entirely, see Why Web Agencies Hide Their Pricing.

Platform and technical questions

  1. "What platform or framework will this be built on, and is it something other developers can pick up later?"
  2. "Will the site be fast on mobile, not just on your demo laptop?"
  3. "Do you build custom, or are we starting from a theme/template?"

There's no universally "right" answer here — WordPress, Webflow, and custom code all have legitimate use cases. The wrong answer is a developer who can't explain the tradeoff, or who can't tell you what stack they use at all. If you want to see what a transparent answer to this looks like, our own approach is laid out at /stack.

Timeline and process questions

  1. "What's the realistic timeline, including the time you'll be waiting on me for content and feedback?"
  2. "How many revision rounds are included, and what happens after that?"
  3. "Who is my single point of contact during the build?"

A good agency will give you a number and explain the variables. A bad one will say "it depends" and stop there.

Support and aftercare questions

  1. "What happens the day after launch — is there a support plan, or am I on my own?"
  2. "Who patches security updates, and how often?"
  3. "If my site breaks at 11pm, what's the actual response time?"

Most contracts go quiet on this. Ask directly, and ask to see their maintenance packages in writing — not a verbal promise. RISE Web publishes these tiers openly at /packages.

Red flags to listen for

During the call, listen for these specific phrases:

  • "Don't worry about the technical stuff" — usually means they don't want you asking about ownership.
  • "We'll figure out pricing as we go" — usually means scope creep is coming.
  • "You don't need access to that" — about anything. You always need access to your own site.
  • "Everyone uses our hosting" — fine in itself, but ask what happens if you want to leave.

None of these phrases automatically mean the developer is dishonest. But they mean you need to push harder on the specific question until you get a specific answer.

How to score the answers afterward

Asking the questions is only half the job. After the call, go back through your notes and score each answer on three things:

  • Specificity. Did they give you a number, a name, a written process — or a feeling?
  • Consistency. Did the answer to question 3 contradict the answer to question 13? Vendor lock-in setups often have agencies that quietly contradict themselves between the sales pitch and the support pitch.
  • Willingness to put it in writing. Anything you were told verbally should show up in the proposal or contract. If it doesn't, it doesn't count as a commitment.

If you're speaking with more than one developer — which you should be — run every candidate through the exact same fifteen questions, in the same order. This is the only way to compare answers fairly instead of comparing how each person made you feel on the call.

What to do if you don't like the answers

Not every weak answer is disqualifying on its own. A small studio might not have a polished support tier yet but could still build you a great site. The point of the checklist isn't to find a perfect score — it's to know exactly what you're agreeing to before you agree to it.

If you get a vague answer, ask a direct follow-up: "Can you send that to me in writing?" A developer who hesitates here is telling you something important, even if they never say it out loud.

Bringing it to the call

Print this list, or keep it open on a second screen. Ask the questions in your own words if that feels more natural — what matters is that you get answers to all six categories before you sign anything: ownership, pricing, platform, timeline, support, and the red-flag phrases above.

If you want the fuller context behind why each of these categories matters and how to weigh agencies against each other, the companion piece — How to Choose a Web Design Agency in Dubai — walks through the evaluation process end to end.

FAQ

Ask who will own the code, CMS, and hosting account after the project is delivered — this single question reveals whether you are walking into a vendor lock-in arrangement before you sign anything.

Ask for a fixed, itemized price in writing whenever the scope is reasonably well defined; this protects you from change orders and makes it clear what is and is not included.

Ask what is included in ongoing support, who handles security patches, and what the actual response time is if the site breaks — a credible agency will have a written support plan, not just a verbal promise.

Speaking with at least three developers or agencies using the same question checklist makes it far easier to spot inconsistent answers and red-flag phrases that one conversation alone might miss.

Yes — a developer who cannot clearly explain what platform or framework they build on, or why, is either inexperienced or intentionally avoiding a question that would reveal lock-in risk.