What Every Strong Submission Includes
Regardless of opportunity type, a high-quality submission typically contains:- A link or attachment to your deliverable — the actual work product the client can review or download
- Notes on your approach — a brief explanation of the decisions you made and why, especially if the deliverable isn’t self-explanatory
- Any files the listing specifically requests — check the requirements section for formats, naming conventions, or supplementary materials
- Context on anything incomplete or in progress — for contract milestones, flag any blockers or questions before the client reviews
Submission Flows by Opportunity Type
- Contract
- Bounty
- Campaign
Contract work is broken into milestones. You submit once per milestone, not all at once at the end.
1
Complete the milestone deliverable
Work through the scope defined for this milestone. Refer back to the listing’s deliverables and milestone description to confirm you’ve met the requirements before submitting.
2
Open the milestone submission form
Navigate to your active contract and open the submission form for the current milestone.
3
Attach your work
Add a link or upload the files for this milestone. If your deliverable lives in an external tool (Figma, GitHub, Notion, etc.), paste a direct link with any necessary access permissions set.
4
Add your notes
Describe what you built or produced, any decisions you made, and anything the client should know before reviewing. Clear notes reduce back-and-forth and help the client approve faster.
5
Submit and wait for approval
Submit the milestone. The client reviews your work and either approves it — triggering the USDC payment for that milestone — or requests revisions.
Each milestone is reviewed independently. Don’t move on to the next milestone until the client has approved the current one, unless your contract specifies otherwise.
Common Submission Mistakes to Avoid
Submitting a broken or permission-blocked link
Submitting a broken or permission-blocked link
Always test your links before submitting. A Figma file set to “only me” or a private GitHub repo gives the client nothing to review. Set sharing permissions to allow the client to view or access the work.
Leaving out submission notes
Leaving out submission notes
Deliverables without context force the client to make assumptions. A few sentences explaining your approach, your choices, and any trade-offs you made can prevent revision requests and accelerate approval.
Submitting incomplete work for a bounty
Submitting incomplete work for a bounty
Bounty submissions must be complete at submission time. Unlike contracts, there’s no revision loop built into the bounty format. Submit only when your work is finished.
Missing required files or formats
Missing required files or formats
Check the listing’s requirements section for specific file types, naming conventions, or supplementary materials. Missing a required element can disqualify your submission.
