A readout to a client's leadership team
Case study

FJ Capital Management automated daily P&L attribution on Microsoft Fabric

Reporting for a $1B+ fund depended on one person running SQL by hand, and Power BI had hit its row limit.

FJ Capital Management

FJ Capital Management · Finance and reporting

4xmore trade history in the live dashboards

The workflow before

FJ Capital Management manages more than $1B, with trade and position data spread across its AlphaDesk order management system, fund administrator files and Excel sheets. One employee ran SQL queries by hand each day and refreshed Power BI, so reporting stopped when that person was out. The dashboards had also hit the Power BI Pro ceiling of about 350K rows, which meant the team could only see part of its own history.

What we built

We built a Microsoft Fabric lakehouse that pulls trade and position data from the AlphaDesk API automatically and moves it through bronze, silver and gold layers. The logic that used to live in one person's head is now written down as infrastructure as code.

We rebuilt the Power BI dashboards to run on the full 8-year history, more than 1.5M rows, without lag. Daily P&L attribution by portfolio manager and by sector now produces itself each morning instead of waiting on a manual run.

Before and after

MeasureBeforeAfter
History in dashboardsAbout 350K rows (Power BI Pro limit)1.5M+ rows, full 8 years
Daily P&L attributionManual SQL and refresh by one employeeAutomated every day, by PM and sector
Key person dependencyOne person held the reporting logicLogic in code, runs without them

What's next

Trade, position and P&L data now sit in one governed lakehouse. That is the foundation for L2 work: an analytics assistant that lets portfolio managers ask about attribution and exposure directly instead of waiting for a report.

ShareLinkedInEmail

Automated extraction from the AlphaDesk API and fund administrator sources lands in Azure Data Lake storage inside Microsoft Fabric, organized as a bronze, silver and gold medallion lakehouse. SQL Server sources were folded into the same pipelines.

Data modeling and attribution logic is version-controlled as infrastructure as code. Power BI semantic models were redesigned for the full 1.5M+ row history, removing the Pro capacity bottleneck.

Next step

Let's build the case study we tell next.