TechPrufer
Get started
Hex
Hex logoHex · Feature trail

Customer Data Hub Evolution

9 posts · Sep 2024 – May 2026

What this trail covers

Hex has evolved its customer data presentation from a static dashboard (Account 360) to a more dynamic, conversational interface (Threads). This shift allows customer-facing teams to ask direct questions of their data, receive real-time answers, and gain deeper narrative insights into customer behavior and history. The underlying data sources (support tickets, product usage, revenue) remain, but the access and interaction model has been significantly improved for speed and depth of understanding. This post details how to build data apps for customer success questions, enabling guided exploration with guardrails (input parameters), layering in business context automatically, and making insights persistent and shareable through features like app subscriptions, comments, @mentions, version history, and saved filter combinations. It emphasizes choosing the right first use case, designing for exploration, involving customer success throughout the process, and measuring key metrics like time from question to answer and actions taken based on findings.

All Hex trails
  1. Why Hex's customer team moved from Account 360 to ThreadsThis post details the evolution from the 'Account 360' static dashboard to the 'Threads' conversational interface for customer data. It highlights the limitations of the previous dashboard (slowness, difficulty in navigation, single-account focus) and the advantages of Threads (direct data interaction, real-time answers, narrative insights). The core data sources and modeling from Account 360 are leveraged in Threads, emphasizing the shift from a dashboard-centric approach to an exploratory, conversational one for customer intelligence.
  2. Fall 2025 Launch: Agents, for analytics, for teamsIntroduces Threads, a conversational analytics interface built on the Notebook Agent framework, designed for self-serve data analysis. Threads leverages Hex workspace context (data connections, semantic models, endorsed tables) and uses existing cells as tools. It offers a new homepage prompt bar and mobile support. The post also details improvements to the Modeling Agent, including synthesizing code into semantic models and a diff view for reviewing proposed changes. New semantic model features include support for snapshot tables with semi-additive measures and cross-model calculations. The Explore feature has been enhanced with Top N, aggregate calculations, and pivot totals/subtotals. The Notebook Agent has been improved with Threads' framework and access to Hex docs.
  3. A Data App for Customer Success: How We Built Our One-Stop Customer Health Command CenterThis post details the evolution of Hex's 'Account 360' from a prototype to a first-class customer investigation tool. It highlights the technical decisions made to unify data from Salesforce, data warehouse, Stripe, and support systems into a single data app. Key architectural choices include making data accessible via dropdowns and filters for non-technical users, balancing real-time needs with system performance by defining appropriate refresh cycles for billing, usage, and support data, and focusing on actionable insights over raw reporting. The app integrates Salesforce account ownership and tracks both committed and actual spend for flexible billing.
  4. Build a data app that answers questions about your customers.This post details the implementation principles for building data apps to answer customer questions, focusing on enabling guided exploration with guardrails (input parameters), automatically layering in business context, and making insights persistent and shareable. It outlines how to map common customer questions into interactive data apps, use input parameters for filtering and analysis, and incorporate contextual information like historical patterns and cohort comparisons. It also highlights Hex's built-in collaboration features (subscriptions, comments, @mentions, version history, saved filter combinations) for capturing investigation context and creating organizational memory. The post emphasizes starting small with a painful, repetitive investigation pattern and designing for exploration rather than just viewing.
  5. How GameChanger used LTV modeling to predict and prevent churnThis post details how GameChanger used LTV modeling to predict and prevent churn. It explains the process of redefining lifetime value (LTV) by calculating 'Lifetime' (using survival regression for time-to-churn) and 'Value' (using ARPU based on subscription plans). It also covers the extension of LTV to free users by modeling advertising potential and likelihood of subscription. The post highlights the use of Hex notebooks for data preparation and exploration, Snowflake for data storage, and dbt for data modeling. It emphasizes how LTV insights clarified churn drivers and enabled revenue forecasting, ultimately leading to a more predictable business.