What to include in a website or software project brief

Explain the business goal and current situation

Start with the change you want: a clearer website, online sales, a customer app, or less manual administration. Describe how the task happens today and what makes it difficult. You do not need to choose the framework or prepare a detailed technical specification.

Name the intended users and one or two core journeys. Explain whether the project is a new product, an improvement, or a replacement. Share links to the existing experience where relevant.

Separate essentials from later ideas

List what a first release must let someone accomplish. Keep later features in a separate list and identify assumptions that need investigation. A short, complete journey is more useful for estimation than a long feature list with no priorities.

• Business goal and intended users
• Current process and main problems
• First-release journeys and priorities
• Existing website, software, and data sources
• Required integrations and account ownership
• Content and design responsibilities
• Budget context and desired timing
• Definition of a successful launch

Make constraints visible

Mention fixed launch dates, legacy systems, permission needs, regional payment requirements, and dependencies on other teams. Identify who approves scope and who will provide content, access, or domain knowledge. Share an initial overview rather than credentials or production records.

Ask for an estimate with assumptions

A proposal should explain deliverables, exclusions, milestones, change handling, ownership, and ongoing costs. If key workflows or integration access are unknown, a discovery phase may be needed before a reliable implementation estimate.

You can use the checklist above as the structure for your inquiry. If budget or timing is uncertain, say so: the first conversation can help distinguish a smaller release from a project that needs more preparation.