Every team ships
like your best team

Everyone, and every agent, working from one product strategy

Book a demo (opens in new tab)

Trusted by

  • Eragon
  • Decisional
  • Presia
  • Aurium
  • Hyperspell
  • Fearn
  • Moda
  • Entelligence AI

Backed by

  • Character Capital
  • a16z speedrun
  • Trust Fund
  • Upside Partnership

We spent all this money, and I’m in the same goddamn meetings.”

A CTO · ON THEIR AI ROLLOUT

Every team rolled out Claude, Codex, Cursor, and Copilot. Engineers got faster. Everything around the code got heavier: more status reporting, more compliance review, more coordination calls, more “what did we agree on?”

Read the essay

PDLC ≠ SDLC

The product development lifecycle is not the software development lifecycle. Coding agents sped up one stage. The other six still run on meetings.

The seven stages of the product development lifecycle, where coding agents work and what Brief reads at each
Stage 1OrganizationWho buys, and why 2GoalsWhere to be next 3RoadmapWhat to build 4RefinementLegal, research 5SpecificationTasks and specs 6BuildCode, QA, release 7Go to marketSales and support
Coding agents Writes codeClaude Code, Cursor
Brief DOC-118ICP and positioningConfluence OKR-Q4Q4 company goalsSlack RM-3Checkout v2 in Q4Jira D-241Seat-based pricingSlack CHK-412Per-seat pricing APIJira !1182Price API changeGitLab DOC-131Checkout v2 launchConfluence
THE LIFECYCLE Every stage loops. A new customer, competitor, or fire drill sends you back to step one.
  1. 01OrganizationDOC-118ICP and positioningConfluence
  2. 02GoalsOKR-Q4Q4 company goalsSlack
  3. 03RoadmapRM-3Checkout v2 in Q4Jira
  4. 04RefinementD-241Seat-based pricingSlack
  5. 05SpecificationCHK-412Per-seat pricing APIJira
  6. 06Build!1182Price API changeGitLabCoding agents work here
  7. 07Go to marketDOC-131Checkout v2 launchConfluence
THE LIFECYCLE Every stage loops. A new customer, competitor, or fire drill sends you back to step one.

Brief is the
product strategy agent

Brief works across all seven stages, not just Build. It captures decisions where they happen, connects them into one graph, and acts on them.

Book a demo (opens in new tab) Read the docs

WHERE IT WAS DECIDED

  • Slack · #checkout-v2“Going with seat-based?”
  • Confluence · Checkout v2 specPricing section reopened
  • Jira · CHK-412Checkout v2 blocked
  • GitLab · MR !1182Changes the price API
D-241Pending

Seat-based pricing for Checkout v2

Waiting on CPO sign-off since Sep 26. Linked to 4 sources, owned by Dana Ruiz.

WHO WORKS FROM IT

  • Claude Code · Checkout engHolds the pricing change
  • Claude · ProductDrafts the enterprise pricing PRD
  • Jamie Cole · EngineeringAsks why CHK-412 can’t ship
  • Dana Ruiz · CPTOSees it in her Friday brief
SOURCES Brief reads decisions from Slack, Jira, Confluence, and GitLab, self-hosted included, so every person and agent works from the same record.

Web App

Your command center. Search every decision, track features and work in progress, and see where things are stalling.

KestrelDecisions
Decision log
IDDecisionSourceStatus
D-241Seat-based pricing for Checkout v2Replaces per-order fees on new plans.SlackPending
D-231One checkout spec for mobile and webPayment flows share a single spec.JiraConfirmed
D-214Separate mobile checkout specReplaced by D-231.ConfluenceSuperseded
D-209Loyalty points expire after 18 monthsMatches the finance policy agreed in Q3.JiraConfirmed
KestrelDecisions
  • D-241SlackPendingSeat-based pricing for Checkout v2
  • D-231JiraConfirmedOne checkout spec for mobile and web
  • D-214ConfluenceSupersededSeparate mobile checkout spec
  • D-209JiraConfirmedLoyalty points expire after 18 months
DECISION LOG The decision log in the Brief web app, with the source and status of every decision.

MCP server and CLI

Your agents ask Brief before they build, so code follows the decisions. Over MCP in Claude Code, Cursor, Windsurf, and VS Code, or from any terminal and CI pipeline with the CLI.

  1. 1The agent asks Brief before it writes code, through brief_ask.
  2. 2Brief answers that the decision is still open, and why.
  3. 3The agent holds the change and flags the security review it found.
Claude CodeBrief MCP
> Add per-seat pricing to the checkout API  brief_ask per-seat pricing  D-241 is pending. Waiting on CPO sign-off since Sep 26.  brief_search checkout  Related: D-231 checkout spec, D-198 security review  Holding the pricing change until D-241 is decided.  D-198 applies, so I'll request a security owner on the PR.
> Add per-seat pricing to checkout  brief_ask per-seat pricing  D-241 is pending on CPO sign-off.  brief_search checkout  Related: D-231, D-198  Holding the change until D-241  is decided. Flagging D-198.
MCP A coding agent checks Brief over MCP before it changes the checkout API.

