FAQ
Questions to expert
What do you look at before a FinTech project gets underway?
I want to understand what the team is trying to change, what is already in place, and where the main constraints are. That includes the product, existing customer journeys, technical setup, and the people involved in the work. It gives us a clearer picture of what the project actually requires before we start designing solutions.
Where do FinTech projects usually lose momentum?
Usually around decisions. A team may have a clear goal but no agreement on priorities, ownership, or what needs to happen first. When those things stay unresolved, designers and developers end up working around them, and the project starts accumulating rework.
How do you usually partner with FinTech teams?
It depends on what the team already has in place. Sometimes we take full ownership and lead the work from strategy to delivery. Sometimes we join an existing team where specific expertise or capacity is needed. And when the strategy and core team are already in place, we work on a specific market or product challenge and bring the FinTech context and execution support needed.
How do you account for tech complexity when working on a FinTech product?
Tech constraints matter even when we are only redesigning a product. We look at the existing architecture, integrations, data flows, and regulatory requirements before making major UX decisions. That gives the design team a clear picture of what can change, what needs more investigation, and where a better experience has to work within the existing system.
What types of FinTech products do you work on?
We work across different parts of the FinTech digital experience — from mobile and web apps to SaaS-based products and brand platforms. The work might involve redesigning a legacy banking app, designing a B2B payment orchestration platform from scratch, or developing a corporate website for a FinTech company along with the brand assets.






