Skip to content

Guidance for Commercial Teams

Introduction

Commercial teams play a critical role in establishing successful SRE managed services.

The commitments made during client engagement, contract development and Statements of Work directly influence how effectively SRE can deliver the service after transition.

SRE is not simply a support function that becomes involved after a platform has been delivered. The operational model, responsibilities, service expectations and contractual commitments established during the commercial phase define the conditions under which SRE will operate.

This section provides commercial teams with guidance on the areas of the SRE framework that apply to their responsibilities.

Commercial and SRE Partnership

SRE and commercial teams have different responsibilities, but both contribute to creating successful managed services.

Commercial teams establish the client relationship, define the commercial agreement and set expectations with the client.

SRE provides the operational expertise required to understand what is needed to support the platform successfully.

Collaboration between commercial and SRE teams is required before commitments are made to clients.

The objective is to create agreements that are commercially appropriate while also being technically achievable and operationally sustainable.

Areas Relevant to Commercial Teams

Understanding the Ensono SRE Model

Ensono SRE operates differently from traditional internal SRE teams.

SRE takes operational ownership of platforms delivered by project teams for external clients. This means services are supported within a managed service model with defined contractual responsibilities.

Commercial teams should understand that SRE success depends on:

  • Clear service scope.
  • Realistic operational commitments.
  • Production-ready platforms.
  • Defined client responsibilities.
  • Effective communication processes.
  • Appropriate transition planning.

Related documentation:

Defining the Scope of Service

The scope of an SRE service must be clearly defined before a contract or Statement of Work is agreed.

Ambiguity around scope creates operational risk after transition.

Commercial agreements should clearly define:

  • Applications supported.
  • Infrastructure supported.
  • Environments included.
  • Cloud platforms.
  • Third-party dependencies.
  • Operational responsibilities.
  • Client responsibilities.
  • Explicit exclusions.

Both the client and SRE must have a shared understanding of what service is being provided.

Related documentation:

Defining Service Levels and Commitments

Service Level Agreements (SLAs), Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs) represent significant operational commitments.

These commitments must reflect what the platform can realistically achieve.

Commercial teams should avoid finalising operational commitments before the platform has been assessed and validated.

For example:

  • A recovery time objective should not be committed before disaster recovery has been tested.
  • Availability commitments should consider platform architecture and dependencies.
  • Support expectations should align with the operational coverage provided.

Proposed service levels can be discussed during early engagement, but final commitments should only be agreed once SRE has confirmed the platform can meet those expectations.

Related documentation:

Production Readiness Requirements

A platform entering SRE support must be capable of being operated reliably.

Production readiness should be considered a prerequisite for SRE accepting operational accountability.

Commercial commitments should account for the activities required before SRE can provide the agreed service.

This includes:

  • Production readiness assessments.
  • Observability implementation.
  • Monitoring and alerting.
  • Disaster recovery validation.
  • Security requirements.
  • Operational documentation.
  • Knowledge transfer.

SRE should not become contractually accountable for a service before the platform has demonstrated that it is ready for operation.

Related documentation:

Communication and Operating Model Expectations

The relationship between SRE and the client requires clear communication standards.

Commercial agreements should define:

  • How requests are submitted.
  • Required notice periods for releases and changes.
  • Client communication responsibilities.
  • SRE communication responsibilities.
  • Escalation routes.
  • Governance expectations.

Operational work should enter SRE through agreed service management processes rather than informal communication channels.

For example, client requests should be raised through the agreed ticketing process. Collaboration tools may support discussion, but they should not replace formal operational processes.

Related documentation:

Defining Client Responsibilities

Managed services depend on collaboration between SRE and the client.

Contracts should clearly identify client responsibilities, including:

  • Providing required access.
  • Communicating planned changes.
  • Providing required approvals.
  • Maintaining ownership of client-managed components.
  • Participating in operational processes.

Where client responsibilities are not fulfilled, the impact on service delivery should be understood and reflected within the service agreement.

Clear responsibilities protect both parties and prevent uncertainty during operational events.

Related documentation:

Resource Allocation and Support Coverage

SRE services require clearly defined resource models.

Commercial agreements should describe:

  • Expected engineering allocation.
  • Support team structure.
  • Scaling mechanisms.
  • Support hours.
  • On-call arrangements.
  • Out-of-hours coverage.

Different service models require different levels of operational investment.

Examples include:

  • Business hours support.
  • Extended business hours.
  • 24/7 operational coverage.

These expectations should be agreed before service commencement to ensure the appropriate operational model is established.

Related documentation:

Transition and Hypercare Planning

A successful transition into SRE requires dedicated time and planning.

SRE cannot reliably operate a platform without sufficient understanding of:

  • Architecture.
  • Application behaviour.
  • Deployment processes.
  • Known issues.
  • Operational procedures.

Commercial planning should include sufficient time for:

  • SRE onboarding.
  • Knowledge transfer.
  • Platform familiarisation.
  • Access setup.
  • Hypercare support.

During hypercare, delivery teams should remain engaged while SRE builds operational confidence.

Related documentation:

Common Commercial Pitfalls

Agreeing Service Levels Before Validation

Committing to SLAs, RTOs or RPOs before the platform has been tested can create obligations that cannot be achieved.

Defining Unclear Service Boundaries

Ambiguous scope creates disagreement over what SRE is expected to support.

Treating SRE as a Post-Delivery Activity

Bringing SRE into discussions only after contracts and delivery commitments have been made limits the ability to establish a successful operational model.

Underestimating Transition Effort

A successful handover requires time, planning and collaboration. It cannot be reduced to a single knowledge transfer meeting.

Missing Communication Expectations

Without clear communication responsibilities, SRE may not receive critical information required to operate the service effectively.

Commercial Engagement Checklist

Before agreeing an SRE managed service, confirm:

  • SRE has reviewed the proposed service.
  • Service scope is clearly defined.
  • Responsibilities are understood by all parties.
  • SLAs and operational commitments are realistic.
  • Production readiness expectations are documented.
  • Client communication responsibilities are defined.
  • Support hours and resource allocation are agreed.
  • Transition and hypercare activities are planned.
  • Client dependencies and assumptions are documented.
  • Contractual protections exist where external factors affect service delivery.

Summary

Commercial decisions establish the foundation for successful SRE delivery.

Clear contracts, realistic commitments and early collaboration with SRE reduce operational risk and create a stronger relationship with clients.

The goal is not to limit commercial flexibility. The goal is to make sure commitments made during engagement align with the operational reality of delivering a managed service.

By involving SRE early and defining operational expectations clearly, commercial teams help create services that can be delivered reliably throughout their operational lifetime.