Shareable pricing page

Send one public pricing page instead of rewriting packages in every buyer thread.

This page is the clean public pricing route: three fixed packages, standard deposits, the same wallet, and the same next step into payment confirmation. The entry package can also travel as a smaller paid first step for buyers who want to start with a teardown. If the buyer is specifically choosing between that smaller start and the fuller sprint deposit, use the teardown vs sprint page before you keep defending the quote. If the quote feels right but timing keeps sliding into later, next month, or "not urgent yet," use why now before you widen the pricing thread again. If the buyer likes the quote but still wants a safer, more controlled buying frame, use risk control before you keep defending price or scope. If the buyer is not rejecting the quote but still says they need to think without naming the blocker, use the buyer checklist first and compress the hesitation into one real decision. If the tier is already chosen but the transfer label or chain route is still fuzzy, use payment type and network check before funds move. If the quote is accepted but the transfer still has not landed, use approval to payment first. If the transfer still drifts after that, use payment follow-up. If the transfer is already sent, use tx hash to close confirmation without another explanation loop. If the sprint is already delivered and the only money left is the remaining balance, use balance collection instead of rewriting the close-out. If the finished sprint clearly points to a new paid bottleneck, use renewal before you reopen the quote thread. If the buyer is already thinking about monthly upkeep after launch, this same route can branch into the public retainer lane. If the first sprint already worked and the buyer accepts a second paid cycle, use next cycle lock before you reopen the whole quote thread.

See Packages Open Public Why Now Open Public Risk Control Open Public Buyer Checklist Open Public Teardown Vs Sprint Open Public Next Cycle Lock Open Public Approval To Payment Open Public Payment Type Open Public Payment Follow-Up Open Public Tx Hash Open Public Balance Collection Open Public Renewal Open Public Retainer Open Payment Page

4 fixed package choices
30% standard deposit framing
72h standard sprint window
USDC preferred stable settlement

1. Pick The Tier Choose the narrowest package that solves one visible bottleneck. If the buyer wants the decision to feel safer, use risk control. If the buyer says “later” without denying the fit, use why now. If the buyer still says "let me think" without naming the blocker, use buyer checklist before defending the tier again. Open Public Risk Control Open Public Why Now Open Public Buyer Checklist

2. Send Deposit Use the listed deposit, ideally in USDC on Base, and compress accepted quotes into one payment event. Open Public Approval To Payment Open Public Payment Type Open Payment Page

3. Close The Transfer Cleanly If the transfer stalls, use follow-up. If it is already sent, collect the tx hash, project name, and brief in the same thread. Open Public Payment Follow-Up Open Public Tx Hash Open Public Kickoff

4. After Delivery, Collect Balance Or Scope Renewal When the sprint is done, use balance collection for remaining payment and renewal for the next paid bottleneck. Open Public Balance Collection Open Public Renewal

Public Pricing

Keep the numbers fixed so approval and payment stay easy to forward.

Entry

$299

$90 deposit

single workflow teardown
light offer page polish
one revision

Open Public Teardown Open Public Teardown Vs Sprint Open Public Payment Type Open Payment Page

Best Start

$799

$240 deposit

sales page + outreach kit
ROI framing
delivery SOP

Open Public Teardown Vs Sprint Open Public Payment Type Open Payment Page

Premium

$1,500

$450 deposit

full sprint setup
handoff docs
post-delivery optimization

Open Public Payment Type Open Payment Page

Recurring

$600 / month

$300 first month

monthly optimization
async support
iteration queue

Open Public Retainer Open Public Next Cycle Lock Open Public Payment Type Open Payment Page

Usage

Use pricing after trust is established, not before the buyer understands the job.

Send This When The Buyer Wants Numbers

Use this page after the buyer accepts the basic problem and now needs fixed package numbers rather than more abstract proof.

Open Public Trust Open Public Proof Open Public ROI Open Public Links Hub

Use Teardown When The Buyer Wants A Smaller Paid Start

If the full sprint feels too large for the current thread, use the entry package as a narrower paid first step before you push a bigger scope or quote.

Open Public Teardown Open Public Teardown Vs Sprint Open Public Scope Boundary Open Payment Page

