Back to Portfolio
Product Case Study

Performance Analytics ROI Dashboard

Stopping churn by proving revenue impact. Transforming ROI from a sales-led workaround into a self-serve product capability that helped customers justify $10K–$50K+ annual renewals.

Client G2
Role Product Designer
Duration 1 Year
Team 1 PM 4 Engineers
Year 2025-26
2→46+
ROI Adoption%
$50k-4M+
Revenue Uncovered
80%
Target Goal
8
Product Teams Impacted
ROI Dashboard — Final Design

The Story

Making ROI proof self-serve, scalable, and trustworthy

The Problem

No Way to Prove Value

G2 was facing significant churn. Customers couldn't justify $10K–$50K annual investments without concrete ROI. Proving value was only possible through manual, ad-hoc analysis for a small subset of cooperative customers.

The Goal

80% ROI Adoption

Transform ROI from a sales workaround into a core product capability. Enable customers to prove G2's impact using their own revenue data, on their own terms—without sales involvement.

The Solution

Self-Serve ROI Dashboard

Connected customer CRM data with G2 buyer intent signals to surface G2's influence across the sales funnel. Customers could identify $50k–$4M+ in G2-influenced revenue.

My Role

Lead Product Designer

I led design for this initiative, partnering with four engineers and a Product manager. My responsibilities included defining the end-to-end ROI experience from onboarding to insights, designing CRM authentication and CSV upload flows with a strong focus on trust, partnering with engineering on data permissions, and working with the business manager to align revenue definitions, attribution logic, and metrics used in renewal conversations.

Why This Was Critical

The Trust Problem

The hardest problem wasn't analytics—it was trust

Why Users Dropped Off

To calculate ROI, customers had to authenticate their CRM (Salesforce or HubSpot) or upload a CSV containing sensitive deals and customer data. Most users dropped off during CRM authentication.

  • Uncomfortable sharing revenue and customer data with a third party
  • Fear that G2 could modify or misuse their CRM records
  • Value of connecting data wasn't clear before granting access
  • If users didn't complete setup, ROI couldn't be calculated at all

Authentication Funnel (Before)

Started Setup — 100%
Viewed CRM Options — 65%
Initiated Auth — 30%
Completed Auth — 12%

Key Design Decisions

Building trust through transparency and choice

1. Prioritizing Trust Over Speed

We explicitly designed CRM connections as read-only, clearly communicating what data would be accessed, what would not be modified, and how data was used exclusively for ROI calculation. This reduced fear and increased completion.

2. Value Before Asking

Rather than asking users to connect their CRM immediately, we framed setup around what they would learn, previewed insights they would unlock, and positioned authentication as answering a business-critical question.

3. CSV as Fallback

Recognizing not all customers would trust CRM authentication, we designed CSV upload as a lower-trust, lower-commitment alternative. We accepted slower setup in exchange for higher adoption.

Trust Messaging Screen
CRM Auth Flow
CSV Upload Fallback

The Complete Flow

From onboarding to actionable insights

1

Value Preview

Before asking for any data, we show users exactly what they'll get: sample ROI insights, example revenue attribution, and the specific questions the dashboard will answer.

  • Preview of ROI insights
  • Example revenue attribution
  • Clear value proposition
Value Preview Screen
2

Connection Options

Users choose between CRM authentication (Salesforce/HubSpot) or CSV upload. Each option clearly explains data requirements, permissions, and what G2 can and cannot access.

  • Read-only CRM access
  • CSV upload alternative
  • Transparent permissions
Connection Options
3

Data Matching

The system reads CRM deal and account data, matches accounts with G2 buyer intent activity, and identifies deals influenced by G2 research.

  • Automatic account matching
  • Intent signal correlation
  • Deal influence tracking
Data Matching Process
4

ROI Dashboard

Customers see quantified revenue influenced by G2, in-pipeline vs closed-won impact, and can answer with confidence whether G2 is worth renewing—backed by their own data.

  • Revenue attribution
  • Pipeline impact analysis
  • Executive-ready reports
ROI Dashboard

Buyer Intent Experience

Turning a product gap into a clear value opportunity

With Buyer Intent

Customers with Buyer Intent could see the complete picture with the all the intent signals:

  • All buyer intent signals sent to them
  • How signals mapped to CRM deals
  • Revenue from intent-influenced deals

Without Buyer Intent

Non-Buyer Intent customers saw only partial ROI. Rather than hiding this gap, we used it to explain what they were missing:

  • Estimated signals not fully mapped
  • Prospects researching but not in pipeline
  • Revenue potentially being missed
Upsell Strategy

Showing Missed Revenue

Instead of pushing a sales message, the upsell card framed Buyer Intent as a way to unlock full ROI visibility. We showed customers exactly what they were missing:

  • Estimated Buyer Intent Signals

    Signals that couldn't be fully mapped without Buyer Intent

  • Key Prospects Researching

    Companies actively researching on G2 but missing from their CRM

  • Total Revenue Missed

    Potential revenue being missed without Buyer Intent data

Upsell Card Design

The Impact

Transforming ROI from sales workaround to product capability

40%+

ROI Adoption

From near zero baseline within one year

$1-4M

Revenue Uncovered

G2-influenced revenue per customer

↓ Churn

Reduced Churn

During critical business period

Enabled customers to confidently justify $10K–$50K+ annual renewals using data-backed insights rather than anecdotal evidence

Scaled ROI proof beyond manual sales analysis, allowing more customers to see G2's impact without direct sales involvement

Established a foundation for reaching the long-term 80% ROI adoption goal

Transformed ROI from a sales-led workaround into a self-serve product capability

Future Improvements

Reduce CRM Drop-off

Further optimize the authentication flow to improve completion rates

Progressive Permissioning

Request only essential permissions initially, expand as trust builds

Pre-Auth ROI Estimates

Show estimated ROI before authentication to increase motivation

Key Learnings

What I learned from this project

01

Trust Is the Product

When asking users for sensitive data, the UX isn't just about usability—it's about building confidence. Every interaction must reinforce that their data is safe and used only for their benefit.

02

Show Value Before Asking

Users are far more willing to share data when they clearly understand what they'll get in return. Previewing outcomes before requesting access dramatically improved conversion.

03

Offer Escape Hatches

Not everyone will trust the primary path. Providing alternatives (like CSV upload) captures users who would otherwise abandon entirely. Lower commitment beats zero adoption.

Community

How We Unlocked $1-4M in Hidden Revenue

Discover how a self-serve ROI dashboard stopped churn and transformed customer renewals