What is Product Context?
Review and edit the product and company information Brief uses to understand your workspace.
Product Context is the workspace page for information about your product and company. It includes Product Address, the starting page Brief uses to understand your product, and fields such as Customers, Service Definition, and Business Model.
This is the place to correct the description Brief uses when it answers questions about your business. Code context tells an assistant what an implementation does; product context explains whom it serves, what the team is trying to achieve, and which tradeoffs matter.
Product context can include several kinds of knowledge: customer needs and feedback, decisions and their reasons, strategy and goals, technical constraints, and the team's development pace. The Product Context page holds the company and goal fields listed below. Related decisions, features, documents, and research live in their own workspace areas.
For example, before asking a coding assistant to add collaboration features, record who the intended customers are and any prior decision about collaboration. The assistant can then ask Brief for those facts through MCP while planning the change.
What the page contains
- Product: Product Address, such as the public page that describes your product.
- Company Context: Customers, Service Definition, and Business Model.
- Competitive Advantages: what distinguishes your product. Use Add advantage or Remove advantage to show between three and ten fields.
- Goals: your Six-Month Goal.
- Development Process: Preferred Release Frequency (Daily, Weekly, Bi-weekly, Monthly, or Quarterly), Decision Pace (1-10), Coordination Pace (1-10), Iteration Pace (1-10), Stack Profile (1-10), Process Rigor (1-10), and Engineering Team Size. These are descriptions of how your team works, not quality scores.
- Key Metrics: Top Metric #1, Top Metric #2, and Top Metric #3.
Customer feedback and past decisions are related context, but they have their own Research Signals and Decisions areas. Connect relevant sources through Integrations when that information lives in another tool.
For example, a work tracker can contribute current work, a documentation connection can provide plans, a meeting notes connection can provide research, and an analytics connection can provide usage evidence. What Brief can use depends on the providers you connect and the content those connections can reach.
Review and edit it
- Open Product Context in the workspace navigation.
- Review Product Address and the company fields. Edit the fields you need to correct or complete.
- Watch the save status: Unsaved changes, Saving changes…, and Changes saved show the current state. You can also select Save changes. If you see Changes couldn’t be saved. Check your connection and retry., select Retry.
The product address is validated and saved when you leave its field. Other edited fields save automatically after a short pause. If Brief suggests a value for a field you already filled in, your existing value is left in place for you to review.
For the product address, enter a public web address. Brief accepts an address without https:// and normalizes it when you leave the field. If the address is invalid, correct the field before saving. If a save fails, check your connection and retry; the page keeps the unsaved state visible. Editing is subject to your workspace access.
To bring more information into Brief, connect your tools. To use this context from an AI assistant, see MCP setup.