Case Study
Pool | Shared Financial Goal Platform
Collaborative savings platform enabling structured group financial goals and transparent contribution tracking.
Problem Context
Saving toward a shared goal breaks down fast. Without one place to track who contributed what, groups fall back on messages and mental math. Pool gives everyone a shared view that updates automatically, no check-ins needed.
No clear view of who contributed what.
Progress feels abstract and unmotivating.
Asking about money creates tension.
One Mental Model
Pool is built around a single idea: one goal, one pool, one shared view of progress. Whether you're saving alone or with a group, the structure is the same. Define a target, track contributions, see where things stand.
Clear Goal Definition
Defines target amount, timeline, and visibility rules.
Contribution Layer
Where contributions are tracked consistently (manual or read-only bank sync).
Real-Time Shared Progress
Collective progress is calculated automatically and visible to all.
Product Logic Engine
Behind the simple mental model lies a robust data architecture designed to ensure trust and strict regulatory compliance. The system is built on an Immutable Ledger, meaning pool balances are updated only after a transaction is fully validated and permanently recorded. Additionally, a KYC verification acts as a mandatory gateway before any financial interaction, ensuring a secure ecosystem for all participants.
System Architecture
In fintech, visual inconsistency breaks user trust. Pool’s design system was built as a strict, semantic engine rather than a static UI kit, ensuring predictability across all financial interactions.
Semantic Token Logic:
UI elements are driven by semantic roles (e.g., action/financial, status/warning), enabling rapid scaling of new features without breaking existing code.
Data-Driven States:
Components react automatically to backend constraints. Error states and financial warnings are handled at the system level, eliminating manual overrides.
Predictable Rhythm:
Strict spatial foundations (spacing and radius variables) reduce cognitive load, making complex financial data feel approachable and secure.
Contribution Framework
Pool separates the responsibility of saving from the social pressure of asking. Each pool has defined visibility rules, a clear contribution structure, and boundaries that keep the experience safe for everyone involved.
VISIBILITY
Transparent Contributions
Each member sees total progress and individual inputs.
FLEXIBILITY
Flexible Saving Modes
Users can track savings manually or connect their bank in read-only mode.
BOUNDARIES
Permission Structure
No one can move money or enforce contributions.
Contribution Flow
Manual Mode
Bank (Read-Only)
Pool Contribution Layer
Shared Progress
Key Screens
Core user flows demonstrating contribution clarity and shared visibility.
Transparency
Group accountability
Passive visibility
Contribution Flow
Flexible input
Read-only bank sync
Trust by design
Start manual, connect later, read-only bank sync is optional
Progress is calculated the same way regardless of input method
What this supports: logging shared costs and settling up without turning money into a social tension point.
Expense logging
Settle up
No social friction
14:30
Back
Almost done! Step 3 of 3
Log expense & settle up
Log an expense & settle up
Expense amount
₪
00000
What was it for?
e.g., Groceries, rent, utilities
Who paid?
[AVT]
You
[AVT]
Michal
[AVT]
Sela
[AVT]
Dan
Each person pays:
₪250 (₪1,000 ÷ 4 people)
Settlement summary:
You
✓ Paid ₪250
Michal
✓ Owes ₪250
Sela
✓ Owes ₪250
Dan
✓ Owes ₪250
How to split?
Split equally
Custom amount
Home
Notifications
Insights
Profile
People don't download financial apps on impulse. Before committing, they want to understand what the product actually does, whether their money is safe, and whether the whole thing makes sense for their situation. The app itself can't answer those questions — by the time someone opens it, the decision to trust has already been made (or not).
That's why I designed a companion marketing website alongside the app. Not as an afterthought, but as a deliberate part of the product experience.
Visibility
Flexibility
Boundaries
Transparency
Group Accountability
Passive Visibility
Flexible Input
Read-Only Bank Sync
Trust by Design
The Trust & Transparency page was designed to answer the question every potential user is silently asking before they hit download.
Goal Completion Rate
Did the group reach its savings target? This is the core promise of Pool. Low completion signals either unrealistic goals or contribution drop-off along the way.
Active Participation Rate
How many group members contribute consistently over time? One active member in a group of four is a UX failure, not a user failure.
Bank Connect Completion
What share of users who start the bank sync flow complete it? Drop-off here signals a trust or clarity problem in the permissions screen.
© 2026 Guy Bar-Sinai. Built with intention.
This site is a design exploration.