10,000 AIdeas: What We Learned

We ran our first global competition on Builder Center, receiving thousands of submissions from 115 countries. It was ambitious, it was messy in places, and it taught us more than we expected. We want to share what we learned, not because we got everything perfect (we didn't), but because this community shaped how we're building future competitions. 

Global reach exceeded expectations. Builders from 115 countries showed up with ideas ranging from deeply personal to wildly ambitious. Builders tackled problems across healthcare access, agricultural resilience, education equity, and disaster response, often for communities underserved by existing tech. When you give builders an open invitation and a real opportunity, they bring their best work. 

We chose flexibility over rigidity. Some articles were missing a tag. Some videos ran long. Some apps were local prototypes rather than publicly accessible. We evaluated these case-by-case rather than auto-disqualifying on technicalities because we wanted to judge ideas and execution, not penalize a builder who was one tag short of a great submission. We drew the line at submissions that were significantly late (6+ days) or from individuals who didn't meet eligibility requirements in the Terms and Conditions. That said, we heard from community members who felt the rules should have been applied more strictly. That's fair, and we're addressing it below. 

Community voting drove real engagement. Articles that inspired people rose to the top, and the engagement was incredible. It brought new members into Builder Center and surfaced what resonated with the community. 

Winner announcements need full verification first. We announced winners with a caveat that entries were "subject to verification of eligibility." When a winner was later disqualified, it undermined confidence in the process . Next time, we will complete the full eligibility review before any names go public. We'll also strengthen technical verification in the judging process so finalist claims are better substantiated before winners are selected.

Submission guidelines need sharper boundaries upfront. We would choose flexibility again, but next time we will publish explicit guidance on what is flexible versus what is a hard requirement so everyone starts on the same page. 

Community voting needs guardrails. When prizes are attached to votes, it changes behavior. We saw a wave of new users join specifically to vote for a friend's article. Popular vote and technical innovation don't always measure the same thing. Going forward, community engagement will be one signal among many so both community favorites and quietly brilliant innovations get recognized on their merits. 

We need a formal feedback mechanism.  Community members independently flagged eligibility and compliance issues that improved our review process - that kind of vigilance makes competitions better. But rather than relying on published articles or comments to surface concerns, we will provide a dedicated form for flagging issues, gaps, or ideas directly to the team. 

To every builder who submitted an idea, thank you. To those who gave us honest, constructive feedback, you will make the next iteration better. And to the community members who celebrated each other's wins throughout the competition, that's what Builder Center is about and we can’t wait to see what you build next. 

If you have any suggestions on how we can continue to improve, please consider creating a Builder Center Wish , or contact Builder Center Support  (select "other"). We also welcome your comments below. Thank you!