1. Confirm The Cycle Type
Decide whether the next paid step is a new sprint or the first month of a recurring retainer. Do not mix the two.
Open Upsell RouterPost-win payment page
Once the next paid step is agreed, lock the next cycle cleanly.
This page is for the moment after a client accepts a second sprint or a first month of recurring work. The job now is not to re-sell the idea. The job is to confirm what this next payment covers, move the funds, collect the tx hash, and activate the next cycle.
- 2 main next-cycle shapes
- 1 payment route
- 1 activation handoff
Next Cycle Map
Use one sequence from next-step agreement to a funded new cycle.
2. Confirm What This Payment Covers
The buyer should know whether the payment is locking one new bottleneck sprint or one defined month of ongoing work.
Open Renewal Board Open Retainer Conversion3. Send The Next Payment
Use the same wallet route again once the scope is clear. A new paid cycle should have a new commercial signal.
Open Payment Page4. Remove Last-Minute Friction
If the payer needs another walkthrough or the transfer drifts, route to the shortest page that solves that exact problem.
Open Payment Guide Open Payment Follow-Up5. Activate The New Cycle
Once the hash is in, move directly into the new brief, kickoff, or monthly operating rhythm instead of leaving it half-open.
Open Kickoff BoardWhen To Use It
Use this page after the next paid step is already accepted.
Second Sprint Approved
Use it when the client wants the next bottleneck solved and the only remaining job is turning that yes into a new deposit.
First Retainer Month Approved
Use it when the client accepts a monthly rhythm and you need a clear first payment event to start the ongoing work properly.
Post-Win Momentum Is Still Warm
Use it while the previous result is still fresh so the next payment feels like a continuation of momentum, not a restart.
Best Next Routes
Match the remaining blocker to the shortest useful page.
Need New Sprint Scope
If the next work is a concentrated bottleneck, route back to the renewal page and tighten the new sprint boundary.
Open Renewal BoardNeed Monthly Scope
If the next work is ongoing support, route back to retainer conversion and package the first month properly.
Open Retainer ConversionNeed Payment Confidence
If the payer accepts the next cycle but needs wallet clarity, route to the payment guide before asking again.
Open Payment GuideNeed Payment Chase
If the payment should already be moving but timing drifts, use the follow-up page instead of rewriting the commercial logic.
Open Payment Follow-UpReady Now
If the next scope is approved and the payer is ready, move straight into the payment page and collect the new transfer.
Open Payment PageWallet
Preferred route: direct payment, tx hash, then new cycle activation.
Use the same wallet route for the next sprint deposit or first month retainer payment. Once funds land, send the hash and move directly into the next brief or operating rhythm.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page
Short Next-Cycle Lines
Use direct language that turns post-win demand into fresh payment.
New Cycle Line
Since the next scope is already clear, the cleanest move is to lock the next cycle with a fresh payment rather than let it drift.
Scope Line
This payment is for the next cycle only, whether that is a new sprint or the first month of ongoing work.
Activation Line
Once the transfer lands and the hash is in, I move it directly into the next brief, kickoff, or monthly rhythm.