Skip to content

Case studies · 18 · 5 domains

Every case study starts with what could not change.

Each of the 18 case studies lays out the decisions and the numbers. None has screenshots, because clients stay unnamed and their systems sit behind logins.

18

Case studies

5

Domains

2

Client products sold

[01] Platforms and design systems01 / 18

The same components had to run on Next.js, Vite and React Native without the web and mobile versions drifting apart.

One component set for Next.js, Vite and React NativeOpen →
01 / 05

Platforms and design systems

Systems other teams build on: component libraries, white-label theming and code standards that the build enforces.

Counted74components in CDS, our own cross-platform design system
Counted30+white-label brands on one design system of ~100 components
Estimate~50%higher team throughput once standards were checked in CI
02 / 05

Marketplace and revenue

A marketplace that earns from what it measures. We spent four years rebuilding it while it kept taking payments.

Counted0recorded outages across four phases
Derived2M+analytics writes a day, read live and kept for a year
Counted506API routes and 194 migrations in the main service
03 / 05

Identity and documents

Software where a mistake has legal weight: passports, remote identity checks, invoices and payment hardware.

Measured~98%cases with a reliable model suggestion, and an operator confirmed every case
Counted100+payment terminals running a React Native app we built
Constraint1 dayoffline window for passport applications taken in the field
04 / 05

Data and infrastructure

Making existing systems fast and cheap without rewriting what already works.

Measured0.2 sfor a report that used to take over 15 minutes
Measured0.1 sfor a second report that took 4 minutes
Measured$2kmonthly AWS bill, down from $24k
05 / 05

Business systems and integrations

Software that works alongside ERP, CRM and payment partners, and leaves them in place.

Counted150,000items across 15 warehouses, with SAP kept as the system of record
Counted4markets, each with the payment partner that market requires
OutcomeSoldthe client’s meetings platform was acquired by a US bank

Case study 19

Working on a similar problem? We reply within one business day.

The first call takes 30 minutes, and you’re under no obligation.

Tell us about your projectcontact@microtech.consulting
AboutWho we are and the work we get called in for.About us →WritingPosts that go deeper into the problems behind these case studies.Read the blog →