One place to run every scenario: Mondelēz on Lyric Studio

Published:

October 23, 2026

Video Duration:

2:31

More than a hundred spreadsheets, across supply chain, R&D, commercial and sourcing, just to arrive at a decision. That is how Natesh Rao, Director of Supply Chain Strategy at Mondelēz International, remembers planning before Lyric Studio. Mondelēz makes iconic snacks like Oreo, belVita and Toblerone across 17 business units, and Natesh leads its supply network design.

Earlier tools could not model the constraints his team works with. Data had to be entered in a set format, the workflow could not change, and neither could the output.

What changed with Lyric Studio:
• Blue notes and green notes that capture every business constraint
• One place where everybody comes to run scenarios
• Models changed at the core and rerun as often as needed
• A team fully trained and building hands-on

The work now spans long-term capacity planning and supply network design across every geography. Natesh is not hands-on himself, but his team is, and he can see "they're really enjoying that." His verdict: "It's just an industry-leading solution."

More Stories

WESCO

How WESCO replaced disconnected planning tools with Lyric Studio

Coca-Cola Consolidated

How Coca-Cola is orchestrating models using Lyric Studio

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.

Mondelēz International

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.