Product Execution Submission Guide
How to submit your product information for Product Execution scoring.
What You Need
Before starting, gather the following:
| Item | Required | Notes |
|---|---|---|
| Live product URL | Yes | MainNet preferred |
| GitHub organization URL | Yes | For verification and metrics |
| Security audit report | Recommended | For audited protocols |
| Documentation link | Recommended | Developer docs, user guides |
| Case studies | Recommended | Customer stories, testimonials |
| Market research | Recommended | TAM/SAM data, industry reports |
Submission Process
Step 1: Access Power Signals
From the project submission flow, navigate to Step 2: Power Signals.
Step 2: Select Product Execution
Click on "Product Execution" to expand the section.
Step 3: Core Product Information
Provide details for each core signal:
Launched Product & Usage Quality:
- Product status (TestNet/MainNet/MainNet-audited)
- Live product URL
- Audit report link (if applicable)
- Documentation URL
Problem-Solution Fit:
- Customer case studies
- Customer quotes or testimonials
- Partnership announcements
- User-generated content showing usage
Market Size & Tailwind:
- Market category definition
- TAM/SAM estimates with sources
- Market research reports
- Growth trends and data
Positioning Within Category:
- Category name and competitors
- Ecosystem listings (Ethereum.org, DeFiLlama, etc.)
- Industry report mentions
- Competitive position data
Step 4: GitHub Information
Provide your GitHub details:
- Organization URL
- Owner/admin verification
- Primary repositories
The following will be automatically calculated:
- Commit frequency
- Active contributors
- Release cadence
- Repo stars
- Used by (dependents)
Step 5: Review and Continue
Verify all information is correct and click "Continue".
Tips for Higher Scores
For Launched Product & Usage Quality
Deploy to MainNet:
- Move beyond TestNet as soon as viable
- Document deployment process
- Ensure stability before launch
Get Audited:
- Use reputable auditing firms
- Make reports public
- Address all critical findings
Build Great Docs:
- Comprehensive developer documentation
- Clear getting started guides
- API reference and examples
- Architecture overviews
For Problem-Solution Fit
Build Case Studies:
- Get customer permission to publish names
- Document specific problems solved
- Quantify results when possible
- Update regularly
Collect Testimonials:
- Ask satisfied customers for quotes
- Include attribution (name, title, company)
- Share across channels
Highlight Partnerships:
- Announce integrations
- Co-create with design partners
- Document collaborative workflows
For Market Size & Tailwind
Use Credible Sources:
- Third-party market research
- On-chain data platforms
- VC firm reports
- Academic research
Be Specific:
- Define your precise market segment
- Dont claim entire "crypto market"
- Show realistic penetration
Document Growth:
- Historical growth rates
- Future projections
- Supporting tailwinds
For Positioning Within Category
Build Ecosystem Presence:
- Get listed on official ecosystem pages
- Submit to DeFiLlama and directories
- Engage with ecosystem teams
Establish Position:
- Use objective data (TVL, users, volume)
- Compare to direct competitors
- Track your ranking
Generate Awareness:
- Speak at conferences
- Publish thought leadership
- Brief analysts and researchers
For GitHub Signals
Commit Regularly:
- Develop in public
- Commit frequently
- Use clear commit messages
Build Your Team:
- Multiple active contributors score higher
- Welcome external contributions
- Distribute work
Release Consistently:
- Adopt semantic versioning
- Create release notes
- Ship regularly
Build Community:
- Create valuable open source tools
- Promote your work
- Engage with developers
Enable Dependencies:
- Build reusable libraries
- Publish packages
- Make integration easy
After Submission
- Your submission is reviewed by Thrive's Guardian network
- Guardians verify all claims and evidence
- GitHub metrics are automatically updated regularly
- Scores are assigned based on verified information
- You can update your submission as your product evolves
Common Issues
Product not accessible:
- Ensure URLs are publicly accessible
- Provide demo credentials if needed
- Test links before submitting
GitHub org not verified:
- Add verified team member as owner/admin
- Link GitHub username to LinkedIn
- Ensure organization is public
No customer evidence:
- Even early-stage projects should have design partners
- Beta users count
- Document any user feedback
Market data unclear:
- Use specific, sourced numbers
- Avoid vague claims
- Cite reputable research
Category positioning weak:
- Apply to ecosystem directories
- Define category clearly
- Identify direct competitors
GitHub metrics low:
- Focus on consistent development
- Build in public when possible
- Document workflow if private
Need Help?
If you encounter issues during submission:
- Review individual signal pages for detailed guidance
- Check methodology pages to understand scoring
- Contact Thrive support for technical assistance
- Join the Thrive Discord for community help
Related Pages
Core Product Signals
- Launched Product & Usage Quality
- Problem-Solution Fit Evidence
- Market Size & Tailwind
- Positioning Within Category