<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2>&nbsp;</h2>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What Is The goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<p>1. The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</p>
<p>2. There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</p>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. <br /><br /><strong>Here&rsquo;s why OpenQ is crucial for the Polkadot community:</strong></p>
<p><strong>1. Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
<p><strong>2. Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.<br /><br /><strong>3. Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
<h2>&nbsp;</h2>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2>&nbsp;</h2>
<h2 id="ourobjectives">Our Objectives</h2>
<p><strong>1. Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.<br /><br /><strong>2. Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.<br /><br /><strong>3. GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
<p><strong>4. User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
<p><strong>5. Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
<h3>&nbsp;</h3>
<h2 id="stakeholders">Working With Stakeholders</h2>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.<br /><br /></p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h2>&nbsp;</h2>
<h2 id="technicaldetailsofourplatform">Technical Details of Our Platform</h2>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2>&nbsp;</h2>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>Continue refining marketing goals and strategies through iterative assessments.<br /><br /></li>
<li>Key questions include:<br /><br />Did teams improve their outcomes? Are there events or strategies that consistently underperform?<br /><br />Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</li>
<li><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement. <br />Due to significant fragmentation, we need to allocate more resources to ensure adequate support.<strong><br /></strong></li>
<li><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</li>
<li><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience"><br />Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet"><br />What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture"><br />How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm"><br />How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3>&nbsp;</h3>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2>&nbsp;</h2>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What Is The goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<p>1. The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</p>
<p>2. There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</p>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. <br /><br /><strong>Here&rsquo;s why OpenQ is crucial for the Polkadot community:</strong></p>
<p><strong>1. Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
<p><strong>2. Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.<br /><br /><strong>3. Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
<h2>&nbsp;</h2>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2>&nbsp;</h2>
<h2 id="ourobjectives">Our Objectives</h2>
<p><strong>1. Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.<br /><br /><strong>2. Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.<br /><br /><strong>3. GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
<p><strong>4. User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
<p><strong>5. Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
<h3>&nbsp;</h3>
<h2 id="stakeholders">Working With Stakeholders</h2>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.<br /><br /></p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h2>&nbsp;</h2>
<h2 id="technicaldetailsofourplatform">Technical Details of Our Platform</h2>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2>&nbsp;</h2>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>Continue refining marketing goals and strategies through iterative assessments.<br /><br /></li>
<li>Key questions include:<br /><br />Did teams improve their outcomes? Are there events or strategies that consistently underperform?<br /><br />Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</li>
<li><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement. <br />Due to significant fragmentation, we need to allocate more resources to ensure adequate support.<strong><br /></strong></li>
<li><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</li>
<li><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience"><br />Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet"><br />What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture"><br />How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm"><br />How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3 id="whataretheteamslongtermplansandintentions"><br />What are the team's long-term plans and intentions?</h3>
<p>To integrate our platform with every dev tooling company, ensuring self-sustainability and reducing reliance on grants or single organizations.</p>
<h3>&nbsp;</h3>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

Tracking ROI for Developer Marketing and Relations in the Polkadot Ecosystem

