Financial Snapshot in Morning Brief
A glanceable card that appears in the daily brief showing account balances, upcoming bills, and any budget concerns worth knowing about.
💰 Money Pulse
Synced 6 min ago📋 This Week
Design Rationale
The financial card appears only when there's something worth knowing - upcoming bills, budget alerts, or unusual activity. On quiet weeks, it can be collapsed or omitted entirely. We show aggregate balances, not transactions - the goal is awareness, not anxiety.
Budget Alert States
Different alert levels depending on what's happening with spending and bills.
⚠️ Budget Warning
Needs attention🚨 Budget Exceeded
Over budget✨ On Track
Looking goodAccount Balance Questions
Simple, direct questions about current account balances.
Quick Responses
Balance questions are answered immediately with cached data (synced via Plaid). We show the account nickname they'll recognize and add context like recent changes or goal progress.
Spending Questions
Questions about spending patterns, categories, and trends.
Bill Questions
Questions about recurring bills, due dates, and amounts.
Family Account Questions
Questions about linked family member accounts (with their permission).
Family Access
Family account access requires explicit linking during setup. For minor children, the parent controls visibility. For spouses/partners, both parties must consent. Umber only shows what each person has permission to see.
Financial Context Store
What we store about your finances - metadata and patterns, not raw transactions. This is what enables Umber to give smart, contextual answers.
Account Profiles
Spending Baselines
Fixed Bills
Goals & Budgets
Key Principle: Metadata, Not Transactions
We don't store individual transactions - those stay in Plaid and are fetched on-demand. We store derived patterns and metadata: "you typically spend ~$520 on groceries" not "you bought milk at Safeway on Jan 3 for $4.29". This is more useful for the AI and better for privacy.
Derived Patterns
Patterns and insights computed from transaction history that help Umber give smarter advice.
💰 Income Patterns
📈 Spending Trends
🔮 Predictive Insights
Technical Design
How the Financial Context Store works under the hood.
Architecture Overview
Financial Context Store Schema
// What we store per user (NOT transactions) FinancialContext { accounts: [ { id: "acc_chase_4821", nickname: "Primary Checking", type: "checking", typicalBalanceRange: { low: 3000, high: 6000 }, lastKnownBalance: 4827.43, lastSynced: "2026-01-10T14:23:00Z" } ], incomePatterns: [ { source: "ACME Corp", frequency: "biweekly", typicalAmount: 2847, typicalDay: "friday", nextExpected: "2026-01-17" } ], recurringBills: [ { name: "Mortgage", payee: "Wells Fargo", amount: 2340, dueDay: 1, autoPay: true, category: "housing" } ], spendingBaselines: { groceries: { monthly: 520, trend: "+5%" }, dining: { monthly: 280, trend: "+18%" }, gas: { monthly: 180, trend: "-12%" } }, budgets: [ { category: "dining", limit: 300, period: "monthly" } ], goals: [ { name: "Emergency Fund", target: 15000, current: 12450, monthlyContribution: 500 } ] }
Data Flow
Privacy by Design
Raw transactions are processed and discarded. We only keep aggregated patterns. If a user asks "what did I buy at Target last week?", we fetch on-demand from Plaid, answer the question, and don't persist the individual transactions.