Commissioned Research
Top 10 Best Big Data Professional Services of 2026

GITNUXSOFTWARE REVIEW

Data Science Analytics

Top 10 Best Big Data Professional Services of 2026

Guide to top big data professional services with a comparison of Wipro, Deloitte, and Cognizant, focusing on fit for enterprise teams.

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

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of 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

Big data professional services firms help analysts and engineering operators design data platforms, integrate streaming and batch pipelines, and enforce governance with RBAC and audit logs across cloud and hybrid environments. This comparison helps decision makers weigh tradeoffs in engineering delivery, API and automation depth, and operating model fit for analytics, modernization, and AI enablement without turning delivery into guesswork.

Wipro is the best fit for big data professionals in enterprises that need managed delivery tied to governance, since its integrated approach connects metadata visibility, RBAC enforcement, and audit logging into production operations, while Slalom is the better alternative when modernization must pair engineering execution with governance-backed operating change from day one.

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

Wipro

Integrated governance deliverables that connect metadata visibility, RBAC enforcement, and audit logging into production operations.

Best for: Fits when enterprises need managed big data delivery that ties governance, pipeline automation, and operations together.

2

Deloitte

Editor pick

Program delivery that bundles ingestion, quality monitoring, lineage, and governance artifacts into one operating workflow.

Best for: Fits when enterprises need governed big data delivery across multiple teams and systems.

3

Cognizant

Editor pick

Large delivery organizations can industrialize workload orchestration across batch and streaming pipelines with integration-ready APIs.

Best for: Fits when enterprises need delivery capacity for big data modernization with governance and integration depth.

Comparison Table

1
WiproBest overall
enterprise_vendor
9.0/10
Overall
2
enterprise_vendor
8.7/10
Overall
3
enterprise_vendor
8.6/10
Overall
4
enterprise_vendor
8.5/10
Overall
5
enterprise_vendor
8.3/10
Overall
6
enterprise_vendor
7.7/10
Overall
7
agency
7.5/10
Overall
8
specialist
7.0/10
Overall
9
6.9/10
Overall
10
enterprise_vendor
6.7/10
Overall
#1

Wipro

enterprise_vendor

Wipro delivers data engineering, cloud transformation, analytics, governance, and managed technology services.

9.0/10
Overall
Features9.0/10
Ease of Use9.0/10
Value9.0/10
Standout feature

Integrated governance deliverables that connect metadata visibility, RBAC enforcement, and audit logging into production operations.

Wipro’s big data work most often fits buyers that need both platform build and run support across multiple environments, including migrations from on-prem to cloud or cross-cloud consolidation. Engineering engagements commonly cover workload orchestration, data quality monitoring, and ingestion design that supports schema evolution and change capture patterns. Governance deliverables typically include metadata catalog alignment and role-based access controls mapped to enterprise policy, with audit logging for traceability.

A tradeoff appears when organizations expect deep, product-specific data modeling work without tight governance collaboration, since success depends on defining ownership, standards, and operational runbooks. Wipro is a strong usage choice for program teams that need repeatable provisioning, API-driven integrations, and automation hooks for pipelines and data products.

Pros
  • +End-to-end delivery covering ingestion, orchestration, governance, and monitoring
  • +Integration-focused automation surface for pipeline and platform extensions
  • +Governed access patterns with audit logging and policy mapping
  • +Hybrid-to-cloud migration support for distributed data estates
Cons
  • –Favors governance maturity, which can slow early pipeline releases
  • –API and automation coverage depends on chosen platform scope
  • –Requires active data owner participation to finalize standards
  • –Operational handoff quality varies with engagement governance
Use scenarios
  • Data platform engineering teams

    Modernize batch pipelines with governance

    Lower pipeline failures and faster fixes

  • Chief data officers

    Establish federated governance at scale

    More consistent access and traceability

Show 2 more scenarios
  • Streaming analytics teams

    Productionize event ingestion and operations

    More stable event processing

    Wipro delivers stream processing builds with operational controls for throughput and late-arriving handling needs.

  • Hybrid migration program owners

    Move data workloads to cloud

    Reduced migration disruption

    Wipro manages cross-environment provisioning, orchestration, and governance continuity during migration waves.

Best for: Fits when enterprises need managed big data delivery that ties governance, pipeline automation, and operations together.

#2

Deloitte

enterprise_vendor

Deloitte delivers data strategy, engineering, analytics, governance, and industry transformation services.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Program delivery that bundles ingestion, quality monitoring, lineage, and governance artifacts into one operating workflow.

