Vendor-funded research
Top 10 Best Music Rights Management Services of 2026

GITNUXSOFTWARE ADVICE

Legal Professional Services

Top 10 Best Music Rights Management Services of 2026

Compare music rights management services for licensing and royalties, with editorial notes for teams choosing between Songtrust, BMI, and PRS for Music.

19 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Gitnux editors write the brief first: the topic, the inclusion rules, and the frame for what belongs.

02Source Research

Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

Music rights management services sit between catalog data and royalty payments by administering publishing and performance rights, issuing licenses, and routing usage and claims through standardized data models that support audit-ready reporting. This comparison helps analysts, operators, and technical teams weigh licensing coverage, royalty workflow automation, API and integration depth, and IP enforcement operations such as audit logs, RBAC, and extensible provisioning.

Songtrust is the best overall pick for publishing teams that need consistent split-aware administration and cleaner royalty settlement outputs, thanks to its mapping of repertoire and work ownership details into structured reporting workflows, while BMI is the stronger alternative for ongoing licensing and performance royalty cycles that require steady rights record governance.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Songtrust

Repertoire and split-led administration workflows that map ownership details into royalty settlement support outputs.

Best for: Fits when publishing catalogs need consistent administration, split governance, and reporting outputs for royalty workflows.

2

BMI

Editor pick

Recurring publishing and neighboring-rights administration workflows that keep rights records aligned for royalty statements across cycles.

Best for: Fits when licensing and royalty administration require steady publishing-rights governance and consistent reporting cadence.

3

PRS for Music

Editor pick

Performance-rights licensing and royalty distribution tied to PRS repertoire administration and contributor statementing routines.

Best for: Fits when venues or broadcasters need reliable performance-rights licensing and royalty reporting alignment.

Comparison Table

1
SongtrustBest overall
specialist
9.3/10
Overall
2
enterprise_vendor
8.9/10
Overall
3
enterprise_vendor
8.6/10
Overall
4
enterprise_vendor
8.3/10
Overall
5
specialist
8.0/10
Overall
6
enterprise_vendor
7.7/10
Overall
7
enterprise_vendor
7.5/10
Overall
8
enterprise_vendor
7.0/10
Overall
9
6.9/10
Overall
10
enterprise_vendor
6.7/10
Overall
#1

Songtrust

specialist

Songtrust administers music publishing rights and collects performance, mechanical, and other royalties.

9.3/10
Overall
Features9.3/10
Ease of Use9.4/10
Value9.2/10
Standout feature

Repertoire and split-led administration workflows that map ownership details into royalty settlement support outputs.

Songtrust is designed for rights holders that need publishing-rights administration work to run from repertoire registration through royalty statement support and internal reconciliation. Its operational model typically fits organizations that already maintain work and recording identifiers and want a partner that can translate those details into usage and settlement-ready data outputs. Reported delivery workflows align best with teams that need governance over ownership splits and chain-of-title inputs feeding into royalty matching and reporting.

The main tradeoff is that deep control over every step usually depends on providing clean metadata and maintaining split-sheet accuracy before administration work begins. Songtrust fits situations where ongoing catalog administration matters more than one-off licensing, such as managing a steady pipeline of releases that require consistent rights registration and royalty operations.

Pros
  • +Structured publishing administration tied to work and split documentation
  • +Metadata-to-reporting workflows that reduce manual royalty reconciliation
  • +Operational support for rights registration through statement-ready outputs
  • +Governance focus on ownership splits feeding royalty routing
Cons
  • –Requires disciplined metadata and split-sheet hygiene to avoid rework
  • –Automation depth depends on integration scope and catalog complexity
  • –Some governance steps shift responsibility back to the rights holder
  • –Reporting workflows can feel process-heavy for small one-catalog teams
Use scenarios
  • Independent labels

    Administer publishing across new releases

    Lower manual settlement workload

  • Publishing rights holders

    Maintain split accuracy for matching

    Fewer split-related disputes

