Overview
Echo is a live portfolio-intelligence platform for wealth advisors, financial professionals, and firms managing client investments.
It converts fragmented financial statements into structured portfolios, calculations, analysis, and interactive reports. The same intelligence can also be exposed through APIs and MCP so dashboards, internal tools, and AI interfaces can rely on one financial logic layer.
The problem
Advisors work with information spread across consolidated account statements, CAMS and KFintech documents, broker reports, spreadsheets, calculators, client notes, decks, and communication threads.
The information exists, but it is inconsistently formatted and disconnected from the decisions an advisor must make. Significant effort is spent reconstructing holdings and preparing analysis before the advisor reaches the work that creates value: interpreting the portfolio and helping the client decide what to do next.
Product hypothesis
Advisors do not need another passive dashboard. They need a system that transforms investment data into preparation, understanding, and action.
Financial intelligence should not be trapped inside one interface, and core recommendations must be traceable to deterministic calculations and portfolio evidence. Trust matters more than novelty in a financial product.
What we learned
Parsing is necessary but not differentiated. The more valuable question is what the product can understand after a statement becomes structured data.
Advisors need evidence before recommendations. A report is only one representation of the intelligence, and firms need different levels of detail and different delivery surfaces.
These insights led us to separate the financial engine from the presentation layer rather than building all domain logic into a single dashboard.
Product direction
We explored a statement parser, portfolio dashboard, interactive client report, advisor copilot, financial-intelligence API, and MCP-connected capability layer.
Echo became a combination of a live portfolio-analysis product, a deterministic financial engine, a report and interface layer, API-accessible intelligence, and MCP-compatible capabilities. It can operate both as a product and as infrastructure.
System architecture
The system begins with investment documents and other data sources, then parses and normalizes investors, folios, schemes, transactions, units, dates, and transaction types. Portfolio reconstruction turns that history into current holdings.
A deterministic calculation engine produces invested value, current value, gains, allocation, exposure, SIP activity, and performance. The intelligence layer interprets concentration, overlap, allocation imbalance, and review opportunities. A delivery layer exposes the result through dashboards, reports, APIs, MCP tools, and future embedded interfaces.
Core workflows
A user uploads a supported statement; Echo validates it, extracts and normalizes the data, surfaces parsing issues, reconstructs holdings, and generates the portfolio view.
From there, the advisor can review the portfolio, investigate an individual holding, identify areas that require professional review, create a client-ready report, or make the same calculations and structured insights available to another interface through APIs and MCP.
Prototyping and decisions
Workflow prototypes tested movement between upload, overview, holdings, analysis, insights, and reporting. Financial outputs were checked against source documents and expected calculations across missing data, multiple folios, duplicate schemes, irregular SIPs, redemptions, switches, and parsing failures.
We used progressive disclosure to manage large portfolios, organized navigation around advisor questions rather than database entities, and avoided presenting the product as a chatbot wrapped around investment data.
What we built
Echo includes CAS upload and processing, portfolio reconstruction, holdings and allocation analysis, performance and gain calculations, SIP and transaction analysis, portfolio dashboards, interactive reporting, financial-intelligence capabilities, API-accessible logic, and MCP-enabled integrations.
The system must continue to handle unstructured documents, large transaction histories, calculation accuracy, explainability, sensitive financial data, and AI-generated explanations that never alter or fabricate deterministic financial values.
Current state and reflection
Echo is live and continues to evolve as new advisory workflows and implementation constraints become visible.
It began as an information-processing problem, but the deeper opportunity was reusable financial logic. A dashboard alone would be conventional; an API alone would be difficult to experience. Echo needs both a working product that demonstrates value and an intelligence layer capable of powering future products.