Deloitte typically supports big data programs that span data lakehouse and warehouse patterns, plus event-driven and batch ingestion designs, with an emphasis on lineage and metadata ownership. Delivery often includes data quality monitoring design, workload orchestration planning, and RBAC-aligned access workflows for enterprise roles. Integration depth is most visible when multiple enterprise systems must be connected into a single governed platform, including hybrid cloud and migration sequencing across existing estates.

A tradeoff shows up in speed to value because delivery requires decision-making around governance, target operating model, and migration sequencing. Deloitte works best when the organization already has a defined data architecture direction, and when stakeholders need documented controls and steady execution through complex release plans. Usage situations include rebuilding ingestion and transformation workflows, standing up governed catalogs, and standardizing operational monitoring across business domains.

Pros
  • +Governance-heavy delivery aligned to enterprise RBAC and audit expectations
  • +Integration planning across batch and event ingestion pathways
  • +Metadata and lineage focus for traceable data operations
  • +Scalable program orchestration for multi-team platform changes
Cons
  • –Requires strong internal decision-making and governance participation
  • –API and extensibility details depend on the delivery scope
  • –Engineering throughput can be slower during migration and control rollout
  • –Output quality varies with client ownership of requirements
Use scenarios
  • CIO and enterprise architecture

    Standardize governed platform across clouds

    Reduced control drift across teams

  • Data engineering leads

    Unify batch and event ingestion

    More consistent downstream quality

Show 2 more scenarios
  • Security and data governance teams

    Operationalize RBAC and audit logging

    Clear access and traceability

    Deloitte implements governance mappings so role permissions and audit evidence align to processes.

  • Analytics platform owners

    Harden metadata catalog and monitoring

    Faster issue localization

    Deloitte builds catalog and monitoring processes that support lineage-aware troubleshooting.

Best for: Fits when enterprises need governed big data delivery across multiple teams and systems.

#3

Cognizant

enterprise_vendor

Cognizant delivers data engineering, analytics, cloud migration, and industry-specific technology services.

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

Large delivery organizations can industrialize workload orchestration across batch and streaming pipelines with integration-ready APIs.

Cognizant is a fit for organizations that need managed end-to-end delivery across data platform builds and ongoing improvements, including pipeline development and operational handoff. Integration depth is usually strong when existing enterprise landscapes include multiple source systems, cloud and on-prem components, and identity-controlled environments that demand RBAC and audit logging. Governance controls tend to show up through metadata management processes, lineage capture expectations, and access policy alignment across environments.

A key tradeoff is that Cognizant often drives value through project structure and consulting delivery rather than through a single proprietary data product surface. Pipeline work can also require disciplined requirements intake to avoid rework when source semantics, data contracts, and orchestration expectations are not stabilized early. Cognizant is a practical option when the work includes platform modernization across distributed systems and recurring throughput requirements, not one-off analytics enablement.

Pros
  • +Integration-heavy delivery across enterprise sources and target platforms
  • +Governance-aligned pipeline operationalization with RBAC and audit expectations
  • +Strong orchestration focus for recurring batch and streaming workloads
  • +API-based integration support for pipeline-to-system connectivity
Cons
  • –Requires clear intake and data contracts to prevent pipeline rework
  • –Less suitable for teams seeking a single turnkey data product
Use scenarios
  • Enterprise data platform teams

    Modernize pipelines with governance controls

    Reduced operational incidents

  • Cloud migration programs

    Move data workloads across environments

    Faster platform cutovers

Show 1 more scenario
  • Integration engineering teams

    Connect pipelines to enterprise systems

    More consistent handoffs

    Cognizant implements API-based connectivity so pipelines can trigger downstream processes reliably.

Best for: Fits when enterprises need delivery capacity for big data modernization with governance and integration depth.

#4

Accenture

enterprise_vendor

Accenture provides large-scale data engineering, analytics, cloud, and artificial intelligence consulting.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Accenture’s delivery programs often standardize data delivery patterns across squads, including operational monitoring and governance guardrails.

Accenture brings enterprise-grade big data delivery through an integration-heavy services model, with governance, orchestration, and platform modernization treated as part of the same program. Teams typically get end-to-end work that links ingestion, transformation, and analytics deployments into production operating models.

Pros
  • +Programme delivery that coordinates ingestion, transformation, and production operations
  • +Strong governance through access control design, lineage practices, and audit-ready reporting
  • +Automation via CI/CD release workflows for data pipelines and platform components
  • +Integration breadth across major data platforms and enterprise systems