Show 2 more scenarios
  • Music licensing teams

    Deliver structured rights reporting

    More predictable reporting cycles

    Songtrust supports standardized reporting outputs tied to administered repertoire for licensing and usage reconciliation.

  • Royalty operations teams

    Reduce reconciliation across catalogs

    Faster internal reconciliation

    Songtrust reduces manual mapping by translating administration inputs into settlement-ready reporting artifacts.

Best for: Fits when publishing catalogs need consistent administration, split governance, and reporting outputs for royalty workflows.

#2

BMI

enterprise_vendor

BMI licenses public performances and distributes performance royalties for affiliated songwriters and publishers.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Recurring publishing and neighboring-rights administration workflows that keep rights records aligned for royalty statements across cycles.

BMI supports end-to-end administration from rights data intake through usage reporting handling and royalty output cycles for publishing-related rights. The service is strongest when ongoing repertoire coverage and recurring statement production matter more than one-off deals, because the workflows are designed to run repeatedly against the same catalogs. It also fits organizations that need consistent territory and term handling in their operational rhythm, including when multiple parties touch the same registrations.

The main tradeoff is that BMI’s workflow depth favors structured intake and standardized operational processes, so teams with highly idiosyncratic metadata formats may spend more effort mapping before value is realized. BMI is a good fit when the organization can commit to steady governance on rights splits and contributor assignments, since downstream matching and reporting depend on those decisions staying consistent.

Pros
  • +Administration workflows built for recurring publishing and neighboring-rights cycles
  • +Strong operational handling of rights records that supports consistent royalty output
  • +Catalog reference data focus supports territory and term alignment
  • +Governance-oriented approach helps keep splits consistent for matching
Cons
  • –Requires structured rights and usage data mapping to avoid downstream mismatches
  • –Integration and automation depend on fit with BMI’s operational workflow assumptions
Use scenarios
  • Music publishers operations teams

    Manage publishing rights and royalty cycles

    More consistent royalty output

  • Record labels rights managers

    License and administer neighboring rights

    Lower friction in administration

Show 2 more scenarios
  • Collective management liaison teams

    Coordinate territory and term handling

    Fewer territory mismatches

    BMI’s catalog and territory alignment supports repeatable handling of registrations tied to specific terms.

  • Royalty finance and reporting teams

    Produce governance-ready royalty statements

    Cleaner reconciliation cycles

    BMI’s operational posture supports governance around contributor splits to reduce downstream reconciliation work.

Best for: Fits when licensing and royalty administration require steady publishing-rights governance and consistent reporting cadence.

#3

PRS for Music

enterprise_vendor

PRS for Music licenses public performance and mechanical rights and distributes royalties to members.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Performance-rights licensing and royalty distribution tied to PRS repertoire administration and contributor statementing routines.

PRS for Music operates as a collective management organization that administers performance rights, manages member and rights-holder interests, and processes licensing and royalty distributions tied to public performance usage. It is distinct for the depth of its repertoire administration and the operational routines that connect performance data inputs to royalty statements for rights-holders and writers. Fit is strongest for organizations that need standardized performance-rights coverage and predictable reporting cycles rather than fully bespoke rights administration.

A key tradeoff is that PRS for Music workflows center on performance rights administration, so teams with heavy master recording, mechanical, or synchronization administration needs may still need other counterpart processes. Usage situations where the tradeoff is manageable include venue licensing and broadcaster licensing where performance-rights scope aligns with PRS coverage. Teams also benefit when they can integrate usage reporting data in the formats PRS expects for reconciliation and distribution.

Pros
  • +Mature performance-rights licensing and royalty distribution operations
  • +Strong repertoire administration for writers and publishers in its remit
  • +Consistent reporting cycles for rights-holders receiving statements
  • +Established governance through a structured membership model
