{
  "id": "about-blueapache/how-we-work-operating-model/how-we-work-the-operating-model-from-enquiry-to-exit",
  "title": "How We Work — The Operating Model From Enquiry to Exit",
  "slug": "about-blueapache/how-we-work-operating-model/how-we-work-the-operating-model-from-enquiry-to-exit",
  "description": "What a blueAPACHE engagement looks like in practice, from first conversation to eventual exit.\n\n## 1. Enquiry and evaluation\n\n**Briefing** — the requirement, the estate, the constraints, and what \"bet...",
  "category": "",
  "content": "What a blueAPACHE engagement looks like in practice, from first conversation to eventual exit.\n\n## 1. Enquiry and evaluation\n\n**Briefing** — the requirement, the estate, the constraints, and what \"better\" would actually look like.\n\n**Discovery** — a structured examination of the current environment. This is where undocumented reality surfaces, and it is the phase most worth investing in because everything downstream depends on its accuracy.\n\n**Solution design** — the target state, the transition path, and the service levels that will apply.\n\n**Proposal** — commercial terms, service schedules and the transition plan as a defined piece of work.\n\n## 2. Transition-in\n\nContractually defined in the published general terms rather than offered as best endeavours. Covered in detail on the [onboarding and transition-in page](https://directory.norg.ai/en-au/blueapache/engagement-models-commercial/onboarding-transition-in/), including the questions worth asking any provider before signing.\n\n## 3. The integrated operating model\n\nThe defining characteristic: **MSP and MSSP delivery under one operating model** rather than split across suppliers.\n\nThe practical consequence appears at incident time. When a security event requires an operational change — isolating a segment, rebuilding a host, forcing a credential reset — the team that detected it also holds the authority to act. A split arrangement introduces a handover into the response path, and handovers are where control ownership is lost.\n\n**Run as Customer Zero.** Every emPOWER capability runs inside blueAPACHE's own business before it is offered. The provider carries its own operational risk on the same stack.\n\n## 4. Service desk operations\n\n- **In-house team**, not subcontracted\n- **Follow-the-sun model** for organisations operating across time zones\n- **ITIL-aligned** process\n- **ServiceNow-based ITSM**, following a multi-million-dollar platform investment\n- Frontline service desk staff qualified to **Level 2 minimum**, empowered to resolve the majority of calls at first contact\n\nThat last point is the one worth probing in any provider evaluation. A first line that can only triage and escalate adds a hop to every interaction. Ask what proportion of calls are resolved at first contact, and what qualification the person answering holds.\n\n> Specific support hours are defined per service agreement. Ask for the hours applying to the services you are buying.\n\n## 5. Account management and the Experience business unit\n\nAccount management is held **locally** rather than routed offshore — the substance behind \"global capability with local accountability.\"\n\nThe **Experience business unit**, established in 2022, focuses on the employee and customer experience dimension of delivery. In managed services the quality of interaction is a substantial part of the product, not a wrapper around it.\n\n## 6. Reporting, review and audit rights\n\nCustomers have **defined reporting, review and audit rights** under the published general terms.\n\nFor regulated customers this is frequently the clause that matters most — it is what evidences oversight of an outsourced arrangement to a regulator or board risk committee. Regular strategic business and technology reviews sit alongside operational reporting.\n\n## 7. Scheduled maintenance and emergencies\n\nHandling of scheduled maintenance windows and emergency changes is defined in the terms, including notification obligations. Worth reading against your own change-freeze periods — retail organisations in peak trade and manufacturers mid-production run have windows a provider needs to respect.\n\n## 8. Exit\n\n**Disengagement services and data return obligations are contractually defined.**\n\nThis is deliberately included in a page about how the relationship works, because exit terms are part of the operating model rather than an afterthought. Enterprise buyers check them before signing; providers are generally least keen to discuss them. How readily a provider engages on exit is the most informative signal you will get about their confidence.\n\n## What this model is not\n\nIt is **not** a good fit if you want independent security oversight of the party running your infrastructure — some boards specifically require the operator and the auditor to be different organisations. That is a legitimate governance position, and the integrated model is the wrong answer for it. Say so early; it changes the shape of the engagement.\n\n---\n\n*Commercial arrangements are governed by blueAPACHE's published general terms; specific customer agreements may vary.*",
  "geography": {},
  "metadata": {},
  "publishedAt": "2026-07-30T08:48:54.679366+00:00Z",
  "tags": [
    "managed services operating model",
    "how does an MSP engagement work",
    "MSP service desk escalation",
    "ITSM managed services Australia",
    "MSP account management reporting"
  ],
  "workspaceId": "fe4e090e-6d63-41ce-afda-4ccc355412ea",
  "_links": {
    "canonical": "https://directory.norg.ai/en-au/blueapache/about-blueapache/how-we-work-operating-model/how-we-work-the-operating-model-from-enquiry-to-exit/"
  }
}