What to ask before you hire a web developer
A short list of questions for business owners hiring someone to build a website or app, so you know what you are paying for and what you will own at the end.
Written byMuwafaq Murad
I talk to a lot of business owners who were burned by a previous developer. The site works, mostly, but nobody can update it, the hosting login is lost, and the original developer stopped answering. Most of that can be avoided with a few questions before any work starts.
These are the questions I would ask if I were hiring someone, and the ones I am happy to answer myself.
Who will own the domain and hosting?
The domain should be registered in your name, on your account. The same goes for hosting, if possible. A developer can manage it for you, but you should be able to log in. If the relationship ends, you keep your website.
Will I get the code?
Ask where the code will live and whether you get access. A Git repository that you own or can access means another developer can pick it up later. "It is on my server" is not a handover plan.
Can I update the content myself?
Prices, photos, opening hours, blog posts: you should not have to pay or wait for small changes. Ask to see the admin panel, or a demo of one, before you agree. If every change needs the developer, factor that into the real cost.
What happens after launch?
Websites need care: security updates, backups, the odd broken form. Ask what is included after launch, for how long, and what ongoing support costs. A clear monthly plan is better than surprise invoices.
Where are the backups?
Ask how often backups run, where they are stored, and whether anyone has ever tested restoring one. A backup stored on the same server as the site does not help much if that server fails.
How will we work together?
How often will I see progress?
Is payment split into milestones tied to work I can see?
What exactly counts as a change that costs extra?
Who do I contact if something breaks on a weekend?
Can I see similar work?
Ask for live examples close to what you need, not just screenshots. Open them on your phone. Check that they load quickly and that the contact form works. If possible, ask one of their past clients how it went after launch, not just during the build.
A good sign
A good developer asks you questions too: who your customers are, what they need to do on the site, and how you will know it is working. If someone gives you a price before asking anything about your business, they are guessing.