Prestige

Both layers are shown below.

Programme

Every case study, one row each. The result is in front; the working is one toggle away.

PRS-2025-003

Ledger Cutover

Month-end reconciliation fell from 3 h 10 min to 14 min, with no downtime in the close window.

Backend · Go · PostgreSQL · Kafka

14 weeks · 4 people · −93%

6 steps · 1 trapdoor

PRS-2025-002

Festival Door

Load-in for 61 trucks cleared in 58 minutes instead of 3 h 05, with no queue on the public road.

Events-Logistics · Airtable · Handheld Scanners · WhatsApp

26 weeks · 3 staff + 9 volunteers · −69%

7 steps

PRS-2025-001

Pickup Point Finder

Support contacts about missing parcels fell 45% after the pickup flow was rebuilt around the question people actually ask.

Product-Design · Figma · Maze · Amplitude

11 weeks · 3 people · −45%

Related trapdoor entries

TD-001 ·

Severity: Minor

Related case study: Ledger Cutover

The cohort that posted twice

What
Cohort 3 posted 212 ledger lines twice for nine minutes during the cutover.
Cause
A consumer replayed an offset after a partition rebalance, and the posting call was not idempotent.
Cost
Three hours of cleanup and reconciliation. No money moved: payments were still gated by the batch.
Changed
Every posting carries an idempotency key. Each cohort starts with a replay drill on a copy.