I'm Kyle, PawPlacer's founder. If your rescue runs on Airtable, Notion, Trello, Monday, or some combination of all four, this post is for you. Before I get into what goes wrong, I want to say it out loud: you did good work. Standing up a functional rescue pipeline in a generic tool takes real thought. The rescues I talk to who built their own systems are often the ones with the best data discipline in the sector, because when the tool doesn't care about pets, the humans have to.
This post is about the point where the tool stops keeping up with the operation.
The build, recognized
I've seen versions of this dozens of times.
An Airtable base with Pets, Applications, Fosters, Adopters, and Medical Log as linked tables. A calendar view for medical follow-ups, a gallery view for adoptable pets, a form for applications.
A Notion workspace with a database per entity, rollup formulas for tallies, and a shared page per animal.
A Trello board with columns for each stage of the adoption pipeline, one card per pet.
A Monday board with timeline views and automations firing off reminder emails.
A Google Form for intake that writes to a Google Sheet that gets copy-pasted into the above.
Each was the right call at the moment you built it. None were built for rescue specifically, which is the whole problem. They're neutral containers. You get to define what "pet" means, what "adopter" means, what "medical record" means. That flexibility is why you picked them. It's also what breaks first.
What breaks, in order
At 10 pets: nothing. The build is fine. Skip this post.
At 30 pets: photos get heavy. Your Airtable attachments are approaching the free-plan storage cap. Notion loads slowly because someone attached full-resolution vet-exam photos to every pet page. People start texting photos to a group chat instead of uploading to the record, and now your data is in a Signal thread.
The first medical confusion shows up. A pet has a rabies vaccine from 2024 and one from 2025. Someone overwrote the field instead of appending. You don't know the real history anymore.
At 50 pets and two or more volunteers: duplicate edits. Two people open the same pet record. Both save. Last write wins. Someone's change silently disappears. Everyone starts DM-ing before they touch anything, which is worse than editing.
Applications pile up. Your Typeform writes to a row. You scan rows manually to decide who's next. Applicants drop off because nobody told them they were third in line. You start pasting their answers into ChatGPT to help you triage.
At 100 pets: Petfinder is stale. Updating it is a separate manual project. Someone adopts a pet on Saturday and the listing stays up for another week. You take inquiries about a dog who's been home for nine days.
Medical scheduling gets scary. Rabies boosters, heartworm tests, spay/neuter follow-ups, flea treatments, all on different cadences, all driven by birthday or adoption date or last dose date. A formula-based reminder system you built in Notion works for the first twenty and falls apart by the fiftieth. A missed booster becomes something a vet tells you about at the appointment.
At 150 pets and an event-driven operation: the Saturday floor at PetSmart breaks the whole system. You're standing there with a tablet, trying to update a Notion page while an adopter signs an agreement you printed off a Google Doc, while a Square reader takes the fee, while the follow-up vet info lives on a sticky note. The adoption "record" is fragments across four tools and none of them talk to each other.
That's the wall.
What a purpose-built tool gives you that a generic one can't
You can extend Airtable forever. It'll never do the things a shelter-first tool does on day one.
Species-aware matching. When an applicant submits, ranking them against every pet in your system requires rescue-specific judgment: species compatibility, energy level, home setup, history with kids or other animals, foster capacity. PawPlacer's matching engine handles this with vector embeddings and five hard guardrails running before the model ever scores. You cannot build this in Airtable. You would not want to.
Petfinder sync. One-way, live, per-pet. The grid updates the moment someone is marked adopted. No manual re-export, no second spreadsheet. How it works.
Medical that knows it's medical. Vaccines carry lot numbers and lot expirations. Prescriptions alert you before the refill window closes. Recurring follow-ups run on cadences from daily through yearly. Twenty-two built-in document types. The adopter leaves with a clean one-click export their vet can actually read. None of this is achievable in a rollup formula.
Mobile QR adoption checkouts. Built for the PetSmart floor scenario specifically. Staff tablet has the pet pulled up. Hand the adopter a QR code. They finish donation, payment, agreement, and e-signature on their phone. The pet auto-marks as Adopted. The record writes itself before you've packed up the X-pen.
Embeddable widgets. Your adoption grid, individual pet pages, and application forms drop into WordPress, Squarespace, Wix, or Webflow with one line of code. Your Airtable embed is an iframe that looks like an Airtable embed. Ours looks like your site.
Your Stripe, straight to your bank. 0% cut. The 2.9% + 30¢ is a separate line on the adopter's receipt so the adopter covers it. You keep the full adoption fee, the full donation, and your processor the day you leave.
What your build actually had going for it
This is the part most shelter software won't acknowledge, so I will.
Airtable, Notion, and Trello worked at all because they're flexible. You shaped them to your workflow instead of the other way around. A lot of shelter software does the opposite: it imposes a rigid data model and asks your workflow to conform. That's why rescues who switch from a DIY build to traditional shelter software sometimes regret it.
PawPlacer's custom form builder and per-entity custom fields were our answer to the flexibility you had. You decide what goes on the adoption application. You decide what custom fields exist on a pet record. You reorder your own table columns, and those settings are per-user, so your medical coordinator's columns and your adoption counselor's columns don't fight each other.
The flexibility you built? We kept it. We just moved it into something that also knows what a pet is.
On migration
This is the part that keeps people stuck. The fear of losing the build.
Export your Airtable base to CSV. Export your Notion database to CSV. Export your Google Sheet. Drag any of them into PawPlacer's AI-assisted CSV importer. It figures out that your "DOB" column is a birthday, that your "K9" entries are dogs, that your dates arrived in four different formats. It previews everything before committing. Leading zeros on microchip numbers stay intact.
Start with the twenty to forty animals currently in your care. The three hundred you've placed over three years can stay in a read-only archive. You'll probably never look at them.
Run both systems for two weeks. Old build stays read-only. Everything new goes into PawPlacer. After two weeks, make the call.
When to stay on what you built
Under ten pets and one person running everything. Your Airtable or Notion build is fine. Don't fix what isn't broken.
Heavy non-rescue operations your tool also handles well. Your Trello board is also your donor pipeline. Your Notion also runs grant-writing. Your Airtable is also inventory. Mixing the rescue side into a purpose-built tool while the rest of your ops live elsewhere is worse than a unified-but-generic setup.
A team that loves the tool. If your foster coordinators have Trello muscle memory, the tax of switching is real even if the thing you're switching to is better. Sometimes "good enough that everyone uses it" beats "better but half the team won't log in."
Why us specifically
The free plan is actually free. No trial, no countdown, no "free until we decide it isn't." Up to 30 in-care pets, five users, every feature. AI matching, the form builder, the medical module, Petfinder sync, the reports builder, the SDK and API, mobile QR checkouts. Free plan.
If it doesn't fit, your data exports cleanly and you're out. No retention tactics. No support ticket required to leave.
You built something clever in Airtable. You could build something cleaner in something made for this.
