REPORTING
A view across mandates.
Bring permitted position and cash records into one reporting view. Trace a figure back to its source.
Inspect the prototype ↗FINANCE · INVESTMENT OPERATIONS
Your firm.
A clearer view.
Financial applications, API integrations and MCP tools for investment firms, portfolio managers and family offices. Built around your team’s work.
An imagined office. A practical conversation.
A room for the work behind the decisions.
Set the mood
BUILT AROUND YOUR DESK
The work between
the systems.
For portfolio managers, wealth firms, family offices and investment operations teams.
OPERATIONS
Make differences visible.
Compare custodian, administrator and internal records. Give exceptions a clear reviewer.
See reconciliation ↗RESEARCH
Keep the sources close.
Search approved documents and prepare source-linked summaries, with agreed access and review rules.
Explore assistant tools ↗COMMUNICATIONS
Prepare. Then review.
Reporting templates, document assembly and draft commentary for your authorised reviewers.
Discuss reporting ↗INTERNAL TOOLS
Connect the handoffs.
Onboarding tasks, investment committee packs or an internal review queue around existing systems.
Explore connections ↗FIRM FINANCE
A clearer operating picture.
Fee reporting, expense views and operating cash workflows based on agreed records and calculations.
Discuss a tool ↗Services available to scope. Examples on this page use synthetic data and do not represent client deployments.
A PROTOTYPE TO INSPECT
A mandate.
The records behind it.
Switch the sample mandate. Inspect its allocation and the differences between two sets of records.
SHAPED SI / ILLUSTRATIVE REPORT
01 OCTOBER 2026The portfolio ledger.
CAD / SYNTHETIC
SYNTHETIC DATA · CAD · SAMPLE SNAPSHOT: 1 OCTOBER 2026
- Recorded source value · CAD
- $11,000,000
- Sample positions
- 3
- Differences to review
- 1
Swipe across the table to see the source, book and difference columns.
| Sample position | Asset class | Source value | Book value | Difference | Review |
|---|
Invented records for an interface demonstration. Allocations use recorded source values; they are not recommendations or performance figures. No custodian, market data feed, trading system or AI model is connected. A production project would agree valuation rules, currencies, timestamps and reconciliation tolerances with your firm.
PERMITTED SOURCES
Your systems.
A useful connection.
Provider documentation, licensing and your firm’s access determine what can be connected.
01 / PERMITTED SOURCES
Custodian records
Licensed datasets
Internal systems
02 / THE DATA LAYERA common
language.
language.
Identifiers · Timestamps
Validation · Access rules
03 / YOUR WORKSPACE
Reporting applications
Exception review
Permitted MCP tools
A proposed architecture. Each connection depends on provider support, licensing and permissions.
- 01
Name the sources.
Custodian records, licensed datasets and approved internal exports.
- 02
Agree the data layer.
Identifiers, currencies, timestamps, access and exception handling.
- 03
Build the application.
Reporting, a review queue or a permitted assistant tool.
- 04
Test the cases.
Missing records, duplicates, failed requests and acceptance criteria.
MCP · TOOLS AND CONTEXT
A specific job.
Agreed access.
Agree what the assistant can read, which calculations it can call and what it may only draft.
Read. Prepare. Review.
We design servers and adapters around a specific financial workflow. Permissions, sources, tool inputs and failure handling belong in the implementation.
Your firm keeps approval of client communications, record changes and investment decisions.
Official MCP architecture ↗THE REVIEW FOLIO / 04 STEPS
GUIDED EXAMPLE · FIXED SAMPLE DATA
- 01 / Scope
- 02 / Read
- 03 / Draft
- 04 / Review
A small tool. A clear purpose.
Walk through a sample mandate and reconciliation review, one step at a time.
Ready to exploreThis is a scripted explanation. No MCP server or AI agent runs here, and nothing is sent or changed.
BEFORE WE BEGIN
A few
useful answers.
Are the examples live integrations?
No. The portfolio prototype uses synthetic records. The guided MCP example is a scripted explanation, with no connected account, model or trading system.
Can we start without sharing account access?
Yes. Start with the workflow, existing systems and output you need. A first prototype can use synthetic or approved records.
Do you manage investments or execute trades?
No. These are software, data integration and workflow services. Your authorised people retain investment decisions and approvals.
What does a project cost?
Deliverables, data access, acceptance criteria, support and pricing are agreed before work starts.
FOR YOUR FIRM
One workflow.
A useful place to start.
Bring the workflow, your systems and the output you need. We’ll agree on a first deliverable.