Case Studies — Real Builds, Real Numbers

Logistics

Legacy rebuild · 2026 · Client under NDA

Fleet dispatch: from 4 seconds to 600ms

A logistics operator ran 120 vehicles from a dispatch platform on shared hosting. Every morning, when every dispatcher logged in at once, pages took four seconds to load. The screens themselves worked — people knew them by heart — so replacing the interface would have added risk without fixing the cause.

120Vehicles

600msp95 morning load

12 wksTo cutover

What we found

Profiling the 6–7 AM window showed three culprits: N+1 query patterns on the main board, missing indexes on the date and depot filters, and dashboard totals recalculated on every page view.

What we changed

Batched vehicle, driver and status lookups into explicit joins
Added composite indexes chosen from the slow-query log
Cached dashboard aggregates in Redis, invalidated on write
Put new endpoints behind the existing routes, strangler-fig style
Ran two weeks of shadow traffic before switching over

The result

p95 morning load dropped from 4.1 seconds to 600ms. Dispatchers saw the same screens on cutover day, so nobody needed retraining. The client received full source, runbooks and monitoring dashboards.

We wrote up the technical detail in Reducing legacy platform load time from 4s to 600ms.

Own product

Product build · SaaS · Live at srt.to

srt.to: a link shortener built for daily use

Every shortener we tried failed in small ways once we depended on it — slugs that couldn't be fixed after a typo, analytics that lagged a day, expiry locked behind enterprise plans. So we built one we'd trust with client campaigns, then opened it to everyone.

<10msTypical redirect

AsyncClick logging

300Free links

How it's built

The redirect path does one thing: look up the slug and redirect. Click events are recorded asynchronously afterwards, so a slow report or a traffic spike on the analytics side can never delay the link someone just tapped. Slugs, expiry, QR codes and workspaces sit behind the same REST API and webhooks we offer to customers. Try srt.to or read why teams outgrow generic short links.

Own product

Product build · Events ERP · Live at evntcue.procellari.com

Evntcue: one record from enquiry to payslip

Event companies typically run sales, crew, stock and payroll in separate tools and re-type the same details at every step. Evntcue keeps a single record that picks up detail as a job moves from lead to quotation, event, roster, attendance, invoice and payslip.

13Modules

2Portals: crew & client

1Login

What's inside

A CRM pipeline and quotation builder for sales; scheduling with an AI-assisted roster, geo check-in attendance and a live crew map for event days; and invoicing with GST, procurement and pay runs for finance. Every list exports to CSV. Explore Evntcue.

Looking for something closer to your project?

Much of our client work can't be published. Tell us what you're planning and we'll share relevant experience within the limits of our agreements. Get in touch.