Route decision page

Choose the next paid lane honestly: fresh sprint or bounded retainer.

This page is for the buyer who agrees something should happen but is still unclear about the shape of the next paid move. Use a sprint when the next bottleneck is new, concentrated, and needs a defined push. Use a retainer when the work is recurring, bounded, and mainly about upkeep, iteration, or monthly optimization. Once the lane is chosen, use next cycle lock to keep the second payment narrow instead of reopening the whole commercial thread.

Open Route Checks Open Public Next Cycle Lock Open Public Pricing Open Public Retainer

1 new bottleneck per sprint
1 bounded lane per retainer
0 hidden scope swaps
1 shared wallet route

1. Name The Next Need Is it a new bottleneck or recurring upkeep on something already live? Open Public Buyer Checklist

2. Pick The Honest Package Shape Use sprint for a new push, retainer for bounded ongoing work. Open Public Retainer

3. Keep Payment Visible Once the lane is clear, lock the next cycle first, then move into the matching payment path without reopening the whole thread. Open Public Next Cycle Lock Open Payment Page

Route Checks

Use these checks to pick the correct lane.

Use A Sprint When The Bottleneck Is New

If the next problem is a fresh sales, automation, or conversion bottleneck that needs one concentrated delivery push, sell a sprint, not a retainer.

Open Public Pricing Open Public Renewal

Use A Retainer When The Asset Is Already Live

If the work is monthly optimization, bounded support, monitoring, or upkeep on something already shipped, a retainer is the cleaner route.

Open Public Retainer

Use Next Cycle Lock Once The Lane Is Chosen

If the buyer already accepts one more sprint or the first retainer month, use next cycle lock to keep the next payment event clean, labeled, and easy to execute.

Open Public Next Cycle Lock Open Public Renewal Open Public Retainer

Do Not Use Retainer To Hide New Scope

If the buyer keeps adding a new larger bottleneck, break it out into a new sprint instead of quietly stretching the recurring lane.

Open Public Scope Boundary Open Public Renewal

Do Not Use Sprint For Small Recurring Tasks

If the work is mostly recurring and bounded, a new sprint can feel heavier than the need. Use the retainer lane instead.

Open Public Retainer

Use Teardown If The Buyer Still Needs A Smaller First Paid Move

If the buyer agrees on the direction but still wants a tiny first step before a bigger sprint or retainer, use teardown to keep momentum.

Open Public Teardown

Keep Payment Explicit Either Way

Once the lane is chosen, the next move should be payment through the same visible wallet, then tx hash back in the thread.

Open Payment Page Open Public Payment Guide

Short Lines

Use direct language that keeps the package shape honest.

Sprint Line

This looks like one new concentrated bottleneck, so the cleaner route is a sprint rather than a recurring lane.

Retainer Line

This looks like bounded ongoing upkeep on something already live, so the cleaner route is a retainer rather than another fresh sprint.

Boundary Line

I do not want to hide new scope inside a retainer or stretch a retainer into a new sprint. The package shape should match the work.

Wallet

Once the lane is clear, keep the payment path simple.

The same wallet can take a sprint deposit, a teardown deposit, or the first retainer month. What changes is the package shape, not the visible payment route.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Public Pricing Open Public Teardown Open Public Retainer Open Public Renewal Open Public Next Cycle Lock Open Public Payment Guide Open Payment Page