Send the same one-page idea to four software suppliers and you will receive four quotes that cannot be compared, because each supplier has had to guess what you meant and each has guessed differently. The cheapest is usually the one that assumed the least. A proper brief removes the guessing, so that the differences between the quotes come from the suppliers themselves. It does not need to be long or technical, and it is best written by the people who know the business.

What Goes in the Brief

  1. The problem, in a paragraph. What is going wrong today, who it affects and what it costs you, in your own words and without naming a solution.
  2. How the work is done now. The steps, the people and the tools involved, ideally as a map of the process.
  3. What must be true when it is finished. Outcomes you could check, such as "a customer can reorder without phoning us", in place of a list of features.
  4. The numbers. How many users, customers, orders or records there are, how fast they are growing and when the busy periods fall.
  5. What it has to connect to. Every existing system that must exchange data with the new one, and who looks after each.
  6. The constraints. Where data must be held, which languages and devices are needed, and any regulation that applies to you.
  7. What is out of scope. The things you have decided to leave for later, so that nobody prices them in or leaves them out by accident.
  8. What you will provide. The people who will make decisions, the time they can give and the access a supplier will have.
  9. How you will choose. What matters most to you and in what order, so that suppliers answer the question you are really asking.

Describe the Problem and Let Suppliers Propose

The commonest mistake is to write the brief as a specification, listing screens and buttons. That tells suppliers to price your design, which may not be the best one, and it hides the differences in thinking that you most want to see. Describe the problem and the outcome, and ask each supplier how they would get there. The answers will tell you more about who understands your business than any number of case studies.

Ask Every Supplier the Same Questions

Ask every supplier forWhy it lets you compare
What is included and what is excludedTwo quotes with the same total can cover very different amounts of work
The assumptions behind the priceAn assumption that turns out to be wrong becomes an extra charge later
Who will do the work, by nameThe people you meet are not always the people who build it
What you will see during the buildWorking software shown regularly reveals problems while they are cheap to fix
Who owns the code, the hosting and the accountsYou should be able to leave with everything you paid for
How changes are pricedEvery project changes, so the method matters more than the first figure
What happens after launchSupport, hosting and further development should be priced now and never left to be discovered

Give Everyone the Same Information

Send the brief to every supplier on the same day, set one closing date and share the answer to any question with all of them. If one supplier learns something the others did not, that quote is no longer comparable with the rest. Offer each the same amount of time with the same people as well, because a supplier who has seen the operation will always write a better proposal than one working from a document.

Lay the Quotes Side by Side

When the quotes arrive, put the answers to each question into one table before looking at any totals. Differences in scope and assumptions usually explain most of the difference in price, and once those are levelled the real choice becomes visible. Where one quote is far below the others, find out what it leaves out before treating it as a bargain. Our guide to choosing a software engineering partner covers what to weigh from that point on.

Three Things That Spoil a Comparison

A budget kept secret

Suppliers who do not know your range will guess at it, and you will receive proposals for three different sizes of project.

A brief from one department

If operations, finance and IT have not agreed it, the disagreement will surface during the build, when it costs the most.

No decision-maker named

Suppliers price the risk of slow decisions, so say who decides and how they can be reached.

BY BANKS helps businesses write the brief, weigh the responses and decide what to build, buy or leave alone through our consultancy, including for projects we will never build ourselves. If you have quotes on your desk that you cannot compare, get in touch and we will help you level them.