Why we built Basecamp HQ
Independent parks were stuck between an aging desktop program and commission-taking marketplaces. Here's why we built a third option that stays yours.
Talk to enough owners of independent campgrounds and RV parks and you hear the same story with different scenery. The park is the retirement plan and the full-time job. The reservation system is either a Windows program from another era running on one aging PC behind the desk, or a slick modern platform that takes a cut of every booking and quietly owns the guest list.
One choice is yours but stuck in 2003. The other is modern but not really yours. We built Basecamp HQ because that's a lousy pair of options for the people running 13,000 of North America's best small businesses.
Start with the thing that can never break
Every park has the same nightmare, and it isn't slow software — it's two families with confirmations for the same site on a holiday weekend, one of them already backing a trailer down the lane.
So the first thing we built was a reservation engine where that can't happen. Every booking claims every night of its stay in one all-or-nothing transaction. Two people racing for the last site — front desk versus website, or two browser tabs at midnight — produce exactly one confirmed booking and one polite "just got taken." Not usually. Structurally. The grid, the calendar, the site map, the online widget, and the AI all write through that same engine, so there's no back door for a double-book to sneak through.
And the view on top of that engine is deliberately familiar: sites down the side, dates across the top, stays as bars. If you've read a tape chart for twenty years, you can read ours in twenty seconds. That was a design requirement, not an accident.
The front desk that answers at 9pm
The second thing every owner told us about was the phone — and the email, and the texts. "Do you have anything for Labor Day?" "What time is check-in?" "Can I bring my dog?" Multiply by a hundred, all summer, including dinnertime.
The AI Front Desk answers those messages with your rules and your live availability — it quotes real prices, places real holds, books real sites, all through the same engine your staff use. And when a conversation gets sensitive — a refund, a complaint, real money — it doesn't improvise. It lands in your queue with the context and a proposed reply, and you approve, edit, or take over.
The same philosophy runs through the pricing advisor: it recommends, with the reasoning attached, and nothing changes until you click apply. We call the pattern recommend-and-approve. You're the operator; the software should act like it knows that.
Respect the data, respect the wallet
Twenty years of guests and bookings live in that old desktop program, and the fear of losing them keeps a lot of parks stuck. So we built the importer early: upload your Campground Master export, and it rebuilds your park — sites mapped, guests de-duplicated, future reservations placed — then hands you a verification report to approve before anything goes live. Minutes, not months. Your history comes with you.
And the business model is the one we'd want if we owned a park: a flat monthly price, sized by your site count. No per-booking fees. No marketplace between you and your guests. The booking widget sits on your own website, your guest list stays yours, and a record-breaking July costs the same as a snowed-in January. We take $0 of your bookings — that's the whole point.
See it for yourself
We could keep describing it, but you run a park; you'll know in five minutes whether this fits. The demo opens a complete park — tape chart full of bookings, guests writing in, the AI answering — in two clicks, with no card and no sales call.
Kick the tires. Read the grid. Ask the front desk something tricky. It's your park — the software should finally act like it.