Start with the reported information.
Public company filings provide the financial inputs. The source material is the starting point for the research workflow.
Source recordsA platform for researching Indian stocks and mutual funds, built around historical information and long-term analysis.
The challenge was to connect what companies report with what a researcher needs to examine: a consistent history, a modelled estimate and the context to interpret it.
Explore the engineering ↓A useful research view needs more than a collection of numbers.
Historical filings arrive in different structures. Labels vary between companies and reporting periods. Before a model can work through years of earnings, those records need a consistent meaning.
Repeating that preparation in separate spreadsheets makes it harder to maintain the same method as new information arrives. MOAT brings the preparation, calculation and presentation into an application workflow.
The product is designed for examining a business over time. That purpose shaped an interface centred on historical research rather than a constantly moving intraday display.
Separating the stages makes the system easier to reason about. An unexpected result raises a specific question: did the source change, was a field interpreted incorrectly, or did the model produce it?
Public company filings provide the financial inputs. The source material is the starting point for the research workflow.
Source recordsLine items and reporting periods need a common representation before calculations can compare the history.
Structured historyThe model uses historical earnings to calculate an estimate. The documented approach works through a decade of earnings.
Calculated resultPresent estimated value in relation to market price, with the distinction between reported information and model output kept clear.
Research viewA calculation cannot resolve a mistake in what an input represents. Normalisation is therefore a substantial part of the application, not a formatting step added at the end.
The system needs a consistent way to represent financial line items across companies and years. The important distinction is between changing a label and establishing that two records mean the same thing.
This is a recurring custom-software problem: a clean interface depends on the decisions made while preparing the information beneath it.
Working through a decade of figures on every page request would repeat the same calculation for each visitor. MOAT computes results when a filing arrives and caches them for subsequent views.
That separates the cost of preparing a result from the act of reading it. The research page can retrieve an available calculation instead of making the visitor wait for the full model to run.
The design still depends on updating calculated results when their inputs change. Caching is a responsibility to manage, not evidence that a result is always current.
MOAT brings stocks and mutual funds into the same product. This case study focuses on the company-filings and valuation workflow; it does not imply that a fund and an individual business are modelled identically.
The research question is the relationship between a modelled estimate and market price. The page needs to make those different kinds of information understandable.
The documented interface omits live ticking prices and intraday charts. That is a product choice aligned with the intended research workflow.
A calculated estimate is an output of a method. It should be read with its assumptions and source information, rather than treated as a fact established by the interface.
The scope connects data preparation, valuation calculations and the research interface. Company filings provide the starting records. Financial line items, reporting periods and units need a common structure so the calculation can work through a consistent earnings history.
The calculation layer applies the valuation method to that prepared history. Results are computed when source information changes and stored for subsequent page views. Keeping preparation and calculation separate from page rendering lets each part of the application have a clear responsibility: update the inputs, recalculate the result, then make it available to read.
The presentation layer brings the calculated estimate and market price into the same research view while distinguishing their meaning. Historical information remains central to the experience, supporting considered comparison across years. The interface hierarchy follows that purpose, with room to examine the business and interpret the model output.
Built with OmnioPHP, the application brings these stages into a shared software foundation. The engineering work centres on consistent records, repeatable calculations and a clear route from source information to the result a researcher examines.
Explore OmnioPHP, the framework used for MOATIf the same information needs collecting, reconciling and calculating every week, tell us how that work happens today. We can help assess whether it belongs in a dedicated application.