Ask these in your discovery call. Vague or evasive answers to any one are typically a sign of pattern problems across the engagement.
01
Who owns the code, content, domain and hosting at the end?
What to listen for: You should own everything end-to-end — domain registered in your name, code in a repository you can access, content exportable, and hosting transferable to any provider. Anything less is a long-term lock-in trap.
02
What's the realistic 12-month total cost?
What to listen for: A clear figure that includes build, hosting, maintenance, plugin licences, and any platform fees. If a quote can't be reduced to one annual number, fees are hidden in the fine print.
03
Which platform do you recommend for my business, and why?
What to listen for: A specific platform recommendation tied to your business needs (content, e-commerce, performance, integrations) — not a one-size-fits-all 'we always use X.' Reputable agencies build on multiple platforms.
04
Can I see 3 case studies from businesses like mine?
What to listen for: Real case studies with named businesses, the problem solved, the platform used, and ideally measurable results. Vague portfolio shots don't count.
05
What does ongoing maintenance cover and what does it cost?
What to listen for: A specific monthly fee, what's included (security updates, plugin updates, backups, content tweaks, performance monitoring), the response time for issues, and whether it's optional or required.
06
How many revision rounds are included? Beyond that, what's the cost?
What to listen for: A specific number (typically 2 – 3 rounds for design, 1 – 2 for development) and a clear hourly or per-change rate beyond that. Vague 'we'll work with you until you're happy' usually means scope creep arguments later.
07
What's the timeline from kickoff to launch?
What to listen for: A specific week-by-week schedule with milestones (discovery, design, build, content, QA, launch). Realistic small-business sites take 4 – 14 weeks depending on scope.
08
What support do you offer after launch, and for how long?
What to listen for: A defined support window after launch (typically 30 – 90 days for bug fixes), plus an ongoing support arrangement (maintenance plan, retainer, or hourly). 'We're always around' isn't a support contract.
09
What happens if I want to leave, or you stop trading?
What to listen for: An exit process that includes handover of code, content, and access to your hosting and domain. Bonus points for documentation. This question often surfaces lock-in arrangements that aren't otherwise visible.
10
Who's actually going to be doing the work?
What to listen for: A named developer or designer, not 'our team' or an offshore agency. For small businesses, founder-led or small-team agencies typically deliver better than larger ones because the senior person is actually building the site.
