Simplifying with tilliX
Designing a seamless QuickPay portal and post-login experience to help customers manage bills with ease and clarity.
Role
UX Designer
Timeline
Sept 2024 - Dec 2025
Tools
Figma, Linear, FigJam, Datadog
Streamlining invoice management and payments for enterprise clients
tilliX is a platform that provides companies with tools to help their customers manage and pay their bills efficiently. The QuickPay portal is a product tilliX is developing to offer companies a seamless way for their customers to handle payments. Additionally, tilliX required an improved post-login experience that offered seamless navigation to invoices, analytics, and payment options.
My goal was to reduce user friction, establish a design foundation that could grow, and ensure every screen reflected the real goals and behaviors of the people using it.
Problem Statement
Companies need a more efficient and secure way to manage and pay invoices.
To address this, tilliX is developing this product to provide a seamless and secure payment solution. The primary challenges included:
Users struggled with navigating existing payment flows.
The post-login dashboard needed a clearer hierarchy to guide users to key actions.
High-priority actions like paying invoices, enrolling in Auto Pay, managing payment methods, and downloading receipts, while still supporting lower-priority needs like communication preferences or support access.
The QuickPay portal had to be optimized for both first-time and returning users.
Security was a key concern, ensuring that users could safely enter and process their payments without risks.
My Role
As the primary UX designer on Tillix’s QuickPay portal, I led the effort to improve how customers, like Washington Gas users, pay invoices quickly and securely. I worked closely with developers and collaborated with stakeholders across engineering and client-facing teams toensure intuitive, accurate and cohesive experience. My focus was on streamlining the payment process, reinforcing trust through clean visual design and clear language, and creating a flexible structure that could support a variety of clients. I also ensured that the new experience aligned with the larger Tillix product ecosystem, contributing to a more cohesive platform experience overall.
Research
I analyzed the system from the inside out to understand what users were really experiencing.
When I joined the tilliX project, there was no formal UX research or existing design system for the company to lean on. I worked closely with a senior software engineer to reverse-engineer the product experience, identifying friction points directly from the interface itself.
I manually mapped out the end-to-end user journey, exploring how users paid invoices, viewed analytics, and navigated after login. This self-led audit helped me surface specific issues:
Payment actions were buried and took too many steps to complete
The login flow dropped users into a cluttered, non-prioritized dashboard
There were no visual cues reinforcing trust or security, despite robust backend protections
The structure lacked flexibility to support upcoming features or third-party integrations
Discovery
When I joined the tilliX project, there was no formal UX research or existing design system for the company to lean on. I worked closely with a senior software engineer to reverse-engineer the product experience, identifying friction points directly from the interface itself.
I manually mapped out the end-to-end user journey, exploring how users paid invoices, viewed analytics, and navigated after login. This self-led audit helped me surface specific issues:
Payment actions were buried and took too many steps to complete
The login flow dropped users into a cluttered, non-prioritized dashboard
There were no visual cues reinforcing trust or security, despite robust backend protections
The structure lacked flexibility to support upcoming features or third-party integrations
Final Creations
How can I design a website that helps enterprise clients understand, trust, and take action on tilli’s product offerings?
QuickPay Portal
Users can easily enter their customer number, verify details, and pay invoices securely.
A progressive disclosure approach keeps the interface minimal yet informative.
Integrated multiple payment methods for flexibility.
Ensured secure payment transactions with data encryption and real-time fraud detection measures.
Post Login Portal
A redesigned dashboard provides clear access to invoices, analytics, and payment settings.
Sidebar navigation improves user flow and reduces cognitive load.
The interface is scalable for future enhancements, such as Google Wallet integration.
Implemented session timeouts and authentication checkpoints for added security.
How the final product addressed user and business needs
QuickPay Portal
Users can easily enter their customer number, verify details, and pay invoices securely.
A progressive disclosure approach keeps the interface minimal yet informative.
Integrated multiple payment methods for flexibility.
Ensured secure payment transactions with data encryption and real-time fraud detection measures.
Post Login Portal
A redesigned dashboard provides clear access to invoices, analytics, and payment settings.
Sidebar navigation improves user flow and reduces cognitive load.
The interface is scalable for future enhancements, such as Google Wallet integration.
Implemented session timeouts and authentication checkpoints for added security.
Reflection
This project was the first time I was given full ownership of a product experience that would directly affect real customers at scale. At first, I was nervous about making the “right” decisions, especially when it came to flows involving money and trust, like Auto Pay enrollment and invoice visibility. 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, even when timelines were tight. There were moments when it felt easier to just accept an engineering constraint or keep the design “safe.” But I pushed myself to ask more questions, revisit real user behaviors, and propose alternative solutions—even if it meant redesigning components late in the game. Those conversations, although uncomfortable at times, helped me grow into someone who can hold both empathy and clarity in the design process.
This experience also showed me how complex enterprise UX can be. Behind a seemingly simple action like “Pay Now” is a tangle of edge cases, backend logic, and third-party systems. I learned to map those connections visually to understand them better and to communicate more effectively across teams. It taught me that good UX isn’t just what you see… it’s also the systems underneath that enable that simplicity.
