BuildBetter Docs

Common Project Workflows

These are the common day-to-day flows in Projects.

Create a Project

Most projects start in Triage and get promoted, but you can also create one directly.

1. Click 'New project'

The sparkles-icon button in the top-right of /projects.

2. Fill in the form

Title (required), description, type (auto-selected, required), optional start/end dates.

3. Submit

Creates a tracked item, promotes it immediately (so it skips triage), and navigates to /projects/{id}.

Promote from Triage

The more common path. In Triage's Signals tab:

1. Open a tracked item

Selecting a row in the Signals tab opens its detail in the right pane.

2. Click 'Promote to project'

The action button in the detail footer.

3. Item appears in /projects

Status flips to in_progress, in_triage flips to false, and the item disappears from the Triage list.

You can also bulk-promote — select multiple rows in the Signals tab, then click Promote N. See Promote & Merge.

Calls bring in real customer context fast.

1. Open the Link a Call modal

From the project's right rail, click Link a call (phone icon).

2. Search or browse

Search by title, or leave the field blank to see recent calls.

3. Pick a call

Click any row. All signals from that call auto-attach to the project, and you'll see a toast: "Linked 'Call title' — attached N signals."

Find & Attach Signals

When you want to attach signals that match the project's theme:

1. Click 'Find related signals'

From the People & Signals card on the detail page.

2. Search and filter

Type a query; filter by boundary (external / internal / all) and interaction type (call, message, feedback).

3. Multi-select and add

Check the signals you want, click Add N to review. They attach in the "suggested" review state — they don't feed the AI rollup until you approve them.

Tip: The Suggested Signals banner does this automatically when a project has fewer than 5 signals — use it for a head start, then refine with Find related signals.

Update Scope from a Call

When a call surfaces a scope change, BuildBetter spots it and surfaces a diff.

1. Open the Update Scope modal

Triggered automatically when a linked call's transcript suggests a scope change.

2. Review the evidence

Left side: the quoted transcript segment with speaker and timestamp. Right side: a draft diff of the scope doc (removed bullets vs. added bullets, grouped under section headings).

3. Approve

Writes the change into the project's scoping doc.

Send a Status Update

Generate a shareable status snapshot for the team, an exec, or release comms.

1. Click 'Status update'

The send-icon button in the list page header.

2. Pick a scope

My projects / All projects / Specific initiative.

3. Pick a window

Default is 7 days; change as needed.

4. Pick an output type

Team status / Exec rollup / Release comms draft.

5. Generate and copy

The output is markdown you can click to copy and paste straight into Slack, email, or a doc.

Close the Loop After Release

When a project ships, you owe a follow-up to the people who asked for it.

1. Open the Close the Loop card

On the detail page, right rail.

2. Review the checklist

One row per linked contact: person name, company, current reply state.

3. Draft the update

Use the composer to write a short message. The same body can be sent across recipients, or you can tailor per-person.

4. Send via Slack or email

One-click per contact. A contact gets auto-marked "replied" once the assignee responds in the designated channel or thread — no manual checkboxes needed.

Merge Duplicates

If the Similar Projects banner appears with candidates:

1. Review the match

Each candidate shows a match % and title.

2. Click 'Merge'

Collapses the candidate into the current project: moves every attached signal, archives the duplicate, and logs a merge event in the timeline.

Update Metadata Inline

The rail dropdowns update fields without leaving the page:

Every change is timestamped and visible in the Timeline tab.