Anonymized engagement summary: Microsoft Teams as the organization-wide communications platform, with Teams Phone and about 1,000 numbers ported, for a construction company (2020–2021)
Contracted — countersigned, two phases (EPC-reported; documents private)First-pass editionA construction company (client not named) · 2020–2021 · Project ID EPC-2020-ANON-CONSTR-TEAMS
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. In November 2020 a construction company countersigned a statement of work with EPC Group to make Microsoft Teams its organization-wide unified communications platform. The scope included a Teams Phone solution: porting about 1,000 existing numbers from the current provider, keeping existing numbers and obtaining new number blocks, and adding voice capabilities and integrations matched to the company's requirements. In April 2021 the company's CTO and CISO countersigned a second phase. It added time for the same rollout and an assessment of Teams telephony usage to confirm the right licensing.
Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The countersigned statements of work are retained privately and are not published in the Evidence Center, so this account is outside the Evidence Center's documented-engagement counts. Every engagement fact below is taken from those documents.
Verification class
Contracted — countersigned, two phases (EPC-reported; documents private). An IT leader at the company signed the first statement of work in November 2020. The CTO and CISO signed the second-phase statement of work in April 2021. No cut-over record, ported-number count after delivery, or outcome measurement is cited or claimed.
Buyer problem and scope
| Item | What the statements of work state |
|---|---|
| Buyer | A construction company (client not named) |
| Objective | Microsoft Teams as the core unified communications platform across the organization, for communication, collaboration and telephony |
| Telephony | A Teams Phone solution; about 1,000 existing numbers ported from the current provider; existing numbers kept and new blocks obtained; voice capabilities aligned with existing requirements, plus further capabilities, integrations and customizations |
| Second phase (April 2021) | More time for the same Teams and telephony rollout; an assessment of Teams telephony usage to confirm proper licensing and costs |
| Enablement | Comprehensive Teams training and knowledge transfer for end users |
| Delivery | Short delivery cycles that each ship a working piece |
Unknowns, not stated in the documents cited: user and site counts, the rollout dates and any measured result.
Approach and artifacts
Plan the numbers. Porting about 1,000 numbers while keeping existing ones and adding new blocks is planned as its own workstream within the Teams rollout.
Match licensing to use. The second phase adds a review of how Teams telephony is actually used, so licensing matches real usage.
Train the whole organization. End-user training on Teams features and practices runs alongside the rollout.
Documents (held privately):
| Document | Date |
|---|---|
| Statement of work, Microsoft Teams consulting and implementation (countersigned) | November 2020 |
| Statement of work, phase 2 (countersigned by the CTO and CISO) | April 2021 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| The company contracted EPC Group for an organization-wide Teams and Teams Phone rollout, then extended it | Countersigned statements of work, November 2020 and April 2021 | Contracted (EPC-reported; documents private) |
| Numbers ported, rollout completed, or measured results | No document cited | Not claimed |
Provenance
- Sources: the countersigned statements of work (November 2020 and April 2021), held privately. Engagement ID: EPC-2020-ANON-CONSTR-TEAMS, an alias unrelated to the client's name.
- Anonymization: industry only, under EPC Group's anonymized-case rule; the company's name, locations, carrier, staff names and commercial terms are not published.
- Not claimed: client endorsement, completion, or any measured result.
- Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group, who signed the statements of work for EPC Group.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's countersigned statements of work.
Related service
Microsoft Teams consulting · Microsoft Teams Phone guide · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.