WSA is a UN-backed organization that gives awards to projects supporting the UN Sustainable Development Goals. Several times a year, they host regional and global events to celebrate award winners and provide valuable networking opportunities for attendees. I was in charge of the WSA website (there is another case study about that). To make the website more helpful, I often followed up with 5–10 people I had met at each event. I asked them what they were hoping to get out of the event and what could be improved.
In these interviews, several recurring themes came up over and over again. One was that the calendar (a PDF sent through a WhatsApp group) was hard to navigate. Another was the inefficiency of the networking. A person working in agritech in Japan had very little to say to someone working in fintech in Chile. Also, the jumble of emails and LinkedIn connections attendees ended up with was often difficult to sort through and follow up on. The WSA community would come together for these events, but would mostly fragment again immediately afterwards.
My first impulse was to address these issues through the website. I built several MVPs, including an AI agent that had access to attendee and project data and suggested connections aligned with each user’s goals. These solutions received mostly positive feedback but were clunky and often drowned out by other communication channels. I also evaluated several SaaS solutions. While many solved the calendar problem, none effectively improved networking or helped maintain community engagement after the event. I considered building a custom app, but WSA did not have an in-house mobile developer or the budget to hire one.
It was around this time that I met Emeka through the WSA community. He had identified a similar need to keep the community connected between events and was willing to work for equity. After discussions with key stakeholders, Emeka and I began developing a solution together.
The first iteration of the app focused solely on calendar functionality. It provided a clear schedule of all sessions, allowed users to sync events with their personal calendars (iCal, Outlook, or Google), view session locations via Google Maps or Apple Maps, and access speaker profiles and LinkedIn pages. The app was embedded within the website so that users who preferred not to download an app could still access the schedule. This successfully solved the calendar problem but did not yet address networking. However, it helped onboard users, which made later iterations easier to roll out.
The second iteration retained the calendar and introduced two new sections: Projects and Community Feed. The Projects section displayed profiles of all winning teams, their objectives, and their social links, allowing attendees to follow up after the event. The Community Feed functioned as a forum where participants could post what they were looking for (investors, employees, or partnerships) and discover others with similar goals. The app also allowed users to browse attendee profiles and identify who might be most relevant to connect with.
The app also featured an AI agent in the bottom right corner that could provide information about winners, the agenda, and attendees. This agent supported networking during the event by suggesting people to connect with based on each user’s expertise and objectives. It also helped attendees use their time more efficiently by recommending the most relevant sessions.