Cons
  • –Requires disciplined stakeholder alignment to avoid slow approvals and rework
  • –Extensibility depends on scoped accelerators and client-specific engineering capacity
  • –Advanced streaming outcomes need explicit design for event semantics and late data
  • –Operational maturity takes time to transition from consultancy to internal ownership

Best for: Fits when enterprises need coordinated big data modernization with governance, orchestration, and production readiness.

#5

Capgemini

enterprise_vendor

Capgemini provides data modernization, cloud engineering, analytics, and artificial intelligence consulting.

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

Capgemini structures delivery around operational controls and integration automation, reducing handoff gaps between ingestion, orchestration, and governed access.

Capgemini delivers big data consulting and managed delivery built around end-to-end platform engineering, from ingestion patterns to operationalization of analytics workloads. Teams typically get architecture, build, and integration help across distributed processing, data platform modernization, and enterprise integration with identity, security, and governance expectations.

Pros
  • +Integration delivery across processing, storage, and orchestration layers
  • +Strong governance alignment with RBAC expectations and audit-ready controls
  • +Automation-oriented provisioning supports repeatable environment rollout
  • +Lineage and metadata practices reduce handoffs between teams
Cons
  • –Complex deployments can require strong platform ownership internally
  • –Automation depth varies by stack choice and target cloud operating model

Best for: Fits when enterprises need managed build-and-integrate support across multiple big data components and governance controls.

#6

Infosys

enterprise_vendor

Infosys provides data modernization, engineering, analytics, governance, and cloud consulting services.

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

Infosys’ delivery model emphasizes operational automation for environment and orchestration handoffs across releases.

Infosys fits large enterprises and regulated teams that need end-to-end delivery across cloud data platforms, data engineering, and operations. Its work typically centers on building and migrating distributed pipelines, integrating data stores, and tying analytics outputs to managed runbooks.

Pros
  • +Enterprise-grade data engineering delivery with repeatable migration patterns
  • +Strong integration focus across cloud warehouses and lakehouse deployments
  • +Automation for environment and workload orchestration in operational workflows
  • +Governance alignment using metadata and access coordination across releases
Cons
  • –Automation and governance depth can add delivery overhead for smaller teams
  • –Complex architectures often require tighter client involvement for smooth handoffs

Best for: Fits when large enterprises need managed delivery across multi-system data integration and operational governance.

#7

Slalom

agency

Slalom delivers data strategy, cloud implementation, analytics, governance, and organizational change services.

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

Delivery teams routinely align data lineage, metadata usage, and operational ownership during implementation, not after go-live.

Slalom differentiates through engineering-heavy delivery for large data modernization programs, combining platform work with governance and operating model design. The firm typically supports workload orchestration, metadata-driven lineage practices, and production hardening for both batch and event-driven pipelines.

Pros
  • +Implementation patterns for production data pipelines across multiple teams
  • +Governance and operating model work tied to delivery, not only documentation
  • +Integration support for data platforms spanning ingestion through orchestration
  • +Strong attention to monitoring design for pipeline and dataset health
Cons
  • –Effective outcomes depend on client-side ownership for data standards
  • –Multi-workstream programs can extend timelines for stakeholder alignment
  • –Automation depth varies by practice area and client engineering maturity
  • –Complex schema evolution plans may require additional discovery cycles

Best for: Fits when data modernization needs both delivery execution and governance-backed operating change across engineering teams.

#8

EPAM

specialist

EPAM designs data platforms, distributed processing systems, analytics products, and cloud-native architectures.

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

Delivery orchestration that connects engineering work to governance artifacts like lineage and catalog workflows across releases.

EPAM pairs large-scale delivery teams with data engineering consulting across cloud and hybrid estates, which helps it handle end-to-end big data programs rather than isolated components. The company’s offerings commonly cover distributed ingestion and transformation buildout, data platform modernization, and operationalization through orchestration and quality practices.

Pros
  • +End-to-end big data delivery across ingestion, processing, and platform operations
  • +Strong integration support for existing cloud, on-prem, and mixed vendor stacks
  • +Mature implementation of governance artifacts such as lineage and catalog workflows
  • +Frequent automation through repeatable pipeline patterns and operational runbooks
Cons
  • –Quality and governance outcomes depend on internal stakeholder time and decision cadence
  • –Complex platform migrations can add delivery overhead beyond pure pipeline engineering
  • –API surface coverage varies by chosen engine and integration pattern
  • –Turnaround on niche extensions can require early architecture alignment

Best for: Fits when enterprises need multi-team big data delivery with governance, integration, and ongoing pipeline operations.

#9

Booz Allen Hamilton

