How we compare
Your systems record the portfolio.
OneBook preserves the decision behind it.
Connect the thesis, exact portfolio state, proposal, risk, policy, approval and outcome in one versioned record. Keep clear ownership of the systems that already run your business.
If your priority is official accounting, custody, administration or an enterprise order-management replacement, evaluate those systems against that mandate first.
OneBook does not replace these responsibilities.
If thesis changes, portfolio proposals, risk checks and approvals are spread across tools, OneBook brings the complete decision state together.
See a connected decisionThis is a guide to system responsibilities, not a feature ranking of individual vendors. Product capabilities, integrations and deployment options vary by configuration and agreement.
| System or approach | Primary job | What to establish in your review | OneBook’s role alongside it |
|---|---|---|---|
| PMS / IBOR / OMS | Portfolio and operational records; order workflows according to the system’s scope. | Which system owns positions, cash, orders and fills? How are discrepancies reconciled? | Link the exact portfolio snapshot and proposal to thesis, risk, approval and outcome. |
| Risk & analytics | Exposure, scenario, stress and model calculations. | Which book, inputs and model versions produced the result? Can you reproduce it? | Attach risk and policy evidence to the specific proposal and its review history. |
| Accounting / custody / administration | Official records and services within the provider’s agreed remit. | Who is authoritative for valuation, settlement and official accounting? | Reference operational evidence while preserving the decision rationale and ownership. |
| Research & data tools | Source information, investment analysis, documents and models. | How do assumptions and evidence versions remain linked to portfolio decisions? | Connect thesis state and supporting evidence to the proposed action and later review. |
| Spreadsheets & messages | Flexible analysis and team communication. | Who owns the current version, exceptions, approvals and the review trail? | Structure the material decision as a versioned object with explicit ownership. |
| Build in-house | A workflow implemented and maintained by your team. | Who owns integrations, permissions, versioning, support and long-term maintenance? | Provide a product foundation with integrations and workflow scope agreed for your team. |
Thesis versions, assumptions, evidence, catalysts and the conditions that would change the view.
The exact book, current and target weights, proposed orders, cash impact and alternatives.
Proposal-linked risk, policy checks, model context, exceptions, approvals and named owners.
Execution references, attribution and a review against the decision state that existed at the time.
OneBook starts where the systems of record stop: at the complete state of the investment decision.
See all product boundaries05 / A useful evaluation
Evaluate the workflow using your team’s responsibilities, source systems and review requirements.
View scope & pricingIdentify the official book, the data sources and the system responsible for each record.
Connect the thesis, portfolio snapshot, risk, policy checks and required approvals.
Inspect what can be reconstructed, which versions are preserved and who owns exceptions.
Define users, books, integrations, controls and support. Review security and architecture documentation.
Let’s work through the fit
A private walkthrough around one real investment decision.
Discuss your workflow