The work is the same work: coding, cleansing, harmonization, keeping the records readable by an agent. What changes is who holds the queue, who answers for coverage, and what happens in the weeks nobody on your side has time.
A catalog is not a project that finishes. Three things differ when the queue belongs to someone else.
A new item in your list is identified and worked without anyone on your side opening a ticket. Backlog stops being a thing you plan around.
Quality is not asserted. A reference set is built for your products and your attributes, every model is measured against it before delivery, and the metrics are agreed with you up front.
Coverage is measured against your own product list, so the quarterly question becomes what the catalog looks like rather than how many hours went into it.
Each of these runs on its own if you would rather keep the queue. Managed Catalog is the same four held to a standing commitment.
Plenty of teams want the data without handing over the queue. That is the same work, delivered as a feed you run yourself.
Take the attributes Harmonya already maintains, deepen the ones you own, or compute a definition you set. Same record, delivered into your stack.
Thirty minutes on your categories. How the attributes get built, and the questions your team could put to them.