Sign in

Sign in with your email and password. You can change your own password from your account. A light/dark theme toggle (☀️/🌙) is in the header, and your choice is remembered.

Capture and refine an idea

1. Open Pipeline and create a new idea. Give it a title and description, and add tags. When you add a tag, the app warns you about similar existing tags to avoid near-duplicates.
2. Open the idea and use its tabs (for example Details and Scoring) to fill in the details.
3. In scoring, use the AI buttons to suggest TAM/SAM/SOM and RICE inputs. Review and adjust the suggestions, then save. The RICE score updates automatically.
4. Use the discovery chat to talk the idea through. If the AI proposes features, add the ones you want and they become feature records.
5. Change the idea's stage from its edit window. Cards on the Pipeline board are not drag-and-drop.

Work the feature board

1. Open Features and filter by app and version.
2. Open a feature to see its Details, Sub-tasks, Amendments and Comments. Save a new idea or feature before adding sub-tasks or comments.
3. To change several features at once, tick their checkboxes (or ⌘/Ctrl-click). A bar showing "N SELECTED" lets you set version, set status, or clear the selection.
4. To review changes made after a feature was specified, use the ⚠ Needs validation (n) filter.

Record an amendment

Open the feature's Amendments tab and add a summary and the change description. An amendment starts as Open. Whoever implements it marks it Implemented and ties it to the version it shipped in. If an attribution later turns out to be wrong, file a new amendment that references the old one instead of editing the finished one.

Set strategic goals

1. Open Goals and add a goal manually, or describe what you want and let the AI draft the name, objective and key results.
2. Link features to the goals they support.

Hand a spec to engineering

From the Features toolbar, open the export window to preview the file tree and Download .zip, or use Build → GitHub to commit the bundle to the app's repository. Features without a version are left out of the bundle, and the window shows how many were excluded.

Release a version

Releasing a version marks that version's features Done and activates the next unreleased version. Each app uses one of two promotion modes, set in Apps & Access:

• One-click (the default): a single confirmed Promote → Prod action merges dev to main, deploys production and releases the version.
• Gated: the same work as separate, individually confirmed steps, Merge dev→main → Deploy prod → Release version. A failed last deploy on the dev site blocks the production step.

Review adoption and satisfaction

Open Analytics to see the portfolio, or select one app to scope the figures. Use ↻ Refresh to reload; the tab shows when it was last updated. Non-production sessions are excluded from the figures by default. Admins can adjust the satisfaction prompt cadence and manage the system feature library from this tab.

Give feedback

Use the 💬 Feedback button at the bottom right to send a comment. You may also see a dismissible 1–5★ satisfaction prompt. Once you dismiss or answer it, it will not reappear on every reload.

Manage access (admins)

In Apps & Access, grant a user a role (and optionally a data scope) on an app. Granting again edits the existing access rather than creating a duplicate. Admins also manage users, teams and companies.