Haskell (The Haskell Company) — Office 365 Phase 0 implementation-strategy initiative (2017)
EPC-reported — statement of work on file; evidence record pendingFirst-pass editionHaskell (The Haskell Company) · 2017 · Project ID EPC-2017-HASKELL-O365-P0
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
EPC-reported — statement of work on file; evidence record pending. Haskell (The Haskell Company) engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for Office 365 Phase 0 implementation-strategy initiative — per EPC Group statement of work v2.0 dated December 22, 2017 (document on file). Project ID EPC-2017-HASKELL-O365-P0. The engagement was completed and paid in full (EPC Group accounts-receivable record).
First-pass edition. The facts in the verification line and the project-facts table come from the documents named there. The engagement narrative below is written by EPC Group from the engagement type and the documented scope, is marked EPC-reported, and is pending review by Errin O'Connor. Delivery status comes from EPC Group's accounts-receivable record as stated by Errin O'Connor on 2026-10-15; no other result is claimed that the documents or project records do not support.
Summary
In 2017, EPC Group completed Office 365 Phase 0 implementation-strategy initiative for Haskell (The Haskell Company) on Office 365, led by Errin O'Connor, EPC Group's founder and the architect named in the engagement documents (the statement of work is prepared by Errin O'Connor), addressing the need for a phased implementation strategy before investing in platform work. The work ran through EPC Group's delivery lifecycle as EPC Group describes its engagements: assess, modernize, govern, operate, enable. The client accepted the deliverables and paid in full, per EPC Group's accounts-receivable record; EPC Group reports that its objectives for the engagement were met. Verification: EPC-reported — statement of work on file; evidence record pending; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported). What the documents establish, and what they do not, is stated in Evidence and limitations below.
Project facts
| Field | Value | Source |
|---|---|---|
| Client | Haskell (The Haskell Company) | document |
| Industry | Architecture, engineering and construction | document / public record |
| Engagement date | December 22, 2017 (SOW v2.0) | document |
| Work | Office 365 Phase 0 implementation-strategy initiative | document |
| Microsoft products | Office 365 | document / scope |
| Scope unit | per EPC Group statement of work v2.0 dated December 22, 2017 (document on file) | document |
| EPC Group role | Consulting and delivery under the instrument named above | document |
| Lead architect | Errin O'Connor — the statement of work is prepared by Errin O'Connor | document |
| Delivery status | Completed; invoiced and paid in full. Source: EPC Group's accounts-receivable record (paid invoices on file, not published because they carry commercial terms), stated by Errin O'Connor on 2026-10-15. EPC Group treats payment as acceptance; no client acceptance record is published for this engagement. | EPC AR record (EPC-reported) |
| Verification class | EPC-reported — statement of work on file; evidence record pending; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) | Evidence Center convention |
| Evidence record | evidence record pending (CC builds it from the document on file) | — |
| External source | none published yet | — |
| Project ID | EPC-2017-HASKELL-O365-P0 | EPC Group |
What the document states
EPC Group Statement of Work v2.0 (December 22, 2017): Office 365 Phase 0 Initiative (Implementation Strategy).
Starting environment (EPC-reported, first pass)
An engagement of this type begins with an organization's existing Office 365 tenant, workloads in use, identity and licensing, and the departments and applications an implementation strategy had to cover. The specific inventory for this engagement is held in EPC Group's project records and will replace this paragraph when published.
Business problem (EPC-reported, first pass)
The need for a phased implementation strategy before investing in platform work.
EPC Group's responsibility
A Phase 0 implementation-strategy initiative for Office 365, as the statement of work describes.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are workload sequencing, governance and identity prerequisites, and the roadmap for subsequent phases. The decisions actually taken for Haskell will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: discovery → strategy and roadmap → phase planning. Dates and acceptance for this engagement will be stated from the project record.
Results
| Metric | Baseline | Observed result | Period | Source | Verification class |
|---|---|---|---|---|---|
| Scope delivered against the instrument | as contracted | Completed; invoiced and paid in full | engagement period | EPC AR record (paid invoices on file; not published) | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Client acceptance | — | Deliverables accepted; EPC Group's objectives met | close-out | payment in full + EPC-reported | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Primary technical outcome (migration completeness, platform live, deliverable detail) | pending | pending project record | — | project record | pending |
| Service interruption during cutover (where applicable) | planned window | pending | cutover | cutover log | pending |
Completion, acceptance and payment are stated from EPC Group's records; the technical rows stay pending until the project record is published. No figure is invented.
Client perspective
The client accepted the deliverables and paid every invoice in full. No client quotation is published on this page; where a client has given a written statement or a review, it is linked from the evidence record.
Evidence and limitations
The source document is on file with EPC Group; CC builds the evidence record (redacted images, SHA-256, transcript) before this page leaves first-pass status. The instrument establishes the client, the supplier, the service and the date as stated above. It does not by itself establish delivery dates, volumes, acceptance or outcomes; those require the project records referenced in the Results table. Completion and payment in full are established by EPC Group's accounts-receivable record (paid invoices on file; not published because they carry commercial terms).
Lessons for similar organizations (EPC-reported)
- Phase 0 is where most of the cost is saved; do not skip it.
Related service
Microsoft 365 strategy and roadmap ·Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-15 · Substantively updated: 2026-10-15.