Climate Salad runs a community for climate tech founders and investors in Australia, connecting members through events, research publications, and a curated directory of companies and investors. The site shows a membership application process that appears to involve a manual approval step, alongside a contact form that routes enquiries to the team for follow-up. Mailchimp and Webflow are both visible in the stack, suggesting the member journey spans at least two distinct systems before someone is fully inside the community.
If we're already off — say so in 20 minutes: book a call.
The membership application on your site prompted a question: when a founder or investor applies to join, how much of the journey between that first form submission and them being active in the community runs on the team's attention rather than on process? The application form is visible and the approval step appears to be manual — which is often the right call for a curated community, but it can also create a stretched interval between someone's moment of peak interest and them actually engaging. The direction worth exploring is whether there's a layer of coordination sitting between the intake form and the welcome experience that absorbs more team time than it needs to. What we can't tell from outside is whether the approval volume is light enough that this is a non-issue, or whether it's quietly becoming a constraint as the community scales.