specialist

Booz Allen Hamilton provides data engineering, artificial intelligence, analytics, and mission technology services.

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

Architecture and delivery governance designed to coordinate data engineering work across security, integration, and operational accountability.

Booz Allen Hamilton delivers big data and analytics consulting through end-to-end system design, implementation guidance, and program execution support for defense and government workloads. Teams engage for data pipeline modernization, data governance operating models, and architecture reviews that connect data platforms to delivery constraints like security reviews and integration timelines.

Pros
  • +Program-level delivery rigor for complex big data initiatives
  • +Governance and oversight practices tied to engineering workflows
  • +Strong integration support across legacy systems and cloud targets
  • +Clear architecture reviews for ingestion, processing, and data consumption paths
Cons
  • –Project engagement style can slow iterative pipeline experimentation
  • –Some implementations depend on client availability for access and approvals
  • –Detailed governance work can add overhead for small data footprints
  • –Automation artifacts may be less transferable without additional enablement

Best for: Fits when government-adjacent programs need governance-heavy big data modernization with delivery oversight.

#10

IBM Consulting

enterprise_vendor

IBM Consulting implements data platforms, artificial intelligence systems, cloud architectures, and analytics programs.

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

Delivery teams commonly structure pipeline operations with environment provisioning, monitoring integration, and governance-aligned rollout controls.

IBM Consulting delivers enterprise-grade big data and analytics delivery through systems integration, data engineering, and platform modernization across cloud and hybrid estates. Delivery is anchored in structured workstreams for architecture, ingestion, transformation, governance, and operations, with a focus on aligning platform capabilities to workload needs.

Pros
  • +Enterprise data platform delivery with end-to-end engineering and operational hardening
  • +Strong integration approach across hybrid environments and multi-vendor landscapes
  • +Governance and lineage support embedded into program workstreams
  • +Automation for environment provisioning and operational runbooks
Cons
  • –Program-driven delivery can slow time-to-first-value for narrow initiatives
  • –Requires strong client-side data ownership to define standards and governance
  • –Deep customization often increases coordination across platform and security teams
  • –May involve reliance on partner tooling for niche ingestion and streaming patterns

Best for: Fits when large enterprises need a managed big data program covering engineering, governance, and platform operations.

Conclusion

After evaluating 10 big data professional, Wipro 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
Wipro

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 Big Data Professional

Which firms focus on integrations and API contracts for big data programs?
Accenture and Cognizant typically build integration-heavy delivery with API-first patterns that connect ingestion, transformation, and downstream consumption. IBM Consulting and Capgemini also prioritize integration across environments, but IBM frames it around provisioning and operational rollout controls. When change control matters across many systems, EPAM often aligns integration deliverables with catalog and release workflows.
How do big data services handle SSO and access security across data platforms?
Wipro and Capgemini commonly tie governance deliverables to identity integration, so access policies stay consistent across ingestion and analytics stages. Deloitte and IBM Consulting usually include RBAC design in their operating model work and connect it to audit log collection for operational visibility. Booz Allen Hamilton adds security review coordination when workloads need governed changes tied to oversight constraints.
When does a data migration engagement become the primary workstream?
Infosys shifts the center of gravity to migration when distributed pipelines and runbooks must move between hybrid and cloud deployments without breaking orchestration. IBM Consulting and Accenture treat migration as a systems integration program when metadata, governance artifacts, and release coordination are required across teams. EPAM often takes migration as the core workstream when traceable handoffs between engineering and analytics teams depend on repeatable delivery cycles.
Which services are strongest at admin controls and production operations handoff?
IBM Consulting and Wipro often deliver admin controls as part of environment provisioning and operational monitoring integration, so governance enforcement continues after go-live. Slalom emphasizes production hardening with handoff artifacts that align lineage ownership and monitoring design to operational responsibility. Deloitte and Accenture add operating workflows that include governance artifacts plus audit-ready documentation linked to day-to-day operations.
Which providers support extensibility through reusable data delivery patterns?
Accenture and Slalom standardize delivery patterns across teams, which helps new data products follow an established data model and schema evolution approach. Capgemini and Cognizant focus on making integrations easier to extend through documented interfaces and API-based pipeline modernization. Wipro typically documents extensibility hooks so governed data products can add workloads without losing access control enforcement.
What breaks if integration and data contract work is delayed in a big data rollout?
When Deloitte delays data contract artifacts, data quality monitoring and metadata management often lag behind ingestion and transformation, which increases downstream reconciliation work. Accenture and Capgemini can also hit friction when cross-system interface definitions arrive late, since orchestration relies on agreed schemas and operational expectations. EPAM and IBM Consulting usually reduce this risk by sequencing lineage and catalog workflows with engineering releases instead of treating them as post-launch tasks.
How do large providers onboard teams that need automated provisioning and repeatable deployments?
IBM Consulting and Infosys commonly start with environment provisioning workflows, then map orchestration, monitoring hooks, and governance checks into repeatable releases. Accenture and EPAM often onboard by defining shared delivery patterns and operational monitoring expectations across squads to reduce handoff variance. Wipro typically adds runbook alignment so operations teams can manage batch and streaming workloads after deployment.
Which firms are best for multi-team delivery when governance spans engineering and oversight groups?
Booz Allen Hamilton and Deloitte frequently operate where governance must connect security reviews, integration timelines, and delivery oversight across many stakeholders. Accenture also fits when standardized delivery patterns must span squads while keeping audit log requirements aligned to rollout decisions. EPAM and IBM Consulting emphasize traceable delivery across release cycles, which supports governance processes that require consistent lineage and catalog updates.
What tradeoff occurs between heavy governance packaging and faster pipeline-only builds?
Capgemini and IBM Consulting often trade pipeline build speed for operational controls, so releases include environment provisioning, governance-aligned access, and monitoring integration. Cognizant can move faster when the scope centers on integration depth and API-based modernization, but it still adds governance alignment when multiple systems and handoffs are involved. Slalom generally slows early execution to align lineage, metadata usage, and operational ownership during implementation rather than after go-live.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Big Data Professional

