Build the deployment
you actually need.
Centro Enterprise is our custom-build practice. We've shipped across hospitality, residential and the workplace vertical we're bringing to market next — and we ship custom for organisations whose shape doesn't fit a productized SKU. Whatever you need, we'll scope it with you and ship it together.
What Enterprise is for
Whatever shape your deployment takes.
If you've looked at our Hospitality or Residential vertical pages and your deployment doesn't fit cleanly, it doesn't mean Centro is the wrong platform — it just means your deployment is an Enterprise build. These are the shapes we ship through this practice.
Custom verticals
A vertical we haven't productized yet — Workplace today; could be healthcare, education, retail, or your own category tomorrow. We build the vertical's value model and capability surface with you.
Multi-vertical portfolios
One organisation operating across multiple Centro verticals — a hotel group with branded residential, a corporate with a hospitality-led campus. One Centro tenant, multiple verticals, unified admin.
Integration-heavy deployments
Custom PMS connectors, BMS integration, ERP/financial system bridges, specialised access-control stacks, bespoke calendar integrations — anywhere the assembled SaaS market hasn't built the connector yet.
White-label deployments
Centro under your brand — partner-led deployments where you take the platform to market and Centro powers the backend. Joint engineering, joint support arrangements.
Enterprise-grade support contracts
Beyond the bundled support that ships with our productized Activate and Optimise tiers — dedicated technical account management, custom SLAs, on-site engineering for major rollouts, executive-sponsor relationships.
Capabilities not yet in productized verticals
If you need something the productized verticals don't include — a new value-model lever, a capability we haven't shipped yet — Enterprise is how we get it built and into your deployment first.
Pricing posture
Pricing is scoped, not published.
Enterprise deployments are bespoke by definition. We'll quote against your actual deployment shape after a discovery conversation, but the three lines below frame how the engagement is priced.
One-time. Scoped to integration breadth, deployment complexity, and the capabilities being built. Larger or multi-property engagements scale from here.
The Centro tenant + the capabilities we ship for you. Quoted per engagement — depends on user count, vertical scope, and feature surface.
Enterprise engagements come with Centro-provided support as part of the deal. SLA, escalation paths and team coverage scoped to your needs.
If your deployment fits one of our productized verticals, you'll get a cleaner economic story on those pages with Activate or Optimise tier pricing. Enterprise is for the deployments that don't — and for the ones where you want the platform built around you, not the other way around.
How it works
Discovery → scope → ship.
Discovery conversation
A 30–60 minute working session with our team. We learn what you’re trying to achieve, where the productized verticals fall short, and what shape your deployment actually takes.
Scoped proposal
We write up the engagement — capability scope, integration plan, timeline, pricing — against your specifics. Fixed-scope or time-and-materials depending on what suits.
Build & deploy together
Our engineering and product team work alongside yours through the build. Implementation, integration, training, launch — we ship it with you, not at you.
Tell us what you're building.
The first step is always a discovery conversation. No deck to send, no standard pricing sheet — we'd rather hear your shape and respond to it.