Product Brain Write our homepage intro.
“Who is it for, what does it do, and why should they use it?”
Didn’t we already decide this?Who actually decides this?Why are we doing it this way?I thought we agreed on something else.Why am I explaining this again?
The shared decision record
for your team and its AI agents.
Connect decisions to your purpose, strategy and work. Your people and agents can check what’s agreed, why, and whose call it is.
Keep working in your connected agent.
Early access · For small teams using agents across functions.
From work to outcomes
Your team gets work done.Results still take too long.
FromWork
- Rebuilding context
- Waiting for clarity
- Doing work again
ToOutcome
Keep direction, knowledge and decision authority connected to the work.
One record. Across the team.
One shared record.
Your agents put it to work.
Decisions, reasons, direction and roles—connected to the work. Your agents consult the same record.
Shared decision recordRole-governedCurrent agreement + its reason
ProductPeople + agents
OperationsPeople + agents
CommercialPeople + agents
How it fits your dayKeep your tools.
Keep your tools.
Connect your agent.
Your agent brings the team’s agreements into the work you delegate. Set its role and working instructions; keep working where you are.
See supported agents →The routine → your agent
Find what applies.Decisions, reasons and related work.
Record your way.Show you first, or capture as you go.
Use it next time.The next agent can build on the shared record.
You make the calls. Your agent handles the record.
Used to write the page you’re reading
A decision becomes
a starting point.
A fresh agent looked up our positioning from its coding environment and drafted this page’s introduction.
Teams using agents.
Across functions.
Why · Keep purpose and strategy connected to daily work.
Owner · Team Lead, Product Brain
History · Recorded 5 October.
The intro above.
“Connect decisions to your purpose, strategy and work. Your people and agents can check what’s agreed, why, and whose call it is.”
Edited from the agent’s draft, with the decision as its starting point.
See it in place ↑Our workspace · Read-only · 11 October 2026. Retrieval proof; no customer result or new acceptance.
Try the work loop →What we retrieved—and what was missing
The agent ran pb orient --task 'Write a homepage intro for Product Brain. Who is it for, what does it do, and why should they use it?' --full --json, then opened the relevant records in full with pb get-many. CLI 0.1.0-beta.9860.
Selected unchanged text from DEC-1924:
“agent-first teams are teams where every person works through agents, across proposals, contracts, operations, program design and marketing analysis, not only engineering.”
The previous coding-only positioning is archived. The decision’s returned published history attributes acceptance to the founder’s agent acting as Team Lead. This run read that existing record; it did not accept or change it.
Orientation was partial. The agent followed up by reading the decisions, their owner, related definitions and published histories. A briefing is a starting point; missing context needs a lookup or a question before acting.
The fixed headline was already approved separately. We asked the agent for a supporting paragraph and edited its draft. This is one writing task, not a complete product recording, fresh-workspace onboarding test or measured time saving.
Early use · UpCurrent
Their first impressions.
On governance and decision-making
“This is governance heaven.”
Ralph ZebregsCEO, UpCurrent
On using Product Brain
“That gives a lot of peace of mind.”
Sylvie van den MeerendonkCo-founder, UpCurrent
Knowledge stays with the team
They’re away.
The reason isn’t.
When someone is away—or leaves—their recorded choices and reasons stay available.
See shared reuseDecision author · unavailable
Accepted decision
One customer. One scoped experiment.
Reason · Learn what it takes before adding it to the offer.
Owner · Product Lead
Sales + agentDelivery + agentMarketing + agent
Customer-request walkthrough · Recorded knowledge stays; it doesn’t replace a person’s expertise.
Why a shared decision record?
Keep the practice.
Connect the record.
| Your current practice | What Product Brain brings together |
|---|---|
| Agent rules files | Reasons, owners and history across functions. |
| A wiki decision log | Agent access during work, with role-controlled changes. |
| An agent’s personal memory | Knowledge other people and agents can consult. |
| Threads and people’s heads | Recorded reasons available while the author is away. |
Briefs, logs and agent instructions can preserve this too. Product Brain connects the record with direction, work and role-controlled changes. Your connected agents help maintain it during work.
Randy HeremanFounder, Product Brain
Why this exists
The decisions were there.
Keeping them useful was a job.
I saw a connected record produce useful briefs and surface contradictions. Keeping it current became a job. I built Product Brain so your agents can help keep that record useful while you work—with clear authority for changes.
Founder’s experience, not a measured customer result.
The experience behind Product Brain
On a replatforming project for a business doing about €20 million in revenue, I saw what a connected record could do: surface contradictions and produce briefs that were on point. Keeping it current felt like a full-time role.
This experience inspired Product Brain; it is not a measured result from customers using the product.
Connect your agent.
Keep working.
Start with one real decision, in a task you already need to do.