SaaS vs Custom

Falls Creek (highest Australian ski resort, 1,932m, opens June–mid-September, ~$180 lift pass/day adult, ~$140 child) + Thredbo (highest snow elevation, 2,228m, similar season, similar pricing) + Charlotte Pass (national park, smaller footprint, day-use focus, $100 lift pass) handle bookings across lift passes, rental gear (skis, boots, helmets, jackets), multi-day packages (lodge + meals), and group assignments entirely via email spreadsheets. A 75-student school camp (Thredbo, July 10–12, 3 nights) generates: 75 lift-pass bookings ($140 child × 75 × 3 days = $31.5k revenue), 75 rental sets (skis + boots + helmet per student, ~$40/day rental × 75 × 3 = $9k revenue), 75 beds (lodge $180/night × 75 × 3 = $40.5k revenue), 10 ski instructors (hired externally, $200/day × 10 × 3 = $6k cost), 1 weather decision (if BoM predicts <5cm fresh snow or >50km/h wind = insufficient conditions, refund 50% lift + rental, rebook next weekend or process credit). Current process: (1) school calls (May), books dates, asks "can you do 75 kids July 10–12?", (2) resort admin copies spreadsheet, creates 75 rows (student name, age, height cm, weight kg, ski level beginner/intermediate/advanced, dietary requirements, emergency contact, parent phone), (3) 2 weeks before: rental dept manually sizes 75 sets (heights + weights, ability flags), (4) 1 week before: instructors confirmed, crew assigned to ability level (10 beginners + 20 intermediate = 1 instructor per 10–12), (5) 2 days before: weather check (BoM forecast, resort snow report, wind speed), if bad = call school, "can you postpone to July 17–19?", school scrambles logistics, 3 days of planning wasted, (6) trip proceeds (or cancels + refund manual processing), (7) post-trip: schools ask "can we get 80 kids July 2027?" → admin opens last year's spreadsheet, copies it again. Zero system logic, same chaos every season.

Six Features Custom Snow Resort Platform Delivers

1. Lift Pass Pre-Booking + Season Pass Tracking + Auto-Renew Reminders

Camp coordinator (school) opens booking portal (May 1). System shows: [Thredbo July 10–12 (3-day package), lift pass child rate $140/day (refundable if <5cm new snow), 75 seats available, lodge $180/night with meals included, rental $40/day per set (skis + boots + helmet)]. Coordinator enters: [75 students, ages 8–12, mix of beginners/intermediate]. System auto-calculates: [75 × $140 × 3 days lift = $31,500], [75 × $40 × 3 days rental = $9,000], [75 × $180 × 3 nights lodge = $40,500], [total = $81,000, due 60 days prior]. Coordinator books (May 1), system locks dates + pricing. System sends: [confirmation email with student roster spreadsheet template (name, age, height, weight, ski level)]. Coordinator populates (May 15), uploads. System ingests: [75 students, auto-assigns to rental size buckets (S, M, L, XL per height/weight/age — 22 size-S, 31 size-M, 18 size-L, 4 size-XL)]. Thredbo rental dept sees (May 20): [75-student group, July 10–12, rental requirements: 22 S, 31 M, 18 L, 4 XL, no custom modifications requested]. Rental ready by June 15. Individual students (returning skiers from Year 10): [Mike booked Fall 2025, now buys 2026 season pass]. System auto-charges: [2026 season pass $399 (10 days unlimited, mid-year pro-rata). Reminder email (June 1): "Your 2026 season pass expires Oct 31, renew for 2027 now at 15% off ($339)? Yes / No"]. Mike clicks Yes (June 1), 2027 pass locked, auto-renewal set for Oct 2026. Revenue visibility: [75 camp pass revenue locked May 1, 150 individual pass sales (2025 + 2026 cohorts renewing), recurring revenue pipeline 6 months out]. Cancellation logic: [if student cancels <30 days prior, refund 50% (cancellation fee funds no-show insurance), >30 days = full refund]. System auto-processes.

2. Gear Sizing Pipeline + Height/Weight/Ability Matching + Equipment Staging

