Product
One view for accounts, budgets, markets, assets, and everyday spending.
One serious product. All the way through.
I built Savyy alone, from product and interface to banking, AI, mobile, infrastructure, and security.
Total balance
€110,130.64- Income
- €3,200
- Expenses
- −€1,200
- Monthly
- +€2,000
Balance evolutionLast 30 days
€110,131total
- Solo full stack
- 4,000+ banks
- Web · iOS · Android
Savyy case study index
Systems
Bank connectivity, transaction processing, private categorization, alerts, billing, and infrastructure.
Releases
One shared product across the web, App Store, and Google Play.
01 / Product
Built around a complete financial life.
Savyy is the product I wanted to use: one place for the daily details and the longer view, without flattening personal finance into a single score.
- 01
See the whole picture
Accounts, balances, transactions, budgets, savings, investments, property, and other assets live in one financial view.
- 02
Turn activity into context
Savyy organizes spending by category and period, keeps cash flow readable, and lets people correct the system when their own judgment is better.
- 03
Move between screen sizes
The web and mobile clients share the same account. Budgets, categories, portfolios, and connected banks stay in sync.
Product judgment
“Useful finance software should leave the person in charge.”
Automation can organize the work, but it should stay inspectable. A category can be corrected. An AI feature can be declined. A bank can be disconnected. The interface keeps those choices visible.
02 / Ownership
Solo means the whole system.
I built Savyy by myself. That includes the product decisions people see and the operational work they should never have to think about.
- 01
Product direction and interface design
- 02
Web application
- 03
Native iOS and Android applications
- 04
Backend, APIs, and data model
- 05
Bridge open-banking integration
- 06
AI features and categorization controls
- 07
Infrastructure, privacy, and security
- 08
Billing, releases, documentation, and support
A connected path
From consent to a useful screen.
- 01
Consent
The user connects a bank through Bridge. Authentication happens with the bank, and Savyy receives read-only access.
- 02
Normalize
Balances and transactions arrive in a consistent shape so the same financial model can serve different banks and markets.
- 03
Interpret
Transactions can be categorized after identifiers are removed. People can review and change every result.
- 04
Deliver
Web, iOS, and Android read and write through the same product system, so a change on one client appears on the others.
03 / Releases
One product, three real clients.
The web app, iOS app, and Android app share the same account and financial model. Each client still has to feel at home on its platform.
- Biometric app lock with PIN fallback
- Home-screen widgets for wealth, budgets, cash flow, and followed instruments
- Push alerts that open the relevant screen
- English, French, and Spanish
04 / Boundaries
Privacy is a product decision.
Financial software earns trust through limits that are clear before they are needed. These are the boundaries I designed into Savyy.
- 01
Bank access is read-only. Savyy cannot initiate a payment or transfer.
- 02
Bank credentials are handled by the regulated connection flow and never pass through Savyy.
- 03
AI features require consent, and financial data is never used to train a model.
- 04
Sensitive data is encrypted, and Savyy documents EU data residency for its infrastructure.
The evidence is live. Open the product.