TestDrive is going into Phase 2
Phase 1 proved the review loop. Phase 2 is about bringing in enough relevant builders to make that loop valuable and sustainable.
Published
Phase 1 was about proving the review loop with a small founding group. Phase 2 is about bringing in enough relevant builders to make that loop valuable. That's why new TestDrives are less frequent, and why the two live campaigns have more time.
What the first campaigns taught us
Our first phase focused on testing the whole experience: joining TestDrive, checking campaign eligibility, testing a product, publishing an original take, verifying the contribution, and testing the reward workflow.
The founding community helped us find rough edges and make that loop real. Our initial whitelist was about 20 people. As of 22 September, the public campaign list carried $5,050 in reward pools across 20 campaigns. That is listed pool value, not confirmed payouts to participants.
The early participation was useful. It showed us people will try products and share first-hand observations. It also showed us that the current participant base is too narrow to support a daily campaign schedule that serves product teams well.
Why the active campaigns have more time
A campaign needs the right participants and enough time for them to try the product properly. Starting another one every day while the eligible pool is still small would send each new reward pool through largely the same accounts. It would give us more activity without enough new reach or learning for the product behind the campaign.
Stanley runs through Friday, 25 September.
Some builders could not submit their review because verification blocked them. They should not lose their chance because of a technical blocker. The extension is through 25 September, 23:59 UTC, with the same reward pool and eligibility rules.
TestDrive “What To Improve?” runs through Tuesday, 29 September.
This campaign followed another TestDrive feedback campaign back to back. Extending it creates room to invite relevant builders who have not yet contributed a perspective, instead of asking the same small group to repeat feedback we already have.
We will follow up on affected submissions individually. If you were blocked, contact the TestDrive team with your X handle, the review link, and the error you saw. An extra deadline only matters if people can actually submit, so we will share a fix or workable route once confirmed rather than treating the new date as the solution.
Phase 2: bring more relevant builders into the network
We announced our Builder Rank referral campaign because people already in the community know builders who would be a strong fit. So far, we have not seen enough new ranked builders complete a first accepted review. A referral entry or signup is an early signal; an active builder who contributes is the result we are looking for.
Our focus this week is personal outreach to relevant Builder Rank accounts: helping interested builders understand TestDrive, join, and make a first useful contribution. We are looking for builders with real product context and an audience that fits the campaign. A large follower count by itself is not the goal.
What makes more campaigns sustainable
The long-term test is whether a product team gets something worth coming back for: relevant builders who actually try the product, honest public reviews, measurable attention, and feedback the team can use. We also need to show that teams will pay enough for that result to cover participant rewards, verification, and operations. We have not proven those economics yet.
- How many eligible builders become active.
- How many complete useful first reviews.
- Whether builders return for another relevant campaign.
- What each campaign delivers to the product team.
The first phase let us test the workflow and find its gaps. This phase is about building a network that makes the campaigns valuable enough to keep running. If you are on Builder Rankings and like trying new products, start with the live TestDrives.
Keep reading