Case Study

QueesSplit & Settle

Making shared money easier to split, reconcile, and settle.

Role: Product DesignerScope: Product design, UX, interaction designPlatform: MobileType: Product concept

The challenge

Shared expenses become difficult after someone pays.

Different people pay for different things, leaving the group to work out who owes whom and how much is still outstanding.

Record — Capture the expense, payer, participants, and split.

Reconcile — Let the system calculate the financial consequences.

Resolve — Surface only the action that actually needs a person.

Simplify — Keep the accounting detail available without making it the interface.

The product idea

The user provides the facts. Quees does the thinking.

Once the group, people, expense, payer, and split are known, Quees handles the reconciliation in the background.

01

Input

Record what actually happened.

02

Calculate

Work out fair shares and existing balances.

03

Reconcile

Offset reciprocal amounts and find the net position.

04

Act

Ask for human approval only when money moves.

01 — Group setup

Give shared money a clear context.

A group brings the people and expenses together. Setup stays deliberately light, with explicit acceptance when someone is invited into a shared-money context.

02 — Expense

Record the real-world facts.

The user only needs to provide information they actually know: what was spent, who paid, and who shared the expense.

03 — Split

Keep the common case simple. Handle the exceptions clearly.

Equal splitting is the default. Custom splitting handles the situations where equal is not accurate, with live validation keeping the total correct.

Exact — The allocation matches the expense and can be reviewed.

Under — The interface shows exactly what remains to be allocated.

Over — The interface shows exactly what needs correcting.

No mental arithmetic — The system continuously validates the allocation for the user.

04 — Review

Make the last decision obvious.

Before the expense becomes part of the group, the user gets one clear summary of the amount, payer, participants, and split. After that, the accounting belongs to Quees.

05 — Reconciliation

Turn many expenses into one clear position.

Quees continuously updates the group as expenses and payments change. The default experience surfaces the final net position, not the accounting work behind it.

One net balance — Show the final position between people instead of exposing every reciprocal amount by default.

Clear direction — Make it immediately obvious who owes whom.

Details on demand — Underlying calculations remain available through progressive disclosure.

Automatic state change — Adding an expense updates the group's financial position without another reconciliation task.

06 — Settlement

Only ask for action when money actually moves.

Once Quees has reconciled the group, the user sees the final amount and direction. Paying requires authorization. Being owed does not require the user to manually chase the other person.

You owe — Pay the final net amount and move directly to authorization.

You are owed — Quees surfaces the amount and handles the appropriate payment prompt on the other side.

Authorization — The person whose money moves is the person who approves it.

Settled — Once payment completes, the balance updates automatically.

07 — History

Keep the trail without turning it into the product.

Split history stays inside Split & Settle. It gives people a useful record of expenses, payments, requests, reminders, and settlements without competing with the core experience.

Outcome

A simpler mental model for shared money.

Quees turns shared-expense management into a simple loop: record the facts, let the system reconcile them, then act only when a payment needs approval.

Less bookkeeping

Clearer net balances

Fewer unnecessary transfers

Human authorization only where it matters

Reflection

Good fintech UX hides work, not truth.

The strongest decision was moving reconciliation out of the user's hands. People already know what happened in the real world. Quees should be responsible for figuring out the financial consequence.

The result is a concept that treats shared money as a coordination problem and uses the product to absorb that work.

Record what happened

Let Quees calculate

Show the net outcome

Authorize only when money moves