“The marketing team asks: "Which campaigns drove the most pipeline last quarter?" The data analyst opens Hex, writes a SQL query to pull campaign data, joins it with pipeline data, and adds a Python cell to calculate attribution.. Something that used to take 30 minutes took 30 seconds. They looked at the old way and couldn't believe they'd tolerated it. That was the aha.”
When I'm the marketing team asks: "which campaigns drove the most pipeline last quarter, I want to write SQL and Python in the same analysis environment without context-switching, so I can build interactive data apps that non-technical stakeholders can explore on their own.
A data analyst or analytics engineer who uses Hex because it combines everything they used to do across 3–4 separate tools into one collaborative environment. They write SQL to pull data, Python to transform it, and build visualizations and dashboards — all in the same notebook. They share their work as interactive apps that stakeholders can explore without learning SQL. They've replaced Jupyter notebooks, Mode, and Google Sheets with Hex. They are the data person who makes data accessible to people who aren't data people.
To reach the point where write SQL and Python in the same analysis environment without context-switching happens through hex as a matter of routine — not heroic effort. Their deeper aim: build interactive data apps that non-technical stakeholders can explore on their own.
hex becomes invisible infrastructure. Write SQL and Python in the same analysis environment without context-switching works without intervention. The old problem — performance on large datasets can slow down, especially with complex Python operations — is a memory, not a daily fight. Performance optimization for large dataset operations and complex Python transformations.
The marketing team asks: "Which campaigns drove the most pipeline last quarter?" The data analyst opens Hex, writes a SQL query to pull campaign data, joins it with pipeline data, and adds a Python cell to calculate attribution. They build a chart showing pipeline by campaign, add filters for date range and campaign type, and publish it as a Hex app. The CMO opens the link, filters to their campaigns, and explores the data. They find an insight the analyst didn't expect: a low-budget LinkedIn campaign outperformed the expensive conference sponsorship. The CMO Slacks the analyst: "This app is great — can it update automatically?" The analyst adds a scheduled refresh and moves on.
Uses Hex as their primary analysis environment. Writes SQL and Python daily across 10–30 active projects. Has published 5–20 Hex apps for stakeholder self-service. Works with 2–8 other analysts in shared workspaces. Connects to Snowflake, BigQuery, or Postgres data warehouses. Schedules 5–15 automated reports. Spends 60–80% of their work time in Hex. Previously used Jupyter + Mode + Google Sheets. Has built a library of reusable SQL templates and Python functions.
The proof is behavioral: write SQL and Python in the same analysis environment without context-switching happens without reminders. They've customized hex beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
The trigger is specific: the transition from notebook-style analysis to published data app requires rethinking the structure, combined with a high-stakes deadline. hex fails them at exactly the wrong moment. That evening, they're reading comparison posts. What makes it irreversible: they fundamentally believe data analysis shouldn't require 4 tools — the same environment should support exploration, transformation, visualization, and sharing, and hex just proved it doesn't share that belief.
Pairs with hex-primary-user for the standard collaborative analytics perspective. Contrast with excel-financial-analyst for the spreadsheet vs. notebook analysis approach. Use with segment-data-engineer for the data pipeline that feeds Hex.