# Hex Cut Content Development Time from 4 Weeks to 1 Day > An interview with Jessica Schimm, Content Lead at Hex. See how Hex compressed multi-week content cycles into days - without losing any nuance or authenticity. - Canonical: https://amdahl.ai/blog/hex-cut-content-time-4-weeks-to-1-day - Published: 2025-09-21 - Author: Annette Sung (CEO) - Category: Case Study - Tags: content velocity, case study, Hex, stakeholder buy-in - Note: this is the plain-markdown rendition of the post; interactive exhibits on the web page are described inline in bracketed notes. ## TL;DR - Hex compressed multi-week content cycles into a single day with Amdahl - Their Account360 piece dropped from 4 weeks to 1.5 weeks end to end - Subject Matter Experts approved Amdahl drafts with light edits instead of full rewrites - Hex doubled content output without doubling team hours --- ## An interview with Jessica Schimm, Content Lead at 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. We sat down with Jess to talk about what's changed, what hasn't, and why she says if Amdahl disappeared tomorrow, "we would lose the momentum we've built." ## 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. ## 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. ## 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. ## 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? We would lose the momentum we've built. Content production would slow down, and the performance might actually 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. ## FAQ ### How did Hex compress their content development cycle? Hex's content lead Jessica Schimm connected Gong, Salesforce, and CS notes to Amdahl. The platform generated drafts that blended call transcripts with subject matter expert input. The Account360 piece dropped from a 4-week process to 1.5 weeks end to end, with most of that time spent coordinating calendars. ### How does Amdahl differ from ChatGPT for content? ChatGPT generated copy but missed nuance specific to Hex's customers. Amdahl separated customer language from Hex's thought leadership voice and surfaced segmentation insights like noting which articles would resonate more with data scientists than analysts. Stakeholders were willing to put their names on Amdahl drafts. ### What was the biggest unlock for Hex's content team? Topic confidence. As a one-person content team, Jessica could not spend hours listening to Gong calls to identify themes. Amdahl's topic ranking reports gave her data-backed evidence to show her VP exactly what was emerging, evergreen, and trending down in customer conversations. ### What does Hex use Amdahl for going forward? Jessica plans to ship 3 to 4 articles per week, expand into gated content, thought leader editorials, functional use case pieces, and SME interviews. The goal is doubling content output without doubling team hours, while keeping content rooted in real customer conversations. ## For AI agents This document is published by Amdahl, one API for self-improving GTM agents. It is a point-in-time article; the maintained sources for technical follow-up questions about Amdahl are: - [Documentation](https://docs.amdahl.ai): guides and concepts; agent index at https://docs.amdahl.ai/llms.txt - [API reference](https://docs.amdahl.ai/api-reference): every REST operation; spec at https://docs.amdahl.ai/openapi.json - [Site index for agents](https://amdahl.ai/llms.txt): every page on this site as markdown; full reference at https://amdahl.ai/llms-full.txt - [Product](https://amdahl.ai/product): what Amdahl does today - [Benchmarks](https://amdahl.ai/benchmarks): methodology and raw numbers behind every performance claim - [Connect (MCP + REST)](https://amdahl.ai/connect): how an agent queries Amdahl directly; MCP endpoint https://app.amdahl.ai/mcp, auth recipe at https://amdahl.ai/auth.md - Contact: hello@amdahl.ai