The worked example
Day 3: a new lodge moving through the pipeline
This is the onboarding board your team would watch. Fitzhugh Lodge is a real Roam Free property, shown here as it looked mid-pipeline.
Fitzhugh Lodge
Ingest & verify Done
- Owner sheet ingested — 212 facts sourced
- Sleeps conflict (14 vs 16) → owner confirmed 16
- Hot tub service day confirmed with vendor
- Permit number verified against county record
Knowledge page Done
- One reviewable page, 9 sections
- Access & codes walled off — team-only
- Manager confirmed Wednesday 9:14 AM
Assets generated In progress
- Listing copy — every channel
- Photo captions — 59 of 59
- Digital guidebook — 9 sections
- PMS configuration package
- Guest-messaging profile → loading into Conduit AI
QA review Queued · Day 4
- Question battery — 70 questions, per home
- Privacy screen — no access facts reachable
- Human sign-off before publish
Generated today, from the verified record
White-label means
- Your brand on the listing, guidebook, and every message
- Your voice — copy follows your brand voice profile
- Your domain, your owner portal, your name on the receipt
- The pipeline, the QA gates, the verification machinery
- Us — no co-branding, no "powered by" unless you want it
- The mess onboarding used to be
Why it's fast and safe
The pipeline already exists
This is not a custom build per home. Your portfolio's record defined the rails; each new home just rides them.
Verified before visible
No asset publishes until the record behind it is confirmed — the same "never let an unverified fact near a guest" rule as everywhere else.
Growth stops hurting
Signing 5 homes in a month used to mean 5 weeks of setup debt. Now it means the pipeline runs 5 times.