SCOPE & TIMELINE PROPOSAL

Proposed Phase 1 SOW, and the 3-Month Pilot built on it

A revised, role-by-role Phase 1 definition — reconciling the Nov 2025 SOW, the prototype, and CPGS's own questionnaire answers — plus a concrete counter-proposal to the chief's 3-month expectation built on that baseline.

Client

CPGS (Clean & Protect Global Solutions)

Requested by

Gerald Washington, CEO

Constraint

3 months, fixed

Status

Draft — not yet committed

◐ All effort and week figures below are illustrative, meant to anchor a conversation — not a committed estimate or contractual timeline. Actual duration depends on team size, the open questions below, and what the chief's deadline is actually driving toward.

Proposed Phase 1 scope of work

What Phase 1 actually means now, role by role — reconciling the Nov 2025 SOW, the prototype, and CPGS's own Pre-Work Questionnaire answers.

Reconciled role model

Role	Who	Platform	Primary purpose

Core functional scope, by role

Cross-cutting requirements

Explicitly deferred beyond Phase 1

Item	Why deferred	Target

Pilot vs. full delivery

Given the scope above, switch between the two delivery paths under discussion.

Dimension-by-dimension comparison

What actually changes between committing to the full SOW vs. carving out a pilot.

Illustrative timeline

Relative scale only — no calendar dates implied.

3-Month Pilot

WEEKS 1–12

Wk 2

Kickoff & setup

Wk 6

Internal test

Wk 10

Client demo

Wk 12

Handoff

Full SOW Phase 1

MILESTONES 1 → 2 → 3DURATION TBD

The SOW itself defines 3 milestones per platform (web + mobile) but states no fixed duration — that absence is itself a signal the original scope was never estimated against a hard deadline.

Open questions blocking a firm estimate

Each of these changes the size of the build — worth resolving with the client before quoting any number, pilot or full.