School intake (May 15): coordinator uploads [75 students: name, age, height (cm), weight (kg), ski ability (beginner/intermediate/advanced)]. System auto-assigns rental: [skis matched by height (boot size = (height – 20) ÷ 2.5, approx) + ability (beginner = shorter, more forgiving flex; advanced = full-length performance)]. Beginner 130cm 28kg (6-year-old) = 80cm skis (soft flex, release-adjusted for light body weight, safety priority). Intermediate 155cm 45kg (10-year-old) = 120cm skis (medium flex, matched technique level). Advanced 172cm 62kg (15-year-old) = 160cm skis (stiffer flex, carving performance). System generates: [rental picking list: 22 × 80cm soft ski, 22 × size-2 boot, 22 × 48cm helmet child]. Rental team picks (July 5): [list shows: each set ID, student name, sizing specs, ability flag, special notes (metal edge sharp? strap adjusted?)]. Sets inspected (July 6–8), placed in racks by student name (alphabetical), taped: [ALEX #1, BAILEY #2, CASEY #3, etc.]. Students arrive (July 10, 9am): [meet rental counter, name called, equipment handed over in order (skis + boots + helmet checked fit, boots clipped in by rental tech for safety), student = happy]. No sizing errors mid-slope, no kid in undersized boots causing ankle damage, no double-booking a set to 2 students. Ability-matched gear = confidence, better learning curve, safety compliance.

3. Group Booking + Instructor Crew Dispatch + Ability-Level Sorting

75-student camp intake (May 15): system asks: [per student, ski ability? Beginner / Intermediate / Advanced]. Coordinator fills: [12 advanced, 35 intermediate, 28 beginner]. Thredbo hires 10 instructors (external contractors, 3 weeks before event). System tracks: [Instructor A: advanced specialist, max 12 students, prefers steeper terrain], [Instructor B: intermediate coach, max 15 students], [Instructor C: beginner guide, max 12 students], [Instructors D–J: mixed ability, max 10–12 per person]. System auto-assigns (June 15): [12 advanced students + Instructor A = group 1], [15 intermediate students + Instructor B = group 2], [12 intermediate students + Instructor D = group 3], [8 beginner students + Instructor C = group 4], [remaining 20 beginners split: 10 + Instructor E, 10 + Instructor F]. Groups balanced (no instructor 15+ students, beginner groups never >12, ability matched). System flags: [3 students with medical notes: Emma (asthma), Jake (knee injury from last season, avoid moguls), Lena (vertigo, prefers wide gentle runs)]. Instructors E, C, F see flags (July 10, briefing): [Emma has asthma inhaler on board, breaks frequent; Jake mogul-free; Lena stick to green runs]. Lesson plan (July 11, 9am): [Group 1 (advanced) = red runs, powder focus if new snow; Group 2 (intermediate) = blue runs, carving technique; Group 3 (intermediate) = blue runs, rhythm building; Group 4 (beginner) = green runs, snowplough control; Group 5 & 6 (beginner) = green runs, balance exercises]. Ability sorting: student confidence up, instructor-to-ability ratio optimized, safety flags tracked, no mixing advanced skiers with beginners learning to snowplough. Scheduling: [if 1 instructor calls sick (July 10, 6pm), system shows: Group 4 (beginner, 12 students, max ratio 1:12) = Instructor C available. Reschedule: Group 4 + Instructor F (already at max 10) = over capacity, wait for Instructor H available next slot 2pm?] Manager decides: offer Group 4 rescheduled 2pm, or offer parent refund (75% lesson + 25% credit future). System processes transparent.)

4. Weather Refund Automation + Snow Guarantee + Forecast Triggers

