Domain · Operator onboarding

What it covers

Moving a signed operator from contract to live, with their inventory published and discoverable. The cycle from "signed" to "first units bookable".

For standard marketplace operators, this ends at units live on rentiful.ai. For White Label operators, it additionally ends at a co-branded microsite configured, a subdomain pointing to it, and the Yardi sync running into the shared unit data model.

Activities

Data access setup — connecting Rentiful to the operator's source systems.
Initial unit data import — pulling inventory into Rentiful's data model.
Data validation and enrichment — ensuring quality meets Rentiful's bar before going live.
First-time publishing — units appear on the marketplace.
Onboarding sign-off — operator agrees their units are correctly represented.
Establishing the ongoing operating cadence with the operator.
For White Label operators: microsite provisioning, theming, subdomain setup, brand sign-off.

Operations

Integration setup operation

Operator signed → integration approach selected (API, feed, manual, hybrid) → access established → test data flowing → integration validated. Onboarding is blocked until this completes.

Initial import and enrichment operation

Source data received → mapped to Rentiful's data model → automated enrichment applied → quality issues flagged → operator consulted on gaps → cleaned data ready for publishing.

First-publish operation

Cleaned units → final pre-publish review → units pushed live → operator notified → operator sign-off captured → onboarding marked complete.

Operating cadence handshake operation

Onboarding sign-off → recurring touchpoints scheduled (monthly check-in, financial close, signal channel) → operator briefed on how Rentiful works ongoing → operator's main contact at Rentiful confirmed.

White Label microsite configuration operation

Runs in parallel with the integration and import operations for White Label operators only. Operator brand assets collected (logo, colours, voice notes) → microsite provisioned and themed, co-signed "powered by Rentiful" → subdomain or URL agreed and pointed → Renter Loop conversation surfaces re-skinned for this operator → operator sign-off on branding → microsite goes live alongside first publish.

Unit data flows through the same enrichment and validation as standard onboarding; the microsite is a presentation layer over the shared unit model, not a parallel system. Depends on platform.multi-brand-config.

Notes

Onboarding cycle time is one of the loop's most important leading indicators. A long gap between signature and first unit live means lost revenue on Rentiful's side and eroding operator commitment. Automation that compresses this cycle — on the integration, the import, and the validation steps — has high leverage.

For White Label operators, the microsite configuration operation adds work but not a separate onboarding path. The loop owner still runs one onboarding per signed operator; the microsite is one more step inside that onboarding, not a second onboarding.

Cross-loop surface

Completed onboarding transitions an operator into steady-state Domains C–F.
White Label onboarding depends on platform.multi-brand-config being shipped and available.