Projects Overview
Projects is BuildBetter's roadmap hub. Every project is a tracked item that brings together the customer signals driving the work, the ARR on the line, the people and PRs delivering it, and a live status view — so you can answer five questions on one screen:
- What should we work on? — Inbox and saved review views
- What are we currently working on? — This week + Active
- Who is working on what? — assignee avatars on every row
- Why are they working on it? — signals, customers, and trend rollups
- What's the status / what's next? — substatus chips, blockers, and next actions
Where Projects Live
Projects often start life as tracked items in Inbox. When you promote an Inbox item, it moves to /projects with in_triage: false and a status of in_progress. From that point on, the Projects Hub is its home.
Info: Projects is gated by the
projectsfeature flag. If you don't see/projectsin the sidebar, contact your workspace admin to request access.
Core Concepts
| Concept | What It Means |
|---|---|
| Project | A tracked item with in_triage: false. Has a title, type, priority, status, stage, optional area, and links to signals/calls/PRs/tickets. |
| Stage | Ordered lifecycle position: Triage → Scoping → In progress → In review → Ready to merge → Shipping → Released → Stable. Drives which rail cards appear. |
| Status | Real-time substate (Drafting, In review, Ready to merge, Blocked, Shipping, Done). More granular than stage. |
| Priority | P0, P1, P2, P3 — urgency for sort and triage. |
| Area | Optional taxonomy path (e.g., Features > Search > Filters). Determines where the project shows up in Areas view. |
| Initiative | A guided grouping that spans multiple projects and can roll up related project, company, person, and metric results. |
| DRI / Assignee | The owner. Avatars carry a small provenance badge — L for Linear-author match, G for GitHub PR author, · for manual. |
| ARR rollup | Cumulative ARR from every distinct customer company linked to the project's signals. |
What's on the Pages
-
Mine / All / Areas views, list and kanban layouts, the AI Roadmap banner, and how taxonomy areas and initiatives organize work.
-
The two-column detail page: timeline + signals on the left, rail cards (Status at a Glance, Rollup, Integration Issues, People & Signals, Post-Release Monitor, Close the Loop) on the right.
-
AI Roadmap clustering, Similar Projects detection, Suggested Signals, AI status suggestions, and the project rollup.
-
Create a project, update scope from a call, ship a status update, attach signals and calls, run close-the-loop after release.
Initiatives and Evidence
Projects now include richer setup and evidence workflows:
- Guided initiative setup helps teams configure initiative metrics and link projects during creation.
- Initiative rollups summarize results from related projects, companies, and people.
- Evidence suggestions recommend calls, signals, tickets, PRs, and other linked items that may explain why the project matters.
- Evidence previews make it easier to inspect linked items before attaching them.
- Approved evidence routing keeps project rollups focused on reviewed, relevant context.
How Projects Connect to the Rest of BuildBetter
- Inbox → promote a tracked item, PR, ticket, topic, or decision to make it a project
- Signals → drive priority via volume, ARR, and trend; attach to projects to record customer demand
- Calls → link a call and attach its signals in one move
- Linear / Jira → attach tickets via Integration Issues; assignees auto-populate from Linear author mappings
- GitHub → linked PRs feed the Status at a Glance card, trigger stage transitions, and roll up into project metrics
- Knowledge → close-the-loop drafts and project rollups can be exported to knowledge pages
Tip: The list page subscribes to your org's tracked-item event stream and live-updates as PRs merge, statuses change, and signals attach. No manual refresh needed.