Booking locked (May 1): [July 10–12 camp, Thredbo, refund policy: <5cm new snow OR wind >50km/h = 50% refund (lift + rental) + full rebook credit; <2cm new snow = 100% refund]. Forecast monitoring (auto, daily 6am): [system checks BoM Thredbo forecast (7-day rolling)]. July 8 (2 days prior): [BoM: July 10 high 4°C, light winds, 2–5mm precipitation (light snow expected, marginal)]. System alert (July 8, 4pm): [forecast borderline, re-check tomorrow morning]. July 9 (1 day prior): [BoM updated: July 10 high 2°C, 10mm precipitation (light-to-moderate snow), winds NW 25–35km/h (gusting to 45km/h by 11am)]. System flags (July 9, 6:30am): [July 10 forecast: 10mm snow (marginal for 5cm threshold), peak winds 45km/h (exceeds 50km threshold 11am–3pm)]. Manager checks system: [July 10, high wind window 11am–3pm, snow light. Options: (1) proceed but restrict group 1 (advanced) to sheltered runs 11am–3pm, (2) delay start to 3pm (afternoon only, 1 full day becomes 0.5), (3) postpone to July 13 (weekend, crowds higher, equipment availability?), (4) auto-refund 50% + rebook July 13–15]. Manager selects (July 9, 8am): [option 3: postpone to July 13–15, auto-offer to school]. System sends email (July 9, 8:15am): [weather forecast: strong winds + light snow, lesson quality compromised. Reschedule to July 13–15 (same 3-day package, same price, no cost to you) or accept 50% refund (lift + rental) + 25% credit future booking]. School replies: [reschedule to July 13–15 accepted, coordinator will adjust their lodging (lodge already holds dates for July 13–15, already paid, no change needed)]. System updates: [group reassigned July 13–15, instructors notified (same crew available July 13–15? confirm. System checks: 10 instructors available July 13–15 = yes)]. Lesson proceeds (July 13, 9am): [snow conditions improved to 8cm fresh, winds 20–30km/h, perfect for learning]. Refund automation prevents: bitter school complaint (we flew to Thredbo in whiteout, lesson cancelled, manual refund nightmare), improves: school feeling cared for (proactive offer, no out-of-pocket), opportunity to upgrade lodge experience (3 nights July 13–15 vs 10–12 shows they trust you, rebook likelihood 95% next year).

5. Accommodation + Meal Planning + Dietary Requirements + Room Assignment

School books (May 1): [75 students, 10 instructors, 3 nights July 10–12, lodge has 17 rooms, capacity 100 beds]. Coordinator intake (May 15): [per student, dietary requirements? (vegetarian, vegan, gluten-free, nut allergy, medical diet), room assignment preference? (with friends / separate from certain people?)]. System tracks: [5 vegetarian, 2 vegan, 3 gluten-free, 1 nut-allergy, remaining omnivore]. Kitchen manager sees: [5 × vegetarian meals/day × 3 days = 15 portions, 2 × vegan × 3 = 6 portions, 3 × gluten-free × 3 = 9 portions, 1 × nut-free × 3 = 3 portions, 59 × standard × 3 = 177 portions, total 210 meal portions needed]. Orders suppliers (July 1): [15 veg boxes, 6 vegan boxes, 9 GF boxes, 3 nut-free, 177 standard, plus 20% buffer]. Room assignment (June 1): [system suggests: 4–5 students per room (15–17 rooms, ~5 per = 75 students), instructors 1–2 per room (10 instructors = 5–6 rooms)]. Coordinator inputs: [Room 1: Alex, Bailey, Casey, Dakota, Emma (5 beginners, mixed genders separated, no conflicts)], [Room 2: Frank, Grace, Henry, India (4 intermediate, dormitory-style), etc.]. System stores: [room assignments + dietary flags = Emma + Lena (both vegetarian, same room = meal prep efficiency)]. Check-in (July 10, 4pm): [receptionist opens system, enters room numbers as students arrive]. System flags: [Emma vegetarian — kitchen prepping her meal separately, Lena vegetarian — same room as Emma, 1 veg meal ready]. Dinner served (July 10, 6pm): [kitchen serves correct meals to each room group, no mix-ups, dietary needs met]. This eliminates: coordinator spreadsheet chaos (copy-paste dietary conflicts, room overcrowding, meal shortages), improves: meal satisfaction (students get what they requested), liability (allergy management transparent, logged digitally).

6. Post-Season Pass Renewal + Engagement Loop + Retention Messaging

Students attend July camp (first-time skiers or returning). System captures: [75 students, contact emails, ski ability + experience level, which runs they preferred (green / blue / red), any injuries / fears noted by instructor, next-year interest?]. Post-season (mid-September, end of Thredbo season): system auto-sends (September 20): [email to 75 students: "Thanks for skiing with us! You crushed it on those blue runs. Want to get better? Early-bird season pass 2026: just $179/year (pro-rata, Oct–June, normally $399). Secure yours now with link."]. 45 students click link, 35 buy pass ($179 × 35 = $6.3k revenue capture, September close). System auto-reminders (Oct–June): [monthly "tips for blue-run carving" content, seasonal discount codes (May half-term: 20% off rental), progression pathways (next summer: advanced camp in Snowy Mountains?)]. By July 2027: [of original 75, 45 return (60% retention). 35 upgrade to advanced group, 10 stay intermediate. New intake: 50 kids from referring schools + families. Net 2027 camp: 95 students vs 75 = +27% growth year-on-year]. Recurring revenue tracked: [35 × $179 = $6.3k from season passes, 95 × $81k camp package (conservative) = $7.7m potential for Thredbo if they run 10 camps/season across regions]. Engagement loop: 1-time sale → repeat → word-of-mouth referral → data-driven upsell (progression, retention messaging) → year-on-year growth.

