A pre-engagement checklist covering tech stack, ownership, CMS access, maintenance, and scalability. Empowers clients to make smarter decisions before signing anything.
After working in web agencies for years — and building one — I've seen both sides of the client-agency relationship.
I've seen agencies charge clients for monthly "maintenance retainers" for sites that needed zero maintenance. I've seen clients handed a website they couldn't access, update, or understand. I've seen contracts that locked businesses into proprietary systems with no exit path.
I've also seen excellent agencies that operate with complete transparency, build genuinely transferable assets, and set clients up to succeed independently.
The difference between these experiences is often visible before you sign anything — if you know what to ask.
Here are the 8 questions I'd ask any web agency before handing over a budget.
1. "What platform will you build the site on — and why?"
This is the first question because the answer shapes everything else: your ability to edit the site, the maintenance costs, the performance, the future flexibility.
Acceptable answers include well-established platforms with clear rationale: Webflow for marketing flexibility, WordPress for certain CMS needs, custom build for specific application requirements.
Red flags: platforms you've never heard of that "we've developed ourselves," or vague answers that avoid commitment. Also: defaulting to WordPress without discussing whether it's the right fit, simply because it's what they know.
The agency should be able to explain why this platform serves your business needs — not just their development preferences.
2. "Will we own the website and all its assets?"
You should own your website. Your domain, your code, your content, your design files. Completely.
Some agencies retain ownership of design files. Some build on platforms that can't be migrated. Some use proprietary themes that belong to them, not you.
Ask explicitly: if we ever want to move agencies, what happens? Can we take everything with us? Get the answer in writing.
3. "How will we be able to edit content after launch?"
Can your marketing team change a headline, update a blog post, add a team member, change a price — without contacting the agency?
If the answer is "we'll handle updates for you" without also offering a self-service option, that's a dependency they're building in by design. It creates recurring revenue for them at recurring cost to you.
You should be able to make routine content changes yourself. Ask to see the editing interface before you sign.
4. "What does your handover process look like?"
What happens at the end of the project? Do you get a training session? Documentation? Access to all accounts? A structured walkthrough of how to maintain the site?
Or do you get a ZIP file and a wave goodbye?
A good agency invests in making clients capable of running their own site. The handover is where you see whether that's genuinely part of their process or an afterthought.
5. "What's your approach to SEO during the build?"
A site can look perfect and still be invisible on Google if the technical foundations aren't in place.
Ask specifically about: URL structure, page titles and meta descriptions, canonical tags, XML sitemap, page speed optimisation, image compression, and structured data where relevant.
This doesn't require a deep technical conversation — but the agency should be able to answer these questions confidently. If SEO is "something we can add on later," that's a yellow flag.
6. "What does ongoing support or maintenance cost — and what does it include?"
There are legitimate reasons to have an ongoing agency relationship post-launch. New features, design updates, strategic campaigns, regular CMS work.
But there are also agencies who charge monthly retainers for sites that run themselves. Know what you're paying for.
Ask for a clear breakdown: what's included at what cost, what's handled by your team, and what falls outside the retainer. No vague "support packages."
7. "Can we see examples of sites you've built at a similar scale?"
Not just portfolio links — actual conversations. What challenges came up on this project? What would you do differently? Can we speak to the client?
An agency confident in its work will welcome this. One that's less confident will deflect or show you only their best moments without context.
8. "What happens if we're not happy with the result?"
Revision rounds, approval stages, escalation processes — how does the agency handle disagreement?
Look for: clear milestones, defined revision rounds, a process for resolving disputes, and an attitude of genuine partnership rather than delivery-and-invoice.
The Meta-Question
Beyond the specific answers, pay attention to how the agency responds to these questions overall.
Do they answer directly and confidently? Do they welcome scrutiny? Do they seem more interested in your business outcomes or in selling the engagement?
The best agencies treat this due diligence as a positive signal — it means you're taking the decision seriously and they're more likely to have a productive working relationship. The worst agencies find it uncomfortable.
That reaction tells you a great deal about the partnership you're about to enter.