Use Teardown When The Buyer Wants A Smaller First Commitment
Choose teardown when the buyer wants a smaller paid move first,
needs the initial workflow to stay narrow, and does not want the
first transfer to carry full sprint scope.
Open Public Teardown
Open Public Buyer Checklist
Use Sprint When The Bottleneck Is Clear Enough To Buy Fresh Scope
Choose sprint when the buyer already knows the exact sales,
automation, or conversion bottleneck that needs a concentrated
build instead of a narrower diagnostic.
Open Public Pricing
Open Public Route Picker
Use Teardown First If The Buyer Wants Proof Before A Larger Deposit
If the buyer is open to paying but still wants proof before the
larger deposit, teardown is the cleaner path because it gives one
bounded paid result before a bigger ask.
Open Public Teardown
Open Public Payment Guide
Use Sprint When Delay Cost Is Already Bigger Than The Extra Deposit
If the revenue leak is already visible and waiting costs more
than the extra deposit gap, moving straight into the sprint is
usually more honest than pretending a smaller test is still needed.
Open Public Pricing
Open Public FAQ
Do Not Hide A Full Sprint Inside A Teardown
If the buyer keeps asking for a larger page, broader flow, or
multiple deliverables, do not force that work into the teardown.
Break it into a fresh sprint with a fresh deposit.
Open Public Scope Boundary
Open Public Pricing
Keep The Wallet Route Visible Either Way
Once teardown or sprint is fixed, keep the wallet, payment label,
and tx-hash handoff explicit in the same buyer thread.
Open Public Payment Guide
Open Payment Page