Australian Ski Season Context — Thredbo, Falls Creek, Charlotte Pass Open Dates + Snow Guarantees

Australian ski season runs June 1–mid-September (typically 13 weeks). Thredbo opens mid-June (weather permitting, BoM forecast checked daily), closes mid-September. Falls Creek similar. Charlotte Pass is smaller, focus on day-use + weekend lodging. "Snow guarantee" terms vary: Thredbo marketing: "50% refund if <5cm new snow within 48hrs of booking", but manual processing = 2-week refund turnaround (school chases resort, resort chases accountant, no good). System automates: <5cm + >50km/h wind triggers instant 50% credit (emailed refund authorization + future-booking credit simultaneously, no phone calls). Multi-year bookings lock rates (school books July 2026 + July 2027 + July 2028 as a 3-year package, single discount 15% off): system tracks expiry dates per contract, auto-notifies (June 2028): "Your 3-year contract expires July 31, renew for 2029–2031 now at 20% early-bird discount?". Instructor certifications: Australia has no federal ski-instructor standard, but resorts typically require: ["Level 1 NZSIA" (New Zealand Snowsports Instructors Association cert, transferable), "First Aid + CPR", "Mountain Safety Awareness"]. System tracks per instructor: [cert type, expiry date], flags (May 1): [Instructor A NZSIA expires June 30, renew by May 31 to teach July camp]. Compliance automation: zero manual cert audits, system auto-disables out-of-cert instructors from dispatch. Insurance: resorts typically carry $10M+ public liability, but camp coordinators (schools) verify instructor credentials. System generates: [instructor credential report for school lawyer review (1 click): "all 10 instructors hold current NZSIA + First Aid, 3 years clean safety records"]. Regulatory paperwork: instant, transparent, school liability mitigated.

Six FAQs

What if a student gets injured on the slope — how does the incident get logged?

