Client Outcomes

Design decisions that held up in production

38 mobile products shipped
since 2014

These are accounts from clients who brought us into existing product teams or greenfield builds. Each one had a different problem, a different constraint, and a different definition of done. What follows is what actually happened — not a curated highlight reel.

Mobile app interface design work in progress at Prizavento studio

Three engagements, three different starting points

Each account reflects a single client project. Figures are approximate and drawn from project documentation shared with our consent.

Logistics · Android & iOS

A driver app that dispatchers refused to touch

Harven Logistics had an internal mobile app built by a contractor 18 months prior. Field drivers used it daily but the dispatch team — who needed to reassign jobs in real time — avoided it entirely and reverted to phone calls. The core issue was not missing features. The information hierarchy made time-sensitive decisions feel impossible to execute quickly.

We spent the first two weeks embedded with the dispatch team, mapping every decision they made during a shift and the data each decision required. The redesign reorganised the entire job-management flow around urgency tiers rather than job type. Dispatchers could see at a glance which assignments were at risk without scrolling through a flat list.

Tobias Wernecke Head of Digital Product, Harven Logistics

"The previous version had all the right data — it just made you work to find it. After the redesign, the dispatch team adopted it within the first week. That was the real test."

11 weeks from audit
to shipped update

Information architecture Field research Android-first

Health Tech · iOS

Onboarding that lost people before the first session

Kettlewood Health launched a guided wellbeing app with strong clinical backing but a registration flow that required 23 taps before a user reached any actual content. Their retention data at day 3 was sitting at 19%. The founding team had iterated on the flow internally several times but each version added steps rather than removing them.

Our approach was to prototype three structurally different onboarding models and run unmoderated remote tests with 12 participants recruited from their existing user base. The version that performed best deferred all preference-gathering to the second session and front-loaded a single meaningful interaction. It cut the registration path to 8 taps. Day-3 retention moved to 41% over the following month of data collection.

Sloane Rafferty Co-founder, Kettlewood Health

"We had been adding things to fix the problem. Prizavento showed us the problem was the adding itself."

8 taps to first
meaningful interaction

Usability testing Onboarding design Retention-focused

Financial Services · iOS & Android

A design system built for one platform, deployed across three

Orvex Financial needed a unified component library that could serve their consumer app, their adviser-facing tablet tool, and an internal compliance dashboard — all from a single Figma source. Their product team had three designers working across these surfaces with no shared token structure, which meant every sprint introduced visual inconsistencies that engineering had to manually reconcile.

We built the system foundation over eight weeks: a token hierarchy covering colour, spacing, and type scale, with component variants documented for both compact and expanded viewports. The adviser tablet tool was the most complex surface — dense data tables needed to remain legible without reducing font size below 14px on any supported device. Every component shipped with accessibility annotations and contrast-checked states.

Priya Nambiar VP Product, Orvex Financial

"Having one source of truth changed how our designers and engineers talked to each other. Fewer review cycles, fewer last-minute fixes before release."

3 product surfaces
from one design system

Design systems Multi-platform Accessibility

Engagement type Embedded & advisory

Typical team size 1–3 Prizavento designers

Delivery format Remote-first, async-capable

Handoff standard Figma + annotated specs

Across all engagements 83%

of clients return for a second project

That figure comes from our own project records across a decade of work. It is not a goal we set — it is a pattern we noticed. Clients tend to come back when the first engagement produced something that worked in the real conditions of their product, not just in the prototype.

The work on these pages represents a fraction of what we have shipped. Some clients prefer not to be named publicly. What all of them share is that the problems they brought us were specific, the constraints were real, and the outcomes were measurable — even when the measurement took a few months to arrive.

4.2

Average project duration Months from kickoff to final handoff, across all completed engagements in the past four years

States and territories reached Client teams based across every Australian state, plus remote-first teams without a fixed office location

Projects handed off without testing Every design we deliver has been validated with real users at least once before the final Figma file is transferred

Accessibility-audited products Formally reviewed against WCAG 2.1 AA criteria, with remediation documented for engineering teams