Most website project problems don't start during the build — they start before it, in a quote that skipped over things the client didn't know to ask about. Here are the questions to ask before hiring a website developer, in the order I'd want a client to send them to me or any other developer, before signing off on a project.
Every one of these came from an actual project that went sideways somewhere — mine or someone else's. None of them are hypothetical concerns; they're the specific gaps that turn a "quick website" into a frustrating three-month back-and-forth.
1. What exactly is included in this quote?
A number alone means nothing. Ask what pages, what SEO setup, what revisions, and what support are included — not just "a website." See our website cost breakdown for what each tier typically includes, or the full website services page for scope details.
2. Will the site be mobile-optimized by default?
This should never be an upsell. If a developer treats mobile responsiveness as an extra, that's worth noticing — most of your visitors will be on their phones.
Ask them to show you a mobile screenshot of a recent project during the quote conversation, not after you've paid. If they can't produce one quickly, that itself tells you something about how much attention mobile actually gets in their process.
3. Is basic SEO included, or is that separate?
Titles, meta descriptions, sitemap, and social sharing previews should be part of a proper website build, not a paid add-on discovered after launch. Ask specifically: "does this include SEO setup, or just the design?"
4. How will inquiries reach me?
Ask exactly what happens when someone fills out a contact form or clicks WhatsApp. Does it notify you immediately, or does it sit somewhere unchecked? This is the difference between a website that generates leads and one that quietly loses them.
5. Can I see real, live examples — not just mockups?
Anyone can show polished design images. Ask to see actual working sites, ideally ones similar to your business type. If you're a clinic, ask for clinic examples — like The Better Lungs Clinic or The Better Kid Clinic — not just generic portfolio pieces.
6. What's the realistic timeline?
Get an actual number of days or weeks, and ask what happens if it slips. A simple landing page should take days, not months. A full site with automation might take a couple of weeks. Vague timelines usually turn into vague delays.
7. How many rounds of revisions are included?
This avoids awkward mid-project surprises. One or two rounds is typical for smaller projects — know the number before you start, not after you've asked for your third round of changes.
8. What happens after launch?
Some developers disappear the moment the site goes live. Ask directly: if something breaks, or you need a small text change in three months, is that covered, or a new invoice?
This question also reveals whether you're hiring someone for a one-time delivery or an ongoing relationship. Neither is wrong, but you should know which one you're getting before launch day, not after your first post-launch request goes unanswered.
9. Who owns the website once it's built?
Make sure domain, hosting, and site files are actually yours, not locked into the developer's account with no way to transfer them if you switch providers later.
10. Can automation be added later, even if I don't need it now?
You might not need WhatsApp or email automation on day one, but it's worth knowing whether the site is built in a way that allows it to be added later without a full rebuild. See automation services for what typically gets added on later.
Two bonus questions worth asking too
Will I see the site before it goes live, or only after? Ask whether you'll get to review sections as they're built, or whether the whole thing gets built silently and revealed on launch day. The first approach catches mismatches early — a wrong phone number, a service you no longer offer — before they're live on Google.
What happens if I want to switch developers later? This one rarely gets asked, but it matters. If the relationship ends for any reason, can you take your site elsewhere cleanly, or is it built on a proprietary system only that developer can touch? Combined with question 9 (ownership), this determines whether you're actually free to leave if you need to.
Red flags to watch for in the answers
A few responses are worth pausing on regardless of price: "don't worry about that" to any of these questions, a refusal to put the quote scope in writing, or pressure to pay the full amount before any work is visible. None of these automatically mean a scam, but together they're a pattern worth noticing.
A quick way to use this list
Send these questions in your very first message to any developer working in India or anywhere else. The quality and directness of their answers will tell you more about how the project will go than any portfolio image will. It's also worth reading freelancer vs agency before deciding who to send them to, and common website mistakes that lose customers so you know what to check once the site is live.