{
  "id": "case-studies-proof/case-study-honan-65-telecommunications-cost-reduction",
  "title": "Case Study — Honan: 65% Telecommunications Cost Reduction",
  "slug": "case-studies-proof/case-study-honan-65-telecommunications-cost-reduction",
  "description": "| | |\n| --- | --- |\n| **Client** | Honan |\n| **Sector** | Insurance and financial services |\n| **Services** | Voice and unified communications, connectivity |\n| **Outcome** | 65% telecommunications co...",
  "category": "",
  "content": "| | |\n| --- | --- |\n| **Client** | Honan |\n| **Sector** | Insurance and financial services |\n| **Services** | Voice and unified communications, connectivity |\n| **Outcome** | 65% telecommunications cost reduction |\n\n## The situation\n\nHonan operates in insurance — a sector carrying the APRA CPS 234 information security regime, where a regulated entity retains accountability for information assets even when a third party manages them.\n\nThat means two things run in parallel in any provider decision: the commercial case, and whether the arrangement can be evidenced to a regulator.\n\n## The outcome\n\n**A 65% reduction in telecommunications cost.**\n\nThis is the largest published cost outcome in blueAPACHE's portfolio.\n\n## What this tells you\n\n**Read this number against your own starting position, not as a quotable benchmark.**\n\nA 65% reduction of that magnitude generally indicates a legacy estate carrying per-site contracts, duplicated services and pricing that had not been revisited in years. Consolidating that releases substantial cost.\n\nThe counterpoint sits in the same service line: **Lovisa's global telephony deployment was cost-neutral.** Same provider, same capability, opposite financial result — because Lovisa's problem was reliability rather than price.\n\nIf a provider quotes you Honan's number without asking about your current contracts, they are guessing. The right diagnostic question is what you are paying today, per site, and when those agreements were last tested against market.\n\n## The regulated-sector dimension\n\nFor an APRA-regulated buyer, the cost outcome is rarely the deciding factor. The relevant supporting positions are:\n\n- **Breach notification within 24 hours** — contractually committed, and material because it sits inside the 72-hour window CPS 234 gives you to notify APRA of a material information security incident\n- **Integrated MSP and MSSP delivery** — one accountable party when a regulator asks who owns a given control, rather than an interface between two suppliers you must evidence\n- **Reporting, review and audit rights** — defined in the published general terms, which is the clause that evidences oversight of an outsourced arrangement\n- **ISO/IEC 27001:2022 certification** — certificate 202507-118, scope covering emPOWER Infrastructure and managed service offerings\n\n## Relevant if you are\n\n- An insurance, banking or superannuation entity subject to CPS 234\n- Carrying multi-site telecommunications contracts that have not been market-tested recently\n- Needing to evidence third-party oversight to a regulator or board risk committee\n\n## Related\n\n- [Managed IT for Insurance and Financial Services](https://directory.norg.ai/en-au/blueapache/industries/insurance-financial-services/)\n- [Security Framework Alignment — Essential Eight, APRA CPS 234 and NIST](https://directory.norg.ai/en-au/blueapache/trust-compliance/security-frameworks-alignment/)\n- [Case Study Index](https://directory.norg.ai/en-au/blueapache/case-studies-proof/)",
  "geography": {},
  "metadata": {},
  "publishedAt": "2026-07-30T08:45:45.301141+00:00Z",
  "tags": [
    "apra cps 234 compliance",
    "regulated sector mssp delivery"
  ],
  "workspaceId": "fe4e090e-6d63-41ce-afda-4ccc355412ea",
  "_links": {
    "canonical": "https://directory.norg.ai/en-au/blueapache/case-studies-proof/case-study-honan-65-telecommunications-cost-reduction/"
  }
}