Product / Fintech

verer

The outcome

A banking app that gets out of the way.

Verer v1 — home

Series A → v1·iOS + Android·16 weeks·Completion up, tickets down·Series A → v1·iOS + Android·16 weeks·Completion up, tickets down·

Stage

Series A → v1

Platform

iOS + Android

Timeline

16 weeks

Result

Completion up, tickets down

The challenge

Verer had the licences, the backend, and a prototype that made simple things feel like paperwork.

Users could move money — they just did not trust that they had. Every transfer ended in a small, quiet moment of doubt. The product was not missing features. It was missing confidence.

2 weeks

with real users was all it took to see the problem was confidence, not features.

What we did

01

Discovery

The problem was confidence, not features.

Two weeks with real users showed the problem was not features, it was confidence. Every screen needed to answer did that work before the user had to ask.

02

Product Design

We rebuilt the core loops around reassurance.

Move, save, confirm — rebuilt around clarity and reassurance. Fewer steps, louder confirmations, no dead ends.

03

Design System

A system the in-house team could extend without us.

Components, tokens and patterns documented so the team could ship confidently after we left.

04

Ship & Iterate

We stayed through launch and cut what did not earn its place.

We watched the funnels and cut the two steps that data said nobody needed.

Move. Save. Confirm.

Gallery

Verer v1 — key flow

Detail — confirmation

Detail — states

States overview

Motion still

Team

Fenn — New York

Disciplines

Research, Product Design, Design Systems

Partners

Verer in-house team

Duration

16 weeks · 2024

Proof

+31%

Task completion on core money-movement flows.

−44%

Support tickets asking did my transfer go through.

They gave our users something we could not: the confidence to trust their own money.

— Dana Osei, Head of Product, Verer

Next project

Open for new work — 2026

Got a problem worth sitting with?