Most finance tools assume one business per person. Entrepreneurs juggling a company, a commercial property, and a portfolio of investments need something structurally different. This is the product thinking behind iByay — and why its data layer is local-first.
The standard personal finance app has a hidden assumption baked into its data model: one user, one set of books. That assumption breaks the moment an entrepreneur is simultaneously operating a business, earning rent from a commercial property, watching an investment portfolio, and keeping personal finances separate from all three. The books do not just need tracking — they need to stay distinct and then reconcile upward into one honest picture. That structural insight is where iByay began.
The data model treats every venture as a first-class entity with its own ledger. Revenue, expenses, and cash flow are recorded per entity, with the entity boundaries enforced rather than merely suggested. The dashboard then aggregates across entities, so the owner sees each property and each business in isolation and the whole portfolio together. The distinction matters for real decisions: a property that is profitable on its own can hide inside a consolidated view, and a consolidated cash position says nothing about which venture produced it.
Analytics had to serve both views from the same store. We settled on Chart.js rendering from a normalized ledger, so per-entity reports and consolidated reports are views over identical data rather than separately maintained numbers. When the same figure appears in two charts, it comes from one computation — a small architectural rule that eliminates an entire category of reconciliation bugs.
The local-first decision came from how this software is actually used. Financial records are sensitive, frequently consulted, and needed in moments when connectivity is not guaranteed — a meeting with an accountant, a site visit, a flight. A local-first layer on IndexedDB with PWA caching keeps the ledger responsive and available offline, and the app installs to a home screen like a native app without an app-store distribution pipeline. For a subscription SaaS, the PWA route also keeps iteration instant: every user is on the latest version the moment we deploy.
The v1.0 release focuses on the core loop — multi-entity ledgers, unified dashboard, per-entity and consolidated analytics — and the roadmap sequences the hard integrations deliberately. Automated bank statement import comes first, because manual entry is the biggest adoption blocker for any finance tool. AI-powered transaction categorization follows, then tax-ready profit-and-loss and balance sheets per entity and consolidated, then multi-currency support for cross-border investments.
The pattern we keep returning to: structure first, intelligence second. Entrepreneurs do not abandon their finance tools because the charts are ugly — they abandon them because the books are wrong, the entities blur together, or the data is unavailable when a decision is being made. Get the ledger structure right, keep it available offline, and every later feature has solid ground to stand on.