Student (July 11, 10:45am): falls on blue run, ankle twist. Instructor immediately: [radios lodge ("Instructor C, student Jake injured ankle, green run by marker 5, 10:50am, can we get ski patrol?")]. Ski patrol arrives (10:55am), assesses: [ankle swollen, probable sprain, not severe fracture]. Jake brought to lodge medical clinic. System (real-time): [Instructor C marks lesson "INCIDENT REPORT" in system]. Fields auto-populate: [student name = Jake, time = 10:51am, location = "blue run, marker 5", injury = "ankle swelling", instructor = "C", witness names = "other 11 students in group"]. Instructor notes: ["Jake was practicing carving technique, caught inside edge, fell forward, landed on medial ankle, able to stand with support, no loss of consciousness"]. System captures: [incident timestamp, location GPS (ski patrol has it), medical response (patrol arrived 5min), treatment: ice + bandage, decided = transport to Cooma hospital for X-ray]. System auto-notifies: [lodge manager, school coordinator (Jake's parent emergency contact), insurance coordinator]. Parent contacted (11:15am): [lodge manager calls, "Jake had small fall, ankle sprain suspected, no fracture signs, being transported for X-ray to confirm, you can drive to Cooma hospital or we can coordinate"]. X-ray (1:30pm): [ankle sprain, mild, no fracture]. Jake released (2pm), returns to lodge (ice + rest). System logs: [incident report complete, X-ray results attached, parent consent signed digitally, incident closed]. Post-incident: [system auto-generates incident summary (1 click) for insurance claim if needed, timeline + witness statements + medical response = airtight documentation]. Liability protection: system shows resort acted promptly, recorded everything, communication transparent. No "did the incident get reported?" scramble.

How do you track instructor availability across multiple resorts?

Velocity X system (regional): [Thredbo, Falls Creek, Charlotte Pass all in one platform, separate resort tabs]. Instructor crew: [some contractors work all 3 resorts (3 days Thredbo, 2 days Falls Creek, weekends Charlotte Pass), others single-resort]. System tracks: [Instructor A: available Thredbo June 15–July 31, then Falls Creek Aug 1–Sept 15. Instructor B: Charlotte Pass weekends all season]. Calendar view: [click instructor name, see 26-week availability heatmap (red = booked, green = available)]. Resort manager (Thredbo) books July 10–12 camp (75 students, 10 instructors needed). System checks: [which instructors available July 10–12? Show 14 available names, with rates + certifications]. Manager selects 10 (emails sent, contracts auto-generated). Instructor C (Falls Creek primary): [available July 10–12 = yes, temporarily transfer to Thredbo for camp week]. System notifies Instructor C (June 20): [Thredbo requesting you July 10–12 camp (10 students, advanced group, $200/day + accommodation + meals provided). Confirm?]. Instructor C: [yes]. System locks schedule: [Instructor C: Falls Creek off-duty July 10–12, Thredbo on-duty July 10–12]. Multi-resort visibility: zero double-bookings, instructors can see gig opportunities across resorts, resorts can poach talent temporarily (contract automation handles it). Regional efficiency: larger operator (2–3 resorts) can pool instructors, balance seasonal demand (Thredbo busier early season, Falls Creek late season), optimize crew hours across the network.

Can we run recurring school camp bookings (same school, same dates, every year)?

Yes. School books first year: [July 10–12 camp, 75 students]. After successful trip (July 15, post-debrief), system sends: [school coordinator email: "Want to book July 2027 dates now? Lock in at 12% discount (3-year early-bird rate). Same dates July 9–11 2027, same package $71k (vs $81k), auto-renew if you confirm now"]. School confirms (July 20). System creates: [recurring booking template: July 9–11 (annually), 75 students (adjustable year-to-year, +/- 10% flexibility), $71k locked rate, auto-renew unless cancelled 90 days prior]. System auto-sends (June 1 every year): [reminder email: "your annual July 9–11 camp is due in 39 days. Confirm student count + dietary updates + room preferences. Confirm or decline to hold/cancel"]. School updates (June 15, Year 2): [75 students again, same meal requirements, room assignments]. System proceeds: [no re-booking friction, all dates locked, pricing locked, equipment pre-staged per year]. Recurring benefits: [school gets predictable rates + dates (no scrambling last-minute), resort gets guaranteed revenue pipeline (75 × $71k = $5.3m multi-year), can budget confidently, hire instructors 12 months out]. Cancellation: [if school can't run Year 3, system auto-emails (90 days prior, April 1 Year 3): "cancel or proceed July 9–11?" School says cancel, system releases dates back to inventory (other schools can book July 9–11), pro-rata refund of any deposit depending on contract term]. Recurring automation: eliminates annual renegotiation chaos, builds school-resort partnership, locks revenue predictability.

How do you handle parent consent forms + liability waivers for minors?

School intake (May 15): system sends coordinator template spreadsheet [75 student names]. Coordinator populates (May 20): [student name, age, emergency contact (parent name + phone), dietary requirements, medical conditions]. System auto-generates: [75 custom parent consent forms (via DocuSign API), each form pre-filled: "Parent/Guardian of [STUDENT NAME], age [AGE], will attend Thredbo ski camp July 10–12. I acknowledge: skiing risks (collision, falls, avalanche, cold exposure). I certify [student] has no medical conditions that would prevent ski participation, or have disclosed them below: [asthma / allergies / injuries / medications]. I authorize emergency medical treatment if injury occurs. I release Thredbo Resort + [school name] from liability. Signature + date"]. System email to school coordinator (May 20): [bulk-send 75 forms to parent email addresses]. Parents sign digitally (May 21–30): [system tracks: Alex signed May 21 3:15pm, Bailey May 22 9am, etc.]. System alerts coordinator (June 1): [72/75 forms signed, missing: Casey (parent email bounced), Dakota (not yet signed, reminder sent June 1 5pm), Emma (signed)]. Coordinator chases Casey (new email), re-sends Dakota reminder. Dakota signs (June 3), Casey's parent replies (June 2): [resent email, now signed]. System updates: [75/75 forms signed, all consent captured, audit log complete]. Thredbo access (July 10): [instructor checks system before lesson: "Jake — consent signed May 24, asthma flag, inhaler on board, green light"]. Post-incident (hypothetical injury): [system generates incident file: incident report + consent form (signed + timestamped) + medical response = airtight liability documentation]. Consent automation: zero paper forms, zero "where's the waiver?" chaos, parental signatures digitally stored + timestamped, minors' medical flags captured + visible to instructors, liability protection transparent.

What if we offer merchandise or ski lesson packages as upsells?

System integrates Stripe (payment) + inventory. Post-booking (May 16), coordinator receives: [package offer email: "Camp already booked? Add-on options for your 75 students: Thredbo logo beanie $25/ea (bulk: 75 = $1,875), instructor video analysis (1-on-1, $50/session, 10-session pack $450), progression workbook ($12/book, 75 = $900), t-shirt merch ($20/shirt, 75 = $1,500)]. Click to add. System upsell: [beanie, video pack, workbook]. Order submitted (May 16, $3,275 revenue). System auto-processes: [beanie inventory check (100 in stock, 75 allocated, 25 remaining), order vendor (June 1, delivery by July 5)]. Video package: [system auto-pairs instructor B (intermediate coach) with 10 video-analysis sessions (1 per week post-camp, recorded on-slope, emailed review)]. Progression workbook: [system auto-sends digital PDF (May 16), instructor + school can reference during lessons + after]. Merch arrives (July 8), packed in room goodie bags (handed out July 10 check-in): [beanie + workbook, creates camp tradition, students remember experience, share photos on Instagram tagging resort]. Upsell revenue: $3,275 from single camp (4% of $81k base package). If 10 camps/season: $32.75k incremental annual revenue (low-friction, high-margin). System also tracks: [beanie attachment: 9/10 camp groups buy, video pack: 3/10 camp groups buy, workbook: 8/10 camp groups buy] → adjust pricing/positioning based on adoption. Merch automation: less manual email back-and-forth ("what shirt sizes do we have left?"), more revenue realized per group.

What's the cost difference between manual spreadsheets vs custom platform?

Current (manual): [Falls Creek + Thredbo combined run ~8 school camps/season (75–150 students each), June–August. 1 resort manager + 1 admin person spend 200 hrs/season on intake (emails, phone calls, spreadsheet updates, rental sizing, instructor scheduling, room assignment, dietary tracking, refund processing). 200 hrs × $40/hr = $8k labor cost. Revenue per camp: $500k (150 students × $3.3k average package = $495k). Refund costs: 12% of camps trigger weather refund (50% loss), 2 camps/season × $250k × 50% = $250k annual refund outflow (uninsured). Upsell miss: no merchandise/video packages = $50k potential revenue lost (4% upsell × 8 camps × $500k base). Total annual cost: $8k labor + $250k refunds + $50k lost upsell = $308k "hidden cost" of manual ops]. Custom Velocity X platform: build cost $180–220k (weather API integration, room assignment logic, dietary tracking, instructor crew dispatch, refund automation, merchandise + upsell Stripe integration, parent consent e-sign, dashboard + instructor mobile app, analytics). Host: $3k/year. Year-1: $215k build + $3k host = $218k. Year-1 value realized: [labor saved (intake + scheduling + refund processing automated, 200 hrs down to 30 hrs = 170 hrs × $40 = $6.8k saved)], [refund loss eliminated through proactive weather rescheduling (12% refund rate down to 5% via forecast automation = 4% saved on $4m revenue = $160k saved)], [upsell captured (merchandise + video packages = $50k new revenue, 50% of potential = $25k incremental profit realized)], [retention improvement (engaged families = 60% book again, manual spreadsheet = 35% rebook = 25% improvement × 8 camps × $500k = $100k new revenue)]. Year-1 gross value: $6.8k + $160k + $25k + $100k = $291.8k. Year-1 net: $291.8k value – $218k cost = +$73.8k profit (payoff month 9 of Year 1). Year 2+: $291.8k value, platform cost $3k = 97x ROI. Running a regional ski operation with multiple camps/season, weather refund chaos, instructor scheduling nightmares, and spreadsheet-based intake? Check Velocity X's custom snow-resort platform, or book a call to discuss your operation (how many camps/season?, students per camp?, biggest pain point this July: intake, refunds, crew dispatch?).