Stop answering
the same
questions

Engineers, sellers, and their agents ask Brief what was decided and why. It answers with the decision, its status, and its source.

  1. Org
  2. Goals
  3. Roadmap
  4. Refine
  5. Spec
  6. Build
  7. GTM
How product teams use Brief

CHK-412 Add per-seat pricing

Jira

  • Jamie Cole 2:14 PM

    Why can’t this ticket ship yet?

  • Brief 2:14 PM

    Three decisions apply.

    • D-241PendingSeat pricing is waiting on CPO sign-off. Hold the change.
    • D-231ConfirmedBuild to the shared checkout spec, not D-214.
    • D-198ConfirmedPayments changes need a security owner before merge.

  • Jamie Cole 2:15 PM

    Who can sign off on D-241?

  • Brief 2:15 PM

    Dana Ruiz, CPTO. It’s at the top of her Friday brief.

LINKED DECISIONS

  • D-241PendingSeat-based pricing for Checkout v2Slack #product-leads
  • D-231ConfirmedOne checkout spec for mobile and webJira, Checkout board
  • D-198ConfirmedSecurity review on payments changesLinear, Platform
  • D-214SupersededSeparate mobile checkout specReplaced by D-231

Jamie Cole, engineer, asks about CHK-412

“Why can’t this ticket ship yet?”

Brief answers

Hold the change. Per-seat pricing is still waiting on CPO sign-off.

D-241 Seat-based pricing Pending

JIRA Brief answers an engineer on the Jira ticket with the decisions that apply.

No AI silos between product and engineering

Coding agents in engineering and Claude in product read the same decisions, so you stop building the graph yourself.

  1. Org
  2. Goals
  3. Roadmap
  4. Refine
  5. Spec
  6. Build
  7. GTM
How AI transformation teams use Brief

Agent activity Today, across product and engineering

Agent activity
AGENTASKED BRIEFANSWERED WITH
Claude CodeCheckout engAdd per-seat pricing to the checkout APID-241Pending
CursorMobile engWhich spec does the payment sheet follow?D-231Confirmed
WindsurfPlatform engDoes this payments change need a review?D-198Confirmed
ClaudeProductDraft the PRD for enterprise seat pricingD-241Pending
  • Claude CodeAdd per-seat pricing to the checkout APID-241
  • CursorWhich spec does the payment sheet follow?D-231
  • Claude in productSummarize the payments review for productD-198

VIA MCP · LAST 24 HOURSMCP SETUP

AGENTS Agents in product and engineering asking Brief, and the decisions it answered with.

What the team decides,
the agents build

Same agents, same 8 tasks, 41 decisions the team had already made. Without Brief, the agents missed the decisions that were never written into the code.

Read the benchmark
Benchmark results, without and with Brief
Decisions followed out of 41Merge-ready on the first pass out of 8
Without Brief46%22 missed2of86 needed rework
With Brief95%2 missed8of80 needed rework

Decisions followed out of 41

Without Brief46%22 missed

With Brief95%2 missed

Merge-ready on the first pass out of 8

Without Brief2of86 needed rework

With Brief8of80 needed rework

BENCHMARK Benchmark, April 2026. One cell per decision or task. Totals as published, 3 runs per configuration. Planned with Claude Opus 4.6, coded with Claude Sonnet 4.6, scored from git diffs by a blind reviewer.

Find where
launches
stall, and why

Brief reads Jira, Slack, and GitHub, names the open decision behind each late launch, and tells you what to unblock first.

  1. Org
  2. Goals
  3. Roadmap
  4. Refine
  5. Spec
  6. Build
  7. GTM
How leadership uses Brief

Friday brief Friday, Oct 9 · for Dana Ruiz

NEEDS YOUR DECISION

D-241PendingSeat-based pricing for Checkout v2

Finance and sales signed off in #product-leads on Sep 26. Engineering is holding the change until you approve.

Launches held
LAUNCHPLANNEDNOWSLIP
Checkout v2Oct 14Nov 4+3 wks
Enterprise plansOct 28Dec 2+5 wks
Partner API pricingNov 11Dec 9+4 wks

WAITING ON YOU · D-241 · PENDING

Seat-based pricing for Checkout v2. Three launches below are holding on it.

  • Checkout v2+3 wks

  • Enterprise plans+5 wks

  • Partner API pricing+4 wks

FRIDAY BRIEF The Friday brief names the decision holding each late launch and who owns it.The Friday brief names the decision holding each late launch and how far each one has slipped.
Paul Xue

Brief is the thing that keeps the product on track and prevents decisions from conflicting with previous ones.”

Paul XueFounder, Spacestation Labs

We wouldn’t document this way without Brief.”

Brief keeps the AI connected to our product, so I get what I actually wanted.”

What teams ask
before a pilot

Talk to us (opens in new tab)

No. Brief is the product strategy agent. It reads decisions from the tools your teams already use, finds where work stalls, and gives every person and agent the same context.

10x the ambition
of your product org.

Brief handles the coordination work between strategy and go to market, so your teams spend their hours on bigger bets.

Book a demo (opens in new tab)