Product guide / Dossiers
where you stand with each relationship
Know where you stand, before the meeting.
Every account carries a dossier: a synthesis of what your company has actually learned about it, rebuilt on its own as first-party signals land, and readable by a person or handed to another agent.
Where this helps
Relationship tools are good at telling you who knows whom. They are much worse at telling you where you stand — and that answer is usually scattered across a report someone sent, a task someone closed, and a meeting note nobody reopened.
The question it puts in front of you
Where do we actually stand with this account?
Where judgment belongs
You decide what the relationship means and what happens next. A dossier is a briefing prepared for you, never a verdict.
What gets prepared for you
A per-account synthesis is rebuilt from first-party signals — observations, tasks, reports, metrics, artifacts — each time they land, and it records how many of each it drew on.
Relationships
How a dossier stays current.
Read a short narrative answering “where do we stand with this account?”, not a raw firm profile.
Check the build line: when it was last built, and how many sources of each kind fed it.
Rebuilds fire on their own when a report is sent, a task moves, an observation is committed, or an AI Inbox item is promoted.
Ask for a refresh from Chat when a burst of activity deserves one sooner.
Dossiers in the real world
Three memories about the same company, deliberately kept apart.
Operalta holds three distinct records of a company and refuses to merge them. The public firm profile is one. The company’s own narrative is another. The dossier is the third: your side of the relationship — what your team observed, sent, agreed, and left open. Asking an agent where you stand returns the third, and says so.
It maintains itself. A busy afternoon produces one rebuild rather than a dozen, and anything left untouched too long gets picked up on its own. Because it is plain markdown, the same dossier reads in the product, downloads, and hands to another agent as context.
What holds up
What it does well, and what it was never meant to do.
Constraints are a design position, not an apology. Everything on the left ships today; everything on the right we decided against.
What you can rely on in Dossiers
- Written in plain markdown, with the date it was built and how many sources fed it.
- Rebuilds itself when a report goes out, a task moves, or an inbox item is approved.
- Ask for a refresh from Chat, or save a version into a Room.
- Never readable outside the company it belongs to.
What we chose not to build
- A dossier synthesizes first-party signals. With no signals yet, there is nothing to build.
- It is not the public firm profile and not the company’s own narrative — those stay separate on purpose.
- It is a briefing, not a verified record and not a decision.
- It reflects recent activity, not the last second.
Outputs & exports
Rendered dossier markdown
Works with
Where Dossiers hands the work on.
Decisions rarely stop where a product does. These are the guides that pick the work up next.
For your company
See how Operalta fits your company.
Bring one current decision or process. We will map it together.