The lesson
Open with the migration result, then show the operational mess that made the new workflow necessary.
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.
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.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.