BRÈCHE
Crypto-paid project planning worksheet
Guide: /guides/hire-developer-with-crypto
Updated: 2026-09-25

Prepare the scope, payment questions and private delivery requirements before agreeing a build. This is a planning aid, not a quote, contract or payment instruction.
Fill this in locally. Nothing is sent to BRÈCHE.
Do not include passwords, API keys, wallet recovery phrases or private customer data.

1. Product and first release
Describe the website, app or integration, its users and one complete flow. Separate development requirements from how you will pay for the work.
Your notes:


2. Acceptance and review
Define the first milestone, its deliverables and observable acceptance checks. Include one failure case and the person who will review the work.
Your notes:


3. Asset and network
Record the proposed crypto asset and network as decisions to confirm in the proposal. Do not paste wallet addresses, private keys or recovery phrases here.
Your notes:


4. Amount basis and validity
What currency or asset defines the price? Record the amount calculation, any conversion reference and the payment window to agree. Leave unknowns open.
Your notes:


5. Payment stages and receipt
Map each payment to an agreed stage. Identify fee responsibilities, receipt confirmation and the person to contact about an unmatched payment.
Your notes:


6. Private delivery
Record who may access the brief, source and review environment. BRÈCHE never shares client projects as references, including anonymised case studies. Separate this rule from the client's own release plans.
Your notes:


7. Source and operation
List the source, account access and setup instructions required at handover. Identify third-party licences, subscriptions and ongoing responsibilities.
Your notes:


8. Changes and cancellation
Record how scope changes, missed dependencies or cancellation will be handled in the agreement. Identify unresolved decisions before approving work or payment.
Your notes: