Product & Product Class in Asset Management: How Many Products Do You Actually Manage?
Ask any asset manager how many products they manage, and you’ll get an immediate answer. Ask three of their systems the same question, and you’ll often get three different numbers.
A single investment strategy rarely goes to market in a single form. It gets wrapped for different investors, priced in different currencies, and structured for different jurisdictions. What looks like one product is often five. Sometimes fifteen. Sometimes fifty. Even in a single product master, those records rarely line up: categorized inconsistently, with nothing tying them to a common strategy. So every number built across them inherits the drift.
Where the Number Comes Apart
Look across a real book of business and the gap widens fast. A firm that says it manages two hundred products is, in operational reality, running several times that many product classes. That is where the numbers actually live: each class has its own valuation, its own identifiers, its own currency, and so on.
When those classes are categorized inconsistently, nothing rolls up cleanly. Ask for AUM by strategy, flows by vehicle, or sales credited to the right product, and you get answers that don’t reconcile. The cost of a broken product structure isn’t one failure; it’s steady operational drag, and decisions made on numbers no one fully trusts.
The Difference Between a Product and a Product Class
The fix starts with a distinction that sounds obvious once you see it but almost never shows up cleanly in legacy systems.
A Product is a strategy delivered through a specific vehicle. The strategy is the underlying investment idea; the vehicle is the legal and operational wrapper that makes it sellable, such as a mutual fund, an SMA, a UCITS, or a CIT.
The consequence is the part that matters: the same strategy delivered through two vehicles is two Products. Each one carries its own universal attributes: name, style/objective, asset class, manager, base currency, domicile, etc.
A Product Class is the actual purchasable version of that strategy and vehicle: a mutual fund’s share class (say, Class A USD or Class I EUR), an SMA’s individual account, a CIT’s unit class. Each Product Class carries its own pricing history, its own start date, its own identifiers.
Simply put, the Product is the what, and the Product Class is the how. One Product, many Product Classes. It’s a clean parent-child relationship that mirrors business reality instead of forcing the business to fit the data model. That relationship is your product hierarchy, and getting it right is what your downstream reporting depends on.
What a Single Strategy Actually Spans
Picture an active equity strategy your firm offers today and ask how many products it really is. Usually more than one: a mutual fund, an ETF, a UCITS for European clients, an SMA, etc. That’s four distinct Products, each with its own Product Classes underneath (the mutual fund’s share classes, the UCITS’s own, each SMA account a class in its own right).
To the business, that’s one strategy in four forms. In the data, it’s usually four records that were set up separately and categorized inconsistently, with nothing marking them as the same strategy. So there’s no clean way to see the strategy whole, whether you’re after total assets across all four, flows by vehicle, or where the growth is coming from. Four expressions of one strategy, and nothing in the data says so.
The Fix: Separate for Accuracy, Aggregate for the Whole Picture
The reliable fix isn’t a reconciliation workflow or a monthly cleanup ritual. It’s modeling products and classes correctly from the start, and the rule is simple: one Product per strategy-and-vehicle combination, one Product Class per purchasable version, every relationship explicit.
This structure represents each vehicle and each purchasable version as its own record, carrying its own attributes, so nothing gets averaged into a single inaccurate number, and because the parent-child relationships are explicit, every product class rolls back up cleanly to its product whenever you need the whole picture.
Separation gives you accuracy; explicit relationships give you the rollup. You stop having to choose between the granular detail and the rolled-up total, because the structure holds both without one distorting the other. That flexibility carries downstream, too: in CRM integrations, you can choose to report financial data at the product or the product class level, with nothing left to reconcile between the two.
Once that’s in place, the outcomes stop being promises and start being properties of the structure:
- AUM attributes to the right product, vehicle, and strategy
- Flows and sales attribution roll up cleanly across vehicles
- Figures that were never comparable stay separate, instead of getting averaged together
A Practitioner’s Perspective
For years, a firm could get away with a loose product structure because the multi-vehicle reality was the exception. That is no longer true.
Assets are shifting from mutual funds to ETFs. Firms are launching active ETF versions of their flagship strategies. The one-strategy-many-forms pattern isn’t an edge case anymore. It’s becoming the default shape of the business.
Structural problems tend to surface as reporting problems. I’ve seen it break analytics dashboards, monthly reports, and CRM data alike, and how a firm models its products is one of the clearest examples.
The fix isn’t complicated. It’s architectural. When every strategy-and-vehicle combination is modeled as its own Product and every purchasable version as its own Product Class, the ambiguity disappears. Teams stop second-guessing their own numbers, and instead of validating spreadsheets and reconciling exceptions, they get back to the work that actually moves distribution forward.
So it’s worth sitting with one of the simplest questions your firm can ask. When you say you manage two hundred products, what are you actually managing? And can your data answer?
You can’t solve the Omni Challenge if you can’t see your products clearly. That’s how a question this basic, what do we offer, finally stops being a guess.
Continue the series
This is the latest entry in our ongoing look at the friction points slowing modern distribution — from solving data fragmentation in asset management and building accurate AUM reporting to account attribution across distribution.
Each one is a layer of the same thing: a deterministic data foundation — governed, auditable, and canonical — that your reports, and increasingly your AI, have to trust before they can act on it. Because solving the Omni Challenge doesn’t happen all at once. It happens one problem at a time.
How many products do you actually manage? Find out.
Request a demo and see how Synfinii models every strategy-and-vehicle combination as its own Product and every purchasable version as its own Product Class — so the count is finally unambiguous and every number rolls up cleanly.
About Synfinii
Synfinii partners with asset managers worldwide to enable data-driven distribution by mastering data, integrating intelligence, and building solutions that help achieve your business objectives. Excellence in client service, deep industry knowledge, technical strength, and extraordinary teamwork have defined us for over 40 years.
Synfinii—our brand since September 2025—was previously known as SalesPage.