PLANNING & MAINTENANCE · 3 MIN READ
How to Write a Website or App Brief That Produces a Useful Estimate
Write a practical website or app brief with users, outcomes, workflows, constraints, and acceptance examples instead of an unprioritized feature list.
A useful project brief gives a developer enough context to ask better questions. It does not need to prescribe every database table or interface component.
Start with the work that should improve and the people who will use the result.
01
Describe the current situation
Explain what happens today, which parts cause difficulty, and what systems are already involved. Include a representative example rather than relying only on broad goals such as “modern” or “easy to use.”
For a hypothetical service business, the problem might be that staff copy appointment requests from email into two systems and cannot see which ones are confirmed. That is more actionable than requesting “a dashboard with automation.”
Identify what works well enough to preserve. A rebuild should not remove a useful workflow simply because it is old.
02
Name the users and decisions
List who submits information, reviews it, changes it, and needs reports. Explain how permissions differ. A customer-facing portal and an internal admin screen may share data while requiring very different experiences.
Write one short journey for each important user. Include the outcome and an exception: what happens if information is missing, a request is rejected, or an external system is unavailable?
03
Prioritize the first release
Separate essential behaviour from useful later additions. State why each essential feature matters. A smaller release can still be complete if it supports one valuable journey from start to finish.
Avoid calling every feature a must-have while also asking the developer to reduce the scope. The trade-off needs a business owner who can decide what is deferred.
04
Include constraints early
Mention existing platforms, available APIs, content ownership, expected data volumes, languages, hosting limitations, and dates tied to real events. Explain budget boundaries if you can; they help frame realistic options.
Include accessibility and mobile use as requirements rather than late visual checks. W3C's preliminary accessibility guidance provides examples of issues to consider, such as headings, contrast, keyboard access, and form labels. It is a starting point, not a complete compliance assessment.
05
Define evidence of completion
Provide examples of what a successful result looks like: a user can submit a request, a reviewer can approve it, the correct record appears in the destination, and both can see its state.
State what needs further investigation. An honest unknown about an external API is more useful than a confident requirement built on an assumption.
The resulting brief can be a few focused pages. Its value comes from clear priorities and observable outcomes, which allow a developer to explain scope, risks, and the work needed to produce a responsible estimate.
06
Discuss the implementation
Explore custom web applications or discuss your project.
KEEP EXPLORING
Sources & further reading
Official documentation for the topics discussed. Check implementation details against the versions and services used by your project.
PUT THE IDEAS TO WORK
Need help with
the implementation?
Explore the approach and scope for custom web applications.
Explore the service