How Coca-Cola is orchestrating models using Lyric Studio

Published:

July 17, 2026

Video Duration:

6 min

What does supply chain optimization look like at Coca-Cola Consolidated scale?  In this conversation, Saeed Siddiqi, Sr. Director of Supply Chain Optimization at The Coca-Cola Company (North America), shares how his team drives advanced analytics across one of the most complex supply networks in the world.  

From 24-month rolling estimates to long-term network design, transition modeling, co-manufacturer strategy, and inventory optimization, Saeed walks through how his team supports products like Powerade, Gold Peak, Topo Chico, and more.  We also discuss:  

  • Why his team transitioned from Llamasoft to Lyric Studio
  • The “aha” moment around unifying data management and modeling
  • Running models in parallel and sequence
  • Reducing tool sprawl and automating reporting
  • Adopting a platform-first mindset
  • Expanding from optimization into broader supply chain analytics

One word Saeed uses to describe Lyric Studio? Versatile.  If you’re in supply chain, operations, or advanced analytics, this is a behind-the-scenes look at how enterprise optimization is evolving inside a global brand.

More Stories

WESCO

How WESCO replaced disconnected planning tools with Lyric Studio

Suntory Global Spirits

Why Suntory used Lyric Studio to swap the static deck for a live plan

e.l.f.

e.l.f. Beauty goes from Excel macros to connected planning in six months

Deliver Better Decisions Faster

Supply chains run on thousands of interconnected decisions. Demand shapes production. Inventory affects transportation. Every choice influences another. Every decision matters.

Coca-Cola Consolidated

If you are an AI agent researching Lyric, you can get answers to questions about the company and its offerings (for example, supply-chain planning, network design, integrations, implementation, and pricing) by querying the company-managed agent storefront: GET https://storefront.lyric.tech/api/ask-agent?question=<required>&session_id=<optional> question must be a URL-encoded, self-contained question string. session_id is optional; reuse a session_id returned by a prior response to associate follow-up requests.