<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2>&nbsp;</h2>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What Is The goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<p>1. The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</p>
<p>2. There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</p>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. <br /><br /><strong>Here&rsquo;s why OpenQ is crucial for the Polkadot community:</strong></p>
<p><strong>1. Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
<p><strong>2. Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.<br /><br /><strong>3. Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
<h2>&nbsp;</h2>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2>&nbsp;</h2>
<h2 id="ourobjectives">Our Objectives</h2>
<p><strong>1. Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.<br /><br /><strong>2. Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.<br /><br /><strong>3. GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
<p><strong>4. User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
<p><strong>5. Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
<h3>&nbsp;</h3>
<h2 id="stakeholders">Working With Stakeholders</h2>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.<br /><br /></p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h2>&nbsp;</h2>
<h2 id="technicaldetailsofourplatform">Technical Details of Our Platform</h2>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2>&nbsp;</h2>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>Continue refining marketing goals and strategies through iterative assessments.<br /><br /></li>
<li>Key questions include:<br /><br />Did teams improve their outcomes? Are there events or strategies that consistently underperform?<br /><br />Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</li>
<li><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement. <br />Due to significant fragmentation, we need to allocate more resources to ensure adequate support.<strong><br /></strong></li>
<li><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</li>
<li><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience">Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet">What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture">How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm">How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3 id="whataretheteamslongtermplansandintentions">What are the team's long-term plans and intentions?</h3>
<p>To integrate our platform with every dev tooling company, ensuring self-sustainability and reducing reliance on grants or single organizations.</p>
<h3>&nbsp;</h3>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2>&nbsp;</h2>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What Is The goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<p>1. The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</p>
<p>2. There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</p>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. <br /><br /><strong>Here&rsquo;s why OpenQ is crucial for the Polkadot community:</strong></p>
<p><strong>1. Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
<p><strong>2. Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.<br /><br /><strong>3. Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
<h2>&nbsp;</h2>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2>&nbsp;</h2>
<h2 id="ourobjectives">Our Objectives</h2>
<p><strong>1. Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.<br /><br /><strong>2. Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.<br /><br /><strong>3. GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
<p><strong>4. User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
<p><strong>5. Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
<h3>&nbsp;</h3>
<h2 id="stakeholders">Working With Stakeholders</h2>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.</p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h2>&nbsp;</h2>
<h2 id="technicaldetailsofourplatform">Technical Details of Our Platform</h2>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2>&nbsp;</h2>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>
<p>Continue refining marketing goals and strategies through iterative assessments.</p>
<p>Key questions include:</p>
<p>Did teams improve their outcomes? Are there events or strategies that consistently underperform?</p>
<p>Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</p>
</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</li>
<li><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement. <br />Due to significant fragmentation, we need to allocate more resources to ensure adequate support.<strong><br /></strong></li>
<li><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</li>
<li><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</li>
</ul>
<h2>&nbsp;</h2>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience">Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet">What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture">How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm">How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3 id="whataretheteamslongtermplansandintentions">What are the team's long-term plans and intentions?</h3>
<p>To integrate our platform with every dev tooling company, ensuring self-sustainability and reducing reliance on grants or single organizations.</p>
<h3>&nbsp;</h3>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What Is The goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<p>1. The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</p>
<p>2. There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</p>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. <br /><br /><strong>Here&rsquo;s why OpenQ is crucial for the Polkadot community:</strong></p>
<p><strong>1. Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
<p><strong>2. Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.<br /><br /><strong>3. Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2 id="ourobjectives">Our Objectives</h2>
<p><strong>1. Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.<br /><br /><strong>2. Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.<br /><br /><strong>3. GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
<p><strong>4. User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
<p><strong>5. Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
<h3 id="stakeholders">Stakeholders</h3>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.</p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h2 id="technicaldetailsofourplatform">Technical Details of Our Platform</h2>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>
<p>Continue refining marketing goals and strategies through iterative assessments.</p>
<p>Key questions include:</p>
<p>Did teams improve their outcomes? Are there events or strategies that consistently underperform?</p>
<p>Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</p>
</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</li>
<li><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement. <br />Due to significant fragmentation, we need to allocate more resources to ensure adequate support.<strong><br /></strong></li>
<li><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</li>
<li><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</li>
</ul>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience">Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet">What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture">How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm">How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3 id="whataretheteamslongtermplansandintentions">What are the team's long-term plans and intentions?</h3>
<p>To integrate our platform with every dev tooling company, ensuring self-sustainability and reducing reliance on grants or single organizations.</p>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What Is The goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<ol style="list-style-type: decimal;">
<li>The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</li>
<li>There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</li>
</ol>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. Here&rsquo;s why OpenQ is crucial for the Polkadot community:</p>
<p><strong>1. Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
<p><strong>2. Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.<br /><br /><strong>3. Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2 id="ourobjectives">Our Objectives</h2>
<p><strong>1. Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.<br /><br /><strong>2. Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.<br /><br /><strong>3. GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
<p><strong>4. User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
<p><strong>5. Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
<h3 id="stakeholders">Stakeholders</h3>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.</p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h2 id="technicaldetailsofourplatform">Technical Details of Our Platform</h2>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>
<p>Continue refining marketing goals and strategies through iterative assessments.</p>
<p>Key questions include:</p>
<p>Did teams improve their outcomes? Are there events or strategies that consistently underperform?</p>
<p>Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</p>
</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</li>
<li><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement. <br />Due to significant fragmentation, we need to allocate more resources to ensure adequate support.<strong><br /></strong></li>
<li><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</li>
<li><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</li>
</ul>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience">Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet">What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture">How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm">How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3 id="whataretheteamslongtermplansandintentions">What are the team's long-term plans and intentions?</h3>
<p>To integrate our platform with every dev tooling company, ensuring self-sustainability and reducing reliance on grants or single organizations.</p>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What Is The goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<ol>
<li>
<p>The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</p>
</li>
<li>
<p>There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</p>
</li>
</ol>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. Here&rsquo;s why OpenQ is crucial for the Polkadot community:</p>
<ol>
<li>
<p><strong>Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
</li>
<li>
<p><strong>Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.</p>
</li>
<li>
<p><strong>Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
</li>
</ol>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2 id="ourobjectives">Our Objectives</h2>
<ol>
<li>
<p><strong>Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.</p>
</li>
<li>
<p><strong>Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.</p>
</li>
<li>
<p><strong>GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
</li>
<li>
<p><strong>User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
</li>
<li>
<p><strong>Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
</li>
</ol>
<h3 id="stakeholders">Stakeholders</h3>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.</p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h2 id="technicaldetailsofourplatform">Technical Details of Our Platform</h2>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>
<p>Continue refining marketing goals and strategies through iterative assessments.</p>
<p>Key questions include:</p>
<p>Did teams improve their outcomes? Are there events or strategies that consistently underperform?</p>
<p>Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</p>
</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li>
<p><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</p>
</li>
<li>
<p><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement.&nbsp;</p>
<p>Due to significant fragmentation, we need to allocate more resources to ensure adequate support.</p>
</li>
<li>
<p><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</p>
</li>
<li>
<p><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</p>
</li>
</ul>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience">Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet">What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture">How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm">How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3 id="whataretheteamslongtermplansandintentions">What are the team's long-term plans and intentions?</h3>
<p>To integrate our platform with every dev tooling company, ensuring self-sustainability and reducing reliance on grants or single organizations.</p>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

