GITNUXSOFTWARE ADVICE
Business Process OutsourcingTop 10 Best Collaboration Project Software of 2026
Top 10 Collaboration Project Software ranked for features and usability, with comparisons of monday.com, Microsoft Teams, and Notion for teams.
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.
monday.com
Workflow automations that update fields, statuses, and assignees based on triggers
Built for teams needing visual project collaboration with automation and live reporting.
Microsoft Teams
Editor pickPlanner integration inside Teams channels for task assignment and status tracking
Built for organizations standardizing on Microsoft 365 for team collaboration and task coordination.
Notion
Editor pickLinked databases with multiple views for kanban and timeline project execution
Built for project teams needing flexible knowledge workflows and lightweight planning boards.
Related reading
Comparison Table
The comparison table contrasts monday.com, Microsoft Teams, Notion, Atlassian Confluence, Asana, and other collaboration project tools across integration depth, data model, and automation plus API surface. Each row highlights schema and provisioning options, extensibility patterns, and configuration details that affect throughput and workflow mapping. Admin and governance controls are summarized through RBAC coverage and audit log behavior, so tradeoffs are visible at a glance.
monday.com
work managementWork management boards coordinate tasks, owners, due dates, and workflows for teams that need collaborative project execution.
Workflow automations that update fields, statuses, and assignees based on triggers
monday.com supports collaboration projects with customizable fields such as statuses, dates, people, time tracking, and numeric data mapped to boards. Teams can enrich work context by attaching files, linking related items, and using dashboards that surface field-level progress across multiple boards.
Workflow automation rules let teams update fields, assign owners, and trigger notifications when collaboration events occur, such as status changes or new comments. A tradeoff is that heavy customization across many boards can add setup time and requires governance to keep field definitions consistent.
One strong fit is coordinating cross-functional efforts where multiple teams update the same set of status and ownership fields while sharing artifacts. Another fit is project reporting, where dashboards and filters rely on the same enriched fields to keep stakeholders aligned without manual spreadsheet exports.
- +Highly configurable boards with fields tailored to project workflows
- +Automation rules streamline approvals, assignments, and status changes
- +Dashboards and reporting surfaces progress across portfolios
- +Real-time collaboration with mentions, comments, and activity history
- –Advanced cross-board reporting can require careful modeling of fields
- –Complex setups may slow teams down during initial rollout
- –Large workspaces can become harder to navigate without strict standards
Agency project managers
Coordinate client deliverables with status fields
Faster approvals, fewer status emails
Product operations teams
Route experiments through workflow stages
Consistent routing, clear accountability
Show 2 more scenarios
IT service desk coordinators
Synchronize incident work across teams
Lower handoff friction
Coordinators enrich tickets with assignees, priorities, and activity history visible in shared boards.
Customer success managers
Manage onboarding tasks and artifacts
On-time onboarding milestones
CSMs store onboarding documents, track dates, and keep owners aligned using dashboards.
Best for: Teams needing visual project collaboration with automation and live reporting
More related reading
Microsoft Teams
team chat meetingsChat, meetings, and shared channels centralize collaboration around files and project discussions with integration to Microsoft 365 apps.
Planner integration inside Teams channels for task assignment and status tracking
Microsoft Teams centers collaboration around persistent team spaces that combine chat, file collaboration, and meetings in one workspace. It supports project collaboration with channels, threaded conversations, assignments in Planner, and shared Office files with co-authoring.
Meeting workflows are strong with calendar scheduling, screen sharing, recording, and live events for larger broadcasts. Integration depth with Microsoft 365, Power Automate, and third-party apps makes it practical for coordinating work across teams and tools.
- +Channels organize discussions and documents per project or workstream
- +Tight Microsoft 365 file co-authoring inside Teams improves review cycles
- +Built-in Planner tasks support assignments without leaving the chat context
- +Meeting recording, transcription, and search aid fast knowledge retrieval
- –Complex permission models can confuse admins across nested teams and groups
- –Planner features can feel lightweight versus dedicated project management tools
- –Large teams can create information sprawl across channels and chats
- –External collaboration requires careful governance to avoid oversharing
Project managers at mid-sized firms
Track tasks across team channels
Centralized task tracking
Operations teams managing cross-department work
Route approvals with automated notifications
Faster approval cycles
Show 2 more scenarios
Engineering teams collaborating on documents
Co-author specs with meeting decisions
Reduced document rework
Engineering teams collaborate on shared Office files while meeting recordings capture decisions for review.
Client services teams running project delivery
Maintain stakeholder updates in shared channels
Fewer status check-ins
Client services teams keep stakeholders aligned using threaded conversations and live meeting updates.
Best for: Organizations standardizing on Microsoft 365 for team collaboration and task coordination
Notion
collaborative workspaceTeam wikis and project pages let groups collaborate on documentation, databases, tasks, and shared knowledge in one workspace.
Linked databases with multiple views for kanban and timeline project execution
Notion stands out with its database-first pages that turn notes into relational project spaces. Teams collaborate using inline comments, mentions, and page permissions, while timelines and kanban views support common planning workflows.
Flexible templates and reusable components speed up standard operating processes across projects. Built-in file handling and versioned content help keep project artifacts tied to the right decisions.
- +Database views support kanban, timeline, and calendar project workflows
- +Inline comments and @mentions keep feedback tied to specific content
- +Permissions and page-level access control enable organized team collaboration
- +Templates and linked databases standardize repeatable project processes
- –Complex permission structures can become difficult to troubleshoot
- –Advanced modeling with linked databases can require training time
- –Real-time coordination depends on good information hygiene practices
- –Built-in reporting is limited for portfolio-level project analytics
Software product teams
Plan releases using kanban and timelines
Clear ownership and delivery tracking
Marketing campaign ops teams
Coordinate asset requests across teams
Faster approvals and fewer reworks
Show 2 more scenarios
Consulting project managers
Centralize client deliverables and notes
Consistent documentation across projects
Permissions and mentions keep stakeholders synced while templates standardize reports and meeting outputs.
Cross-functional operations teams
Run recurring SOPs with reusable templates
Repeatable workflows at scale
Reusable components and databases organize procedures, owners, and checklists for ongoing operations.
Best for: Project teams needing flexible knowledge workflows and lightweight planning boards
More related reading
Atlassian Confluence
team documentationTeam knowledge spaces provide collaborative documentation, inline comments, and page-level permissions for project teams.
Space-level permissions plus page version history for controlled, auditable collaboration
Confluence stands out with a wiki-first workspace that turns meeting notes and project knowledge into reusable pages with strong structure. It supports Atlassian integrations like Jira for linking issues, building release and sprint context, and keeping documentation close to delivery.
Collaboration works through page editing with comments, mentions, and change histories, plus permissions and spaces for organizing project areas. Automation like content templates and tasks tied to Atlassian workflows helps teams standardize documentation without building custom systems.
- +Wiki pages with templates standardize project docs and reduce rework
- +Jira linking keeps requirements, issues, and documentation connected
- +Granular spaces, permissions, and audit history improve governance
- +Comments, mentions, and inline editing support fast collaboration
- –Cross-page project plans require workarounds compared with dedicated PM tools
- –Search and large knowledge bases can need careful information architecture
- –Heavy customization for workflows often needs additional Atlassian components
Best for: Project teams maintaining living documentation, decisions, and Jira-linked context
Asana
project managementProject management workspaces track tasks, timelines, approvals, and team collaboration through structured workflows.
Timeline view for project scheduling with dependencies and milestone tracking
Asana stands out with task-first work management that turns conversations into structured work across teams. It supports project views including boards, timelines, and calendars for planning, tracking, and scheduling work.
Built-in automation rules and reusable templates reduce manual coordination across recurring initiatives. Reporting centers on dashboards and workload visibility to surface status, blockers, and ownership.
- +Task dependencies and milestones keep cross-team progress tightly coordinated
- +Multiple views like timeline and board align execution with planning needs
- +Automation rules reduce repetitive updates across projects
- +Workload and status reporting make ownership and bottlenecks visible
- –Advanced workflows can require careful setup to avoid clutter
- –Permission complexity increases effort for large orgs with many teams
- –Reporting setup can feel limited for highly customized analytics
Best for: Teams managing multi-project delivery with visual planning and lightweight governance
ClickUp
all-in-one PMTask tracking, docs, goals, and dashboards support collaborative planning and execution across project teams.
Automation rules that trigger on task events, updates, and status changes
ClickUp stands out with a highly configurable workspace that blends tasks, docs, chat-like updates, and dashboards in one system. Core collaboration centers on custom statuses, automations, nested tasks, and visual views like Kanban, Gantt, and timelines.
Team execution improves with workload views, approvals, and recurring tasks that reduce manual project hygiene. Reporting is supported through dashboards, goal tracking, and exportable metrics for cross-team progress visibility.
- +Custom statuses and workflows let teams match existing processes
- +Dashboards and goals provide quick cross-team progress visibility
- +Nested tasks and multiple views scale from small projects to programs
- +Automation rules reduce repetitive work like assignments and status changes
- –Highly configurable setup can slow adoption for new teams
- –Advanced reporting can feel complex without clear metric design
- –Permissions and workspace structure require careful planning early
Best for: Teams running complex projects needing customizable workflows and dashboards
More related reading
Trello
kanban boardsKanban boards coordinate card-based work, assignments, and team collaboration for lightweight project execution.
Butler automation rules that trigger card moves, due-date logic, and field updates.
Trello stands out with card-and-board planning that turns project work into a visual workflow across lists and columns. It supports collaboration through comments, mentions, attachments, due dates, checklists, and assignment to members for shared task execution.
Team coordination scales via templates, reusable boards, advanced filters, activity tracking, and automation with Butler for rules like move card when conditions match. Integration coverage with tools like Slack, Google Drive, GitHub, and Jira connects Trello boards to existing workstreams and reduces manual status updates.
- +Board and card model makes workflows understandable at a glance
- +Comments, mentions, assignments, and checklists keep collaboration inside the task
- +Butler automations move cards and apply actions based on defined rules
- +Filters and search quickly narrow work across large boards
- –Complex dependencies and resource planning require workarounds
- –Reporting for portfolio-level progress is limited versus dedicated PM suites
- –Maintaining many interrelated boards can increase governance overhead
- –Spreadsheet-style data views are not as powerful as dedicated project databases
Best for: Teams needing simple visual project tracking and lightweight automation
Google Workspace
collaboration suiteShared documents, spreadsheets, and real-time editing power collaborative project work with integrated chat and scheduling.
Docs and Sheets real-time co-authoring with version history and threaded comments
Google Workspace stands out with tightly integrated collaboration across Gmail, Calendar, Docs, Sheets, Slides, and Chat. Real-time co-authoring is supported for documents, spreadsheets, and presentations with version history and structured commenting.
Project coordination is reinforced by Google Chat threads, shared spaces, and calendar-based scheduling with meeting recordings captured in Drive. Admin controls, identity management, and security reporting support organization-wide collaboration governance.
- +Real-time co-authoring in Docs, Sheets, and Slides with granular change tracking
- +Deep integration between Drive, Gmail, Calendar, and Chat for fast collaboration handoffs
- +Powerful search across Drive content plus metadata-aware organization via Drive folders
- –Project management features are light compared with dedicated task and roadmap tools
- –Advanced workflows require add-ons and can fragment collaboration across apps
- –Commenting and approvals lack native, repeatable release workflows seen in specialized suites
Best for: Teams needing Google-native collaboration with basic project coordination and document-centric work
More related reading
Slack
team messagingChannel-based messaging and file sharing coordinate project collaboration with integrations into common work management tools.
Threaded conversations that keep discussions organized within channels
Slack centralizes team communication with channels, threaded conversations, and searchable chat history. It supports cross-team collaboration through file sharing, workflow automation, and integrations with common productivity and development tools.
Rich notification controls and robust permissions help manage large organizations without drowning teams in alerts. Its project execution remains dependent on integrations and external project tools rather than providing a full native project management suite.
- +Threaded conversations keep decisions tied to context
- +Powerful search finds messages, files, and shared links quickly
- +Channel permissions and Slack Connect support controlled cross-org collaboration
- +Workflow automation via Slack workflows and integrations reduces manual coordination
- –Native project management features are limited compared with dedicated PM tools
- –Information can fragment across channels and integrations
- –Notification tuning and governance require active admin effort
Best for: Teams coordinating work through chat-driven collaboration and integrations
Linear
issue managementIssue management with sprint-ready workflows helps teams collaborate on product and project delivery.
Issue Linking with smart relationship context across tasks, comments, and planning
Linear centers collaboration around issue-first work with fast, keyboard-driven workflows and a clean board view. Teams manage tasks, prioritize with custom fields, and run planning in sprints while keeping work connected through linked issues.
Real-time collaboration shows updates directly in tickets, and integrations keep product and engineering discussions synchronized with GitHub and Slack. Search and reporting help teams trace delivery progress across projects and labels.
- +Keyboard-first issue creation speeds daily coordination and triage
- +Linked issues and threaded comments keep context attached to work
- +Custom fields and saved searches support consistent reporting workflows
- +Tight GitHub and Slack integrations reduce status handoffs
- –Less native customization than enterprise project suites for complex processes
- –Reporting depth can be limited for multi-department portfolio governance
- –Workflows depend on Linear’s issue model, which may not fit every org
- –Advanced automation options are narrower than full work-management platforms
Best for: Product and engineering teams coordinating issue-driven delivery and planning
Conclusion
After evaluating 10 business process outsourcing, monday.com 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.
How to Choose the Right Collaboration Project Software
This buyer's guide maps collaboration project software needs to concrete tools including monday.com, Microsoft Teams, Notion, Atlassian Confluence, Asana, ClickUp, Trello, Google Workspace, Slack, and Linear.
Coverage focuses on integration depth, data model decisions, automation and API surface, and admin governance controls so buyers can evaluate extensibility and control depth instead of only interface fit.
The guide also calls out common rollout mistakes seen across board work systems, wiki spaces, chat-first tools, and issue-driven platforms.
Collaboration project workspaces that coordinate tasks, artifacts, and decisions
Collaboration project software stores project work in a structured model like boards, databases, pages, or issues and connects that model to comments, files, and planning views. It solves coordination problems by tying ownership, due dates, and status fields to the right artifacts and conversations so teams do not reconcile updates across tools manually.
Tools like monday.com centralize work in customizable boards with workflow automations that update fields, statuses, and assignees based on triggers. Teams in Microsoft Teams combine channels, shared files with co-authoring, and Planner task assignments inside the same project workspace.
Evaluation criteria for integration, schema control, automation, and governance
Evaluation should start with the integration depth a tool offers into the systems teams already use for identity, files, development, and scheduling. monday.com and Microsoft Teams typically reduce handoffs by connecting work updates to dashboards, file collaboration, and workflow automation.
Next, the data model determines how durable and reportable the work history becomes because statuses, permissions, and linked objects must align with a consistent schema. Notion, Atlassian Confluence, and Linear each model projects differently, so governance and automation depend on how their structure behaves under change.
Workflow automation that updates structured fields
monday.com automations update fields, statuses, and assignees from triggers so approvals and assignment changes propagate through the project record. ClickUp and Trello use event-driven rules that trigger on task or card updates so teams can keep execution moving without manual status edits.
Integration depth with existing suites and task systems
Microsoft Teams integrates with Microsoft 365 so shared Office files co-author inside channels and Planner tasks track assignment status in the same context. Trello supports integrations with Slack, Google Drive, GitHub, and Jira so board progress can connect to communications and development workstreams.
Data model for project objects and relationship mapping
Notion uses database-first pages with linked databases and multiple views, which makes kanban and timeline planning depend on a defined relational schema. Linear uses an issue-first model with linked issues and custom fields so delivery progress and planning remain tied to tickets rather than freeform pages.
Admin governance controls through permissions and audit history
Atlassian Confluence supports space-level permissions plus page version history so controlled collaboration has an auditable trail. Microsoft Teams and Slack both support permission models and governance patterns, but nested teams and active admin effort can become a management cost when collaboration spans many groups.
Extensibility via automation surfaces and workflow orchestration
Microsoft Teams connects automation through Power Automate so approvals and notifications can run as workflow steps across Teams. monday.com focuses automation rules on field updates and status changes, which creates a predictable surface for connecting work execution to downstream systems.
Reporting surfaces that match the work schema
monday.com dashboards and filters rely on the same enriched fields used by boards, which helps keep portfolio reporting tied to the execution model. Atlassian Confluence is strongest for documentation governance, while tools like Trello and Slack tend to leave portfolio-level reporting to integrations rather than native analytics.
Select a tool by mapping schema, automation triggers, and governance to the rollout plan
A practical selection starts by defining what must be structured for reporting, like statuses, owners, due dates, and the relationships between tasks and artifacts. monday.com and Asana excel when those structures drive dashboards and workload visibility.
The next decision is whether the collaboration center should be a board model, a documentation model, or an issue model, because that choice governs permissions troubleshooting and automation scope. Notion and Confluence typically work best when governance and knowledge structures are central, while Linear and Asana fit execution tracking around issues or tasks.
Choose the collaboration center that matches the data model requirement
Use monday.com when projects require a board schema with customizable fields, linked items, and dashboards based on those fields. Choose Linear when execution must stay issue-first with linked issues, custom fields, and sprint planning connected to delivery.
Define automation triggers that update structured work objects
Pick tools with automation rules that directly update structured fields instead of only sending notifications. monday.com updates fields, statuses, and assignees from triggers, while ClickUp and Trello trigger on task or card events to move cards and apply defined actions.
Validate integration depth for identity, files, and workflow execution
Standardize on Microsoft Teams when the organization runs Microsoft 365 because channels combine shared files with co-authoring and Planner assignments inside the same project space. Use Trello when teams need board updates connected to Slack, Google Drive, GitHub, or Jira so work stays linked across communication and development systems.
Test governance fit for permissions, auditability, and scaling
Use Atlassian Confluence when audit history and structured permissions matter because it provides space-level permissions plus page version history. Plan admin workload carefully for Microsoft Teams nested permission structures and for Slack notification governance when collaboration spans many channels and external partners.
Confirm reporting capability aligns to the same schema used for execution
Prefer monday.com when dashboards and filters must reflect the same enriched fields used by boards to avoid spreadsheet exports. Use Asana when timeline view with dependencies and milestones is the primary reporting mechanism for multi-project delivery.
Which teams benefit from each collaboration project workspace model
Collaboration project software fits different operating models based on whether work is tracked as boards, databases, pages, tasks, issues, or cards. The right fit determines whether automation stays tied to the work schema and whether governance scales without manual reconciliation.
The audience segments below map to the best-fit tool patterns for execution visibility, documentation control, or issue-driven delivery.
Cross-functional delivery teams needing field-based automation and live reporting
monday.com fits when coordination depends on customizable statuses, owners, due dates, and workflow automations that update fields and trigger notifications. Its dashboards and filters surface progress across boards using the same enriched schema.
Organizations standardized on Microsoft 365 that want chat, files, and tasks in one workspace
Microsoft Teams fits when channels act as project spaces with threaded conversations and shared Office file co-authoring. Planner tasks inside Teams channels help keep assignment and status tracking inside chat context.
Teams building repeatable project knowledge and flexible planning views
Notion fits when projects require database-first relational structure with linked databases and multiple views for kanban and timeline workflows. Atlassian Confluence fits when living documentation needs space-level permissions and page version history with Jira-linked context.
Delivery teams that organize work around tasks, dependencies, and scheduling
Asana fits when timeline view with dependencies and milestone tracking drives multi-project coordination with approvals and intake forms. ClickUp fits when complex projects need configurable statuses, nested tasks, and dashboards tied to goals and recurring hygiene.
Product and engineering teams running sprints with issue-linked execution
Linear fits when planning and reporting depend on an issue-first model with linked issues, custom fields, and sprint roadmaps. Jira-integrated workflows work well in this style when delivery discussions must stay attached to ticket context.
Common rollout and design pitfalls that break collaboration accuracy or governance
Many failures come from mismatches between the automation triggers teams expect and the schema structures the tool actually enforces. Tools that are highly configurable can also magnify inconsistency if field definitions are not standardized.
The pitfalls below reflect issues seen across board systems, wiki spaces, chat tools, and issue platforms.
Creating too many inconsistent custom fields across boards or projects
monday.com can support highly configurable boards, but heavy customization across many boards increases setup time and requires governance to keep field definitions consistent. ClickUp and Notion also depend on consistent schema design, so field and linked-database standards should be documented before scaling.
Overestimating native portfolio reporting when work sits in chat or lightweight boards
Slack coordinates through threaded conversations and integrations, but native project execution reporting depends on external work tools rather than being a full PM analytics surface. Trello also limits portfolio-level progress reporting versus dedicated PM suites, so cross-board metrics require careful modeling or reporting design.
Using complex permission structures without a troubleshooting plan
Atlassian Confluence provides space-level permissions and audit history, which supports governance, but teams still need a clear information architecture for large knowledge bases. Microsoft Teams nested permission models can confuse admins, and Slack notification tuning and governance require active admin effort to avoid oversharing.
Relying on freeform documentation instead of structured work objects for automation
Notion’s linked databases enable automation through linked pages, but advanced modeling with linked databases can require training time to keep relationships correct. Google Workspace offers co-authoring with version history, but advanced repeatable release workflows require add-ons, which can fragment automation across apps.
Trying to force dependencies and cross-team planning without the right execution model
Trello can handle visual cards and Butler rules, but complex dependencies and resource planning require workarounds. Linear and Asana manage dependencies and planning through issues or timelines, so dependency-heavy execution should map to their execution model rather than to chat threads.
How We Selected and Ranked These Tools
We evaluated monday.com, Microsoft Teams, Notion, Atlassian Confluence, Asana, ClickUp, Trello, Google Workspace, Slack, and Linear using criteria captured in the reviewed scores for features, ease of use, and value. The overall rating is a weighted average in which features carries the most weight at 40 percent, while ease of use and value each account for 30 percent. This editorial research focused on concrete mechanics like board field modeling, automation rules that update structured objects, integration depth into productivity and development systems, and governance signals like permissions and audit history.
monday.com separated from lower-ranked tools because workflow automations update fields, statuses, and assignees from triggers while dashboards reflect the same enriched fields used for execution. That combination raised the features factor by tying automation throughput to schema-backed reporting, and it also improved ease of use because teams can act on visible field-level progress rather than chasing updates across artifacts.
Frequently Asked Questions About Collaboration Project Software
How should a team choose between monday.com, Asana, and ClickUp for project status reporting across multiple workstreams?
Which tools offer the strongest integration and API paths for connecting collaboration data to existing systems?
What is the practical difference between building project workflows in templates versus relying on automations?
How do monday.com and Notion compare for modeling relationships between tasks, decisions, and artifacts?
Which platform is better for meeting notes that stay connected to delivery work, and why?
What should an admin look for when setting identity, access, and audit visibility across projects?
How do teams handle data migration when moving from spreadsheets or other tools into a structured collaboration system?
What are common failure points when setting up RBAC-like permissions for collaboration workspaces?
Which tools best support issue-driven delivery workflows with traceable relationships between work items and discussions?
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.