Kaye Collective Remote Operations Studio
Case studies

Three operations,
rebuilt to run without me.

Every engagement below is real work for a real portfolio. Client names, addresses and figures are redacted or generalised where the work was confidential.

01STR · Cluster operations at scale

Cluster operations at 15,000 units.

ClientLavanda
RoleCluster Head
ScopePeak-season STR operations

The situation

Multiple property teams, thousands of units, and a peak season where guest issues arrive faster than any one person can triage them. At that volume, nothing survives on memory or good intentions — an operation either has rules or it has chaos.

What we built

Cluster-level coordination across property teams: a single triage path for guest escalations, scheduling that held across shifts and time zones, and defined ownership so every issue had a named owner within minutes rather than hours.

What changed

Escalations stopped bouncing between teams: each one landed with a named owner within minutes, and the same playbook held across every team through the busiest dates of the year. When the season ended, the triage path stayed — because it was written down, not remembered.

Cluster coordinationPeak season
One triage path NAMED OWNER · SLA · ESCALATION
Each mark is a unit under coordination · red denotes an escalation
02LTR · Full lifecycle ownership

Forty-plus units, lease to close.

Portfolio40+ long-term rentals
RoleSole operator
ScopeEnd-to-end management
StackRentec · documented SOPs

The situation

A long-term rental portfolio where every stage — tenant vetting, leasing, maintenance, renewals, reporting — landed on the owner's desk. Growth had made the portfolio bigger without making it easier to run.

What we built

One operator owning the whole lifecycle, with the process written down at each stage: screening criteria that didn't move, a maintenance path with vendors already vetted, renewal timelines that started before they were urgent, and reporting the owner could read instead of assemble.

What changed

Forty-plus units ran through vetting, leasing, maintenance and renewals on one operator and a documented process — renewals started before they were urgent, and the owner’s involvement shrank to reading a weekly report instead of fielding daily questions.

Tenancy lifecycleOwned end-to-end
VETTING LEASE MAINTENANCE RENEWAL 40+ UNITS, ONE OPERATOR
Every stage documented, so the loop runs without the owner in it
03Systems · Infrastructure build

Four tools, one source of truth.

EngagementSystems Build
RoleOperations architect
ScopeSOPs · dashboards · automation
StackClickUp · Airtable · GHL · Make · n8n

The situation

Work spread across spreadsheets, inboxes and half-adopted tools, with the real process living in one person's head. Nothing was broken enough to fix, and everything was slow enough to hurt.

What we built

An audit of every recurring task and handoff, then the infrastructure underneath it: written SOPs, ClickUp and Airtable builds that matched how the work actually ran, and automation across GoHighLevel, Make and n8n to remove the copying-between-tabs entirely.

What changed

The copying-between-tabs disappeared: work entered once and moved through ClickUp, Airtable and the CRM on its own. And because every step was written down, the process stopped depending on any one person — a new team member could run it from the SOPs.

Before & afterSame work, fewer hops
BEFORE AFTER SPREADSHEETSINBOX CLICKUPAIRTABLE WHATSAPPHEADS One system WRITTEN SOPsONE DASHBOARD AUTOMATED HANDOFFSNAMED OWNERS
The tools didn't change. Where the truth lives did.
Also on the books

Selected engagements.

Work that didn't need a full case study — same standard, same documentation.

NextHome Modern Realty49-page comparative market analysis — property comparisons, pricing insights, valuation ranges, branded layout.Real estate admin
Sarasota property managementScheduling, correspondence, documentation and coordination for a fast-paced real estate operation.Ops support
EMRG ImagingMulti-system standardization — one documented process where several tools used to disagree.Systems build
Holiday rental proposalMarket-backed STR proposal built on AirDNA and PriceLabs data.STR analytics
Work with us

Your portfolio, documented.

If any of the above sounds like your operation, the first call is twenty minutes and costs nothing.

Where your time actually goes20 min
Which stage is leakingFree
What we would build firstNo pitch

No pitch deck, no pressure. Replies within one business day.