<aside> 💬

Where the content of this case comes from. This is an iteration on a single screen —the most important one in the product— rather than an entire flow, so the case is deliberately shorter. Golden rule: every outcome metric comes from the Postmortem — Result: Result Experiment & Smart Result (30 Apr → 6 Jul 2026).

</aside>


1. Context

<aside> ⭐

In a nutshell. I iterated on Result —the most important moment and the only permanent screen in the product— so users understand what TaxDown adds on top of the Tax Agency's draft, and convert.

It's the last screen users see before deciding whether to pay, and the only one that's always there.

Average savings ≈€400.

~80% of users see their result when they finish the flow; the rest are left without a number.

</aside>

Role Product Design Lead — I led the iteration end to end
Platform TaxDown app (Desktop, iOS, Android, Responsive)
Team Imagineering squad (product, tax, ops, support, engineering, AI)
Timeline April → July 2026 · experiments and Smart Result shipped mid tax season

2. Business Problem

<aside> ⭐

In a nutshell. If users don't understand the screen, they don't convert. And conversion drops depending on the result: we only hold it up when it's a refund → a scalability problem.

Result is a critical point in the funnel: many users come in just to find out their result and, once they have it, leave without buying a plan.

If the Result screen doesn't win them over, we don't generate the lead that turns into a paying customer.

The problem had three sides:

3. User Problem