1. Scope Stays Narrow And Written
The standard engagement is one bottleneck, one sprint, and one visible delivery boundary. If the buyer wants a broader build, that should be re-scoped before payment.
Open Public Pricing Open Public Scope BoundaryPublic working terms
Review the public terms before payment moves, including the smaller-start route.
This page makes the default working rules visible before funds move: one agreed sprint scope, one deposit rule, one kickoff condition, one revision boundary, one rescheduling expectation, one public refund path, and one clear payment-confirmation path. If anything differs, write it explicitly before payment. If the buyer wants the same rules in a smaller written first commitment, use the teardown instead of forcing a full sprint too early. If the written need is ongoing support on a live asset, use the retainer and keep that monthly boundary explicit before payment too.
- 6 default working terms
- 30% standard deposit route
- 72h standard sprint framing
- 1 shared wallet route
Terms Map
Use one public page to make the working model visible before the transfer.
2. Deposit Follows Written Alignment
Standard route is a 30 percent deposit after the tier, scope, wallet, asset, and preferred network are written clearly enough that no one is guessing what the payment is for.
Open Public Approval Open Public Deposit Lock2B. Use Teardown If The Buyer Wants A Smaller Written First Commitment
The same written discipline applies to the teardown: one workflow, one visible boundary, one kickoff condition, and a fixed $299 total with a $90 deposit before work starts.
Open Public Teardown Open Payment Page2C. Use Retainer If The Written Need Is Ongoing Support
If the buyer is not buying one fresh sprint but a bounded monthly support lane, keep the same written discipline: one defined lane, one payment event, one review rhythm, and a visible boundary for what fits inside the month.
Open Public Retainer Open Public Renewal3. Kickoff Starts After Confirmation
Work starts after payment confirmation and receipt of the minimum kickoff packet: transaction hash, brief, and any relevant links.
Open Public Kickoff Open Public Payment Follow-Up4. Revisions Stay Inside Scope
Revisions are for tightening the agreed sprint assets. New deliverables, new workflows, or a new bottleneck become new scope instead of hidden expansion.
Open Public Scope Boundary Open Public FAQ5. Rescheduling Must Be Explicit Before Work Starts
Deposits reserve delivery capacity. If the start date or rule set needs to change, write that change before the booked sprint opens rather than assuming the original path still applies.
Open Public Deposit Lock Open Public Refund And Reschedule6. Sender Confirms Network And Asset
Confirm the exact asset and network before transfer. Using the wrong network or unsupported route can delay confirmation and create avoidable support friction.
Open Public Payment Guide Open Payment PageShort Lines
Keep the terms easy to forward and hard to misunderstand.
Scope Line
I keep the first sprint narrow on purpose so payment, delivery, and approval stay clear.
Revision Line
Revisions tighten the agreed sprint. If the job itself changes, that becomes new scope.
Reschedule Line
If timing changes, I want that written before the reserved sprint opens so the delivery path stays explicit.
Payment Line
I only want payment after the scope, network, and kickoff condition are written clearly enough to forward.
Smaller Start Line
If you want the same written terms in a smaller first commitment, the teardown keeps it simple: one workflow, $299 total, $90 deposit, and the same kickoff confirmation path.
Open Public TeardownRetainer Terms Line
If the real job is monthly support on something already live, I want the same written clarity there too: one bounded lane, one review rhythm, and one visible payment route.
Open Public RetainerWallet
Use the same wallet route once the written terms are aligned.
Public terms work best when the payment route is just as explicit as the scope: same address, same preferred network, and the same confirmation step into kickoff for the main sprint, the smaller teardown, or the first retainer month.