Scope Creep Resolution — 2026-04-01

Overview

During the weekly sync on 2026-04-01, Mark and Melissa identified that the Agility Recovery project has significantly exceeded its original scope. Excessive revision cycles and out-of-scope creative work have consumed the budget. The decision was made to formally notify the client that the original scope is complete and that any further work requires a new agreement.

Background

The original proposal defined a fixed set of modules to be built with an expected one-to-two revision cycles each. In practice, the client submitted revisions repeatedly — described as "800 times" — and the team performed additional creative work (including Loom video walkthroughs) that was not anticipated in the original scope. The project is now over-budget on time and effort despite some modules technically remaining unfinished.

Key Decision

"The original scope — we're done. If you want us to keep going, we're going to need another agreement."
— Mark Hope

The team agreed that the original contractual obligations have been met when accounting for the volume of additional work performed throughout the engagement. Completing the remaining modules under the current agreement is not viable.

Action Items

[ ] Mark Hope — Contact Gus (Agility client contact) to communicate that the original scope is fulfilled and a new agreement is required for any further work
[ ] Melissa Cusumano / Evoke — Attend the Friday meeting with Agility prepared to present the scope-complete position and discuss a new engagement if the client wishes to continue

Notes

Agility is a well-funded company; the expectation is that the client contact (Gus) can escalate internally to secure additional budget without significant friction
The Friday standing meeting is the planned venue for delivering this message
Evoke has been looped in to assist Melissa on this account going forward

^[1] — Source meeting where this decision was made
^[2] — Agility Recovery client overview