I spent 25 years building enterprise systems at a large financial institution. Then I started fostering.
I found myself on the other side of the world. Rescue work is so much fun, and love, a mission everyone agrees on, and teams pulling off amazing feats to save pets.
What I didn't find were processes, infrastructure, roles, playbooks, benchmarks, goals. I really didn't miss them at first. Until I started thinking: why is it taking so long to get pets adopted from the South when there is a shortage of pets in the North?
The gap almost broke my brain.
In my day job, I watched logistics get solved decades ago. FedEx gave you a tracking number in 1994. Amazon turned package delivery into a notification stream by 2005. Enterprise software figured out how to give every party exactly the information they need, and nothing they do not, so drivers stay focused, receivers know what is coming, and the system hums without forty people in a group chat.
Then I'd open my phone and see a rescue transport thread. Fifty people. The driver, every rescue, every adopter. What's the address for stop three? Did the paperwork for the lab mix get packed? Running 30 minutes late. Relevant questions buried under noise, and the driver scrolling through messages at a rest stop instead of driving.
The Notebook
The rescue's transport coordinator keeps a spiral notebook. Every run: the pets, the adopters, the addresses, the stops, the paperwork envelopes. One wrong weight, one mismatched pairing, one forgotten detail, and there is a problem nobody catches until a pet is at the wrong exit on I-81.
Meanwhile, the transport provider is juggling the same data across multiple rescues, trying to plan their load. They're texting back and forth to confirm pet weights, crate sizes, pickup windows. Every exchange is an opportunity for error. Every error cascades.
What Enterprise Logistics Solved 30 Years Ago
Here is what I know from the other side.
One record, every party
When a shipment moves through a supply chain, there's one canonical record. Everyone sees what they need. Nobody duplicates data across notebooks and text messages.
Per-party views
The driver doesn't see billing. The receiver doesn't see supplier costs. Each role gets exactly their slice: no noise, no confusion, no scrolling past forty irrelevant messages to find their stop address.
Confirmation flows
Professional delivery tools have one-tap confirms, checkoffs, arrival photos. The driver stays focused on the road. Operations knows the run is progressing. Receivers know when their shipment arrives.
Rescue transport has none of this. Not because it's hard. Because nobody has built it.
The Real Cost
This isn't a technology complaint. It's about the people doing the work.
The rescue's transport coordinator is a project manager running logistics without tools. The transport provider is a driver fielding forty texts while behind the wheel. The adopter is refreshing their phone wondering if the 2 p.m. arrival is still happening. And the pet? The pet is in a crate with a paper envelope taped to it, hoping nothing got lost.
These are animal people, not logistics people, not project managers. They're doing whatever's asked with whatever tools they've got. The problem isn't them. It's that nobody ever gave them the infrastructure.
What Changes When You Build It
When every party gets exactly the information they need (one record, per-party views, professional delivery tools), everything downstream changes.
Three things happen
- The driver stays focused on the road, not on a group text.
- Errors get caught before they reach the highway, not after a pet is at the wrong exit.
- Receivers get clarity. They know when their pet arrives, not when someone remembers to text.
This isn't science fiction. It's what every logistics company figured out in the 1990s. Rescue deserves the same.
I built enterprise systems for 25 years. I've fostered hundreds of pets. I've watched this gap cost time, money, and safety, for years. So our team is building the platform that closes it.