Cons
  • –Limited scope for master recording and mechanical rights administration
  • –Setup for data feeds must align with PRS usage reporting expectations
  • –Less suitable when granular chain-of-title control is required end-to-end
  • –Automation depth is concentrated on distributions rather than custom tooling
Use scenarios
  • Music licensing operations teams

    Venue performance licensing under PRS repertoire

    Reduced reconciliation workload

  • Broadcaster rights managers

    Performance royalty flows for aired music

    More predictable royalty statements

Show 1 more scenario
  • Publishing administrators

    Contributor royalty administration through PRS

    Fewer downstream disputes

    Rights-holder statements reflect PRS-managed repertoire administration processes.

Best for: Fits when venues or broadcasters need reliable performance-rights licensing and royalty reporting alignment.

#4

ASCAP

enterprise_vendor

ASCAP licenses public performances and distributes performance royalties to songwriter and publisher members.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Work administration within a collective performance-licensing system that consistently connects public-performance usage categories to royalty processing.

ASCAP is the collection-management organization that administers performance royalties for music works, with member-driven governance and established repertoire coverage across U.S. public-performance channels. Its core capability is performance reporting support that feeds royalty processing based on declared and observed usage categories.

Pros
  • +Strong performance-royalty administration and repertoire coverage for public uses
  • +Rights-holder workflows for work representation within ASCAP’s administration model
  • +Predictable licensing and reporting categories aligned to performance monitoring
  • +Member governance and policy structure tailored to collective licensing operations
Cons
  • –Limited fit for master-recording workflows and direct synchronization licensing needs
  • –Metadata requirements around work identification can be time-consuming to keep consistent
  • –API and automation access is not oriented around custom data pipelines
  • –Territory and media restrictions still require manual handling for complex licensing deals

Best for: Fits when music rights teams need dependable performance licensing and royalty administration under ASCAP’s representation model.

#5

Music Reports

specialist

Music Reports provides mechanical licensing, rights administration, royalty processing, and music-use reporting.

8.0/10
Overall
Features8.0/10
Ease of Use8.0/10
Value8.0/10
Standout feature

Managed workflow orchestration that ties together licensing inputs, rights splits, and royalty administration outputs for continuing statement cycles.

Music Reports handles rights management operations for music catalogs, including licensing workflow support and royalty administration coordination. The service is oriented around music-rights data capture, rights party mapping, and usage-to-royalty processing inputs needed for downstream statements and payments.

Pros
  • +Operational focus on licensing and royalty administration workflows
  • +Structured handling for rights ownership splits and party mapping
  • +Catalog reporting cadence supports ongoing royalty statement cycles
  • +Clear handoffs from usage inputs to royalty processing artifacts
Cons
  • –Automation and API surface are not a primary part of the offering
  • –Workflow quality depends on rights data completeness and cleanup
  • –Governance controls require disciplined onboarding and catalog setup
  • –Reporting customization has less breadth than highly configurable admin suites

Best for: Fits when teams need hands-on administration for licensing and royalty workflows with consistent rights-party mapping.

#6

ICE Services

enterprise_vendor

ICE Services provides music copyright administration, licensing, usage processing, and royalty distribution.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

Rights conflict workflow support that coordinates ownership splits to reduce misallocated claims across recording and work relationships.

ICE Services supports music rights administration and licensing workflows with an emphasis on tracking rights ownership splits and usage reporting so royalty processing can stay consistent. It also covers rights conflict resolution support that maps deliverables to the right parties across works and recordings. The service is geared toward operational teams that need structured metadata delivery and audit-ready documentation for recurring royalty cycles and licensing activity.

Pros
  • +Strong split-sheet handling for rights ownership and payout alignment
  • +Usage reporting workflows that connect reporting to royalty statements
  • +Rights conflict resolution support for multi-party claims
  • +Documented deliverable structure for metadata handoffs
