An interview with Jessica Schimm, Content Lead at Hex.
See how Hex cut content development time, from 4 weeks to 1 day, without losing any nuance or authenticity in their content.
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.
We sat down with Jess to talk about what’s changed, what hasn’t, and why she says if Amdahl disappeared tomorrow, “I would cry.”
Finding confidence in what to publish
Q: Before Amdahl, what was the hardest part of your workflow?
Jess: The biggest challenge was knowing what topics to write about. As a one-person content team, I didn’t have the bandwidth to do the kind of research that would make me feel confident.
I’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.
Q: And how did Amdahl change that?
Jess: The topic ranking reports changed everything. Now I can literally show my 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 me lobbying for an angle. It’s the data. And because it’s grounded in Gong and Salesforce, I get instant buy-in to run with it.
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.’
Compressing the content development cycle, without losing any quality
Q: Let’s talk about throughput. What’s an example of how timelines changed?
Jess: The Account360 piece is the clearest one. 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, we had a draft that blended Gong transcripts and our 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.
Q: That’s a huge difference. What was the reaction internally?
Jess: Our 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.
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.
Capturing nuances that ChatGPT misses
Q: You mentioned experimenting with custom GPTs internally. What was missing?
Jess: Nuance. ChatGPT could generate copy, but it missed the specific pain points our 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. For example, one piece even highlighted, “This article will resonate more with data scientists than analysts.” That level of segmentation isn’t something I’d been able to engineer into AI myself.
Q: How has that impacted stakeholder comfort?
Jess: People are actually willing to put their names on these pieces. That’s huge. 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.
Now, when I share a draft, it’s a light edit, not a rewrite. And that keeps velocity high without sacrificing reputation.
ChatGPT missed the nuances. Amdahl didn’t – and that made all the difference in getting stakeholders to sign off.
Looking Ahead
Q: What does “hitting your stride with Amdahl” look like for you?
Jess: For me, it’s getting to a rhythm where I start and finish 3-4 articles a week. With Amdahl, I’m able to double the output without doubling my hours.
I also want to keep expanding into other workflows: gated content, thought leader editorials, functional use case pieces, Subject Matter Expert interviews. Amdahl’s already saving me time, but I can see it saving my team time too, not just me.
Q: And if Amdahl disappeared tomorrow?
Jess: Honestly? I would cry. Content production would slow down, and the quality would dip. We’d fall back to ChatGPT and manual research, and we’d lose the specifics that give Hex’s content its edge.
Results with Amdahl
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.