I’ve been exploring and participating in an incentivised platform called @testdriveso , and I’ve noticed that some people still don’t fully understand how it works. 📌 So here is the simple version. Test Drive connects product builders with people who can actually use their products, test them, and share honest feedback publicly on X. It is not simply “post about a product and get paid.” ✅ The important part is the TEST. 📌 A typical Test Drive looks like this: 🔸 Find a campaign you’re eligible for 🔸 Read the brief and requirements 🔸 Use the product yourself 🔸 Register your draft before publishing 🔸 Share your honest experience on X 🔸 Submit the post link 🔸 Your participation is independently checked 🔸 If your review qualifies, you receive the campaign reward And yes, your review can be positive, mixed, or critical. You are not required to praise a product just because the campaign is incentivised. That distinction matters. 📌 Now, let's talk about the Builder Rank. I initially thought the ranking was basically another engagement leaderboard. But it isn’t. @testdriveso says Builder Rank reflects an interaction and influence graph around people who build, test and explain products publicly. 📌 So what actually matters? • Showing work that is genuinely yours • Testing and talking about products you actually used • Giving specific observations instead of generic praise • Having meaningful conversations with other builders • Building a recognisable track record around what you create, test or explain 📌 And what DOESN’T help? • Buying followers, views or replies • Engagement pods • Copy pasting comments everywhere • Mass tagging builders for attention • Asking people for follow backs or reciprocal engagement • Praising a product you never actually used In other words, Test Drive isn’t really asking: “How loud is your account?” It’s closer to: “Are you a credible person who actually builds, tests and contributes useful context?” 📌 One more important thing: Being visible on the public Builder Rankings does NOT automatically mean you’re eligible for every Test Drive. Each campaign can have its own eligible audience, product-fit requirements and rules. So the rank is useful, but it isn’t a guaranteed ticket into every campaign. That’s what makes the model interesting to me. You’re not being rewarded simply for having an audience. You’re being encouraged to create a useful feedback loop: 🔸 PRODUCT 🔸 REAL USEAGE 🔸 HONEST REVIEW 🔸 PUBLIC CONVERSATION And if you are a creator who wants to participate, the best place to start is not by trying to “game” the ranking. Start by making useful contributions. 🔸Test things. 🔸Build things. 🔸Explain what you learn. 🔸Have real conversations. 🔸Let your work become the signal. That’s probably the part of @testdriveso I think more creators should understand. Builders, what do you think should matter most when ranking someone who tests and explains products publicly?

I just joined @rarelistio and I’m curious to see how far this can go. What caught my attention isn’t just the $50K Season 1 prize pool. It’s the idea of rewarding people for actually contributing to projects early, researching, creating, participating and sharing useful perspectives. I’m putting it to the test this season. If you’re a Web3 creator too, come join me 👇 rarelist.io/r/AlphaLady__

One thing about @HyperliquidX that deserves more attention: HIP-3 changes who gets to decide what can become a market. Instead of waiting for the platform itself to list every asset, builders can deploy their own perpetual markets on Hyperliquid, subject to the protocol’s requirements. That sounds simple, but it creates an interesting market discovery experiment. If someone sees demand for a market that a traditional exchange would never prioritize, they can try to build around that demand. The real question now isn’t just what will Hyperliquid list? It’s what markets will people prove they actually want? $HYPE

I wanted to see if @LeadpoetAI could do more than give me a generic list of prospects, so I tested its lead request flow. The useful part was being able to tell it exactly what buying intent to look for, rather than simply saying “find Web3 companies.” I narrowed the request to US companies and specified the company sizes, contacts and channels I wanted. One friction point: the product is desktop-only, which limits when and where I can run a prospecting workflow. My request is now processing, with results expected within 24–48 hours. The real test for me will be whether those leads actually show the intent I asked Leadpoet to find.

I tested @LeadpoetAI to see how it handles prospects showing buying intent. I liked that I could define the buyer beyond just an industry: ICP, what I offer, specific buying signals, location, company size, number of companies and contacts. The setup was easy to follow, but two things stood out. Leadpoet currently runs on desktop, so I couldn’t do the test from my phone. Also, after submitting my request, I was told results can take up to 24–48 hours. That means I haven’t seen the actual leads yet, but I now have a clear request in the pipeline to evaluate.