Talk about your next project
Hex case study

The lesson

Open with the migration result, then show the operational mess that made the new workflow necessary.

The move

The page opens with the LangChain logo, the headline “LangChain Completed a 6-Week Migration, 90% by Hex's Agent,” and a short summary about moving off a legacy BI platform. It follows with firmographics, then grouped outcomes under “Outcome” and “Scale achieved,” including “6-week dashboard migration,” “100% of company accesses data via Hex,” and “90% migration by agent.” The story then moves through “The challenge: Legacy BI tooling couldn’t keep pace with exponential growth,” “The solution: One platform that compounds context across the organization,” and “The legacy BI data migration was completed in 6 weeks,” with quotes from Emily Hawkins and Logan Cochran.

Why it works

  • Our readThe headline gives the migration timeline and agent contribution before the reader reaches the body copy.
  • Our readThe outcome block separates company adoption, dashboard migration, onboarding, retention, and team capacity so different buyers can find their concern quickly.
  • Our readThe narrative names the old workflow, the data team bottleneck, and the dashboard audit, which makes the migration feel operational rather than abstract.

What not to copy

Don't copy LangChain's legacy BI context, Context Studio details, YAML migration workflow, or the exact adoption and dashboard numbers. Keep the structure of a quantified migration headline, a grouped outcomes block, then a problem, solution, migration-process story with named customer quotes.

More from Hex

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.