People ask us this a lot, usually some version of "do you work with city shelters?" The short answer is no. The longer answer is that it's one of the more deliberate decisions I've made with PawPlacer, and it's probably worth explaining.
Two very different worlds
Municipal animal control and independent rescue sound like they're in the same business. They're not.
A city shelter operates under government mandates. Legal hold periods, bite quarantine protocols, court-ordered seizures, stray intake requirements, and a mountain of compliance reporting. Their software needs to generate state reports, manage evidence chains for cruelty cases, and integrate with law enforcement databases. A large metro shelter might process 10,000+ animals a year with a staff of 50.
A volunteer-run rescue pulling dogs from that same city shelter? Completely different universe. No building, no kennels, no government reporting. Just a network of foster homes, a shared Google Drive that's seen better days, and a group chat where someone at 11 PM asks "can anyone take an emergency intake tomorrow morning?" followed by seven thumbs-up emojis.
What that rescue needs is simpler on paper but harder to actually build well: a way to keep track of animals spread across dozens of foster homes, medical records that follow the pet instead of living in someone's notebook, adoption applications that don't disappear into an email inbox, and a Petfinder integration that doesn't make you want to throw your laptop out a window. On a phone. For free or close to it. And it has to be learnable in five minutes because your volunteers are donating their Saturday, not signing up for a training webinar.
Why not build for both?
Money, mostly. Municipal contracts pay well. A single county deal can be worth more than a thousand small rescue subscriptions. I get why other platforms chase them.
But here's what happens when you do. Your roadmap gets pulled toward compliance features, government integrations, and enterprise sales cycles. You need a sales team and implementation consultants. Your interface gets heavy because the workflows are heavy. And your small rescue customers, the ones who just need something simple that works on their phone, start seeing their feature requests sit in a backlog behind the next county contract.
I've watched this happen to other platforms. They start with real love for the rescue community, land a few municipal deals because the revenue is impossible to turn down, and slowly the product shifts. The free tier gets worse. The UI gets more complicated. The people who found the platform first, the three-person rescue running everything from a kitchen table, stop recognizing the tool they signed up for.
I didn't want to build that version of PawPlacer.
What it actually means
It means everything in PawPlacer, the features we build, how we price things, the way the mobile experience works, what gets prioritized on the roadmap, is based on how volunteer-run rescues actually operate. Not how a government facility operates. Not how a software company thinks a rescue should operate.
When a foster coordinator in Ohio tells me "I need to update medical records from my car between vet appointments," that goes on the roadmap. Not behind a county IT department's request for a custom compliance report.
If you're a municipal shelter reading this: genuinely, no hard feelings. The platforms that serve you have been at it for decades and they know your world. We're just not trying to be them, because trying to be them would make us worse at the thing we're actually good at.
And if you're a small rescue wondering whether anyone's building software with you specifically in mind, yeah. That's the whole point.
