One platform, three planning teams: ACCO Brands on Lyric Studio

Published:

October 30, 2026

Video Duration:

2:50

Every Kensington privacy screen starts as a puzzle: how many fit on one sheet of raw material without wasting any of it? It used to take an engineer and a planner three to four days. Vijay Ganti, Director of Supply Chain Analytics at ACCO Brands, has seen Lyric Studio cut that to under an hour. ACCO Brands is the consumer products company behind Kensington, Swingline and Mead. Before Lyric Studio, work ran across several tools, and every time one study fed the next, the data had to be validated and transformed.

What changed with Lyric Studio:
• Demand, supply and transportation teams working in one platform at the same time
• Network, inventory and planning work in one place
• Cutting templates sent straight to the laser cutter

Next is container loading, where lifting fill rates from 75-80% toward 90-95% could save $300K to $500K in inbound costs. Pick path optimization follows, and then every operational decision inside the four walls of the distribution center. Vijay says the team has "barely scratched the surface."

More Stories

Suntory Global Spirits

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

Mondelēz International

One place to run every scenario: Mondelēz on 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.

ACCO Brands

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.