Back to blog

ProductJun 10, 2026 · 6 min read

Designing Clever Clerk’s zero-inbox workflow

Most tools help you process work faster. We wanted Clever Clerk to help you finish. The design decisions behind a queue that is actually meant to hit empty.

Hands writing in a notebook with a pen, beside a stack of books

Inbox-style interfaces have a dirty secret: they are designed to be refilled. Infinite lists, badges, "smart" resurfacing — the metrics they optimize reward time spent, not work finished.

Clever Clerk processes clerical casework, and casework has a property most software ignores: a case is either done or it is not. We decided the interface should be as binary as the work.

One case at a time

The core screen shows exactly one case. Not a list with a preview pane — one case, full width, with every document and decision it needs. The queue exists, but you have to deliberately leave the case to see it.

In testing, this felt slower to everyone and measured faster for everyone. Median case completion dropped 22% because nobody was half-reading three cases at once.

The queue hitting zero is a designed moment. It has its own screen. People screenshot it.

Letting the interface end

When the queue is empty, Clever Clerk does not suggest more work. It shows a summary of what you closed and stops. The absence of a next thing is the feature.

Six months in, the pattern held: teams on the zero-inbox flow close 31% more cases per week than teams on the classic list view — and report lower stress doing it.

Related insights

Keep reading