Rivlet · Legacy Shop-System Rescue

Your shop system is dying. The shop doesn't have to notice.

The desktop app from 2008. The Access database on one aging PC. The legacy E2 or JobBOSS install the vendor stopped caring about. When it fails, production doesn't wait — so the rescue can't either. We stabilize what's running, recover what it knows, and replace what hurts, piece by piece, while the factory keeps shipping.

You're Here Because

One of these is true.

The orphaned system
No one to call

A custom system — Access, FoxPro, a one-developer desktop app — and the person who understood it is gone. Every reboot is a small act of faith.

The sunset product
Support went quiet

Legacy E2, old JobBOSS, a shop package the vendor stopped selling years ago. The forced migration on offer loses your history and your customizations — and you'd still be renting.

The spreadsheet empire
Truth lives in Excel

The system of record stopped being the system of record. Pricing lives in one person's head and three workbooks with names like FINAL-v7-USE-THIS-ONE.

The Rescue

Fixed prices. Known up front.

01 · Free call
An honest read
Free

Tell us what you're running and where it hurts. We'll tell you straight whether a rescue makes sense — including when the honest answer is an off-the-shelf system.

02 · Discovery
The plan
$5,000 · one week

We take the legacy system apart — database, backups, even the application binaries — and hand you a written, actionable rescue plan. Yours to keep and execute with anyone, even if it isn't us.

03 · The rescue
$20–40k, typical
Fixed two-week sprints

Replace what hurts first — order desk, pricing, floor tracking — in fixed-price sprints that each commit to a KPI and end in deployed software you can click. The legacy system stays up until the new one has earned trust. Production never stops.

After cutover: an ongoing platform retainer from $3,500/mo keeps the system evolving with the shop — or hand it to any competent engineer; you own the code, the data, and the deployment.

What it costs against the alternative: a typical rescue lands at or below what shops pay for an off-the-shelf 20-user system — and at the end you own something shaped like your shop instead of renting something shaped like everyone else's.

Proof

We've done this. Recently. Verifiably.

A decades-old make-to-order manufacturer, an undocumented failing 2012-era system, a corrupt first backup, no developer to call. Under eight weeks to a first live deployment; zero days of production stopped.

<8 wks
from kickoff on an undocumented system to a first live deployment
268,861
historical builds replayed to verify the new pricing & production engine
100%
of writes audit-logged — enforced by automated tests
0
days of production stopped during the rescue

The full story — data archaeology, the formula error 400,000 real records settled, the evidence discipline — is on the main page.

Before It Fails On A Friday

Twenty minutes. An honest read. Free.

Tell us what you're running. Worst case, you leave with a clearer picture of your options — including the ones that don't involve us.