Planning · By AnCasper
What to put in a project brief
A useful brief describes the outcome, the audience and the constraints. You do not need to write a technical specification.
Start with the job the project needs to do
Describe the problem in ordinary language. For a business site, that might be helping visitors understand a service and send an enquiry. For a community, it might be helping new players choose a server and join. The goal helps decide what belongs on the page.
Explain who will use it
Include the main audience, their questions and what they need to do next. An internal dashboard and a public landing page need different levels of explanation and navigation.
Show what exists already
Share the current website, brand files, platform or server version. List integrations that must keep working. Say who will provide copy, photographs and product information. Never include passwords in a first enquiry.
Give a budget range and timing
A range helps decide whether to improve an existing setup, build a small first version or plan a larger project. Separate a real launch deadline from a preferred date. Mention any event or dependency behind the deadline.
Include a few references, with reasons
Two or three useful examples are better than a long list. Explain what you like: the navigation, tone, page structure, colour or interaction. References guide the discussion; they are not a request to copy someone else’s work.
Ready to discuss the work?
Send a project enquiry.
The form asks what you need, your budget, timing and contact details.
Describe your project