Cons
  • –Integration depth requires detailed metadata mapping work up front
  • –Automation coverage depends on how licenses and usage are fed into operations
  • –Governance controls feel service-led rather than self-serve for edge cases
  • –Throughput during peak royalty windows can be scheduling sensitive

Best for: Fits when a music rights team needs split-aware administration and managed reporting-to-royalty workflows.

#7

SoundExchange

enterprise_vendor

SoundExchange collects and distributes U.S. digital performance royalties for sound recordings.

7.5/10
Overall
Features7.5/10
Ease of Use7.5/10
Value7.5/10
Standout feature

Centralized digital performance royalty collection and distribution for sound recordings through participation-driven reporting and royalty accounting.

SoundExchange manages the collection and distribution of digital performance royalties for sound recordings, including reporting intake, royalty statement generation, and payment workflows tied to participating entities. It is distinct for its role as a collective management organization focused on neighboring-rights style digital performance flows for recorded music rather than direct licensing for every use case.

Pros
  • +Proven digital performance royalty collection and distribution workflow
  • +Clear participation and reporting expectations for participating entities
  • +Structured repertoire onboarding tied to royalty accounting operations
  • +Operational focus on consistent royalty statements and payments
Cons
  • –Narrower scope than licensing-first providers for broader rights grants
  • –Integration expectations can require careful data readiness from submitters
  • –Usage-to-royalty matching depends heavily on correct identifier inputs
  • –Automation depth and extensibility are less visible than API-centric vendors

Best for: Fits when rights holders or platforms need dependable digital performance royalty administration.

#8

PPL

enterprise_vendor

PPL licenses recorded music use and distributes neighboring rights royalties to recording rightsholders and performers.

7.0/10
Overall
Features7.0/10
Ease of Use7.0/10
Value7.0/10
Standout feature

Usage data to royalty allocation workflow for sound recordings, built around PPL repertoire administration and contributor statement cycles.

PPL is a music rights management organization that coordinates licensing and royalty administration for recorded music and related rights, with catalog and rights administration grounded in established UK industry workflows. PPL’s operational focus centers on collecting usage data from broadcasters and platforms, matching it to repertoire and rights information, and issuing royalty statements tied to performance of sound recordings.

Pros
  • +High-throughput usage reporting processing for sound recordings
  • +Clear repertoire-based administration aligned to collective licensing workflows
  • +Structured rights documentation flow across participating rights owners
  • +Institutional governance familiarity with UK collective administration norms
Cons
  • –Limited flexibility for custom licensing and reporting models
  • –Metadata reconciliation depends on timely, accurate supplier data
  • –External program-level automation is less developer-friendly than API-led peers
  • –Territory and term constraints can create multi-channel reporting overhead

Best for: Fits when UK-focused sound recording licensing and royalty administration needs high-volume, governed processing.

#9

The Mechanical Licensing Collective

enterprise_vendor

The MLC administers blanket mechanical licenses and distributes eligible U.S. digital audio mechanical royalties.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

Statutory mechanical administration through a collective management process that reconciles rights entitlements with reported usage.

The Mechanical Licensing Collective administers mechanical licensing for U.S. repertoire by coordinating rights, usage data, and royalty flows that connect publishers and service providers. It is distinct from agency-style licensing because it operates as a collective management organization with a standardized process for mechanical royalty administration.

Pros
  • +Designed for mechanical royalty administration at collective-management scale
  • +Structured licensing intake supports consistent rights and usage reconciliation
  • +Governance model clarifies responsibilities in mechanical royalty workflows
  • +Metadata and identifier usage helps reduce ambiguity in entitlement mapping
Cons
  • –Usage and metadata requirements demand careful pre-processing
  • –Workflow depth is mechanical-focused rather than cross-rights orchestration
  • –Operational troubleshooting often depends on domain-specific royalty knowledge
  • –Integration complexity rises when data formats do not match expected identifiers

