PepsiCo, Inc. — MyPepsiCo intranet custom master page and branding initiative (2009)
EPC-executed instrument + work productFirst-pass editionPepsiCo, Inc. · 2009 · Project ID EPC-2009-PEPSICO-SP
Evidence record: PepsiCo, Inc. evidence record with redacted documents and SHA-256 hashes
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
EPC-executed instrument + work product. PepsiCo, Inc. engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for MyPepsiCo intranet custom master page and branding initiative — EPC-executed statement of work EPC-50490; countersigned copy not published. Project ID EPC-2009-PEPSICO-SP. 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 2009, EPC Group completed MyPepsiCo intranet custom master page and branding initiative for PepsiCo, Inc. on SharePoint Server, led by EPC Group's senior architects addressing an intranet whose look, navigation and templates had to match the corporate brand and scale across business units. 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-executed instrument + work product; 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 | PepsiCo, Inc. | document |
| Industry | Consumer packaged goods | document / public record |
| Engagement date | 2009 | document |
| Work | MyPepsiCo intranet custom master page and branding initiative (Statement of Work EPC-50490) | document |
| Microsoft products | SharePoint Server | document / scope |
| Scope unit | EPC-executed statement of work EPC-50490; countersigned copy not published | document |
| EPC Group role | Consulting and delivery under the instrument named above | document |
| Lead architect | EPC Group senior architects (the published instrument does not name the lead; EPC-reported) | EPC-reported |
| 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-executed instrument + work product; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) | Evidence Center convention |
| Evidence record | https://www.epcgroup.net/evidence/pepsico-sharepoint-branding-2009 | — |
| External source | none published yet | — |
| Project ID | EPC-2009-PEPSICO-SP | EPC Group |
What the document states
Statement of Work EPC-50490 (custom master page initiative) executed by EPC Group, plus MyPepsiCo intranet design work product (2009). The record is deliberately marked below Contracted because the copy held is not countersigned. EPC Group also reports later Office 365 initiatives for PepsiCo (EPC-reported; instrument not published).
Starting environment (EPC-reported, first pass)
An engagement of this type begins with a global consumer-products intranet (MyPepsiCo) on SharePoint, its master page and branding standards, and the organization's design guidelines. 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)
An intranet whose look, navigation and templates had to match the corporate brand and scale across business units.
EPC Group's responsibility
A custom master page initiative and intranet design work for the MyPepsiCo intranet, under an EPC Group statement of work.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are master page and page-layout architecture, branding implementation approach, and how templates propagate across sites. The decisions actually taken for PepsiCo will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: design → master page and layouts → templates → rollout guidance. 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 evidence record at https://www.epcgroup.net/evidence/pepsico-sharepoint-branding-2009 publishes the document(s) with redacted page images and SHA-256 hashes. 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)
- Branding on SharePoint is an architecture decision; build it once at the master-page layer.
- Templates are what make an intranet scale.
Related service
SharePoint intranet design and branding ·Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-15 · Substantively updated: 2026-10-15.