Final payment page

Confirm delivery, collect the balance, and close the sprint cleanly.

This page handles the part right after delivery: what counts as approval, when to ask for the remaining balance, how to frame light revisions, and when a request becomes new scope instead.

Open Balance Path Open Payment Page

1 approval step
1 balance request
1 scope boundary

Balance Path

Use the same sequence after delivery every time.

1. Summarize Delivery

Send the delivery proof pack or a short summary so the client can see exactly what changed before you ask for the remaining balance.

Open Delivery Proof Pack

2. Confirm Approval

Ask whether the agreed sprint assets look good or whether one light revision is needed inside the original boundary.

Open Client Recovery

3. Collect Remaining Balance

Once delivery is confirmed, send the payment route for the remaining balance and keep the next step simple.

Open Payment Page

Ready-To-Send Lines

Keep the balance ask calm and specific.

Standard Balance Ask

The agreed sprint assets are now delivered. If everything looks good, the next step is the remaining balance, then I will finalize the handoff package.

With Light Revision

If there is one light revision inside the original scope, send it now and I will tighten it before final handoff.

Short Version

Delivered and ready for approval. If it looks good, send the remaining balance and I will close out the sprint cleanly.

Scope Boundary

Do not let balance collection reopen the sprint.

Light Revision

Small tightening on copy, CTA wording, or structural clarity is a normal close-out step if it stays inside the original sprint.

New Scope

New flows, extra pages, or another bottleneck belong in a new sprint and should not block the current balance collection.

Open Renewal Board

Final Handoff

After balance and approval, hand over the final assets, notes, and owner-facing material in one clean package.

Open Handoff Board