It’s mid-March, and you’re the director of a camp that enrolled six hundred campers last summer. Registration opened three weeks ago and the forms are arriving faster than you can read them. You have three full-time staff, and between now and June you’ll hire close to ninety counselors and specialists. The medical forms are trickling in as PDFs. Your bookkeeper is matching Stripe payouts against a spreadsheet roster by hand. And the two camp systems you looked at last fall both felt wrong in opposite directions: one was a name-brand suite priced and built for an institution three times your size, the other was the duct-taped stack you already run, just rebranded.
That gap is real, and it’s where a lot of independent camps live. You’re too big for the spreadsheets — the by-hand work has quietly become the job — and too independent for the enterprise suite, which assumes a headcount and an IT department you don’t have. This is the buyer’s case for the middle: a camp serving 150 to 800 campers needs one coherent system sized to it, not an enterprise tier and not a pile of point tools. It’s part of choosing camp management software honestly — judging fit by your real operating shape, not by feature count.
The size that falls between two stacks
Most camp software is built for one of two camps, and neither is yours.
The enterprise suites are sized for institutions — multi-site organizations, year-round programs, the kind of operation that has staff whose whole job is administering the software. Their configuration depth and per-module billing make sense when there’s a team to absorb them. Drop a lean independent camp into that, and the director who is also the registrar and the bookkeeper inherits a surface area built for people they don’t employ.
The duct-taped stack runs the other way. A form tool, a payment processor, an email tool, a spreadsheet, a PDF packet for medical forms — each honest about its one job, welded together by hand. For a new or tiny camp that’s the right call; it’s cheap and it’s real engineering. The trouble is that the seams between the tools don’t scale with you. At a few hundred campers, the matching and re-keying and chasing between tools turns from an annoyance into the structure you run on. The deeper version of this break — exactly where stitched-together tools leak — is its own piece: all-in-one vs. point solutions.
The middle band needs neither. It needs a system whose architecture matches a camp that runs registration, payments, medical records, and seasonal staff on one calendar — and whose pricing tracks the size of the season rather than a tier built for an institution.
Registration that arrives in a rush
The first pain of the size is timing. Registration doesn’t come in steadily; it comes in a wave the morning forms open, and then in a long tail of incompletes you chase for weeks. At a few hundred families, you can’t hand-watch each one.
What a mid-size camp needs here is a registration flow that does the watching. A returning family’s record prefills next year’s form instead of starting blank. A sibling links to the household instead of being keyed in fresh. Required documents and waivers are collected inside the same flow, so a signature isn’t a separate email thread. And the incompletes surface on their own — the system knows which registrations are missing a form and can send the reminder — instead of you building that chase list by hand from a spreadsheet. Camp Runner carries registration, returning-family prefill, sibling links, and waiver collection on one camper record, so the rush leaves you with a queue the system already sorted, not a pile you triage. The longer case for registration that holds at this scale is its own subject in the switching guide.
Seasonal staff churn of 40 to 120
The second pain is the one the registration-focused tools forget. A mid-size camp doesn’t just enroll campers; it hires and onboards a small workforce every spring — somewhere between forty and a hundred and twenty seasonal staff, most of them new, most of them arriving in the same compressed window.
That’s its own operation: applications to collect and review, onboarding items and documents to track per hire, certifications and background checks with expiry dates that have to be current before opening day, and a schedule to build once everyone’s in. A duct-taped stack handles this in a second spreadsheet and a shared drive, and the spreadsheet is where a lapsed certification hides until it matters. A system sized to the camp keeps the staff record next to the camper record: applications, onboarding progress, certification and background-check status, and scheduling live together, so you can see at a glance who’s cleared to work and who’s still missing a document. The director leads the hire; the system keeps the paper trail current.
Medical forms that have to reach someone
The third pain carries the highest stakes. At a few hundred campers, the medical forms are a stack, and in a stitched stack each one is a document — a PDF or a free-text field that lands in a folder and waits. An allergy typed into a comments box can’t be sorted or flagged. A missing form looks exactly like a complete one until someone opens it.
A system sized to the camp treats the medical record as structured data tied to the camper, not a file. Allergies, medications, and conditions arrive as fields, so an incomplete form surfaces on its own before the season starts, and a flagged allergy or a medication schedule reaches the staff responsible for that camper instead of waiting to be found. Camp Runner collects medical information during registration and carries it as structured records — alerts, medication schedules, daily screening — so the information moves with the camper rather than sitting in a folder no one opened. At this size you can’t personally read every form on arrival day; the system has to surface the ones that need action.
A season that won’t close itself
The last pain shows up in the worst week of the year. Close-out in a stitched stack is a reconciliation project: export the payments, line them up against the roster, chase the medical forms nobody flagged, rebuild the returning-family list from memory, and hope three tools agree. None of that work is hard. All of it exists only because no single tool held the whole picture.
When registration, payments, and medical records share one camper record, the season closes against itself. The financial summary already knows which session each payment belongs to. The returning-family list builds from this season’s registrations. Camp Runner gives close-out its own checklist and a season wizard, so the last week is reading off a picture the system kept all along instead of rebuilding one by hand. That’s the difference the size makes: at scale, the by-hand close-out isn’t a long afternoon — it’s the tax on every seam you ran all summer.
How to judge the fit
You can’t compare these systems honestly on invented numbers, and you don’t need to. Compare on the axes you can see. The architecture shape: does a thing you enter once travel to the payment, the medical record, and the staff schedule, or do you re-enter it? The pricing-model shape: is the quote one rate that tracks your season, or a base that climbs as you turn on the modules you assumed were included? And what ports cleanly when you leave — because the exit tells you more about the architecture than the demo does. The detail of how to run that evaluation is the director’s checklist.
Camp Runner’s pricing-model shape is one published rate — $1.50 per active camper, per month — so the bill tracks the size of your season instead of a tier built for an institution or a stack of point-tool subscriptions. You can run the math for a camp your size with the cost calculator before you talk to anyone.
You run the camp, and you make the call. If you’re in the band that’s outgrown the spreadsheets but doesn’t want the enterprise suite, the fit is a system sized to exactly that — one camper record carrying registration, payments, medical, and staff through the season. Join the waitlist to start with your own data rather than a sales pitch, and the feature tour walks a real registration end to end.
Common questions
- What counts as a mid-size independent camp?
- Roughly an independent overnight or day camp serving 150 to 800 campers each season, run as a real business by a director or owner-operator with a small full-time team. The seasonal staff swells to somewhere between 40 and 120 in summer. It's the band that's outgrown a spreadsheet but isn't the multi-site institution the big incumbent suites are built and priced around.
- Why isn't an enterprise camp suite the obvious choice at this size?
- The large incumbent suites are sized for institutions with dedicated IT and admin headcount to absorb their configuration and per-module billing. A mid-size independent camp runs lean — the director is also the registrar, the bookkeeper, and the IT department. A system built for an institution tends to bury that director in setup and surface area meant for a team they don't have.
- When does a duct-taped Jotform-plus-Stripe-plus-Sheets stack stop working?
- It holds fine for a small or new camp and gets expensive in time as the camp grows. Somewhere in the mid-size band, the by-hand work between the tools — matching payments to registrations, chasing medical forms, re-keying returning families — grows faster than the camp does. The seams between the tools quietly become the system you actually run on.
- Does one coherent system mean giving up the best tool for each job?
- That's the honest trade-off. A dedicated point tool can go deeper on its single job than a system that does many jobs. For a camp running registration, payments, medical records, and staff on one calendar, coherence — entering a thing once and having it available everywhere — usually pays back more than per-tool depth.
- How does Camp Runner price for a mid-size camp?
- One published rate — $1.50 per active camper, per month — so the bill tracks the size of your season rather than a stack of module fees. There's no demo gate to see it. You can join the waitlist and start with your own data rather than a sales call.
