GITNUXSOFTWARE ADVICE
Business Process OutsourcingTop 10 Best Process Mapping Services of 2026
Top 10 best Process Mapping Services ranked by fit, BPMN workflows, automation, and reporting, with provider notes on QPR, Celonis, IBM Consulting.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
QPR
Governed process modeling with schema-controlled element types and relationships tied to lifecycle states.
Built for fits when enterprises require governed process mappings integrated with automation systems..
Celonis
Editor pickConformed process data model that standardizes activities and case structure across mappings.
Built for fits when enterprises need governed process mapping backed by strong integrations and automation..
IBM Consulting
Editor pickGovernance-led process mapping that connects diagrams to API-driven automation and audited change control.
Built for fits when enterprise process maps must drive execution, APIs, and audited governance..
Related reading
- Business Process OutsourcingTop 10 Best Business Process Mapping Services of 2026
- Business Process OutsourcingTop 10 Best Business Process Modeling Consulting Services of 2026
- Digital Transformation In IndustryTop 10 Best Business Process Automation Services of 2026
- Business FinanceTop 10 Best Process Mapping Software of 2026
Comparison Table
The comparison table evaluates process mapping service providers by integration depth, data model design, and the automation and API surface exposed for schema mapping, provisioning, and extensibility. It also benchmarks admin and governance controls, including RBAC, audit log coverage, configuration management, and sandbox support to assess throughput and operational control under load.
QPR
enterprise_vendorProcess mapping and process management consulting that delivers executable process documentation, governance controls, and automation-ready process models for operational teams.
Governed process modeling with schema-controlled element types and relationships tied to lifecycle states.
QPR maps processes into a structured model that can be configured for consistent element types, relationships, and lifecycle states. Integration depth is strongest when teams need process artifacts to connect to reporting, analysis, and workflow execution rather than remain as static diagrams. The automation and API surface supports schema-driven provisioning workflows so process updates can flow from external sources. Admin and governance controls support RBAC-style access patterns and operational traceability through audit log capabilities.
A key tradeoff is that deeper schema control can require tighter process discipline so model governance stays consistent across business units. QPR fits best when an enterprise needs high throughput of process changes and expects repeatable provisioning, validation, and publication of updated process models. Use cases also work well when mapping must stay synchronized with operational systems that can call into the API for updates.
- +Schema-driven process model supports consistent mapping and validation
- +API and automation surface supports provisioning and integration workflows
- +Governance controls include RBAC patterns and audit-oriented visibility
- +Extensibility fits setups that need model-to-workflow connectivity
- –Schema governance increases onboarding and process-design effort
- –Integration work can require careful alignment of external data mapping
- –Automation configurations demand disciplined lifecycle management
Process excellence teams
Maintain governed maps across business units
Fewer mapping inconsistencies
IT integration teams
Provision process models via API
Automated model updates
Show 2 more scenarios
GRC and compliance teams
Track changes and approvals
Stronger change traceability
Apply RBAC and audit-oriented features to control access and monitor model changes.
Operations leadership
Connect process models to execution
Faster operational alignment
Integrate process artifacts into workflow and reporting so process changes reflect in operations view.
Best for: Fits when enterprises require governed process mappings integrated with automation systems.
More related reading
Celonis
enterprise_vendorProcess mining and process mapping delivery that produces process maps aligned to execution events, with integration patterns for data models, APIs, and workflow automation.
Conformed process data model that standardizes activities and case structure across mappings.
Celonis fits teams that need process mapping grounded in high-fidelity event data and traceable governance. The data model links activities, process instances, and case context to support end-to-end mapping views and drill-down analysis without manual spreadsheet reconciliation. Integration depth covers both native connectors and extensibility options that can bring external systems into the same schema.
A key tradeoff is that correct mapping depends on data model configuration and event semantics such as case identifiers and activity definitions. Teams typically use Celonis when throughput and governance matter, such as rolling out process maps across departments with shared controls like RBAC and audit log evidence. Automation is most effective when APIs and workflow hooks are used to standardize updates to mappings and downstream actions from the same curated model.
- +Governed RBAC and audit logs for mapping changes
- +Configurable data model ties cases, activities, and context
- +Extensible integration surface with documented APIs and automation hooks
- –Process mapping accuracy hinges on case and activity semantics
- –Model and schema configuration adds upfront admin overhead
Operations excellence leaders
Standardize end-to-end process maps
Consistent mapping across sites
Data engineering teams
Connect event streams into schema
Lower manual data staging
Show 2 more scenarios
Enterprise automation architects
Trigger workflows from process insights
Repeatable operational execution
Uses APIs and automation interfaces to push actions tied to mappings.
Process governance teams
Control publishing and changes
Traceable approvals and rollbacks
Applies RBAC and audit logs to manage who can change mappings.
Best for: Fits when enterprises need governed process mapping backed by strong integrations and automation.
IBM Consulting
enterprise_vendorBusiness process engineering and process mapping programs that define process architecture, target state models, and integration requirements for outsourcing governance.
Governance-led process mapping that connects diagrams to API-driven automation and audited change control.
IBM Consulting is a strong fit for process mapping work that must connect process schemas to execution services. Integration depth tends to cover workflow engines, enterprise applications, and data platforms through defined interfaces. Automation design is typically framed around API contracts, configuration management, and deployment controls that support repeated throughput without manual diagram rewrites.
A tradeoff appears when a process mapping effort only needs static documentation because IBM Consulting optimizes for operable mappings with data model and governance controls. The best usage situation is a transformation program where process changes must propagate to systems and where RBAC, audit logs, and admin approvals manage who can edit mappings and publish revisions.
- +Integration depth across enterprise apps and workflow execution services
- +Process-to-execution mapping with explicit API contracts and governance
- +RBAC and audit-log controls for change traceability and approvals
- –Less aligned to diagram-only deliverables without system integration needs
- –Heavier governance and modeling effort can slow early iterations
Enterprise operations leadership
Map and operationalize cross-team workflows
Consistent process execution across teams
Integration architects
Define process-driven API contracts
Reduced integration rework
Show 2 more scenarios
Process governance teams
Enforce RBAC for mapping changes
Improved traceability and compliance
Adds admin approvals and audit logs to control who can publish mapping revisions.
Automation engineering teams
Connect diagrams to configurable automation
Higher automation throughput
Implements automation layers that reference schema-driven configuration and versioned mappings.
Best for: Fits when enterprise process maps must drive execution, APIs, and audited governance.
Accenture
enterprise_vendorEnd-to-end process mapping and redesign for outsourcing programs that specify process integration, control points, and governance artifacts for delivery teams.
Governed process model lifecycle with RBAC and audit logs tied to a defined data model.
Process mapping services at Accenture connect process discovery outputs to enterprise systems through integration-heavy delivery and controlled governance. Teams get process model artifacts tied to a defined data model, including mapping rules, element metadata, and lifecycle status for handoff.
Automation support typically includes configurable workflow stages and API-driven integrations between mapping work, execution tooling, and downstream reporting. Admin and governance controls focus on RBAC, audit logging, and review checkpoints to maintain schema and modeling consistency across organizations.
- +Delivery teams map process models into enterprise data schemas for controlled handoffs
- +Integration-first approach ties mapping artifacts to execution systems through APIs
- +Governance emphasis includes RBAC and audit logs for model change traceability
- +Extensibility via configuration supports repeated mapping workflows across programs
- –Automation depends on implementation scope and system integration availability
- –Cross-team schema governance can add overhead for small process mapping efforts
- –API surface is typically delivered project-by-project rather than standard out of the box
Best for: Fits when enterprises need governed process mapping linked to execution systems and downstream analytics.
KPMG
enterprise_vendorProcess mapping and operating model design for outsourcing that includes governance controls, audit log requirements, and data model alignment across systems.
Governed process artifact documentation with traceable review and approval workflows across stakeholders.
KPMG performs process mapping services that translate operational workflows into controlled process artifacts for governance and execution alignment. Delivery centers on process documentation, process improvement workshops, and structured mapping outputs that teams can maintain across programs and functions.
Integration depth is driven by how KPMG organizes process data models, workflow schemas, and handoffs into target systems and downstream reporting. Automation and API surface depend on the implementation partner and tooling choices, while admin and governance controls typically show up as RBAC-aligned review workflows and auditable change management for mapped artifacts.
- +Method-driven process mapping with clear workflow structure and documented handoffs
- +Strong governance artifacts for stakeholder review, approval, and traceability
- +Practical data model thinking for aligning process schemas to reporting needs
- +Change management support with auditable mapping revisions
- –Automation and API surface are indirect and depend on chosen implementation tooling
- –Schema extensibility varies by engagement scope and mapping depth requirements
- –Throughput for frequent change cycles may be limited by consulting delivery model
- –Sandboxing and integration testing support is typically implementation-dependent
Best for: Fits when regulated enterprises need governance-heavy process artifacts and cross-team alignment.
Capgemini
enterprise_vendorProcess mapping and business transformation delivery that formalizes process architecture, integration interfaces, and automation backlogs for outsourcing execution.
Governance-led process artifact release with RBAC controls and traceability via audit logs.
Capgemini fits enterprises that need process mapping tied to delivery governance, not just diagramming. The service integrates process discovery outputs into enterprise data models used by transformation programs and downstream tooling.
Integration depth shows up in cross-system provisioning, schema mapping, and controlled rollout practices across process, data, and workflow layers. Automation and extensibility typically center on API-linked workflows, repeatable configuration, and RBAC-aligned governance with audit log expectations.
- +Integration mapping across process, data model, and workflow tooling
- +RBAC-ready governance patterns for process artifacts and releases
- +Extensible delivery automation through API-linked workflow orchestration
- +Audit log practices support traceability from mapping to execution
- –Mapping-to-execution alignment depends on defined target schemas
- –Extensibility requires governance setup for consistent configuration
- –Throughput can lag without dedicated model ownership and review cadence
Best for: Fits when enterprise teams need managed process mapping with controlled integration and governance.
WNS
enterprise_vendorOutsourcing delivery that maps end-to-end processes across customer operations, defines control gates, and standardizes runbooks for governance.
Governance controls that pair RBAC with audit log trails for process mapping changes.
WNS delivers process mapping services with governance-first delivery practices that focus on controlled mapping artifacts and repeatable execution. Work is typically organized around domain discovery, process modeling, and workflow design that align to target process architecture and operating model.
Integration depth is driven through documented interfaces between process artifacts and downstream enterprise systems, including requirements for data schemas and mapping standards. Automation and API surface are oriented toward provisioning and configuration flows that support controlled changes across process versions and stakeholders.
- +Governance-centered mapping artifacts with clear versioning and change control expectations
- +Integration work aligns process models to enterprise data schema and workflow requirements
- +Automation and configuration support targets repeatable provisioning across environments
- +RBAC and audit logging expectations support controlled access to mapping assets
- +Extensibility through schema-driven approach enables consistent additions to process attributes
- –API automation surface depends on integration scope and system accessibility
- –Deep governance requires defined stakeholder roles and approval workflows upfront
- –Complex data model mapping can add time if source schemas are inconsistent
- –Process throughput outcomes depend on modeling effort and downstream workflow readiness
Best for: Fits when enterprises need governed process mapping integrated into live workflow and data systems.
Capita
enterprise_vendorPublic sector outsourcing and service design that maps delivery processes, defines operating controls, and documents integration requirements for providers.
Mapping-to-implementation governance reviews that control schema, configuration, and change across system workflows.
Capita serves as a process mapping services provider with delivery capabilities tied to enterprise operating models across public services and regulated industries. Process work is typically coupled with integration planning for workflow, case, and document flows so schemas and handoffs stay consistent across systems.
Integration depth is shaped through configuration, governance, and documented interfaces for connecting mapping outputs to execution tooling. Automation and API surface depend on the target workflow stack, with extensibility focused on repeatable mapping-to-provisioning processes.
- +Integration planning aligns process schemas with case and workflow system handoffs.
- +Governance review supports controlled change across mapped process variants.
- +Delivery teams can translate process maps into configuration artifacts.
- +Audit-friendly operating approaches for regulated process documentation.
- –Automation depth varies by target workflow tooling and existing integration posture.
- –API extensibility depends on connector availability for each systems landscape.
- –RBAC granularity is constrained when process steps span multiple domains.
- –Sandboxing and throughput validation take extra scoping for complex process graphs.
Best for: Fits when regulated organizations need controlled process mapping mapped into governed system changes.
Atos
enterprise_vendorManaged services and outsourcing delivery that produces mapped operational processes, control points, and integration specifications for run automation.
RBAC and audit log traceability for governed process schema and mapping changes.
Atos delivers process mapping services with integration into enterprise delivery workflows, not just document output. Delivery relies on defined process artifacts tied to a data model that can be governed across teams.
Integration depth centers on API-connected process catalogs, schema-aligned mappings, and automation hooks for provisioning and change control. Admin and governance controls support RBAC scoping and audit log traceability for controlled iterations of process schemas and mappings.
- +Integration work ties process maps to enterprise delivery workflows.
- +Schema-aligned mappings support a consistent process data model.
- +Automation hooks enable repeatable provisioning and controlled updates.
- +RBAC scoping and audit log traceability support governance workflows.
- –Automation depth depends on available API surfaces in target systems.
- –Schema alignment requires upfront governance and modeling effort.
- –Extensibility workflows can slow iteration when change control is strict.
Best for: Fits when enterprise teams require governed process mappings with API automation and strong auditability.
How to Choose the Right Process Mapping Services
This buyer's guide covers process mapping services and how nine providers handle integration, data modeling, automation, and governance controls. It references QPR, Celonis, IBM Consulting, Accenture, KPMG, Capgemini, WNS, Capita, and Atos.
Each section translates provider strengths into evaluation criteria you can apply to mapping programs that must connect diagrams to execution systems. Coverage focuses on schema-driven modeling, API and automation surfaces, and admin controls like RBAC and audit logs.
Governed process mapping that turns modeled activities into execution-ready artifacts
Process mapping services convert business process descriptions into structured process artifacts that teams can validate, publish, and connect to execution tooling. The category typically solves governance gaps in process documentation by using a defined data model and lifecycle states so process changes remain traceable across teams.
QPR implements schema-controlled process modeling with automation-ready structure and API-driven integration workflows. Celonis pairs governed mappings with a conformed process data model that standardizes case and activity structure across mappings.
Evaluation criteria for mapping services with integration and governance control depth
Integration depth decides whether process maps remain documentation or become input into execution systems. A provider can also specify how mappings map into schemas and how those schemas stay consistent across teams.
Automation and API surface decide how quickly mapping artifacts can be provisioned, configured, and updated across environments. Admin and governance controls decide who can publish changes and how audit visibility is maintained.
Schema-controlled process data model with lifecycle states
QPR uses schema-driven element types and relationships tied to lifecycle states so process models support consistent mapping and validation. Celonis also emphasizes a conformed data model that standardizes activities and case structure so governance can apply to shared semantics.
Integration depth into execution systems through documented interfaces
IBM Consulting and Accenture focus on process-to-execution mapping that includes integration planning for existing applications. Atos and Capgemini stress schema-aligned mappings tied to enterprise delivery workflows, which controls how process artifacts connect to system interfaces.
Automation and API surface for provisioning and configuration
QPR provides an API surface that supports provisioning, configuration, and integration with adjacent systems. Celonis similarly centers extensible integration patterns with documented APIs and automation hooks, while Atos highlights automation hooks that enable repeatable provisioning and controlled updates.
Admin governance controls with RBAC and audit-log traceability
Celonis and Accenture use governed RBAC patterns plus audit logging so mapping changes remain controlled and visible. QPR also includes governance controls with RBAC patterns and audit-oriented operational features, and WNS pairs RBAC with audit log trails for mapping changes.
Controlled publishing and change visibility tied to the process model lifecycle
Celonis and Accenture emphasize controlled publishing and review checkpoints so teams keep model and schema consistency during collaboration. QPR’s schema governance adds structure that supports validation, while Capita and KPMG focus on mapping-to-implementation governance reviews and traceable review and approval workflows.
Extensibility strategy for adding process attributes without breaking governance
QPR supports extensibility through its API surface and structured data model so teams can connect models to workflow artifacts. Capgemini and WNS rely on schema-driven extensibility with governance setup, while Atos and IBM Consulting tie extensibility to governed process artifacts and API-linked automation.
A decision path for selecting a process mapping provider that can govern changes across integrations
Start by verifying whether the provider uses a defined process data model with schema-controlled element types and lifecycle states. QPR and Celonis are direct matches when the requirement is governed modeling with a structured schema foundation.
Then confirm the automation and API surface that can provision and configure mapped artifacts. Finally, assess admin and governance controls for RBAC and audit-log traceability so mapping changes remain reviewable across stakeholders.
Map the target execution reality to a conformed schema
Choose QPR if the process mapping program needs schema-controlled element types and relationships tied to lifecycle states so teams can validate mappings consistently. Choose Celonis if standardizing activities and case structure across mappings is required so downstream execution can rely on conformed semantics.
Require documented integration interfaces that connect artifacts to systems
Select IBM Consulting or Accenture when process maps must drive execution and the engagement must define integration requirements and explicit API contracts. Select Atos or Capgemini when the mapping service must integrate into enterprise delivery workflows through API-connected process catalogs and schema-aligned mappings.
Validate the automation surface for provisioning and controlled updates
Prefer QPR when provisioning and configuration need to be performed through an API surface that supports integration workflows. Prefer Celonis or Atos when automation hooks and APIs must enable controlled updates to governed mappings across environments.
Test governance controls with concrete RBAC and audit-log requirements
Use Celonis or Accenture when RBAC and audit logging are required for mapping change control and visibility. Use QPR when audit-oriented operational governance and structured schema controls are required for traceability of process model elements.
Confirm review checkpoints and publishing control for model lifecycle changes
Choose KPMG or Capita when traceable review and approval workflows across stakeholders are central to governance-heavy environments. Choose WNS when governance needs RBAC paired with audit log trails and versioning expectations for controlled changes.
Assess extensibility effort against change cadence
Choose QPR when extensibility must fit setups that need model-to-workflow connectivity without losing schema validation. Use Capgemini or WNS when extensibility depends on governance setup and configuration consistency, then confirm the engagement can support that model ownership and review cadence.
Which organizations benefit from governed process mapping tied to automation and auditability
Process mapping services fit organizations that must treat process artifacts as governed assets that connect to execution systems. These programs typically require a structured data model, controlled publishing, and admin governance controls that keep mapping changes traceable.
Providers like QPR and Celonis fit requirements that prioritize integration depth and automation surfaces, while KPMG and Capita fit governance-heavy environments that demand review and approval workflows.
Enterprises needing governed process mappings integrated with automation systems
QPR fits this need because it delivers schema-driven process modeling and an API surface that supports provisioning and integration workflows. Celonis also fits because it uses governed integrations to feed an execution-ready data model with documented APIs and automation hooks.
Enterprises that require process maps to drive execution with audited change control
IBM Consulting is a match when process maps must connect diagrams to API-driven automation under audited governance. Accenture also aligns when the requirement includes RBAC, audit logs, and governed process model lifecycle tied to a defined data model.
Regulated organizations that need governance-heavy process artifacts across stakeholders
KPMG fits when stakeholder review, approval, and traceability are required for mapped artifacts and auditable revisions. Capita fits when mapping-to-implementation governance reviews must control schema, configuration, and change across system workflows.
Enterprises standardizing process semantics across cases and activities for consistent mapping outputs
Celonis fits because its conformed process data model standardizes activities and case structure across mappings. QPR fits when enterprises want a schema-driven approach to keep process element types and relationships consistent and validated.
Organizations integrating mapping into enterprise delivery workflows with schema-aligned provisioning
Atos fits when schema-aligned mappings must include automation hooks for repeatable provisioning and controlled updates with RBAC scoping and audit traceability. Capgemini fits when the service must formalize process architecture and integrate into cross-system provisioning with governance-led release practices.
Pitfalls that derail process mapping efforts with integration and governance requirements
Common failures arise when schema governance and integration alignment are treated as secondary work. Several providers highlight that schema governance increases modeling effort and external mapping alignment requires careful discipline.
Automation and extensibility also fail when lifecycle management lacks defined ownership and review cadence. Governance work can slow early iterations when governance and modeling effort are heavier than the team expects.
Choosing diagram-only deliverables when execution integration is required
IBM Consulting and Atos prevent this mismatch by connecting process maps to API automation hooks or schema-aligned mappings that tie artifacts to execution. Avoid using KPMG or WNS as the sole integration mechanism when the program needs explicit API-connected process catalogs or provisioning automation.
Underestimating schema governance effort and lifecycle alignment work
QPR and Celonis require upfront schema configuration because schema governance and conformed semantics affect mapping accuracy and validation. In regulated contexts, KPMG and Capita also add governance artifact workload, so teams should plan for review and approval cycles instead of expecting rapid iteration.
Assuming automation will work without disciplined lifecycle management
QPR notes that automation configurations demand disciplined lifecycle management, so releases must be planned with governance. Capgemini and WNS also warn that extensibility and configuration consistency depend on governance setup and defined review cadence.
Building governance without clear RBAC scope and audit visibility
Accenture and Celonis focus on RBAC plus audit logs for mapping changes, so governance stays attributable to roles and decisions. Atos and QPR also emphasize audit-oriented traceability, so teams should avoid governance plans that do not specify RBAC scoping and audit-log expectations.
Treating extensibility as free-form instead of schema-bound
QPR and Celonis keep extensibility tied to structured data models, which prevents broken semantics when teams add process attributes. Capita and KPMG keep governance tied to review and approval workflows, so extensibility should be treated as a controlled change rather than an ad-hoc edit.
How We Selected and Ranked These Providers
We evaluated QPR, Celonis, IBM Consulting, Accenture, KPMG, Capgemini, WNS, Capita, and Atos on capabilities tied to integration depth, data model governance, automation and API surface, and admin control coverage like RBAC and audit-log traceability. We also scored ease of use and value to reflect how much upfront schema and governance work teams typically face when mapping must stay consistent across stakeholders.
Overall ratings are a weighted average in which capabilities carry the most weight at 40 percent, while ease of use and value each account for 30 percent of the final score. QPR set the pace because its schema-controlled process modeling with lifecycle states and its API surface for provisioning, configuration, and integration directly connect governance to automation workflows, which elevated capabilities and ease-of-use outcomes together.
Frequently Asked Questions About Process Mapping Services
How do process mapping services differ when the goal is execution-ready automation?
Which provider best fits enterprises that require a governed process model lifecycle with auditable change visibility?
What integration depth options matter most for connecting process mapping artifacts to existing systems?
How do service providers handle role-based access control and audit logging for process mapping collaboration?
What data model and schema practices reduce rework when multiple teams map the same process elements?
How do integration and automation interfaces typically get defined during onboarding and delivery?
Which provider is a stronger fit for teams that need extensibility through APIs and controlled provisioning flows?
What common failure points arise when process mappings do not match execution tooling, and how do services mitigate them?
How do providers approach getting new teams operational on existing process documentation and artifacts?
Conclusion
After evaluating 9 business process outsourcing, QPR 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.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Business Process Outsourcing alternatives
See side-by-side comparisons of business process outsourcing tools and pick the right one for your stack.
Compare business process outsourcing tools→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 ListingWHAT 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.