How to brief a software development agency: a founder's checklist

What to include

• The business problem, and what it currently costs you.
• The outcome that would make the project a success.
• Who will use it, and what they do today instead.
• Systems it must work with, and who controls them.
• Hard constraints: budget range, deadline, compliance, existing contracts.
• What is explicitly out of scope for the first release.

What to leave out

Avoid prescribing the technology or the screen layouts unless you have a real constraint. Describing the outcome instead lets suppliers offer a cheaper route you had not considered — and makes their thinking easy to compare.

Sharing your budget

A range is not a weakness. Without one, suppliers guess, and you receive proposals for different projects. With one, they tell you what is achievable for that money.

How to compare responses

Look for written assumptions, a first phase with a clear outcome, named people doing the work, a plan for who owns the code, and honesty about what they would cut if the budget dropped. Quotes without assumptions are not really quotes.

What a good brief contains

A useful brief explains the problem before the solution. Describe who the users are, what they struggle with today, what success would look like in six months and any constraints such as deadlines, budget range, systems that must be kept and compliance needs.

Include examples: screenshots of current tools, sample documents, competitor products you like or dislike and why. These help an agency understand the job far faster than a long feature list.

• The business problem and who has it.
• What success looks like, with measures.
• Must-have versus nice-to-have features.
• Existing systems and data to integrate.
• Budget range and key dates.

Sharing a budget range helps you

Many businesses hold back their budget, worried it will be spent in full. In practice, a range lets an agency propose the right approach for your money, whether that is a lean first version or a more complete product. Without it, quotes are hard to compare because each supplier is guessing at a different scope.

A good agency will tell you honestly if your budget does not fit your goals and suggest what to cut or phase.

Questions to ask every agency

Ask how they run discovery, how often you will see working software, who will actually do the work, how they handle changes in scope and what support looks like after launch. Request references from clients with similar projects and check you will own the code.

Pay attention to the questions they ask you. Agencies that challenge your assumptions and ask about users and outcomes are usually better partners than those who simply agree to everything.