Simplifying with tilliX
Hack4Impact is working with Edu-Futuro, a non-profit service that works with immigrants and the Latinx community with the mission of breaking the cycle of poverty.
🖊️ Role
Solo UX Designer
🗓️ Timeline
Sept 2024 - Dec 2025
🔧 Tools
Figma, Linear, FigJam, Datadog
Streamlining invoice management and payments for enterprise clients
Context
When money moves through screens, what makes the experience feel safe?
tilliX empowers companies to simplify how their customers manage and pay invoices.
I led the design of two pillars: QuickPay, a fast lane for one-time payments, and the post-login dashboard, where users track invoices, analytics, and payment methods.
This project was about removing friction, scaling clarity, and grounding every flow in how people actually pay, not how we assume they do.
Problem Statement
How do we design a system that earns trust with every transaction?
tilliX aimed to bridge two opposing efficiency and security in the way companies handle payments.
Users struggled with fragmented flows and unclear priorities.
Designing for Two Paths, One Purpose
QuickPay and the post-login dashboard served the same goal -> helping users pay confidently but demanded two entirely different mindsets.
QuickPay was built for speed and trust at first sight… a lightweight, single-task flow that minimized decisions. Every element served immediacy: one screen, few inputs, visible verification, and clear reassurance.
Post-Login required depth and continuity. A system that scaled across invoices, analytics, and payment management. It emphasized persistence: saving context, maintaining history, and empowering long-term control.
To differentiate them, I designed for intent.
QuickPay speaks to action without commitment — fast, frictionless, transient.
Post-login speaks to relationship and structure — organized, persistent, expandable.
User Research
I spoke with client teams, reviewed support logs, and mapped user behaviors across the payment flow.
Patterns emerged:
Users hesitated to trust on-screen confirmations.
Dashboards overwhelmed more than they guided.
Payment flows demanded too many steps.
These insights reframed the problem that trust wasn’t just technical; it was emotional and visual.
Final Creations
Designing a platform that builds understanding, trust, and confidence in action.
QuickPay Portal
Users can review multiple invoices, verify details, and complete payments securely — all within one screen.
Integrated verification and real-time OTP authentication to reinforce security.
Users can review multiple invoices, verify details, and complete payments securely, all within one screen.
The new QuickPay interface reduces friction by surfacing payment clarity, trust, and speed.
Post Login Portal
Users can review multiple invoices, verify details, and complete payments securely — all within one screen.
In the Invoices Overview, users see everything that matters at a glance, totals, due dates, and payment status, organized through clear visual hierarchy. The sidebar navigation grounds orientation while preserving space for what’s essential: action.
Reimagined transparency by merging invoice review, payment, and conversation into one screen. Clarity without context-switching.
The wallets purpose was to have a place to fix all card related issues in advance to payment checkouts.
Across these interfaces, the design system holds a single promise: clarity builds trust. Every component reinforces that paying bills should feel as structured as it is secure.
Takeaways
At first, I was nervous about making the “right” decisions, especially when it came to flows involving money and ensuring security, like knowing their information and protected and the right steps to proving that. I found myself second-guessing small interactions, wondering if they were intuitive enough or if I'd missed something a user might struggle with.
One of the biggest lessons was learning to slow down and truly advocate for the user. I pushed myself to ask more questions with the engineers, asking about the restraints and try to understand concepts within software engineering that I was unfamilar with, revisit real user behaviors, and propose alternative solutionse even if it meant redesigning components late in the process.
I came away from this project with a deeper trust in my process. I learned that with with revisions and sketchs and asking questions, clarity builds.