Options differ in how they let big data professional work connect to data, automate runs, and keep results consistent over time. The biggest splits show up in integration depth, automation and API surface, and admin and governance controls—especially RBAC and audit log coverage.

Integration depth with data sources

Why it matters

Integration depth with data sources determines how much glue you build versus how much gets handled for you in real workflows. For big data professional work, that directly affects throughput and fewer dead ends during setup.

How to check

In the demo, ask them to connect the same sample dataset from at least two different source types and show the full path from ingestion to query. Confirm whether they document the connector behavior, required credentials, and supported transformations for each source.

Automation and API surface for pipelines

Why it matters

Automation and API surface matters because big data professional work often needs repeatable runs, parameterization, and controlled promotions across environments. Manual clicking breaks later when schedules and replays start.

How to check

Request an example workflow that runs on a schedule and accepts parameters (like date ranges) via an API or job definition. Then ask how you trigger re-runs, monitor run status, and capture run logs programmatically.

Data model clarity across processing stages

Why it matters

Data model clarity across processing stages reduces surprises when results move from raw inputs to curated outputs. For big data professional work, ambiguity here leads to mismatched fields, broken assumptions, and rework.

How to check

Use their sample project (or your own small schema) and trace one dataset through at least two stages. Check whether the interface shows the expected schema at each stage and whether it flags mismatches early.

RBAC and project scoping controls

Why it matters

RBAC and project scoping controls decide who can read, transform, and publish datasets and jobs. For big data professional work, wrong boundaries create both operational risk and audit gaps.

How to check

Ask for a demo with two roles: one limited to read and one allowed to run jobs. Verify you can restrict access to datasets, jobs, and outputs, and that permissions behave consistently across projects or workspaces.

Audit log detail for actions

Why it matters

Audit log detail for actions helps big data professional teams explain changes, debug incidents, and prove what happened when data or jobs shift. If logs are shallow, governance becomes guesswork.

How to check

Perform a controlled change in the demo (create a job, update a config, rerun a job) and then locate it in the audit log. Check whether the log includes actor, timestamp, object affected, and whether you can filter by project and job.

Operational handling of large jobs

Why it matters

Operational handling of large jobs affects how big data professional work meets deadlines without constant babysitting. You want predictable behavior during heavy runs and clear signals when something goes wrong.

How to check

Run a workload close to your typical scale (or the closest demo dataset) and ask what happens under load. Check for job states, progress indicators, cancellation behavior, and how retry or failure is documented in run history.

Red flags

  • Permissions look similar across roles, or restrictions only apply to the UI.
  • Audit logs omit the object and actor, making changes hard to trace.
  • The pipeline automation relies on manual steps or has limited API control for reruns.

Fit by situation

  • If we need to connect many upstream systems quickly, prioritize integration depth with data sources.
  • If we run scheduled jobs and want repeatable promotion across environments, prioritize automation and API surface for pipelines.
  • If we must control access and prove what changed during incidents, prioritize RBAC and project scoping controls.
Commissioned 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.