Run a community pilot you can learn from

Write the hypothesis before inviting people

State who the site serves and what should improve for them. For example: “Members discussing this competition will return for the next fixture because the market page puts the question, context, and conversation together.”

Choose an event already in the catalog and use the first-week playbook. Keep the invitation consistent so you can interpret the response. Do not confuse publishing a site with attracting a customer.

Ask questions that reveal understanding

• What do you think this gives you?
• Where do you think your trading funds go?
• Why would you use this instead of your current site?
• What would stop you sharing it?
• Which fee or settlement condition is unclear?

Let people answer before explaining the product. Record their wording and the screen where they hesitated. Do not collect private keys or ask people to show sensitive wallet information.

Keep a small weekly scorecard

• Number invited and the invitation channel.
• External visitors and how they were measured.
• First external traders, excluding owner tests.
• Returning traders in a stated follow-up period.
• Eligible volume, actual builder fees, and attribution limitations.
• Partner rewards, promotion spend, and support hours.
• Repeated questions, failures, and product changes made.

Use the console’s available data and record missing measurements as unavailable. A wallet is not necessarily a person. Avoid presenting estimated fees as received income or attributing shared-protocol activity to your site without evidence.

Turn evidence into a case study

Ask permission before naming the community, quoting a member, or publishing screenshots. State the observation period, audience source, starting position, actual results, costs, and limitations. Include the work involved and what did not work.

Report weak results too. A launch with no repeat traders is useful information about audience fit or the experience. Do not replace missing evidence with hypothetical customer numbers.

Use observed activity in the activation calculator. Decide whether to repeat the experiment, improve onboarding, or stop. A successful pilot supports the next step, not a guarantee of future revenue.