Explain the business goal in one sentence
Before a feature list, describe the intended outcome. Receiving better enquiries, speeding up a task and validating a product idea are different goals. If there are several, define the priority for the first release. This creates a common basis for later design and engineering decisions.
Describe the user and their core task
Write down who will use the product, on which device and in what context. Are they finding information, completing a transaction or managing an account? Describe where the task begins and ends instead of guessing the number of screens. Record uncertain assumptions as questions to validate.
List content and existing assets
Brand files, copy, photography, translations and existing URLs affect the scope. For a redesign, identify what should be preserved and which addresses matter. When sharing reference sites, explain the navigation, visual approach or interaction you like. A reference gives direction, not permission to reuse another brand’s content.
Make dependencies and constraints visible
Note payment, CRM, inventory, email or AI services from the start. API availability and existing account status can change the scope. Share a budget range and target date if known, treating them as planning inputs rather than delivery promises. Never include passwords or secret keys in a brief.
Separate the first release from later ideas
Distinguish essential needs from features that can come later. End the first meeting with open questions, owners and a clear next review. A useful brief does not contain every answer; it exposes the right questions. Once scope is clear, a proposal and delivery plan can be prepared more reliably.
Further reading
Google — Core Web VitalsLet’s bring this idea to your product.
Define your project goals and technical needs with us.
Let’s talk about your project

