Spire Financial Forecaster

Overview

Spire Financial Forecaster started as a semester-long customer project for Spire, a financial consulting firm. On paper, I was backend. In practice, the work kept returning to foundation and understanding: figuring out how the financial model should behave, where the spreadsheet assumptions were unclear, and how the backend could give the system a shape.

I am currently reworking the project into something larger than the original class scope, so the old class-project version is the starting point, not the whole project. The customer context and repository constraints still matter, which means I need to be careful about what I show.

My Role

My work centred on the backend logic and the financial implementation layer. That included forecast calculations, stress-test behaviour, loan and bond logic, residual effects, and the shared utilities that made those pieces consistent.

The important part was not just writing endpoints. It was understanding what the calculations were supposed to mean and building enough foundation that the rest of the app could depend on it.

Current Direction

This project shows backend ownership through foundation work: calculation structure, model understanding, validation, and the parts of the system that other work depends on.

The next useful artefact is a sanitised architecture note or diagram that explains the forecasting and stress-testing foundation without overclaiming the original frontend polish.