Skip to Content
Customer successEnterprise onboarding

Enterprise onboarding

The Nebbos enterprise onboarding programme delivers a production-ready deployment in six phases. Each phase carries a named owner, an exit artefact evidencing completion, and a gate that must be cleared before the subsequent phase commences.

Phase overview

#PhaseDurationOwnerExit artefact
01Kickoff & scope confirmation3 daysNebbos deployment leadSigned statement of work
02Identity & tenancy provisioning5 daysOperations plus customer ITSSO live; test operator identities issued
03Cradle provisioning7 daysOperations plus named operatorsCradles provisioned; first attested read recorded in the chain
04Data ingestion & Pearl training10 daysOnboarding team plus customer operationsPearls returning scoped answers with citation trail
05Approval-graph configuration5 daysOnboarding team plus customer complianceApproval graphs live; first end-to-end attested write
06Production sign-off3 daysCustomer security officer plus Nebbos deployment leadSigned production-readiness attestation

Aggregate duration: thirty-three business days end-to-end. Compressed schedules are supported for smaller deployments; extended schedules apply to highly regulated deployments.

Phase 01 — Kickoff and scope confirmation

Kickoff call

Sixty-minute session with the Nebbos deployment lead, the customer executive sponsor, the customer operations lead, and the customer security lead. Scope confirmed; blockers identified; per-side deliverables agreed.

Written scope confirmation

Nebbos issues a written statement listing in-scope departments, operator identities, Cradle count, and the production sign-off exit criterion. The customer executive sponsor countersigns.

Shared coordination channel

A dedicated shared channel is established between the customer team and the Nebbos deployment team. Every subsequent onboarding artefact is delivered through this channel.

Phase 02 — Identity and tenancy provisioning

SSO connection

Customer IT configures the single sign-on connection to the customer identity provider (Okta, Azure Active Directory, Google Workspace, or generic SAML 2.0). Configuration typically completes within thirty to sixty minutes with the identity-provider administrator available.

Group and department mapping

The customer defines the mapping from identity-provider groups to Nebbos departments and to authorised operator tiers. This mapping anchors substrate tier gates to the customer identity plane.

Test operator provisioning

Two test operator identities per tier (Guest, Host, Architect) are provisioned for the customer team ahead of Cradle provisioning.

Phase 03 — Cradle provisioning

Executed under the procedure specified in Cradle provisioning.

Phase 04 — Data ingestion and Pearl training

Data-source registration

The customer registers the systems from which each Pearl will read (customer relationship management, enterprise resource planning, ticketing, document store, meeting recordings). Nebbos maps each system to the corresponding ingestion connector.

Row-level scope declaration

For each registered system, the customer declares the rows and documents accessible to each department’s Pearl. Row-level isolation is enforced at ingestion, not applied retrospectively.

Pearl training

Each department’s Pearl is trained on twenty to one hundred yes/no decisions supplied by the customer department. The recorded decisions populate the Pearl’s memory registers.

Phase 05 — Approval-graph configuration

Approval-flow specification

For each operational decision requiring human approval — contract execution, refund issue, code deployment, task escalation — the customer specifies the tier gate and the human role authorised at that tier.

Graph configuration

The onboarding team configures the approval graphs within the platform. Each graph consists of a sequence of steps carrying per-step tier requirements. Configuration duration is one to three hours per graph.

End-to-end verification

A test-scoped request is walked through each graph. Every attested approval produces an audit-chain entry. Graphs that do not produce a complete chain end-to-end are not promoted to production.

Phase 06 — Production sign-off

Production sign-off is a written attestation from the customer security officer that the deployment satisfies customer internal control requirements. Nebbos does not classify a deployment as production-ready in advance of this attestation. Gates specified in phases 01 through 05 must be cleared before phase 06 commences.

Scope boundaries

The Nebbos onboarding programme does not include:

  • Customer identity-provider administration on the customer’s behalf
  • Customer data classification (row-level scope declaration remains the customer’s responsibility)
  • Pearl retraining without customer authorisation (each retraining event is a distinct audited action)
  • Production promotion in advance of a completed phase-06 attestation, regardless of contractual urgency

Post-onboarding support

The named deployment lead remains available in the shared channel through the onboarding period. For post-onboarding operations, see the Admin guide and FAQ.