betaForBeta

This is a dope idea but you need more projects on platform unless I just am not seeing them. I know, it's a chicken and egg thing. Maybe DM projects on Product Hunt 1-4 weeks after their launch and ask them to join your platform? There's also the PH competitors you can hit up too, also try posting in /entrepreneurs on reddit and all those related subs. Find old projects on the reddits subs and DM them. Also the ycombinator library: https://www.ycombinator.com/library, techstars library: https://www.techstars.com/portfolio. I would go with recent, smaller projects. Anything old could be dead.

This is a nice concept. Testing for testing, its a win win for all

Good idea, but the question is if you will find enough users to realize the idea.

I've built so many projects in the hopes that one of them would become an overnight success. After too painfully long, I started to realize that I was doing something wrong. How did other people launch products with such success immediately? THAT is where I was wrong. It wasn't immediate, and it reminded me of the famous quote by Y-Combinator's co-founder, Paul Graham. "Do things that don't scale". It seemed counter-intuitive when I read it the first time, but the more I thought about it, the more I started to see it play out in how other people grew their user base and momentum in the early stages of their projects. Launching a product with an early following takes a lot of manual work making connections one-at-a-time with other entrepreneurs, developers, and interested early adopters. I naturally asked myself the question, "Where do I find other entrepreneurs and product developers?". "How do I make those initial connections?" My mind immediately went to Reddit, but Reddit didn't cut it for several reasons. The most important reason: nearly everyone on Reddit was still interested in overnight success. I created betaForBeta to help myself, and other product developers, live out this idea of "doing things that don't scale." When you test a project, it gives you the right to receive a single developer's feedback. If you test two projects, you get two different developers' feedback. The amount of time you put in is directly proportional to the amount of benefit you get in return. It's a straightforward way of doing things that don't scale so you can create projects that do scale. Oh, and while you're at it, go ahead and make some connections while you're here too. I promise, it'll help tremendously.