Auto-apply labels from custom fields when creating items in GitHub Projects board

Many engineering teams still spend a disproportionate amount of time on manual triage: when an item is added to a GitHub Projects board they must copy values from project custom fields into issue labels, which is repetitive and error-prone. This pain is especially acute for teams doing sprint planning, support triage, and cross-repo program management, and it likely affects a large addressable audience—roughly 18 million development teams by our estimate. You could build a lightweight GitHub App that auto-applies labels from project custom fields at item creation, offering rule-based mappings, reusable templates, and ML-assisted suggestions to infer mappings from historical behavior. Ship it as an in-UI configuration experience and a Marketplace-listed app with a low-permission mode that only touches relevant repo metadata to minimize security friction and adoption barriers. The timing looks favorable: platform consolidation and automation-first workflows make teams more willing to pay for embedded, low-friction integrations, and the estimated addressable market of $3.6B (18M teams × $200/year) with a market score of 88/100 and revenue potential of 80/100 suggests healthy unit economics if you can capture a small share. To stand out, focus on a first-class GitHub UX, privacy-minimizing permissions, and value-added features like team-wide policy templates, audit logs, SSO, and ML suggestions for mapping; these address real buyer concerns and enable higher ARPU. Be honest that challenges include GitHub API nuances and rate limits, medium-strength competition from Actions and third-party automation platforms, and the need to demonstrate clear time-savings to convert free users to paid customers.