Work

Systems we built and still look after.

Client names are withheld under NDA. Each summary is written with the client's approval and describes the problem, what we built, and what changed.

Server racks with colored cabling

Logistics · Web · Mobile · Cloud

Regional logistics dispatch platform

A 120-truck regional carrier was running dispatch on a desktop application from 2009 and a wall of whiteboards.

  • Built: cloud dispatch console, driver mobile app with offline proof-of-delivery, customer tracking portal.
  • Integrated: existing accounting system and telematics provider; no data re-entry.
  • Result: same-day deliveries up 31% in the first quarter; dispatcher headcount unchanged while volume grew 2×.

Engagement: 7-month build, then ongoing maintenance retainer.

Analytics dashboard on a laptop screen

Healthcare · Systems integration

Multi-site clinic operations

Nine clinics, three scheduling tools, two billing systems, and a monthly report assembled by hand over four days.

  • Built: an integration layer and data warehouse that reconciles scheduling, billing, and the EHR nightly.
  • Kept: the EHR. Replacing it was never the right call.
  • Result: the monthly report runs itself; billing errors caught within 24 hours instead of 30 days.

Engagement: 4-month build, HIPAA-aligned hosting and monitoring ongoing.

Engineer at a laptop in a manufacturing lab

Manufacturing · Automation · Advisory

Shop-floor automation

A precision machining shop quoted every job by hand from CAD files and email threads. Quotes took days; errors cost margin.

  • Built: automated quoting from CAD metadata and material pricing, with work-order generation into the shop's existing ERP.
  • Advised: fractional CTO support while they hired their first in-house developer.
  • Result: four days of admin per week became forty minutes; quote accuracy up, turnaround from 3 days to same-day.

Engagement: 10-week build plus 12 months of advisory.

Laptop showing business analytics charts

Financial services · Cloud · IT consulting

Cloud migration and cost reset

A lending firm's cloud bill had tripled in two years. Nobody could say what most of it was for.

  • Assessed: full inventory of workloads, access, and spend in three weeks.
  • Migrated: consolidated two cloud accounts into one with infrastructure-as-code and least-privilege access.
  • Result: 38% lower monthly spend; passed their next SOC 2 audit with no infrastructure findings.

Engagement: 3-week assessment, 3-month implementation.

We had been told by two other firms that we needed to replace everything. Livid told us we needed to replace almost nothing. They were right.
Practice Administrator, multi-site clinic client

Have a similar problem?

Tell us about it. We will share the closest thing we have done and what we learned.

Start a conversation →