Hiring a web development partner is one of those decisions where the cost of getting it wrong is hidden until it's too late. The website looks fine at launch. Then you need a change and can't make it, or you find you don't own the code, or the traffic slides and no one can say why, or the "cheap" quote grows a tail of extras. A year later you're paying someone else to rebuild it.
Almost all of that is avoidable at the start, with the right questions. We build websites for a living, and these are the twelve questions we'd want a client to ask us — because the answers separate a genuine partner from a vendor who'll disappear at launch.
01Ownership and control
1. Will I own the website, the code, and all the accounts?
This is the one that catches people out. You should own your domain, your hosting account, your content, and — for a custom build — the code. Some arrangements quietly keep you locked in: the agency owns the domain, or the site is built on a proprietary platform you can't leave without starting over. Ask directly, and get the answer in writing. A partner who builds for your independence is telling you something good about how they operate.
2. What happens if we part ways?
A fair partner has a clean answer: here's how you'd take your site, your data, and your accounts elsewhere. If the response is evasive, or leaving sounds painful by design, treat that as the answer to a different question — how much they rely on lock-in rather than results.
02Quality, SEO and performance
3. How will you make sure the site is fast and passes Core Web Vitals?
Speed is a ranking and conversion factor, and it's designed in, not bolted on afterwards. A partner who takes performance seriously will talk about it unprompted — image handling, code weight, the current thresholds. One who treats it as a later problem will hand you a slow site and an upsell.
4. If this is a redesign, how will you protect my existing Google rankings?
This is where redesigns most often go wrong. The right answer involves inventorying the current site, mapping and redirecting URLs, and preserving ranking content — the discipline we lay out in protecting your rankings through the build. "We'll just build the new one" is not an answer; it's a risk.
5. Will the site be built to be found — and to convert?
A website should do a job. Ask how they'll make sure it's discoverable (structured properly for search and, increasingly, AI answers) and how it's designed to turn visitors into enquiries. A partner who only talks about how it will look is building you a brochure. You want a site that actually generates leads.
6. How will you handle accessibility and mobile?
Most of your visitors are on a phone, and accessibility is increasingly a legal as well as an ethical expectation. Both should be assumed, not offered as extras. If mobile is an afterthought in the conversation, it'll be an afterthought in the build.
03Process and communication
7. How will we work together, and how often will I see progress?
You want to know the shape of the project before it starts: the stages, who your point of contact is, how decisions get made, and how you'll review work along the way. Vagueness here becomes silence later. A clear process is the single best predictor of a smooth project.
8. Can I see work you've done for businesses like mine?
Not just a gallery of pretty screenshots — real, live sites you can visit, ideally in a similar field or of a similar scope. Ask what the goal of each was and whether it met it. How a partner talks about past work tells you how they'll talk about yours.
9. Who actually does the work?
It's fair to ask whether the people you meet are the people who'll build your site, or whether it's handed to a team you'll never speak to. Neither is automatically wrong, but you deserve to know, so the communication you're promised matches the communication you'll get.
04Timeline, support and cost
10. What's the realistic timeline — and what would delay it?
A confident partner gives you a timeline and names the things that could push it: content that arrives late, rounds of feedback, third-party integrations. Someone who promises a fast launch with no caveats is either inexperienced or managing your expectations rather than the project.
11. What happens after launch?
A website isn't finished at launch — it needs updates, security, monitoring, and fixes. Ask what support looks like, what it costs, and what's included versus billed. A partner who plans for the life of the site, not just its birth, is thinking about your business; we explain why in what happens after launch.
12. What's the total cost — everything included?
Get the whole picture: design, build, content, third-party services, and the ongoing costs of hosting, licences, and support. The cheapest quote is often the one with the most left out, and the gap surfaces as invoices later. A trustworthy partner would rather tell you the real number now than surprise you with it in three months.
05Frequently asked questions
What's the most important question to ask a web development agency?
"Will I own the website, the code, and the accounts?" Ownership determines whether you're building an asset you control or renting one you can be locked out of. Everything else — quality, support, cost — matters, but a lack of ownership can undo all of it.
How do I know if a web development agency is trustworthy?
Trustworthy partners answer awkward questions plainly, show real live work, are transparent about total cost and what happens if you leave, and plan for the site after launch. Evasiveness about ownership, cost, or exit is the clearest warning sign — more telling than any portfolio.
Should I choose the cheapest web development quote?
Rarely. The lowest quote is often the one with the most excluded — content, SEO, performance, support, third-party costs — which reappears as extra invoices. Compare quotes on what's actually included and the total cost of ownership, not the headline number.
How long should a business website take to build?
It depends on scope, but a straightforward business site is typically a matter of weeks, and a larger or custom build longer. More important than the number is whether the agency can explain what drives it and what would cause delay. Beware anyone promising a complex build unrealistically fast.
06Where this leads
The right questions do two jobs: they tell you whether a partner is a good fit, and they tell you how that partner thinks — about ownership, about your customers, about being honest when the answer is inconvenient. A partner who welcomes these questions is usually one worth hiring.
We wrote this the way we'd want to be interviewed, because it's how we work: you own what we build, we design for search and conversion, and we're around after launch. See how we work across every stage, and when you're weighing your options, start a conversation with our team — awkward questions welcome.
