Platforms still running.

The work worth showing is the work that survived contact with production for a few years. That is the only kind that gets written up here.

Our standard

What has to be true before something appears here.

Nothing behind a form

Case studies are readable without an email address. Gating a case study tells you the case study is marketing.

Numbers, cleared by the client

Every figure on a case study page is one the client has seen and agreed to publish. That is slower than writing them ourselves and it is the only way they mean anything.

Still in production

We write up platforms that are still running, not projects that shipped once and were quietly replaced.

Case study

Eighteen months on one platform, shipping every week.

Weel runs last-mile delivery for pharmacies: an order raised at the counter, picked up by a courier, signed for at the door, reconciled against what was actually collected. We came in on the interface layer and stayed — the design system every screen is drawn from, order creation and dispatch, proof of delivery, and the reporting pharmacies hand to their own auditors.

Weel Systems Inc.

18months, and still the same engagement

7dbetween production releases

21dfrom inception to production

4product areas shipped end to end

Nine identical milled aluminium tiles laid out in a precise grid, each anodised in the same cyan-to-violet gradient.

Pharmacy last-mile logistics

A design system the product is assembled from

Two token files now generate every colour, type and spacing value in the product, with 16 documented components behind them.

Styling had been decided screen by screen. We moved it to a single pipeline: primitives and semantics in source control, generating both the CSS variables the app consumes and typed tokens the engineers import. Light and dark are one switch rather than two stylesheets, and a new screen is assembled from documented parts instead of redrawn.

A single anodised aluminium ribbon dividing into three parallel routes that curve away across a white surface.

Pharmacy last-mile logistics

Order creation rebuilt around the counter

Nine findings from a single client review shipped in one release, including the two that pharmacy staff raised first.

The customer picker showed a phone number where staff needed the delivery address, the person raising the order typed their own name into a free-text field, and opening an order meant finding a small icon in a crowded row. We watched the work being done, then shipped the whole set together: address on select, submitter filled from the session, the full row clickable.

A stack of thin milled aluminium sheets fanned apart like pages, each edge anodised cyan to violet.

Pharmacy last-mile logistics

Proof of delivery, and the report that settles the argument

An eleven-column delivery report that resolves a disputed drop-off without an investigation.

A patient said a delivery never arrived; it had been left at reception. The record now captures who received it and in what capacity, and the report prints the whole chain — status, courier, prep time, actual completion, signature, amount requested against amount collected — on one A4 page a pharmacy can hand to an auditor.

If you want a reference rather than a write-up, ask. We will put you in touch with a client directly, which is a stronger signal than a page we wrote about ourselves. hello@infinite.dev

Want the version with the numbers in it?

Tell us the sector and we will send the closest engagement we are cleared to talk about.

Start a conversation

Tell us what you are trying to ship.

You will get a reply from an engineer, not a form handler. If we are not the right firm for it, we will say so and tell you who is.

Head office — 3465 Platinum Drive, Mississauga, Ontario

Delivery office — Islamabad

hello@infinite.dev