7 questions to ask before you hire someone to build software

The seven questions

1. Is the price fixed, or an estimate? An estimate can grow. If it's fixed, ask exactly what's included and what counts as a change.
2. When will I see something working? A date for a first working version, not a date for "the designs". Seeing it early is how you catch misunderstandings cheaply.
3. Who owns the code once I've paid? Under UK law the person who writes the code is usually the first owner of the copyright, not the person who pays. Ownership only moves to you if the contract says so in writing.
4. Where will it be hosted, and who pays for that? Get the monthly or yearly cost in writing, and whose name the hosting account and domain are in.
5. What happens after launch? Who fixes bugs, how quickly, and at what cost? Is there a support plan, or is it charged by the hour?
6. Is it accessible and GDPR-compliant? The current web accessibility standard is WCAG 2.2, and level AA is the usual target. Public sector bodies, including councils, are generally required to meet WCAG 2.2 AA. For GDPR, if the developer will host or handle personal data for you, UK GDPR requires a contract setting out how they process it.
7. If we part ways, can someone else take it over? That means you get the code, the logins and some basic notes on how it's set up.

What good answers sound like

Good answers are specific and written down. "£X, fixed, for these features." "You'll see a working version on this date." "The code is yours once the final invoice is paid." "Hosting is about £Y a month, in your name."

Vague answers aren't always a warning sign. Sometimes a supplier genuinely needs more detail from you. But they should be able to tell you what they need to know to give a firm answer.

The two that matter most

Questions 3 and 5 are the ones that cause the most trouble later, because nobody thinks about them until something goes wrong.

If you don't own the code, you may not be able to move to another developer. If support isn't agreed, a small fix after launch can turn into a surprise invoice.

A simple way to compare quotes

An illustrative example. Two quotes for a booking system:

• Quote A: £2,000 estimate, hosting "to be confirmed", support charged hourly.
• Quote B: £2,600 fixed, hosting £15 a month, support £25 a month.

Quote A looks cheaper, but you can't compare it yet. Ask for its hosting and support costs and whether the £2,000 is fixed. Then add up the first two years for each. That's the real comparison.

Before you sign

• Get the answers to all seven in the written quote or contract.
• Check there's a clause assigning the code to you.
• Check hosting and domain accounts will be in your organisation's name.
• For larger contracts, have someone with legal experience read it.

For our own answers to these questions, see how we work.

Sources

• GOV.UK: ownership of copyright works
• W3C: Web Content Accessibility Guidelines (WCAG) 2.2
• GOV.UK: accessibility requirements for public sector websites and apps
• ICO: when is a controller-processor contract needed

Related

• How we work
• Our terms of business
• How much does an app cost in the UK

← Card payment fees explained for UK halls, clubs and charitiesWho owns your app's code? It isn't always you →