Priority Change Cost Disclosure (Retention)

Priority Change Cost Disclosure (Retention)

1. 01

   Log the change request in the roadmap tool the same day the client raises it

   Capture the requester, the date, and the exact wording of the ask. A verbal request that never lands in the system cannot be priced later.

2. 02

   Classify the request as swap, addition, or acceleration before estimating anything

   A swap trades one committed item for another at roughly neutral cost. An addition consumes new capacity. Acceleration pulls work forward and usually carries a premium.

3. 03

   Quantify the displacement in sprint weeks, not in vague effort language

   State which committed items move and by how many weeks. ProdPad's Now-Next-Later framing makes this legible to non-technical stakeholders without a Gantt chart argument.

4. 04

   Attach a dollar or retainer-hour figure to each option you present

   Offer three paths: absorb the change inside the current retainer, extend scope at a stated rate, or defer to the next planning cycle. Clients negotiate faster against numbers than against principles.

5. 05

   Send the trade-off summary in writing within 24 hours of the request

   One page: what changes, what slips, what it costs. Productboard and airfocus both export roadmap views that can be attached as the visual appendix.

6. 06

   Require a written approval before any reprioritization takes effect

   A reply email confirming the chosen option is sufficient. This is the artifact that protects the agency when the client later questions why a feature slipped.

7. 07

   Update the shared roadmap and notify delivery leads the same day approval lands

   Stale roadmaps are the most common source of delivery disputes. If the client-facing view and the internal sprint board disagree for more than a day, the negotiation lever is gone.