Questions to Ask a Developer
The questions that separate good developers from bad ones — and help you evaluate proposals.
Process & Approach
These questions reveal how the developer approaches projects and communicates about unknowns.
1. How do you approach discovery?
Why it matters: Good developers don't start coding immediately. They understand your business, goals, and audience first.
Good answer: "We spend 1-2 weeks on discovery. We interview you, analyze competitors, understand user needs. We create wireframes and a detailed scope document before any design or development."
2. Can you show me examples of similar projects you've built?
Why it matters: Demonstrates experience with your type of project. You want to see quality work.
Good answer: They show 3-5 relevant examples, explain their role, discuss outcomes. Portfolio sites are red flags (can't show client work).
3. How do you handle scope changes and unexpected requirements?
Why it matters: Requirements always change. How they handle it determines whether you'll get surprised with extra costs.
Good answer: "Scope changes are documented. We renegotiate timelines and budgets if major changes occur. Minor changes (under 5 hours) are covered by contingency."
4. What's your process for getting client feedback?
Why it matters: Feedback loops determine how many revisions are realistic and how the project flows.
Good answer: "We use [Figma, Basecamp, etc.] for feedback. You get drafts at weeks 1, 3, 5, etc. We incorporate feedback incrementally rather than in bulk at the end."
5. How many rounds of revisions are included in your quote?
Why it matters: Unlimited revisions kill projects. Clarity prevents disputes.
Good answer: "2 rounds of major revisions. Minor tweaks are unlimited. Changes beyond 3 hours count as change requests billed separately."
Technical Decisions
6. What platform/tech stack will you use, and why?
Why it matters: This determines future scalability, flexibility, and cost.
Good answer: "For your needs, [WordPress/Next.js/Webflow] is best because [specific reasons]. This gives you [scalability/flexibility/low cost] and lets us [migrate/scale/customize] later."
7. How will you ensure the site is fast? What are your targets?
Why it matters: Page speed affects rankings and conversion. Vague answers are red flags.
Good answer: "We target Lighthouse scores of 85+. We'll use [image optimization, caching, CDN]. We'll test on [tools]. Expected load time: under 2.5 seconds."
8. How will you handle SEO? What's included?
Why it matters: Many developers ignore SEO. A good one bakes it in.
Good answer: "Technical SEO is built in: fast pages, mobile-responsive, clean URLs, sitemap, schema markup. We're not doing content optimization or backlink building (separate service) but structure supports it."
9. Will the site be mobile-responsive? How do you test it?
Why it matters: Non-negotiable in 2025. Testing shows they take it seriously.
Good answer: "Yes, mobile-first design. We test on real devices and emulators. We'll provide a test device list before launch."
10. What's your approach to security?
Why it matters: Hacked sites are costly and damage reputation.
Good answer: "We use [HTTPS, security headers, input validation]. We follow OWASP guidelines. We'll set up [WAF, automatic updates]. Post-launch, we recommend [security plugin/service]."
11. How will you handle browser compatibility?
Why it matters: Sites should work on all modern browsers, not just Chrome.
Good answer: "We test on Chrome, Firefox, Safari, Edge. We support last 2 versions of each. Older browsers degrade gracefully but may not have full features."
Project Management
12. What's your typical timeline from start to launch?
Why it matters: Reveals realistic scoping. Unusually fast or slow timelines are suspicious.
Good answer: "Discovery: 2 weeks. Design: 2-3 weeks. Development: 3-4 weeks. Testing/refinement: 1-2 weeks. Total: 8-12 weeks for a medium project."
13. How do you track progress? Can I see updates?
Why it matters: Transparency prevents surprises. You should see regular progress.
Good answer: "We use [project management tool]. You get weekly updates and can view progress anytime. We do check-in calls every [2 weeks]."
14. What happens if the project goes over budget or timeline?
Why it matters: Overage policies reveal whether they'll communicate early or surprise you.
Good answer: "We'll alert you if we see we're tracking over 10% of timeline/budget. We'll discuss options: reduce scope, extend timeline, or absorb cost. We don't exceed budget/timeline without approval."
15. Who is my main point of contact?
Why it matters: Communication breaks down with unclear contacts.
Good answer: "[Person name] is your project manager. Email/Slack response time: within 24 hours. For emergencies: [contact info]."
Ownership & IP
16. Who owns the code, domain, hosting, content?
Why it matters: Critical for exit planning. You should own everything.
Good answer: "You own all code, content, and data. We'll provide everything: source code, database backups, hosting access. You can move to another developer anytime."
17. Can I switch hosting providers after launch?
Why it matters: Being locked into their hosting is expensive and risky.
Good answer: "Absolutely. We'll provide all files/databases. We'll help with migration if needed. You're not locked in."
18. Can I modify the site myself after launch?
Why it matters: Determines your future flexibility and dependence on them.
Good answer: "Yes. We'll provide training and documentation. Content changes are easy. Technical changes require a developer, but you can hire anyone."
19. What happens to my site if your company closes?
Why it matters: Freelancers and small agencies can disappear. You need contingencies.
Good answer: "You own all code/files. We'll keep you with hosting/domain credentials. Even if we close, your site keeps running. You can hire another developer."
20. Who retains copyright on the design/code?
Why it matters: Rarely matters in practice but important for clarity.
Good answer: "You retain copyright on everything. We can't reuse your design or code for other clients without explicit permission."
Security & Hosting
21. Where will the site be hosted? Why that host?
Why it matters: Host choice affects performance, security, and cost.
Good answer: "We recommend [host] because [reasons: good uptime, security, customer support]. You can switch if you prefer. Our recommendation is unbiased."
22. What backup/disaster recovery plan do you have?
Why it matters: Data loss is catastrophic. Good backups prevent it.
Good answer: "Automatic daily backups. Stored in multiple locations. We test restore quarterly. We'll document the backup process for you."
23. What's your SSL/HTTPS plan?
Why it matters: HTTPS is mandatory. Free SSL is fine; just confirm it.
Good answer: "We'll set up free SSL (Let's Encrypt) with auto-renewal. All traffic is HTTPS by default. No additional cost."
Post-Launch
24. What support/maintenance is included after launch?
Why it matters: Post-launch support prevents emergencies.
Good answer: "[X] hours of free support during first month. Then we offer a maintenance retainer at $[X]/month for [updates, monitoring, minor fixes]."
25. How will you handle bugs discovered after launch?
Why it matters: Critical bugs need fast fixing.
Good answer: "Critical bugs are fixed free within [X] days. Non-critical bugs covered under maintenance retainer. After [30 days], all bugs are paid support."
26. What analytics/monitoring will you set up?
Why it matters: You need data on how your site performs.
Good answer: "We'll set up Google Analytics 4, Search Console, performance monitoring. We'll document how to use each."
27. How will you handle WordPress/plugin updates in the future?
Why it matters: Unpatched software gets hacked.
Good answer: "If using WordPress, we recommend automatic updates for security patches. Major updates should be tested first. A maintenance retainer covers this."
Pricing & Contracts
28. Can you provide a detailed breakdown of your costs?
Why it matters: Transparency prevents disputes.
Good answer: "Design: 40 hours @ $100/hr = $4k. Development: 60 hours @ $100/hr = $6k. Testing/deployment: 20 hours = $2k. Contingency (10%): $1.2k. Total: $13.2k."
29. What are your payment terms?
Why it matters: Payment structure affects risk and commitment.
Good answer: "25% deposit to start. 25% at design approval. 25% at development completion. 25% on launch. Or milestone-based: we invoice when milestones complete."
30. What happens if I'm not happy with the final result?
Why it matters: Recourse prevents conflict.
Good answer: "We build in testing/refinement phases so issues are caught early. If major issues exist at launch, we fix them. If you change your mind about scope, that's a change request."
31. Do you have a written contract?
Why it matters: Written contracts prevent disputes.
Good answer: "Yes, we use a standard contract. It includes scope, timeline, payment terms, ownership, and support terms. Our contract protects both of us."