Best for: Fits when organizations need reliable U.S. mechanical royalty administration across large catalogs and frequent usage reporting.

#10

Kobalt

enterprise_vendor

Kobalt provides music publishing administration, copyright management, licensing, and royalty collection.

6.7/10
Overall
Features6.7/10
Ease of Use6.7/10
Value6.7/10
Standout feature

Catalog-scale rights reconciliation that links enriched metadata to licensing and recurring royalty reporting outputs.

Kobalt focuses on rights management for music catalogs with workflow support for both licensing operations and royalty processing. Its differentiator is automation around metadata enrichment, rights ownership administration, and catalog-scale reconciliation tied to recordings and works.

Pros
  • +Strong metadata and catalog reconciliation workflows for ongoing rights administration
  • +Operational reporting designed for recurring royalty statement production
  • +Licensing and rights administration process coverage spans multiple rights contexts
  • +Extensibility supports integrations that fit catalog-heavy organizations
Cons
  • –Governance expectations are high when ownership splits and territories are complex
  • –UI workflow depth can require training for teams managing large filing volumes
  • –Automation output quality depends on clean intake metadata and identifier discipline
  • –API and configuration details can take time to align with internal reporting models

Best for: Fits when catalog owners or administrators need consistent metadata-driven rights administration at scale.

Conclusion

After evaluating 10 music rights management, Songtrust stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Songtrust

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Music Rights Management

How do ASCAP and PRS for Music differ in how they handle performance-rights licensing workflows and royalty distribution inputs?
ASCAP anchors operations around performance categories and works under its administration, then routes the usage categories into royalty processing and statement support. PRS for Music runs performance-rights licensing and contributor-focused distribution around PRS repertoire onboarding and usage reporting routines, with member-governed statementing as the core cadence.
Which service providers handle split-aware administration when rights ownership splits affect work and recording relationships?
ICE Services focuses on tracking ownership splits and supporting rights conflict resolution so royalty processing maps deliverables to the correct parties across works and recordings. Songtrust also centers on work splits and royalty routing, using end-to-end repertoire ingestion and rights confirmation workflows to keep royalty settlement outputs aligned to recorded ownership details.
How do Kobalt and Music Reports approach metadata normalization for rights parties, territories, and downstream royalty statements?
Kobalt emphasizes metadata enrichment and catalog-scale reconciliation that links enriched metadata to licensing inputs and recurring royalty reporting outputs. Music Reports emphasizes operational data capture and rights party mapping so licensing and usage-to-royalty processing stays consistent for continuing statement cycles, with integration depth driven by reporting formats and governance expectations.
Which providers are most operationally aligned with high-volume digital performance royalty processing for sound recordings?
SoundExchange focuses on digital performance royalties for sound recordings through participation-driven reporting intake, royalty statement generation, and payment workflows. PPL centers on collecting usage data from broadcasters and platforms, matching it to repertoire and rights information, then issuing royalty statements tied to recorded-music performance conventions in its UK-aligned processing model.
What data model and identifier coverage matters most for statutory mechanical administration in the U.S.?
The Mechanical Licensing Collective operates on reconciliation between work and recording identifiers, metadata delivery, and usage reporting inputs so split entitlements align to royalty flows. ICE Services and Songtrust also work with identifier-linked administration, but MLC is shaped around the statutory mechanical process and standardized reconciliation between entitlements and reported usage.
How do onboarding and delivery expectations differ between collective-management workflows and catalog administration services like BMI and Songtrust?
BMI runs steady publishing and neighboring-rights administration with recurring reporting cadence and rights-governance posture designed for administration rather than ad hoc licensing requests. Songtrust runs repertoire ingestion, rights confirmation workflows, and structured reporting outputs for rights holders, so onboarding often centers on catalog-scale metadata and split governance rather than membership-based representation.
What automation patterns and throughput constraints commonly appear in catalog-scale reconciliation, and which services address them?
Kobalt is built around automation for metadata enrichment, rights ownership administration, and catalog-scale reconciliation tied to recordings and works, which supports sustained throughput during recurring royalty cycles. Music Reports can sustain recurring statement workflows through managed orchestration of licensing inputs, rights splits, and administration outputs, but its integration depth and governance expectations can limit throughput when catalog identifiers and reporting formats do not match its operational assumptions.
When rights conflict resolution becomes unavoidable, how do ICE Services and Songtrust differ in their conflict-handling workflows?
ICE Services provides rights conflict workflow support that coordinates ownership splits and maps deliverables to the correct parties across works and recordings. Songtrust emphasizes rights confirmation workflows during repertoire ingestion and split governance, so conflicts often surface as data normalization and confirmation gaps that must be resolved before royalty routing.
How should teams plan security controls and RBAC for access to rights records and audit trails with these providers?
ASCAP and PRS for Music run member and rights-holder governance models, so access controls typically follow representation and contributor structures alongside usage-category processing controls. Songtrust and ICE Services support rights-management operations with rights party mapping and structured outputs, so teams should verify that role-based access control, provisioning, and audit log coverage align to who can edit rights records, confirm split details, and approve deliverables.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Music Rights Management

