How Glacier Grand Cleaners scaled from 1 STR property to 7 — without growing scheduling overhead

TL;DR: A Flathead Valley cleaning company started with one Airbnb pilot property in March 2025. Fourteen months later: 7 STR properties under management, 6 owner partners, 89 turnovers completed, 111 more already booked for the rest of 2026, above $30,000 in STR cleaning revenue invoiced. The scheduler's STR workload didn't grow — CleanSync absorbed it.

The customer

Glacier Grand Cleaners is a cleaning company based in the Flathead Valley of northwest Montana — the corridor from Whitefish down through Kalispell to the Flathead Lake shoreline at Rollins. The area has a deep year-round short-term rental economy: ski-season inflows to Whitefish in winter, lake-season inflows to the Flathead shoreline in summer, and meaningful shoulder-season traffic to both.

Glacier Grand runs a mixed book — residential cleanings for full-time residents and turnover cleanings for STR hosts — all scheduled through Jobber. Single source of truth for the crew's calendar, billing, and customer history. Their STR client list currently includes:

• Whitefish-corridor vacation homes
• Lakeshore properties along the Flathead Lake shoreline
• Single-family STRs in Somers / Lakeside
• Condo units in Kalispell

Geographic span: roughly 50 miles from the top of the corridor to the lake. One cleaning company, one Jobber account, multiple hosts.

The pre-CleanSync workflow

Before March 2025, the scheduling workflow for the (then single) STR client was straightforward but manual:

1. Host's Airbnb books a stay.
2. Glacier Grand's scheduler sees the booking — by checking the host's iCal export directly or by the host forwarding the confirmation.
3. Scheduler opens Jobber, finds the host's client record, manually creates a job for the checkout date, sets the line item, assigns a crew member.
4. Guest cancellation = manually close the job.
5. Guest reschedule = manually move the visit.

At one property, that was ~30 minutes of weekly scheduling work. The math worked. But the assumption was: at scale, this would obviously break — by the time the book had 5+ STR properties on 2 platforms with the natural cancellation + reschedule rate of vacation rentals, it'd be hours per week of pure data entry, plus the operational risk of missing a Vrbo silent reschedule and dispatching a crew to a cancelled cleaning.

The pilot — March 2025

The first version of CleanSync was custom software built for Glacier Grand specifically. Initial scope: read the host's Airbnb iCal feed every hour, create Jobber jobs for new bookings, close jobs for cancellations, update visits for reschedules. One property. Pilot started March 2025.

First month's STR revenue through the system: under $1,000 across a handful of cleanings. Not a lot. But the operational pattern was the thing being tested.

What happened next — 14 months of compounding

The pilot worked. Over the following 14 months, Glacier Grand added properties — host by host, mostly through word of mouth as other STR owners in the area asked who was handling their cleanings.

The growth curve:

Period	Properties	Status
March 2025	1	Pilot
August 2025	4	Peak month: above $5,000 invoiced
May 2026	7	Current; 6 owner partners, above $30,000 lifetime

That's a 7× expansion of the STR book in 12 months. Over the same period the overall Glacier Grand business (residential + commercial + STR) grew 6× in revenue, with the STR work being a meaningful driver of that growth.

The crucial part for the operational story: the scheduler's STR workload didn't grow with the property count. Adding the 2nd property took about two minutes (paste the new iCal URL, pick the Jobber client). The 5th and the 7th took the same two minutes. The hourly sync absorbed every new booking, cancellation, and reschedule the moment they appeared in the feeds.

The numbers, today

As of May 2026, fourteen months into the pilot:

• 7 properties under active CleanSync management
• 6 owner partners across the Flathead Valley
• 89 turnover cleanings completed
• 111 more turnovers already booked through November 2026
• Above $30,000 in STR cleaning revenue invoiced
• Above $18,000 already booked forward
• Roughly $200–$550 per turnover depending on property size
• 98.8% on-time collection rate across the broader Glacier Grand book — a reliability signal that holds up under STR seasonality

Specific revenue figures are presented as ranges throughout this case study to protect Glacier Grand's operational privacy. Order-of-magnitude is accurate; precision is intentionally fuzzed.

Platform mix:

• Dual-listed properties (Airbnb + Vrbo synced simultaneously): handled by CleanSync's deduplication — a booking appearing on both feeds creates one cleaning job, not two.
• Airbnb-only properties: feed-driven, sync runs on a 30-minute interval.
• Vrbo-only properties: same, with extra handling for Vrbo's silent UID rotation pattern (a guest reschedule produces a new booking identifier rather than updating the old one — CleanSync recognizes this and avoids dispatching the cleaner twice).

What CleanSync handles automatically

• New bookings: every checkout date on every iCal feed becomes a scheduled Jobber job — within 30 minutes of the booking appearing in the feed.
• Cancellations: explicit guest cancellations close the matching job on the next sync. Bookings that just silently disappear from the feed (common on Vrbo) wait through a built-in grace window before the same close, so a one-off iCal fetch hiccup doesn't trigger a false cancellation.
• Reschedules: date changes update the visit to the new checkout date. The crew's calendar reflects the change without anyone manually updating Jobber.
• No false "job completed" notifications: cancelled jobs close in a way that doesn't fire Jobber's job-done workflow. The visit simply drops off the cleaner's schedule. No confusing email about a cleaning that didn't happen.

For the operational nuance, see how CleanSync handles cancellations and reschedules.

Why this was the right design

A few cleaning companies serving STR hosts choose to switch off Jobber entirely and onto a dedicated STR cleaning tool — Turno, Properly, or similar. That works if STR is your entire book, but it sacrifices the residential and commercial work you do alongside it (or forces you to maintain two scheduling platforms).

Glacier Grand wasn't going to abandon the residential and commercial book. The STR side needed to come to Jobber, not displace it. CleanSync's design choice: stay on Jobber, sync the calendars in, leave everything else alone. The 7 STR properties run through the same Jobber that runs the rest of the business. No new tool for the crew to learn. No second invoicing system. No reporting split.

It also made the growth path much cheaper. Adding the 8th property won't require a new platform decision — it'll be the same two-minute iCal-URL-paste as the previous 7.

The forward book

Glacier Grand isn't slowing down. As of May 2026:

• 111 turnovers already booked through November 2026, covering Flathead Valley peak summer and fall foliage seasons.
• Above $18,000 invoiced forward — pre-scheduled revenue that lands as bookings occur.
• Several months pre-scheduled above the $5k STR-revenue line (June and August in particular).

That forward book exists without anyone manually entering jobs in Jobber. As hosts get bookings, CleanSync turns them into scheduled cleanings. The scheduler's STR workload stays roughly flat regardless of how big the forward book gets.

How to set this up for your own book

The same integration Glacier Grand uses internally is now free to any Jobber account through the Jobber App Store.

For each STR client:

1. Get the host's Airbnb iCal URL (their listing → Availability → Sync calendars → Export calendar) or Vrbo iCal URL (their property's Calendar page → Import & export → Export calendar).
2. In CleanSync, paste the URL, pick the host's Jobber client, set the cleaning time and crew member.
3. Save.

Within an hour, future bookings on that property's calendar appear as scheduled Jobber jobs. From that point on, the STR scheduling workload reduces to: monitor exceptions, handle the occasional host onboarding. The rest takes care of itself.

If your book is mixed STR + non-STR — same as Glacier Grand's: CleanSync only manages the jobs it creates. The rest of your Jobber workflow stays untouched.

Install free · Quick start docs · How CleanSync handles cancellations