Technical enablement · 05

Implementation flow

The order of operations to stand {{product.name}} up for a client, and — crucially — which steps unlock which capabilities. Most products have a natural dependency graph: foundational setup unlocks the core data, which unlocks individual capabilities, some of which combine. Follow the spine, branch when ready.

💡

Template guidance. The diagram and steps below are a scaffold. Edit the node labels in the SVG (each node is one <rect> plus two <text> lines), then make the numbered steps match. Keep the rule: every step states what it unlocks.

The unlock graph

Each capability depends on the ones feeding into it. You don't need everything at once, but some things cannot be done out of order. [Replace: name one real example, such as "you cannot enable X before Y exists".]

1 · Provisionenvironment / tenant 2 · Configuresecrets, integrations 3 · Accessusers, roles 4 · Core datathe keystone input 5 · Capability A[Replace: setup] 6 · First run[Replace: initial job] Outcome A[Replace: dashboards] 7 · Connect source[Replace: integration] Outcome B[Replace: alerts, signals] 8 · Capability Cneeds A-core + B Outcome C[Replace: combined view]
Figure 1 — Capability unlock graph (scaffold). The left spine is mandatory setup; tracks A and B branch from the core data; capability C needs both. Replace labels with {{product.name}}'s real capabilities.

Step by step

Each step lists what it delivers and what it unlocks next.

  1. Provision the environment (or request a tenant)

    Either stand up dedicated infrastructure (see dedicated deployment) or request a tenant on the managed platform (see managed model).

    Unlocks: access to the gateway, services and data stores.

  2. Configure secrets and integrations

    Set credentials for third-party services and identity. Store them in the secret store, never in config files. [Replace: list the required keys by name.]

    Unlocks: services that call external providers can start.

  3. Create the tenant and first administrator

    A platform admin creates the tenant and its first admin, who can then invite users (see tenancy and access).

    Unlocks: authenticated, tenant-scoped access.

  4. Load the core data

    Import the client's foundational data and settings. [Replace: what it is and the accepted formats.]

    Unlocks: every capability that reads this data.

  5. Set up Capability A and run it for the first time

    [Replace: configuration and the first job or scan to trigger.]

    Unlocks: Outcome A — [Replace: first visible result].

  6. Connect an external source for Track B

    Point the integration at the client's system. To use a different vendor, see integrations.

    Unlocks: Outcome B and the input Capability C needs.

  7. Enable Capability C

    With core data and Track B both in place, switch on the combined capability.

    Unlocks: Outcome C — [Replace].

  8. Hand over to operations

    Confirm monitoring, alerts and runbooks are live (see operations) and agree the support route with the client.

    Unlocks: production go-live.

Minimum-viable vs full activation

PathStepsYou get
Minimum-viable (proof of value)1 → 5[Replace: the fastest demonstrable result for one client or use case.]
Connected1 → 6[Replace: the above plus live external data.]
Full activation1 → 8[Replace: the complete product, handed to operations.]
💡

If components are optional, say so: a proof of value may not need every service deployed. See deployment models and the components catalogue.