AI project brief builder
Answer questions about the work, the systems it touches and what success looks like, and get a one-page brief you can share with any partner.
Early days. Fill in the sections below before sending this to a partner.
- What the core problem is, in your own words.
- Who does this work today.
- How often the work happens.
- What kind of help you are looking for.
- Which systems or data sources are involved.
- Where the information for this work lives today.
- What success looks like in practice.
- How you will measure success.
- Whether there are constraints, such as data residency, a fixed budget or a fixed deadline.
- Who the business owner is for this project.
- Whether a technical or data contact is available.
- When you would want this working.
Your brief
Summary
Project: not named yet. The kind of help needed is not chosen yet.
The problem
Not answered yet.
How the work runs today
Done by: Not named yet. Frequency: Not given.
Systems and data
Systems involved: Not named yet. Where the information lives: Not given.
What success looks like
Not answered yet. Measured by: Not decided.
Constraints
No constraints noted yet.
People
Business owner: Not named yet. Technical or data contact available: Not given.
Timing
Not given yet.
Want a second read on this before you send it out? Share it with us.
How the brief is checked
- The brief is built directly from your answers: each section states what you entered, in plain sentences, with "Not answered yet" where a field is empty.
- Completeness counts 12 fields across 7 sections. Constraints is not counted toward the percentage, because a genuinely empty answer there is not a missing one, though it still appears under what a partner will ask.
- A choice such as "Not decided yet" or "Not yet" counts as answered for the percentage, but it is still listed under what a partner will ask, because it flags a decision still to make.
- 85% and above reads as ready to send. 55% to 84% is close, with a few gaps to fill. Below that, start with the sections that are still empty.
- The structure follows our guide to writing a requirements brief a development partner can use, shortened into a first draft any partner could scope from.
What to do next
Carry this into the next step, the full guide or the service behind it.
Have a brief ready?
Send it to us. We will tell you what we would need to know before anything is scoped.
Request a discovery call