The 7 questions to ask before you sign
You've requested proposals, seen presentations, and now it's time to decide. But most proposals are difficult to compare. One agency itemises everything, another gives a lump sum. One lists hosting separately, another bundles it in. What you're missing isn't a lower price. It's a way to assess what you're actually buying.
These seven questions make that clear.
1. Am I buying a website or a process?
A website is a snapshot. A good process is what keeps that website working, current, and growing with your organisation two years from now. Don't just ask what you'll get at launch. Ask how it works afterwards. Who handles updates? How do you request changes? What if your organisation evolves?
A good website without a workable process is often just a polished front on organisational noise.
2. What's included in the proposal, and what isn't?
The cheapest proposal is often the one that leaves the most out. Content migration, SEO setup, testing, training, hosting, SSL: these all surface at some point during the project. Ask explicitly: what's included and what isn't? And if something isn't included, what does it cost if I need it later?
You're not buying a website. You're buying predictability under uncertainty.
3. Who owns what afterwards?
Domain, DNS, hosting, email configuration, analytics, CMS licences, content. Who owns what? At many agencies, everything runs on their infrastructure, under their accounts. That works fine as long as the relationship is good. But the moment you want to switch, you have a problem.
Ask before you sign: what can I take with me if we part ways? And will I get help with the transition?
4. How do changes work after launch?
The website goes live, and then the real work begins. Copy needs updating, a page needs adding, a form doesn't quite work as expected. How does that work? Is there an hourly rate? A retainer? A maintenance contract? And what's the turnaround time?
This is where most frustration arises: not during the build, but in everything that follows.
5. What about backups and security?
Everyone says they have backups. But a backup is a feeling until you've done a restore. Ask: how often are backups made? Where are they stored? How quickly can a restore be completed? And who's responsible for security updates?
6. What if I want to leave?
This is the question most agencies would rather not hear. But it's the most important one. Can you take the code with you? Can you get an export of your content? Can you transfer the domain without the agency's cooperation? Is there a notice period in the contract?
A good partnership is strengthened by a clear exit, not weakened by one. An agency that can't lose you doesn't have to compete on quality.
7. Can I speak to a reference?
Not a case study on the website. A real client I can call or email. Ask how the collaboration went, not just the end result. How was communication? Were deadlines met? And how did the agency handle setbacks or disagreements?
Seven questions. None of them are about pixels or colours. All of them are about whether you'll end up with a partner, or a problem.