Notes
Guidance for people commissioning software
Short answers to the questions that decide whether a project goes well, whoever you hire.

Writing a brief
How long should a first brief be?
One page is plenty. Describe the problem in your words, who it affects, what you do today and why that is no longer good enough. Avoid specifying screens or technology at this stage.
Should we include a budget?
A range is genuinely helpful. It lets a supplier suggest the right size of solution rather than guessing. Stating a range does not oblige you to spend it.
What if we do not know what we need?
Then the first piece of work should be a specification, not a build. Be wary of anyone who quotes a fixed price for an unclear requirement.
Ownership and risk
Who should own the code repository?
Your organisation, from the first day. The supplier should be a collaborator on your account, not the other way round.
Who should own the hosting account?
Again, you. A supplier can manage it, but billing and administrator access should sit with you so that a dispute cannot take your system offline.
What is a realistic first version?
The smallest thing that does one complete job for real users. Everything else is a later increment.
Choosing a supplier
What should we ask a prospective developer?
Who exactly will do the work; how you will see progress; what happens if they become unavailable; how changes are priced; and what the handover will include.
Is cheapest ever right?
Sometimes, for a clearly specified, low-risk piece of work. For anything uncertain, the cost of a misunderstanding usually outweighs the difference in day rates.
Should we get a review before hiring?
If you are inheriting an existing system, yes. An independent review gives you a baseline and makes quotes comparable.