Why I built my own finance dashboard instead of opening a Monarch account
Monarch lets you rename every category they ship. The dashboard still only answers the questions a product team thought to ask.
What you actually buy from Monarch
Personal-finance apps make the same trade. You hand them your bank connections, they hand you back a dashboard. They let you rename categories, recolor things, write a few rules, hide accounts you don't want to see. Then the customization ends.
Mint did this for fifteen years until Intuit shut it down in March 2024. Monarch picked up most of the refugees at $99 a year. Copilot is $95. YNAB is $179. They've all converged on roughly the same shape: a fixed data model under a thin layer of cosmetic settings. You can rename categories. You can't add a new dimension to a transaction. You can pick which of their charts to show. You can't ask the dashboard a question they didn't pre-imagine.
Why a fixed model is the whole product
This isn't a knock on the products. A fixed shape is the only thing that scales. The Monarch PM can't ship "let every user define what they want to track" because the support burden alone would kill the company. They have to lock the model and let you customize the surface, which is exactly the layer where it doesn't matter much.
Most personal-finance apps are wrappers around the same underlying transaction data. They pull from Plaid, hold it in their own database, and paint a dashboard on top. The customization they give you lives in the paint. You can change colors and category names. You can't add a dimension to a transaction or change what the dashboard can ask of it.
You can rename their categories. You can't change the questions a dashboard answers.
The categories I actually use
The dashboard I'm using day-to-day pulls transactions from every account my partner and I have, through the same Plaid plumbing Monarch uses. After that, the resemblance stops.
The categories aren't just "Dining" and "Groceries." They're "Subscriptions I'm considering canceling" and "Gifts for friends & family." Every transaction that comes in gets routed against rules I wrote, in language that matches how my partner and I actually think about money. They sort by intent: what we're trying to do, which decisions are still open. That sort is what makes them worth looking at.
When the question changes, so does the dashboard
The views work the same way. My partner and I sit down once a month to review our shared finances together, and the dashboard is shaped around that conversation. One screen with the numbers we actually care about and none of the ones we don't. When a question comes up during the review, like whether the recurring chart is drifting away from the credit-card statement or whether one category is being driven mostly by one of us, I add the view that helps us answer it before the next review. The dashboard isn't a dashboard a product team shipped me. It's a dashboard that catches up to whatever question we're asking now.
What this means for your stack
Most SMBs don't think about their internal tools this way. They pick the best-rated SaaS in a category, work around the parts that don't fit, and assume an upgrade tier will eventually close the gap. When the tool is mostly a dashboard sitting on top of data you already have, it won't. The ceiling there is structural, not budgetary.
If you've been working around an internal tool that almost fits, an Implementation Sprint is a fixed-scope build where I ship the version shaped to how you actually work.