Use Teardown Vs Sprint When Deposit Size Is The Real Decision

If the buyer is not arguing about value but is still choosing between a smaller proof-first deposit and the fuller sprint deposit, compare those two package shapes directly.

Open Public Teardown Vs Sprint Open Public Route Picker Open Public Buyer Checklist

Use Payment Type When The Transfer Label Is Still Fuzzy

If the buyer accepts the tier but still needs to confirm whether the transfer is a teardown deposit, sprint deposit, balance, or first retainer month, label the payment before funds move.

Open Public Payment Type Open Payment Page

Use Network Check When Wallet Friction Is The Last Blocker

If the quote is already accepted and the only remaining friction is asset, network, or wallet confirmation, use the network check page instead of rewriting transfer instructions in chat.

Open Public Network Check Open Public Payment Guide

Use Payment Follow-Up When The Quote Is Accepted But The Transfer Still Has Not Landed

If the package is agreed and the deal is warm but the transfer is dragging, use payment follow-up to keep the thread on payer, wallet, amount, and one clear next action only.

Open Public Payment Follow-Up Open Payment Page

Use Tx Hash When The Transfer Is Already Sent And You Only Need Confirmation

If the payment is already on-chain, stop explaining the wallet and only collect the tx hash, payment type, and project label.

Open Public Tx Hash Open Public Kickoff

Use Next Cycle Lock When The Current Sprint Already Earned The Next Yes

If the first sprint already worked and the buyer now accepts one more sprint or the first retainer month, use next cycle lock to keep the second payment event narrow and operational.

Open Public Next Cycle Lock Open Public Renewal Open Public Retainer

Use ROI When The Buyer Questions Value

If the package price is clear but the buyer still asks whether it is commercially worth it, route them through the ROI page first.

Open Public Comparison Open Public ROI Open Public Proof

Use Comparison When They Compare Categories

If the buyer is not resisting the price itself but keeps comparing agencies, freelancers, or internal build paths, show the fit difference before you keep negotiating the tier.

Open Public Comparison Open Public Proof

Use FAQ For Timing Or Payment Friction

If the buyer still asks about timing or payment mechanics, send the FAQ instead of expanding the quote thread.

Open Public FAQ

Use Scope Boundary For Hidden-Extra Anxiety

If the buyer accepts the price but fears scope creep, make the boundary explicit before you keep negotiating the package.

Open Public Scope Boundary Open Public FAQ

Use Risk Control When The Price Is Not The Real Problem

If the buyer accepts the numbers but wants a safer, more controlled decision, route risk before you defend the tier again.

Open Public Risk Control Open Public Scope Boundary

Use Approval Before Deposit

When the tier is confirmed but the buyer still needs a final operational step, move into the approval page first.

Open Public Approval

Use Async Close When Scheduling Is The Only Friction

If the buyer wants everything in writing and a call would only delay the payment path, keep the whole close thread async.

Open Public Async Close Open Public Approval

Use Deposit Lock When Timing Matters

If the buyer wants the current sprint window, switch from vague timing into a clean deposit-lock step before kickoff.

Open Public Deposit Lock

Use Retainer When The Build Already Exists

If the buyer is not deciding on first delivery anymore and actually needs monthly optimization, maintenance, or ongoing support, route to the retainer page instead of reopening sprint scope.

Open Public Retainer Open Public Renewal

Payment route

Use the same wallet across pricing, FAQ, and payment pages.

Consistency matters more than extra explanation. Keep the wallet, network preference, and confirmation step identical everywhere the buyer can see.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Public Trust Open Public Proof Open Public Comparison Open Public ROI Open Public Why Now Open Public Risk Control Open Public Scope Boundary Open Public Approval Open Public Approval To Payment Open Public Async Close Open Public Deposit Lock Open Public Teardown Vs Sprint Open Public Payment Type Open Public Network Check Open Public Payment Follow-Up Open Public Tx Hash Open Public Balance Collection Open Public Renewal Open Public Retainer Open Public Next Cycle Lock Open Public Kickoff Open Payment Page Open Public Teardown Open Public FAQ Open Public Links Hub