Hex logo
Hex

Cut content development time from 4 weeks to 1 day

How Hex's one-person content team used Amdahl to compress multi-week content cycles into days - without losing nuance or authenticity.

faster content cycles
4x
Weeks to days per piece
4 → 1
Content output
2x
Stakeholder approval rate
100%

What they said

3 quotes
Before Amdahl, topic selection felt like guesswork. Now I can put a data-backed ranking sheet in front of my VP and say, 'this is where we invest.'
Jessica SchimmContent LeadHex
What would have taken four weeks, we shipped in a week and a half. And the Subject Matter Expert actually said it was better than what she would have written herself.
Jessica SchimmContent LeadHex
ChatGPT missed the nuances. Amdahl didn't - and that made all the difference in getting stakeholders to sign off.
Jessica SchimmContent LeadHex

Meet Hex

Hex is a collaborative data workspace built for modern teams. Their platform makes it easy for data leaders and practitioners to explore, analyze, and share insights in real time. With customers ranging from high-growth startups to Fortune 100 organizations, Hex helps teams move faster from raw data to actionable decisions - without the bottlenecks of traditional BI tools.

Before Amdahl

For Jessica Schimm, leading content at Hex was like running a one-person publishing house. As the leader and executor of her function, she had to identify high-performing topics, research and draft long-form thought leader pieces, and coordinate with busy stakeholders to review them - all while meeting the greater marketing team's growth goals of shipping more content, faster.

That changed when Hex adopted Amdahl - the content engine that analyzed Hex's entire database of Gong, Salesforce and CS notes into data-driven customer insights and near-publish-ready content.

Finding confidence in what to publish

The biggest challenge was knowing what topics to write about. As a one-person content team, Jess didn't have the bandwidth to do the kind of research that would make her feel confident. She'd try to listen to Gong calls for hours, pull out themes manually, and maybe notice "four people mentioned this." But that still felt anecdotal.

Amdahl's topic ranking reports changed everything. Now she can literally show her VP and manager: "Here are the patterns coming out of customer conversations. Here's what's emerging, what's evergreen, and what's trending down." It's no longer lobbying for an angle - it's the data. And because it's grounded in Gong and Salesforce, she gets instant buy-in to run with it.

Compressing the content development cycle

The Account360 piece is the clearest example. Pre-Amdahl, that would've been a four-week process. Between stakeholder interviews, drafting from scratch, and waiting for approvals - it would just drag.

With Amdahl, they had a draft that blended Gong transcripts and their Subject Matter Expert's input. It took about a week and a half end-to-end, and most of that was just coordinating calendars and final sign-offs.

Hex's head of customer success - who manages a team of 10+ - was floored. She's very particular about writing quality and would never have had time to draft it herself. But with Amdahl's draft, she only needed a quick review. She said it was better rounded than what she could have produced on her own.

Capturing nuances that ChatGPT misses

Jess experimented with custom GPTs internally, but something was always missing: nuance. ChatGPT could generate copy, but it missed the specific pain points customers actually talk about. It couldn't blend Gong data with the Subject Matter Expert's voice.

With Amdahl, it's different. The system knows how to separate customer language from Hex's thought leadership voice. One piece even highlighted, "This article will resonate more with data scientists than analysts." That level of segmentation isn't something she'd been able to engineer into AI herself.

People are actually willing to put their names on these pieces. Early on, some stakeholders were skeptical - worried about tone or accuracy. But once they saw drafts that sounded like them and included real customer context, the resistance melted. When she shares a draft now, it's a light edit, not a rewrite.

The results

Hex didn't adopt Amdahl to "do AI content." They adopted it because it solved the exact problems holding Jess back:

  • Confidence in what to publish - grounded in real customer conversations
  • Faster throughput - cutting multi-week cycles down to days
  • Nuance and trust - outputs Subject Matter Experts actually want their name on

For Jess, it means less guesswork, fewer bottlenecks, and more space to focus on the art of editing. For Hex, it means scaling content velocity without sacrificing the quality their brand demands.

Ready to ship content grounded in your own customer conversations?