The Treasury Mistake That Makes Every Crypto Number Suspect
- Assuming the numbers add up
- Designing for the analyst, not the demo
- Treating risk and reporting as afterthoughts
- Skipping validation before the build
The most common mistake in crypto treasury tooling is treating aggregation as a display problem. Teams pull wallet balances into one screen, call it a dashboard, and assume the hard part is done. It isn’t. Aggregation is a data integrity problem, and a treasury view that looks unified while resting on shaky inputs is more dangerous than no view at all, because people act on it.
Assuming the numbers add up
Assets sit across multiple wallets, exchanges and chains, each with its own quirks: different timestamps, different price sources, tokens with the same ticker and different contracts. Stitch those together carelessly and the totals drift. The damage isn’t a wrong figure on a screen. It’s that nobody trusts any figure, so decisions get made on instinct or on a spreadsheet someone maintains by hand. A treasury product that can’t survive a reconciliation check has failed at its only real job.
Designing for the analyst, not the demo
Dashboards built to impress in a pitch tend to optimise for the wrong moment. They show a beautiful portfolio view and skip the questions a treasurer actually asks: what changed since yesterday, what’s my exposure to this asset, what’s liquid if I need it this week. When those flows aren’t mapped before design starts, the result is a screen that looks institutional and answers nothing. The design work that matters happens earlier, in understanding how treasury decisions get made and what evidence supports them.
Treating risk and reporting as afterthoughts
Risk monitoring and reporting often get bolted on late, once the portfolio view exists. That ordering is backwards. Exposure limits, concentration, liquidity and the reporting that goes to a board or a foundation’s stakeholders are the reasons the platform exists. If they’re retrofitted, the data model usually can’t support them cleanly, and the reports end up as exports someone tidies by hand. The same applies to compliance expectations: they shape what the product must record and prove, not just what it displays.
Skipping validation before the build
Prototypes get skipped when timelines tighten, and treasury products are where that shortcut costs most. Real-time analytics, asset performance views and reporting flows are hard to reason about on paper. Without something interactive to test against real scenarios, teams discover the gaps during development, when changing the data model is expensive. Continuous checking of data accuracy and security through the build matters more here than in most products, because the output is money.
A good result is unglamorous: one view you can reconcile, performance and exposure that update without manual help, and reports you’d be comfortable putting in front of a board. Mosaic, the platform Foundry 5 built, was designed around that goal — unified visibility and control rather than a prettier spreadsheet. The full guide sets out the research, UX flows, dashboard design, real-time integration and testing that get a treasury platform to that point, and it’s worth reading there.
Write a comment