The four-stage Suite Profit pilot programme
Suite Profit engages hotel groups through a governed pilot programme, not through self-serve activation. The programme runs for roughly 90 elapsed days, is delivered by a named account manager, and always finishes with a signed group rollout playbook — a document your CFO and CIO can act on when funding the wider adoption.
Stage 1 — Kickoff & scoping memo
Kickoff workshop with the corporate revenue office, group operations office and district manager for the pilot property. The Suite Profit engagement lead drafts a scoping memo, a security questionnaire, and a per-entity billing schedule for the CFO to sign off.
Stage 2 — Data migration on the pilot property
Suite Profit provisions the operator console tenant, the group's IdP is federated over SAML 2.0 or OIDC, and Profitroom Suite is bound with property-scoped tokens. Rate history, guest CRM records and channel mapping are migrated for the pilot property only.
Stage 3 — Pilot property live for 60 days
The pilot property runs on Suite Profit for a governed 60-day window. Weekly steering with the group operations office, mid-cycle QBR with the account manager, incident and SLA reporting streamed to the group's SIEM.
Stage 4 — Group rollout playbook
Suite Profit delivers the group rollout playbook: property-by-property migration order, per-district onboarding, entitlements matrix, per-entity billing schedule, and an executive report the CFO and CIO can present to the board.
Governance across the pilot
Every stage has a named contact on the Suite Profit side and a named contact on the group side. The engagement lead runs the weekly steering; the security engineer partners with the group's DPO; the migration engineer works alongside the district manager for the pilot property. All governance artefacts — steering minutes, incident reports, change tickets, SLA statements — live in the operator console and stream to the group's SIEM.
The pilot programme is priced on a fixed scope basis and captured in the Master Subscription Agreement, so procurement and finance can approve the envelope on day one without surprises at stage four.
What the group receives at each stage
Stage 1 ends with a signed scoping memo, a pre-filled security questionnaire, and an order form ready for procurement. Stage 2 ends with a bound operator console, federated identity, and a migrated pilot property. Stage 3 delivers weekly steering artefacts, an SLA compliance dossier, and a mid-cycle QBR. Stage 4 delivers the group rollout playbook, the executive report, and the go / no-go recommendation from the Suite Profit engagement lead.
The 60-day live window is deliberately long enough to cover the pilot property's compression and non-compression demand cycles, so the KPIs on the pilot are representative rather than seasonal noise.
Prerequisites at group level
- Live Profitroom Suite subscription across the properties in scope, with API access on the enterprise plan.
- Identity provider with SAML 2.0 or OIDC support — Okta, Microsoft Entra ID (Azure AD), or Google Workspace.
- Named executive sponsor at the corporate revenue office and named DPO for the security questionnaire.
- Willingness to sign a Master Subscription Agreement per legal entity, invoiced in EUR by Suite Profit Sp. z o.o.
- Nominated pilot property whose district manager can commit to weekly steering for 60 days.