Case notes

8 min read

The four-minute pay run

How we cut a three-hour task to four minutes by removing decisions, not screens.

When I joined Orrin, a pay run took most of an afternoon. The interface wasn’t bad; it just asked the same questions every month.

I timed eleven real pay runs. Two steps took 80% of the time: matching invoices to people and re-checking bank details that hadn’t changed.

We moved both into the background. The pay run card now shows only what changed since last month, and everything else is pre-checked.

The lesson I took away: count decisions, not clicks. A screen with one real decision beats a wizard with five fake ones.

[05]

KEEP READING

More from the journal

[12]Next step

Got a messy workflow? Let's untangleText · 104 it.

Tell me what's slow, confusing or costing you support tickets. I reply within one working day with a first idea and a fixed price.

Book a 20-min intro

Local time ● online

--:--:--
Rotterdam. I reply within one working day, usually faster.

Version history v26.10

v26.10Added the Kiln Audio case studyv26.07New journal: receptionists and booking flowsv26.04Orrin pay run results are inv26.01Portfolio rebuilt as a design file
© 2026 Noor Castell. Built in Framer.Rotterdam · AmsterdamBack to top ↑

Create a free website with Framer, the website builder loved by startups, designers and agencies.