How to brief a software team in one page

You don’t need a 40-page specification to start. You need six clear answers.

A useful brief answers six questions: what problem you’re solving, who has it, how it’s handled today, what success looks like, what must be true (deadlines, budget, regulations), and who decides.

Notice what’s missing: a feature list. Features come once the problem is understood. Starting with features often means building the wrong thing well.

Fit those six answers on one page and any good team can give you an honest estimate and a sensible first step.