Pick the closest one. It decides which of the next questions you actually see — most people skip about a third of them.

Roughly is fine. If it turns out to be something else once we have talked, that is a normal outcome.

The problem, not the solution. What is actually happening today is more useful to us than what you think should be built.

Who sits in front of this thing, and roughly how many of them.

The question most briefs never answer. It changes what we would build first more than any feature list does.

Including the parts you are not proud of. A spreadsheet doing a system's job counts, and tells us a lot.

Anything you leave as not needed, we will assume is out of scope for now.

We will tell you straight away what we think of the date.

Not so we can spend it. So we can tell you honestly whether the thing you have described can be built for it.

The single best predictor of whether a project goes smoothly. We ask everyone.

Your copy of the brief goes to this address, and so does our reply — usually within one working day.

The only field we insist on. Everything above is optional — a half-finished brief is still worth sending.