Write a brief the AI can actually use
Paste the raw client material rather than a tidy summary, and fill in the four optional fields.
Who this is for: Anyone creating a project from a client enquiry.
Paste the raw material
The brief field is designed for whatever the client actually sent. Email threads, meeting notes, a Slack export, a bulleted wish list. Do not summarise first: summarising removes the ambiguity the clarifying questions are there to find.
The four optional fields
| Field | Why it changes the output |
|---|---|
| Client name | Appears on the proposal as Prepared for, and is included in the frozen snapshot behind a public link. |
| Project type | Steers the shape of the scope, for example web app versus mobile app versus API work. |
| Budget range | Gives the model an anchor. Without one it tends to produce a mid-market number that may be far from your market. |
| Deadline | Feeds the timeline section and the payment milestones. |
What not to paste
- Personal data about the client's staff that the project does not need. It is transmitted to a model provider the moment you generate.
- Credentials, API keys or access tokens.
- Your internal cost base, if you would not want it appearing in an AI-drafted sentence you later forget to delete.
Related
- Clarifying questionsByteflare generates the questions a competent consultant would ask before quoting, and your answers are what make the scope specific.
- Scope Creep DetectorA free public tool that checks a client brief for vagueness and underquoting traps before you commit to a price.
- Privacy, data and AIGenerating a scope sends your brief to a third-party model provider. This page explains exactly what leaves Byteflare and what is kept.