CAPITAEDGEX
A concept demo for AI-assisted invoicing, payment reminders and client collections for freelancers and small businesses.
- Type
- Concept demo
- Industry
- SaaS / Fintech
- Year
- 2026
- Focus
- Invoice triage UX
CapitaEdgeX is a self-initiated product exploration. It processes no payments, connects to no bank or accounting system, and has no users, invoices or revenue behind it. Every figure shown in the interface is invented for demonstration.
01 — Product hypothesis
Invoicing tools store records. Freelancers need to know who to chase.
Show how invoicing and collections software could feel if the interface made the next action obvious instead of burying it inside settings and tables.
Intended user
Freelancers and small teams
Situation
Money owed, attention scarce
Hypothesis
Lead with the decision
02 — Category UX problem
Financial interfaces hide the next action inside density
The demo was designed against three failure patterns common to small-business finance tools.
Ledger as home screen
Opening onto a sortable table of every invoice pushes triage work onto the user each time they log in.
State buried in text
Status expressed only as a word in a column forces reading rather than scanning.
Invisible follow-ups
Reminder automation hidden inside settings makes users distrust it and re-send manually.
03 — Primary journey
The invoice lifecycle the interface is built around
This is the designed product flow expressed in the prototype. It is a demonstration of interface states, not an operating financial system.
- 01
Created
Draft invoice assembled; nothing is chased yet.
- 02
Sent
Marked as issued and enters the waiting state with a due date.
- 03
Due
Approaching the date; surfaced early so the reminder is not a surprise.
- 04
Overdue
Escalated visually and promoted into today's attention list.
- 05
Reminder sequence
A visible ordered set of follow-ups the user can read and edit.
- 06
Resolved
Closed out and removed from the attention list.
Designed flow only. No payment processing, banking connection or automated sending exists in this prototype.
04 — Interface decisions
Reducing complexity without hiding money
- 01
Open on attention, not on records
The dashboard's first block answers what needs chasing today; the full ledger is one step away for the times it is actually needed.
Trade-off — Users who want a spreadsheet view have to navigate rather than land on it.
- 02
Express invoice state visually
Draft, sent, due, overdue and resolved each carry their own weight and colour so a list can be scanned instead of read.
Trade-off — State colour must survive contrast checks and never be the only carrier of meaning, so labels stay alongside.
- 03
Show reminder sequences as a timeline
Follow-ups are presented as a readable ordered sequence rather than automation rules, so the user always knows what would go out next.
Trade-off — Less power than a rule builder; deliberately narrower.
- 04
Keep numbers calm
Tabular figures, restrained accent use and generous spacing keep financial density legible instead of alarming.
Trade-off — Fewer values per screen than a conventional finance table.
05 — Experience architecture
How the surfaces stack
A map of the prototype's designed surfaces and shared components. It documents structure, not backend infrastructure — no services, ledgers or integrations sit behind these screens.
06 — Interface view
The prototype in one screen
07 — Responsive behaviour
Financial density on a phone
1440px
Attention list and ledger sit side by side without either dominating.
1024px
Ledger drops below the attention list; state badges keep full labels.
768px
Table rows become stacked cards so amounts and states stay paired.
390px
One decision per row, tabular figures kept intact, no horizontal scroll.
08 — Role & contribution
Role & contribution
Self-initiated concept demo. It has no paying users and no measured commercial results — it exists to demonstrate product thinking and frontend execution in a fintech context.
Concept
Self-initiated; no client brief and no commercial engagement.
Product thinking
Invoice lifecycle model and dashboard hierarchy.
UI/UX design
Attention list, invoice states and reminder sequence surfaces.
Frontend build
Responsive React and TypeScript prototype.
Data
Every client name, amount and date in the demo is invented.
Boundaries of this concept
- No payment processing, card rails or settlement of any kind.
- No banking, accounting or tax integrations.
- No AI automation is claimed — reminder sequences are designed flows, not learned behaviour.
- No users, invoices, revenue or measured collection results exist.
09 — Outcome
Design outcome
A dashboard organised around decisions rather than records
An industry-specific interface system for financial data
A responsive product experience across all breakpoints
Reusable component architecture for SaaS surfaces
What this demonstrates is design judgement in a financial context — not product traction.
Want work like this for your project?
Trust Me Studio takes on a small number of projects at a time. If this is the standard you're looking for, start a conversation.