The story comes from a post by /u/RallyMantis on r/ClaudeAI, titled "I built my own Monarch-style finance dashboard with Opus 5.5 for less than $20."
The poster describes building SharkFin, a personal finance dashboard modeled on Monarch Money, using Claude's Opus 5.5 model on a standard Claude Pro plan.
Monarch Money is a paid app for tracking spending across bank accounts. According to the poster, building a personal version of what it does cost less than a single month of a $20 a month Claude Pro subscription, in the AI usage it took to build it.
What actually got built
SharkFin connects bank accounts through a service called SimpleFin, then hands that data to Actual Budget, an open source budgeting tool, to do the underlying accounting. The poster says the reason for choosing Actual is that it is open source, so the financial data is stored locally rather than sitting inside another company's servers. A React front end sits on top of that.
The front end was built using Opus 5.5 running on the "medium" reasoning setting, and the poster says the whole build used around 35 percent of a $20 a month Claude Pro plan's weekly limit. They add they were happy with what medium reasoning produced and never felt a need to raise it higher.
The order the build happened in
Two choices stand out in how the poster describes the process. First, before writing any interface, they had Claude research existing financial dashboards and pull screenshots of them, then build the UI working from those images rather than from a description alone.
Second, the poster's own advice is to get one part of the app working well before moving to the next, and build on that momentum. They started with the cash flow page, got it working the way they wanted, and only added the rest of the dashboard after that. Their favorite result of this approach came later: because the app was customizable, they set up a separate page to track each of the properties they own individually, so they can see the cash flow, or the loss, on each one on its own.
What you can do tomorrow morning
Two things from this are worth taking into your own next build, whether it involves money or not.
First, if the tool you are building has a visual interface and something like it already exists, feed the model pictures of the ones you are trying to match, not a text description of what you want. A model working from a screenshot makes fewer guesses about layout, spacing and hierarchy than one working from an adjective.
Second, pick the one screen or feature that matters most, and do not move on until it genuinely works the way you want. The poster's cash flow page came first, and everything else got layered on once that page was solid. That is the same order that tends to separate an AI build that stalls from one that finishes, get one real path working end to end before you widen the scope.