Work

Four systems, and what they replaced.

Two of them were aging systems that cost too much to keep. Two began as spreadsheets someone had outgrown. We describe them in operational terms and keep client specifics out of it.

ProjectSectorPattern
VIA · Benchmarking for ExcellenceAssociationModernization
Children's Health PartnersHealthcare-adjacentModernization
Achieve Physical Therapy · Practice EdgeHealthcare-adjacentSpreadsheet to system
MedGym · Baseline testingHealthcare-adjacentSpreadsheet to system

Modernizations

Systems that still did their job but cost too much to keep running, rebuilt on current foundations.

VIA · Benchmarking for Excellence

An aging application, modernized

Sector
Association
Was
A dated application, slow and costly to host
Is
A faster member program with richer data behind it
Changed
Hosting to $0; room to expand and monetize

An existing application still did its job, but it was slow, dated for its users, and carried a monthly bill to keep running. We took it apart and rebuilt it on current foundations.

Performance and the user experience improved substantially, hosting cost went to zero, and the rebuild gave the organization room to expand the program, monetize it, and collect deeper engagement data on its members than the old system could produce.

$80 → $0
Monthly hosting cost
Expanded
Program reach and revenue
Deeper
Member engagement data

Children's Health Partners

A public presence staff can actually run

Sector
Healthcare-adjacent
Was
An aging site on an old stack, with hosting costs and developer-only edits
Is
A fast, mobile-friendly site with a modern CMS
Changed
Hosting to $0; staff publish their own content

The same modernization pattern, applied to the public side of an organization: an old stack rebuilt on current technology, with hosting cost taken to zero and performance and mobile experience improved in the process.

The important change was operational rather than visual. A modern CMS put publishing in the hands of the staff who write the content, so updates no longer wait on a developer, and the rebuild was structured for search and AI-assistant discovery rather than retrofitted for it later.

$0
Monthly hosting cost
Staff-published
No developer in the loop
Faster
Turnaround on changes

Spreadsheet to system

Processes that had outgrown the file they started in, turned into software — and then kept going.

Achieve Physical Therapy · Practice Edge

A spreadsheet that became a product

Sector
Healthcare-adjacent
Was
A sheet tracking where patients came from
Is
A system tying marketing spend to patient ROI
Changed
Became a SaaS product, expanding past physical therapy

Achieve Physical Therapy was tracking where their patients were coming from in a spreadsheet. It answered the first question and none of the ones that followed.

Over time it became a deep system that shows where marketing resources are going and how that spend relates to patient ROI. The model worked well enough — and pointed at a clear gap in the market — that it was turned into a SaaS product, now being expanded beyond physical therapy.

Spreadsheet
→ internal system → SaaS

MedGym · Baseline testing

Four manual steps into one application

Sector
Healthcare-adjacent
Was
Appointments, waivers, data entry and reporting, all by hand
Is
One internal application administrators run the service from
Changed
Less friction per test; deeper insight from the metrics

Baseline testing is a service MedGym offers, but the tracking and the tests themselves were managed by hand across spreadsheets: appointments in one place, waivers in another, data entry after the fact, and reporting rebuilt each time it was needed.

Turning it into an internal application put appointments, waivers, data input, and reporting in one place. Friction dropped at every step of the testing process, and the metrics that came out the other side supported deeper insight than the sheets ever had.

4 → 1
Places the work lives
Less friction
Per test administered
Deeper
Insight from metrics

What the four have in common

Each started with something an organization had outgrown — a sheet, or a system too expensive to keep — not with a platform decision or a technology preference.

Each ended up costing less to run than what it replaced, and produced better data as a side effect of doing the work in one place.

Each kept going after launch. None of them would look the way they do now if the engagement had ended at delivery.

Before Orbitech

Where the experience came from

Systems Brock built before founding Orbitech, for other employers and organizations. They are not client work, but they are the reason the patterns above are familiar.

Manufacturing

Plant operations management

Managers dispatched forklift jobs from a web interface; operators picked them up on the floor from an alert on a Raspberry Pi with LED indicators. Office and floor working from the same queue, with the timing recorded as a by-product.

Internal tool · dispatch · hardware integration

Nonprofit

Food pantry inventory and donation intake

Inventory management with an internal dashboard for donation intake and organization — what came in, what was on hand, and where it went, in one place instead of across several logs.

Internal tool · intake · reporting

Adjacent work

Operational software is the centre of the practice, but the same modernization work often covers the public side — a rebuild on current technology, a CMS your staff can run, and a structure built for search and AI-assistant discovery from the start.

Website rebuildsCMS migrationSEO and AEO structurePerformanceHosting cost reduction

Tell me what is still living in a spreadsheet.

Describe your processBook a 30-minute call