Contracted — countersigned (EPC-reported; documents private)First-pass editionAn investment management firm (client not named) · 2020 · Project ID EPC-2020-ANON-AM-TEAMS

Last updated October 25, 2026 by Errin O'Connor, Founder & Chief AI Architect, EPC Group

Opening answer. In August 2020 an investment management firm's CFO executed a statement of work with EPC Group to make fuller use of Microsoft Teams as its organization-wide communications platform. The scope:

one consistent Teams platform for each of the firm's three investment teams, built on best practice
a publishing process within Teams
best practices for where files and chats are stored
proper security and recovery features
a business assessment of stakeholders, champions, user profiles, departments and offices
end-user training

Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The executed statement of work is retained privately and is 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 that document.

Verification class

Contracted — countersigned (EPC-reported; documents private). The firm's CFO signed the statement of work in August 2020. No rollout record, acceptance or outcome measurement is cited or claimed.

Buyer problem and scope

Item	What the statement of work states
Buyer	An investment management firm (client not named); signed by its CFO
Situation	Microsoft Teams in use, which the firm wanted to make fuller use of as its organization-wide platform
Design	Teams for communication and collaboration across the firm; a similar platform for each of three investment teams, kept to best practice
Process	A publishing process implemented within Teams
Storage and protection	Best practice for file and chat storage; security and recovery features
Assessment	Stakeholders, champions, user profiles, departments and office locations, with needs gathered at organizational and user level
Enablement	Comprehensive Teams training on features, functions and best practice, led by EPC Group's unified-communications architects with the founder

Unknowns, not stated in the document cited: user counts, the content published, the rollout date and any measured result.

Approach and artifacts

Same pattern for every team. Each investment team gets a similar Teams structure built on the same practices.

Publishing inside the workspace. A publishing process is built into Teams itself.

Protect what the firm stores. File and chat storage practices are set alongside security and recovery features.

Document (held privately):

Document	Date
Statement of work, Microsoft Teams consulting and implementation (executed by the CFO)	August 2020

Results and limitations

Claim	Basis	Status
The firm contracted EPC Group for a consistent Teams design across three investment teams with publishing and recovery practices	Executed statement of work, August 2020	Contracted (EPC-reported; documents private)
Rollout completed, adopted, or measured results	No document cited	Not claimed

Provenance

Source: the executed statement of work (August 2020), held privately. Engagement ID: EPC-2020-ANON-AM-TEAMS, an alias unrelated to the client's name.
Anonymization: industry only, under EPC Group's anonymized-case rule; the firm's name, strategies, office locations, 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 statement of work for EPC Group.

Revision history

2026-10-25: anonymized engagement summary published from the engagement's executed statement of work.

Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.

Anonymized engagement summary: a consistent Microsoft Teams design for three investment teams, with a publishing process and storage and recovery practices, for an investment management firm (2020)