We look for music rights management options that differ most in how they license, administer, and report rights in practice—especially around data model and reporting auditability. The biggest separation usually shows up in how well an option handles rights territory handling and rights status workflow transitions from request to outcome.

Licensing workflow automation

Why it matters

Licensing workflow automation matters because music rights management often turns requests into approvals, conditions, and outcomes. If automation is thin, teams end up re-keying and risking mismatches between what was licensed and what was tracked later.

How to check

In the demo, start a licensing request and walk it through to an approval or denial outcome. Ask whether the system generates the downstream actions (contracts/permissions records, task assignments, and required fields) without manual copying.

Rights status workflow states

Why it matters

Rights status workflow states matter because rights change over time, and the system must reflect that for correct licensing and reporting. Clear states reduce the chance that a track is treated as available when it is pending or disputed.

How to check

Ask the provider to show a rights item moving through at least three states (for example, available, under review, and inactive). Confirm what fields change, what users can edit in each state, and how the audit log records those transitions.

Rights data model and schema extensibility

Why it matters

The rights data model and schema extensibility matter because music rights information is messy and varies by catalog and use case. A flexible model helps you represent conditions, roles, and exceptions without building spreadsheets that break later.

How to check

Request a sample import template and try mapping one of your real catalog samples (one work or one recording plus roles). Ask whether custom attributes or fields can be added without vendor work, and show how those fields appear in search and reporting.

Rights territory handling and use constraints

Why it matters

Territory handling and use constraints matter because licensing outcomes depend on where and how content is used. If territory and constraints are modeled poorly, the system may generate permissions that are too broad or too narrow.

How to check

Create or edit a license grant with multiple territories and at least two different usage constraints. Then run a scenario search to verify the system returns the correct permissions per territory and use type.

Reporting audit log for outcomes

Why it matters

Reporting audit log for outcomes matters because music rights management output is often challenged during reconciliation. A trustworthy audit trail links decisions, input changes, and the resulting reports users share.

How to check

Generate a report for a small test set and then trace from one reported line item back to the originating request and its approval history. Confirm what changed, who changed it, when it changed, and whether report regeneration reflects those changes.

Red flags

  • Rights requests require lots of manual copying between screens to produce a valid outcome
  • Rights states change but don’t lock fields or record the reasoning consistently
  • Reports can’t be traced back to the exact request inputs and approval history

Fit by situation

  • If we must process many licensing requests with consistent approvals, prioritize Licensing workflow automation.
  • If we manage catalogs where rights availability changes frequently, prioritize Rights status workflow states.
  • If stakeholders will review reports for reconciliation and disputes, prioritize Reporting audit log for outcomes.
Vendor-funded research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.