Skip to main content
Claimdesk

Fictional direction · NDA · Dashboards

Claimdesk

Claims sorted, not piled

Scroll to explore

01 · The brief

Claims sorted, not piled

Show a credible interface without exposing a real client. Same craft level, clear journey, playable interactions.

02 · Inside the product

One scroll, one screen

Each section locks to the viewport — scroll naturally.

Claimdesk

Sort the queue, don’t pile it

Triage the queue

Priorities

128 k€

Close

98,2 %

Focus

14

Close

Triage the queue
Alpha Corp12.4 k€
Bravo SAS16.1 k€
Charlie SARL19.8 k€
Delta SAS23.5 k€
Echo SA27.2 k€
Foxtrot30.9 k€

Clear a Claimdesk queue

Triage the queue

Sélection

Claims sorted, not piled

Fictional tickets · local actions.

Activité

  • We clear P1s before coffee — no opaque pile.

    Élodie · claims

  • Closing a case takes a second, not an email.

    Bruno · mutual

03 · Playable prototype

Touch it

Click, filter, navigate — everything reacts. Nothing hits a real backend: it’s an intent demo.

  • Hero + below-the-fold sections (not just a hook)
  • Visual hierarchy and primary CTA
  • Information density vs readability
Open the full app
Claimdesk

Water damage

P1

Glass claim

P2

Theft report

P1

Local demo — no data is sent.

04 · Same family

Other directions of the same type — to compare density and mood.

Nord/Sud — Cash flow you can read
Nord/SudCash flow you can read
Signal — API health at a glance
SignalAPI health at a glance
Kanban — The board your team actually opens
KanbanThe board your team actually opens
Helm — Sales pipeline, no spreadsheet
HelmSales pipeline, no spreadsheet

05 · What to look at

  1. 01Hero + below-the-fold sections (not just a hook)
  2. 02Visual hierarchy and primary CTA
  3. 03Information density vs readability
  4. 04Interactive states (hover, selection, feedback)

A project in this spirit?

Claimdesk — Claims sorted, not piled | Ilyesse