# A brief for the software you need

> Six steps: who will use it, what it keeps, how the work flows, what it talks to, what limits it and where the data is today. At the end you get a phased brief and the questions for the first call.

## How the brief is put together

The six steps become a structured brief. Phase 1 is the step you marked as the one that hurts most. Each phase gets a relative size (small, medium or large), worked out from the number of data types, steps, connections and the data move by one fixed table. The risks and the questions for the first call come from your answers. Everything happens in your browser.

## What people ask

### What is a software brief?

A description of the program before anyone writes it: who uses it, what data it keeps, how the work flows, which programs it talks to and what limits it. A supplier sizes the scope from it.

### Do I need one before I ask for a quote?

It helps. With it, the first call is about your process rather than general questions, and every quote is made from the same description.

### Why is there no timeline or price?

Because both depend on the scope, which becomes clear after the call. The builder shows a relative size for each phase (small, medium or large) so you can see the order of work.

### What do you do with my description?

If you send it to us, we read it and write back with the questions for the first call. Until you press Send, the description stays in your browser.

Page: https://tnb-tech.com/en/software-brief/