Write a brief that
gets you somewhere.
You do not need a finished specification to start. A useful brief explains the problem and gives your technology partner enough context to ask better questions.
1. Explain the problem and the people
Describe what is difficult today, who experiences it and what a better result would look like. Include a real workflow example rather than only a list of requested features.
2. Separate essentials from possibilities
Identify what the first release must accomplish. Keep future ideas visible, but separate them from launch requirements so the initial scope remains manageable.
3. Document the systems involved
List current software, data sources, integrations and access constraints. Existing technology can shape both feasibility and the amount of work required.
4. Share commercial constraints
A budget range, target date and internal decision process help a partner suggest a realistic approach. Explain why a deadline matters and whether it is flexible.
5. Agree how success will be assessed
Define acceptance criteria and the evidence that will show whether the product works. Include handover, training and support expectations so launch is not treated as the end of planning.
A short brief.
A useful next step.
Tell us about your business and what you want to achieve. Your enquiry goes into our project review queue.
- Discuss the right website or product approach.
- Clarify your scope, budget and timing.
- Receive a proposal for the agreed requirements.
Big ideas deserve
a brilliant next step.
A new product. A complex challenge.
A business ready for more.