<h2 id="intro">Intro</h2>
<p>Hello Polkadot Community,</p>
<p>I'm Rick, one of the creators of OpenQ, a Developer Relationship Management Platform. We've collaborated with leading chains and web3 tools like BuildGuild, Filecoin, Polygon, Scroll, Aptos, Near, and Consensys to measure the ROI of developer marketing and relations initiatives through detailed developer activity stats.</p>
<p>In this post, I&rsquo;ll outline what we do, our goals with Polkadot stakeholders, and our plans as we prepare for a treasury proposal. Your feedback is highly appreciated.</p>
<h2 id="whyopenqwhatisthegoal">Why OpenQ What is the Goal?</h2>
<p>First it's important to address a major issue within the ecosystem. Polkadot currently faces challenges in leading developer marketing initiatives and accurately calculating the ROI of these efforts, as well as setting clear KPIs for each initiative.</p>
<p>The primary reason for this challenge is the fragmentation of efforts across various teams. Numerous initiatives funded by the Web3 Foundation are being executed without a standardized format for data collection, making it difficult to track the outcomes and understand how these efforts are enhancing developer community engagement over time.</p>
<p>Furthermore, there's a significant gap in understanding the overall impact of marketing and developer relations spending on ecosystem growth due to two main reasons:</p>
<ol>
<li>
<p>The lack of centralized data collection across different teams complicates the aggregation and analysis of results.</p>
</li>
<li>
<p>There is no dedicated entity collaborating with these teams to measure and interpret developer activity metrics and integrate this data with existing records to present a comprehensive view of developer activity within the ecosystem.</p>
</li>
</ol>
<p>This fragmentation leads to another issue: since teams do not collaborate closely, there is no shared knowledge base on what marketing strategies or developer relations efforts are effective. Without a unified database accessible to all relevant parties, it's impossible to build upon previous successes or learn from past mistakes.</p>
<p>Lastly, the lack of oversight by the foundation means that both the foundation and community members who vote on new or continuing initiatives lack the necessary information to make informed decisions.</p>
<p>As Polkadot continues to decentralize, our vision at OpenQ is to become the central entity for all data collection related to developer marketing and relations initiatives, addressing these challenges directly. Here&rsquo;s why OpenQ is crucial for the Polkadot community:</p>
<ol>
<li>
<p><strong>Centralized Data Collection</strong>:<br />We collaborate with stakeholders to accurately measure the impact of initiatives such as educational programs, hackathons, and other events that attract developers to the Polkadot ecosystem, optimizing efforts for growth.</p>
</li>
<li>
<p><strong>Unified Ecosystem Effort</strong>:<br />As a data hub, OpenQ fosters collaboration across Polkadot, reducing reliance on external sources like the developer report from Electric Capital and improving ecosystem representation.</p>
</li>
<li>
<p><strong>Enhanced Ecosystem Visibility</strong>:<br />Our tools help the community track and report developer activity, contributing to a transparent view of ecosystem health and strengthening Polkadot's global standing.</p>
</li>
</ol>
<h2 id="howourplatformworks">How Our Platform Works</h2>
<p>For a demo, check out my recent ETHcc presentation at the WebZero-organized Polkadot demo hour <a href="https://drive.google.com/file/d/1CjEIojdd7vNacgZkuGtPCabAS3aCPb6r/view">here</a>.</p>
<h3 id="generalflow">General Flow</h3>
<p><strong>Access and Collaboration</strong><br />Our platform is accessible to various teams within the Polkadot ecosystem, including a general team for the Web3 Foundation, ensuring broad access to insights.</p>
<p><strong>Core Functionality: GitHub Code Search</strong><br />A powerful GitHub code search and scraping tool lies at the heart of our platform, enabling users to analyze extensive code data without limitations.</p>
<p><strong>Campaigns: Organizing Initiatives</strong><br />Create "lists&rdquo; to track marketing efforts like hackathons, educational programs, conferences, meetups or even the whole community. Our platform can also identify whether projects are deployed on Polkadot based on open source data we track and provide comprehensive overviews.</p>
<h2 id="ourobjectives">Our Objectives</h2>
<ol>
<li>
<p><strong>Measure ROI of Developer Marketing Initiatives</strong><br />Accurately calculate ROI for marketing and relations initiatives, supporting sustainable growth and empowering stakeholders to measure their impact to drive more value. Also showcase total developer activity.</p>
</li>
<li>
<p><strong>Comprehensive Developer Data Aggregation</strong><br />Aggregate developer data, both top-down and bottom-up, identifying active and at-risk projects to help stakeholders provide targeted support.</p>
</li>
<li>
<p><strong>GitHub Repository Discovery for New Projects</strong><br />Use our project discovery tool to identify and support new projects within the Polkadot ecosystem.</p>
</li>
<li>
<p><strong>User-Friendly Platform for All Teams</strong><br />Offer an easy-to-use platform for marketing and relations teams to add projects, measure impact, and enhance the accuracy of developer data through crowdsourcing.</p>
</li>
<li>
<p><strong>Identify Activity from Closed Source Projects</strong><br />Address the challenge of capturing closed-source contributions, requiring manual effort but offering significant long-term benefits.</p>
</li>
</ol>
<h3 id="stakeholders">Stakeholders</h3>
<p>Stakeholders are entities involved in developer marketing or relations initiatives, including marketing, event, or dev rel teams funded by grants, investors, or revenue.</p>
<p>Here&rsquo;s who we&rsquo;ve engaged with so far. If you're not listed, contact me via Telegram to work with us together: @rickkdev.</p>
<p><strong>Stakeholders:</strong></p>
<ul>
<li>WebZero</li>
<li>Polkadot Academy</li>
<li>Parity</li>
<li>Web3 Foundation</li>
<li>Missing-link</li>
<li>Chainsafe</li>
</ul>
<p>Naturally, stakeholders will include developer tools for the Polkadot ecosystem, which are public goods funded by the Web3 Foundation. We will assist them in tracking their impact and developer usage, ensuring their tools are distributed effectively while also gathering feedback for improvement. These projects can reach out to us and request access.</p>
<h4 id="technicaldetailsofourplatform">Technical Details of Our Platform</h4>
<p>The OpenQ process initiates by importing data such as repositories, GitHub users, or organizations. For those starting from scratch, we provide features to assist in discovering relevant projects. Imported URLs are first sent to a Kafka queue, which then passes these URLs to a parallelized Go program known as Gitguru.</p>
<p>Gitguru is essential for cloning each repository, analyzing each commit for specified dependencies across various files, and identifying genuine and relevant users by tracking when they started and their engagement over time. Our dependency tracking system searches within files to check if a specific dependency is used, which helps in determining whether a project is deployed on a particular blockchain or uses a specific tool.</p>
<p>After Gitguru has processed and created a deeply searchable database of GitHub repositories and users, the next step involves our second module, the Evaluator. The Evaluator assigns various scores and metrics to these repositories and their contributors based on their activity and dependency usage. Following this individual assessment, we compile a comprehensive analysis for all projects evaluated. This includes calculating the total developer activity over the past 12 months, providing a timeline of activity which serves as a crucial KPI for understanding growth and engagement trends within the ecosystem. This metric is vital as it showcases the dynamic engagement and development progress over time, helping stakeholders gauge the effectiveness of different initiatives.</p>
<h2 id="timelineandfundingmilestones">Timeline and Funding Milestones</h2>
<p>To achieve our objectives, we have structured our project into four key milestones, each with specific goals and budget requirements:</p>
<p><strong>Milestone 1: Data Collection and Initial Analysis (3 months - $30k)</strong></p>
<ul>
<li>Gather and analyze existing data, onboard ecosystem leaders, and enhance metric accuracy.</li>
</ul>
<p><strong>Milestone 2: Ecosystem Leader Improvements (3 months - $25k)</strong></p>
<ul>
<li>Collaborate with stakeholders to review and refine data, improve accuracy, and apply actionable feedback to enhance ecosystem strategies.</li>
<li>Our primary goal is to evaluate each developer marketing initiative comprehensively, determining their effectiveness and areas for improvement. This analysis will recur throughout each milestone, with stakeholders conducting monthly reviews based on the data we provide.</li>
</ul>
<p><strong>Milestone 3: Continued Feedback and Results (3 months - $25k)</strong></p>
<ul>
<li>
<p>Continue refining marketing goals and strategies through iterative assessments.</p>
<p>Key questions include:</p>
<p>Did teams improve their outcomes? Are there events or strategies that consistently underperform?</p>
<p>Additionally, monitor and verify data submission from all teams. While participation isn't mandatory, only data-submitted initiatives will be included in the comprehensive community report in Milestone 4, highlighting effective strategies and areas needing improvement.</p>
</li>
</ul>
<p><strong>Milestone 4: Final Analysis and Community Engagement (3 months - $20k)</strong></p>
<ul>
<li><strong>Finalize Analyses</strong>: Ensure all data and results are accurate and comprehensive.</li>
<li><strong>Publish Results</strong>: Release a detailed report to the Polkadot community, outlining effective strategies and areas for improvement.</li>
<li><strong>Community Engagement</strong>: Host a webinar and kickstart discussions to present findings and discuss future plans.</li>
<li><strong>Continuous Improvement</strong>: Plan to extend this process, incorporating community feedback to enhance reports and potentially increase their frequency to quarterly updates.</li>
</ul>
<h2 id="costoverview">Cost Overview</h2>
<ul>
<li>
<p><strong>AWS Services: Compute &amp; Storage | Managed Solutions: Postgres, Kafka, Kubernetes | Non-AWS Managed Solutions: MongoDB Atlas &amp; Confluent</strong>: Monthly expenses of $4-5k/m to cover our platform cost for general data scraping, management as well as monthly updates and frontend. Initial data evaluation will be more costly due to the need to clone all repositories, rather than just updating them.</p>
</li>
<li>
<p><strong>Customer Support and Stakeholder Onboarding</strong>: Extensive support is required to help teams and stakeholders understand data collection, submission, and analysis. This ensures the creation of effective strategies and high post-event engagement.&nbsp;</p>
<p>Due to significant fragmentation, we need to allocate more resources to ensure adequate support.</p>
</li>
<li>
<p><strong>Reporting and Community Webinar</strong>: Costs include preparing and delivering detailed reports and hosting a community webinar at the project's end, requiring year-round preparation to integrate all team data effectively.</p>
</li>
<li>
<p><strong>Consulting Services</strong>: We provide in-depth consulting to enhance the value and effectiveness of each event and initiative, aiding in strategy development and increasing developer engagement. Our core expertise lies in developer relations, with both founders bringing together over a decade of combined experience in the field.</p>
</li>
</ul>
<h2 id="faq">FAQ</h2>
<h3 id="whereandhowdoesyourprojectfitintotheecosystem">Where and how does your project fit into the ecosystem?</h3>
<p>Our platform supports marketing, developer advocacy, ecosystem management, product development, grant review, and leadership roles.</p>
<h3 id="whoisyourtargetaudience">Who is your target audience?</h3>
<p>The Web3 Foundation, key ecosystem participants, Parity, and those responsible for ecosystem growth, improving developer experience on Polkadot and its Parachains.</p>
<h3 id="whatneedsdoesyourprojectmeet">What need(s) does your project meet?</h3>
<ol>
<li><strong>Quantifying Developer Activity</strong>: Identifying active developers in the Polkadot ecosystem.</li>
<li><strong>Impact Assessment</strong>: Helping stakeholders measure impact and prioritize tasks.</li>
<li><strong>Measuring ROI</strong>: Evaluating the ROI of events for developer growth or retention.</li>
</ol>
<h3 id="howdoyouplantofinancetheprojectinthefuture">How do you plan to finance the project in the future?</h3>
<p>We plan to license the platform annually, ideally through yearly grants after proving our value.</p>
<h3 id="howdoyouintendtouseenhancepromoteandsupportyourprojectintheshortterm">How do you intend to use, enhance, promote, and support your project in the short term?</h3>
<p>We aim to become the go-to brand for measuring developer activity in web3, already partnering with organizations like Polygon, Consensys, Aptos, and others.</p>
<h3 id="whataretheteamslongtermplansandintentions">What are the team's long-term plans and intentions?</h3>
<p>To integrate our platform with every dev tooling company, ensuring self-sustainability and reducing reliance on grants or single organizations.</p>
<h3 id="summary">Summary</h3>
<p>To wrap things up, OpenQ is here to help the Polkadot ecosystem grow by tracking and measuring the impact of developer marketing and relations efforts. Our goal is to give stakeholders the data they need to make better decisions and drive real growth. This is crucial for the treasury to make informed choices about which partners to support, whether they&rsquo;re launching new initiatives or continuing existing ones. We want to help kickstart a new phase of ecosystem growth for Polkadot.</p>
<p>We&rsquo;ll be submitting our proposal to the treasury soon and would love to get your feedback. Feel free to reach out directly on Telegram at @rickkdev if you have any questions or want to discuss potential partnerships.</p>
<p>Thanks for your support!</p>

- **Problem Statement:** Polkadot lacks centralized data collection for measuring developer marketing ROI, leading to fragmented efforts and ineffective decision-making.
- **Audience:** Web3 Foundation, key ecosystem participants, Parity, and stakeholders driving Polkadot's growth.
- **Significance:** Fragmentation hinders tracking marketing impact, setting KPIs, and making informed decisions, impacting ecosystem growth.
- **Proposed Solution:** OpenQ aims to centralize data collection, measure ROI, aggregate developer data, and enhance ecosystem visibility.
- **Expected Outcomes:** Improved ROI measurement, targeted support for projects, enhanced ecosystem collaboration, and transparent ecosystem health reporting.

#2518 Tracking ROI for Developer Marketing and Relations in the Polkadot Ecosystem

No Active Proposals