What makes financial services UX different from other enterprise design?
Three things compound. Regulation dictates parts of the interface, so some friction cannot be designed away and the job becomes making it tolerable. Legacy core systems constrain what a new front end can do, which means design decisions get overruled by architecture nobody wants to discuss. And consequence is asymmetric, since a mistake in a transfer or a trade costs real money and trust that does not return. Ask a candidate agency about a flow they were not allowed to simplify. The answer separates domain experience from a good portfolio.
Should we hire a specialist or a strong generalist?
For core banking, treasury, underwriting, or anything with heavy compliance surface, hire the specialist. The vocabulary and workflows take months to learn and you would be paying a generalist to learn them on your project. For a consumer-facing product with straightforward mechanics, a strong general product studio often brings fresher thinking to an interface the specialists have designed the same way for years. The clean test is whether your hardest problem is domain knowledge or design craft.
How do we test whether an agency really understands compliance?
Ask for a specific example where a regulatory requirement changed the interface, and what they did about it. Then ask who they interviewed. Agencies with genuine depth talk about compliance officers, underwriters, and relationship managers as users with their own research needs. Agencies without it talk only about customers and describe compliance as a constraint they worked around, which usually means they redesigned something and legal rejected it.
How much does the internal system matter compared to the customer app?
More than most institutions budget for. The customer app gets the attention and the executive sponsorship, but the internal system determines how fast your staff can actually serve those customers, and it is usually the older and worse-designed of the two. If your service metrics are the problem rather than your acquisition metrics, the internal tooling is where the design money should go.
What does financial services UX cost?
More than comparable general product work, because domain knowledge is part of what you are buying and review cycles run longer. A defined product engagement commonly starts in the tens of thousands. Enterprise programmes with multiple user types, a design system, and compliance review run well into six figures. European studios sit materially below US rates for comparable quality, which is a real option on a long engagement rather than a compromise.
How long should we expect a project to take?
Twelve to twenty weeks for research and design on a defined product, with stakeholder and compliance review rather than design time accounting for most of the difference from consumer work. Core banking and enterprise programmes are multi-quarter and phased by necessity. Build legal and compliance review into the schedule as a named step with an owner, because discovering it late is the most common reason financial design projects slip.
