Why ask at all?
Most website problems aren’t technical. They come from assumptions nobody checked at the start: who owns the website’s accounts, what “support” actually includes, or what happens when you want a small change in two years’ time.
These questions take ten minutes to ask. A good developer or agency will be glad you did, and their answers will tell you more than any portfolio.
About the work
1. What do you need from us, and when?
Content, photos, logins and decisions are the usual cause of delays. A good answer is specific: who provides what, and by when.
2. What exactly is included?
Ask for a list of pages and features, how many rounds of changes are included, and what counts as extra. If it isn’t written down, assume it isn’t included.
3. How will we be able to update the site?
Ask them to show you, not just tell you. You should be able to make everyday changes (text, images, a new page) without filing a ticket.
4. How do you make sure it works for everyone?
Look for mentions of mobile testing, page speed and accessibility (WCAG). A fast, accessible site is better for visitors and for search.
Ownership and access
5. Will we own all the accounts?
The website’s address, hosting and any services it relies on should be registered in your name, in accounts you control. This is the single most important question on the list.
6. Who will own the website and its code?
Make sure you can take the site elsewhere if you need to, along with any design files, images and content.
7. Where will it be hosted, and who has the logins?
You should have your own access to hosting, email and any third-party services, even if the developer manages them day to day.
After launch
8. What happens after the site goes live?
Who looks after updates, security and backups? Is that included, a monthly fee, or down to you? Ask how quickly they respond if something breaks.
9. How will we know it’s working?
A good answer covers how enquiries reach you, how you’ll see visitor numbers (ideally without invasive tracking), and how the site is monitored.
10. What will you leave us with?
Look for documentation: logins, how things are set up, and how to make common changes. It should never all live in one person’s head.
Cost
11. What will this cost over three years, not just to launch?
Hosting, licences, plugins, support and renewals add up. A clear three-year view avoids surprises and makes quotes easier to compare.
12. What could make it cost more?
An honest developer will name the risks: unclear content, new features mid-project, or integrations with other systems.
What good answers sound like
Good answers are specific, written down and unhurried. Be cautious if you hear “don’t worry about that”, if key accounts will be set up in their name rather than yours, or if nobody can tell you what happens after launch.
If you’d like an independent second opinion on a proposal or quote before you sign, that’s exactly the kind of thing our technical advice covers.