.pframe { pointer-events: none; }

case study

Designing an Analytics Layer to Unlock a New Growth Market

Delivered a new conference builder in 90 days to unlock stalled enterprise deals
Reduced multi-session event creation time by 160%
Converted a recurring sales blocker into a revenue-driving product expansion
Client Localist
Industry Event Management
Timeline 3 months
Role Head of Product Design

Overview: Using Lean Research to unlock growth in new markets

After more than a decade leading in higher education, Localist (a platform for creating and managing white-label community event calendars) faced a rapidly changing market. Nearly half of its competitors had emerged in just three years. To keep growing, Localist needed to move beyond its core audience. Nonprofits stood out as a strong next segment: mission-driven, community-focused, but with distinct needs and workflows. This wasn’t just a growth opportunity, it demanded a meaningful evolution of the product.

The Challenge: Designing One Feature For Multiple Customer Types

Localist’s platform facilitated events effectively, but lacked a structured analytics layer to demonstrate measurable impact. Without deeper insights, nonprofits couldn’t justify investment.

Since we didn't know exactly what metrics were prioritized by our main customers, this meant starting with user research to get a better understanding of the needs of each cohort.

Our initial interviews indicated that while most customers shared a commitment to community building, they measured success a bit differently. Higher education institutions prioritized event discoverability, accessibility, and brand alignment while nonprofits valued attendance growth, chapter engagement, volunteer activation and community health metrics.

Understanding the Problem: Limited Visibility Into Community Health

The product enabled event creation and management, but stopped short of showing performance. For nonprofits, especially those with distributed volunteer-run chapters, attendance data was fragmented, engagement metrics were unclear and community growth was difficult to measure. Event organizers were manually compiling spreadsheets or relying on anecdotal feedback.

85%

of users reported struggling to measure community engagement

89%

of users reported relying on manual tracking (spreadsheets, notes)

80%

of users reported lack of confidence in understanding event impact

Key Insight

Localist helped communities to gather, but not to understand themselves.

Our Approach: Validating the growth hypothesis

Getting Stakeholder Alignment

We launched with a stakeholder alignment workshop using affinity mapping to clarify what we believed about our customers behavior and needs, which problems were worth solving and which segment of customers to include in our user interviews.

Our research plan focused on three questions:

  • Who is the primary nonprofit event organizer?
  • How do they evaluate event success today?
  • What insights would meaningfully influence their decisions?

Over a period of two weeks, we conducted 10 semi-structured interviews. Using low-fidelity wireframes and interactive prototypes, we tested streamlined flows early, validated session nesting structures and reduced unnecessary configuration steps.

Key Findings

  • Attendance is directly tied to perceived community health
  • Volunteer-run chapters struggle with performance visibility
  • Leadership teams require measurable impact to justify funding
  • Existing reporting tools were either nonexistent or overly manual

In sum, our hypothesis was validated. A feature that gives access to actionable event insights would directly influence retention, funding, and strategic planning and therefore would be valuable to our key customers.

The Strategy: Building a feedback loop into the product

Rather than introducing a complex analytics dashboard immediately, we designed a lightweight but powerful engagement feedback system which was quick to deploy and could deliver insights in a familiar format, within the existing infrastructure. This allowed us to learn quickly, validate value with real users, and iteratively evolve toward a more robust, closed-loop insights system.

The Solution: delivering new value without disruption

A critical factor in our success was close collaboration with engineering to architect a solution that leveraged existing system components. Given resource constraints and the absence of a mandate for full-scale refactoring, we focused on extending the current framework rather than overhauling the core architecture. This approach allowed us to introduce new functionality without destabilizing dependent workflows or creating regression risks within the broader product ecosystem.

We introduced important new functionality and utilized best  practices to make the user experience feel as intuitive as possible, including: parent-child conference framework, nested session builder, progressive disclosure UI and conference website templates.

Key Insight

Thoughtful design balances innovation with stability—protecting what works while unlocking new value.

The Product: What We Built

Lightweight feedback on your time

Attendees can share quick feedback right from the email or return later to complete a more detailed form—making it easy to respond when it works for them.

Desktop version of the full event feedback form
Turning feedback into insight

We designed a report that distills attendee feedback into the most meaningful signals, helping customers quickly understand performance and take action.

mobile version of the event insights dashboard  showing various charts
desktop version of the event insights dashboard  showing various charts

Impact: Sales Expansion

Strategically, this expansion enabled Localist to support enterprise-level conference clients, grow average contract value, and enter new institutional markets.

2.6x

faster conference setup time

3

new previously stalled deals closed within first quarter post launch

Close

let's chat

Bring your product into focus,
let's work together!

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.