GITNUXSOFTWARE ADVICE
Business FinanceTop 10 Best Organizational Management Software of 2026
Ranked comparison of top organizational management software, with features and tradeoffs for teams evaluating Wrike, Smartsheet, and Oracle HCM Cloud.
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
Choose Wrike if you need governed intake, approvals, and dependency-aware execution across departments, while Smartsheet is a strong pick for ops teams that want approvals and dashboards without custom workflow apps; if you’re looking to start with HR org control, Oracle HCM Cloud is the budget-minded entry.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Wrike
Wrike request forms can launch structured work items into predefined workflow stages with approval routing.
Smartsheet
Editor pickAutomation rules can trigger from form submissions and record edits to route approvals and status updates.
Oracle HCM Cloud
Editor pickPosition-centric role and approval interactions with RBAC-aware governance for org changes.
Related reading
Comparison Table
This comparison table covers organizational management software from tools such as Wrike, Smartsheet, Oracle HCM Cloud, Notion, and Asana. It focuses on integration depth, automation and API surface, and admin and governance controls so readers can map each platform’s configuration and extensibility to team workflows.
Wrike
enterpriseCollaborative work management with enterprise-grade organizational controls.
Wrike request forms can launch structured work items into predefined workflow stages with approval routing.
Wrike delivers organizational management through structured workspaces, task hierarchies, and workflow stages that teams can standardize across departments. Organizations can model handoffs using forms, request-to-workflows, and approval steps tied to accountable roles. Reporting can aggregate progress across projects, programs, and portfolios, so leaders see planned versus actual movement.
A key tradeoff is governance overhead when many teams share templates and automation rules, since inconsistent naming and owner assignment breaks rollups. Wrike fits situations where cross-team planning needs recurring intake, approvals, and dependency tracking, such as marketing campaign demand routed from multiple request sources.
- +Workflow stages with approvals reduce ad hoc email handoffs
- +Dependency tracking keeps cross-team schedules tied to execution
- +Portfolio reporting aggregates status across many workstreams
- +Automation rules connect intake, tasks, and notifications consistently
- –Template and naming standards require ongoing governance discipline
- –Advanced rollups can lag when work is created via complex automation
- –Matrix-style responsibility needs careful modeling to avoid ambiguity
- –Some admin controls feel granular but time-consuming for large tenants
Program management offices
Portfolio reporting across many delivery streams
Faster status decisions
Operations and process owners
Standard intake with approvals
Lower cycle time
Show 2 more scenarios
Department leads
Dependency tracking for cross-team work
Fewer schedule surprises
Connects tasks across workspaces so timelines reflect blocked work and readiness states.
IT and systems teams
Integrate work with existing tools
Reduced manual updates
Uses API-based integration patterns to synchronize work events with external systems.
Best for: Fits when organizations need governed intake, approvals, and dependency-aware execution across departments.
Smartsheet
enterpriseSpreadsheet-based platform for enterprise work and organizational process management.
Automation rules can trigger from form submissions and record edits to route approvals and status updates.
Smartsheet is a good fit for organizations that want one shared system for intake, task execution, and status reporting without building custom apps for every workflow. The platform provides reusable templates, structured sheets, and reporting views that can be linked across teams to keep rollups consistent. Automation runs around events like form submissions and record edits, which reduces manual handoffs across departments.
A key tradeoff is that Smartsheet’s org structure coverage is less purpose-built than HR-centric tools, so building complex position control and role hierarchy requires careful sheet modeling. Smartsheet works well when workflows map cleanly to records, approvals, and timelines, such as portfolio governance or cross-team operational change tracking.
- +Spreadsheet-native editing with grid, timeline, and reporting views
- +Approval workflows tied to records and deadlines
- +Automation based on events like form submission and field changes
- +Admin governance includes role-based permissions and activity visibility
- –Complex org modeling needs careful sheet schema design
- –Advanced automation can require disciplined rule naming and testing
- –Data governance depends on consistent templates and controlled sharing
- –Cross-system automation often needs integration tooling for scale
Program management teams
Track approvals across project work
Faster cycle times and fewer handoffs
Operations governance teams
Centralize intake and portfolio reporting
Single source of operational truth
Show 2 more scenarios
Project coordinators
Coordinate dependencies and due dates
Lower schedule slip rates
Teams use linked views to reflect dependency changes in time and status reports.
Admin and compliance owners
Control sharing and track changes
Better governance and audit readiness
Admins apply role-based access and review activity for configuration and content changes.
Best for: Fits when ops and project teams need approvals and dashboards without custom workflow apps.
Oracle HCM Cloud
enterpriseIntegrated HR cloud suite for global talent and organizational management.
Position-centric role and approval interactions with RBAC-aware governance for org changes.
Oracle HCM Cloud supports organizational hierarchies through a position and assignment-centric approach that maps people to positions and reporting structures. Admins can model functional org structures, matrix reporting with dotted-line relationships, and cost center hierarchies used for span and headcount reporting. Automation is supported through Oracle integration services plus a broad API surface for synchronization and custom workflow triggers.
A key tradeoff is that the position taxonomy and location to department code mapping require careful upfront configuration to keep org reporting, approvals, and permissions aligned. The strongest fit is workforce planning and authorization-heavy org changes where changes must cascade to reporting, approvals, and audit trails without manual spreadsheets.
- +Position-driven org modeling keeps reporting aligned with assignments
- +APIs and integration services support automated org provisioning
- +Audit logs and RBAC enable controlled admin operations
- +Identity support covers SAML SSO and SCIM provisioning
- –Position taxonomy setup demands governance and ongoing maintenance
- –Matrix configuration can add complexity for new org designers
- –Some org reporting views depend on consistent coding practices
- –Advanced customization often requires implementation support
HR operations teams
Run position-controlled org restructures
Fewer mismatched org snapshots
IT identity engineering
Provision users into HCM securely
Reduced manual provisioning work
Show 2 more scenarios
Finance workforce planners
Plan headcount by cost hierarchy
More consistent forecast inputs
Use structured cost center hierarchies tied to positions for forecast views and reporting.
Enterprise integration teams
Automate org data synchronization
Higher update throughput
Integrate external org data using published APIs and integration workflows.
Best for: Fits when enterprise org changes need position-based control, automation, and identity-managed provisioning.
Notion
SMBAll-in-one workspace for docs, wikis, projects, and organizational knowledge.
Template-based database views let org data, workflows, and artifacts stay linked through a consistent page structure.
Notion combines doc editing, databases, and workspace pages into a single system for tracking work across teams. It supports configurable workflows through linked databases, templates, and views that can model projects, roles, and reporting relationships.
The permission model offers space-level access controls and edit restrictions, while its API and integrations enable synchronization with external tools and internal apps. Organizational management tasks work best when the needed structure can be expressed as interconnected databases and consistent page templates.
- +Database-backed pages keep org data linked to projects and policies
- +Templates and views reduce repeat work for recurring reviews
- +API and webhooks support external sync and workflow automation
- +Granular page controls support separation between team spaces
- –Complex org charts require more manual structuring than dedicated tools
- –Reporting relationships become harder to audit when many custom properties exist
- –Approval workflows need careful setup for consistent routing
- –Admin governance for large enterprises is limited compared with HR suites
Best for: Fits when teams need a database-driven org workspace with flexible views and automation via API.
Asana
SMBWork management platform for goals, portfolios, and team coordination.
Rules-based automation that triggers on task and project events to drive approvals, nudges, and status transitions.
Asana tracks work through task lists, project boards, and timelines so teams can plan, assign, and follow progress at scale. It supports operational coordination with rule-based automation, status updates, and portfolio-style views that aggregate work across multiple projects.
Asana also integrates with collaboration and developer tools through an automation and app ecosystem, and it provides APIs for custom workflows. Org management often uses Asana for approval paths and cross-team execution, even when it is not a full HRIS or formal org-chart system.
- +Timeline and dependency views connect planning with delivery status
- +Automation rules reduce manual follow-ups across recurring workflows
- +API and webhooks support custom integrations and sync patterns
- +Fine-grained project roles support safer collaboration boundaries
- –Automation rules can become harder to reason about at high scale
- –Advanced governance needs careful workspace and project structure
- –Work graphs fit execution better than formal role hierarchy modeling
- –Data model limits make bulk org roster imports less native than HR suites
Best for: Fits when teams need assignment-level tracking, automation, and cross-project reporting without an HR-grade org model.
ClickUp
SMBProductivity platform combining tasks, docs, goals, and team management.
ClickUp Automations can trigger cross-space actions, like assigning ownership and starting review cycles from status and custom field changes.
ClickUp is an organizational management tool that centers on workspaces, tasks, and dashboards rather than fixed org-chart modules. It supports cross-functional planning with customizable views, reusable templates, and large-scale task tracking that can map to role-based processes.
Reporting and governance come through permission controls, status workflows, and automation rules that connect approvals, ownership changes, and recurring reviews. ClickUp also offers an API and webhook-style integrations that support syncing HR data into operational workflows.
- +Flexible views and dashboards for role and team visibility
- +Automation rules can drive recurring reviews and handoffs
- +Deep integration surface with API and third-party connectors
- +Granular permissions support multi-team workspace governance
- –Org-structure modeling needs careful configuration to stay consistent
- –Large workspaces can become slow without disciplined organization
- –Reporting on delegation and hierarchy is indirect versus dedicated models
- –Advanced setups rely on admin ownership of templates and rules
Best for: Fits when org processes can live in task workflows and dashboards with controlled admin governance.
PeopleSpheres
SMBUnified HR platform integrating people data and organizational workflows.
A change workflow engine that binds structural edits to delegated authority and approval steps in one operational flow.
PeopleSpheres targets org and workforce management with a governance-first approach to structures, roles, and workflows. Core capabilities include role and position modeling, org chart visualization, and approvals tied to structural changes.
Admin control features focus on permissioning for who can edit elements and run change workflows, with audit-friendly activity tracking built into day-to-day operations. Integration support emphasizes employee data onboarding and ongoing synchronization so the organizational model stays consistent with HR records.
- +Clear separation between positions, people assignments, and role rules
- +Approval workflow coverage for structural edits reduces process bypass
- +Org views support fast span-of-control and reporting-line checks
- +Configurable permissioning limits who can change sensitive entities
- –Complex role hierarchy setup takes time before automation pays off
- –CSV roster import mappings can be brittle for nonstandard fields
- –API and automation breadth lag behind systems focused on workforce planning
- –Matrix reporting edge cases need extra configuration for dotted lines
Best for: Fits when enterprises need controlled org maintenance with approvals and strong permissioning, not just visual charts.
Trello
SMBKanban-based board tool for visual task and team organization.
Butler automation rules can move cards, assign users, and post comments based on card activity.
Trello is a visual work management tool built around boards, lists, and cards. Teams use it to track tasks, ownership, and status changes with low setup friction.
Core capabilities include drag-and-drop workflow, card comments and attachments, labels, due dates, and board permissions for shared collaboration. Trello also supports automation via Butler and integrates with external apps through public APIs and connector ecosystems.
- +Boards, lists, and cards enable fast task tracking without complex configuration
- +Drag-and-drop workflow keeps status management easy for distributed teams
- +Butler automations handle triggers, rules, and reminders without writing code
- +Public API supports programmatic updates to cards, boards, and users
- –Workflow depth stays limited for approvals and role-based delegation
- –Governance controls are lighter than enterprise workflow engines with audit-grade histories
- –Data modeling for cross-board reporting remains manual and template-driven
- –Reporting stays basic for capacity planning and span-of-control style views
Best for: Fits when teams need visual task workflows and light automation without code across shared boards.
Jira
enterpriseIssue and project tracking tool for agile and cross-functional teams.
Jira workflow engine supports scripted-like governance using conditions, validators, and post-functions on every transition.
Jira turns work requests into tracked issues with workflow states, assignment rules, and status history. Jira’s core capability is project-based issue management with configurable workflows, issue types, and dashboards that summarize progress across teams.
Automation rules connect triggers like issue created or status changed to actions like transitions, field updates, and notifications. Jira also has an automation and API surface through Atlassian apps and webhooks that support custom integrations with external systems.
- +Configurable workflows with conditions, validators, and transition permissions
- +Automation rules trigger on issue events and drive transitions and field updates
- +Dashboards aggregate status, burndown, and custom reporting for multiple projects
- +Extensible via REST APIs and webhooks for external process integration
- –Workflow design can become complex when many issue types share transitions
- –Reporting for org-level structures needs careful modeling in custom fields
- –Cross-team governance requires consistent permissions and project-level configuration
- –Some advanced automation patterns depend on additional marketplace apps
Best for: Fits when organizations need configurable issue workflows and cross-team reporting backed by integration-ready APIs.
Basecamp
SMBSimplified project and team communication tool for small organizations.
Message boards link discussion threads to project context, reducing back-and-forth between tools.
Basecamp fits teams that manage work through shared projects, threaded discussions, and lightweight timelines rather than enterprise org structures. Core capabilities include message boards per project, file and link sharing, to-do lists, and a calendar view for deadlines and milestones.
Organization management is handled indirectly through project-level roles and consistent workspace conventions rather than directory-based provisioning. Basecamp also supports integrations via a public API, enabling automation around posts, tasks, and project data.
- +Project threads keep decisions attached to work items
- +To-do lists and milestones cover day-to-day execution
- +Calendar view makes deadlines visible across projects
- +API enables automation around projects and tasks
- –No native org chart or position control features
- –Limited governance tools for company-wide role hierarchy
- –Workflow automation is lighter than dedicated operations engines
- –Admin audit log depth is not designed for compliance-heavy teams
Best for: Fits when teams need shared project execution and conversations without building an org hierarchy.
Conclusion
After evaluating 10 business finance, Wrike 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 organizational management software
This buyer's guide covers organizational management software tools used to run structured org changes, approvals, reporting relationships, and cross-team execution in one place. It compares Wrike, Smartsheet, Oracle HCM Cloud, Notion, Asana, ClickUp, PeopleSpheres, Trello, Jira, and Basecamp.
The guide turns the tools' concrete capabilities into evaluation criteria and decision steps. It also flags recurring governance and modeling pitfalls, based on how each tool handles approvals, automation, permissions, and org-structure representation.
Organizational management software for controlled structure changes and approval-driven workflows
Organizational management software coordinates how org structures get defined, changed, approved, and reported, with traceable status across departments and roles. It typically links structural inputs such as positions and assignments to workflow steps, notifications, and reporting views.
Tools like Oracle HCM Cloud model org structures through position-centric control tied to RBAC-aware governance, while Wrike turns request forms into structured work items that enter predefined approval stages. Teams also use Smartsheet to route approvals from record edits and form submissions without building custom workflow apps.
Evaluation criteria for org modeling, approvals, and governance automation
Organizational management succeeds when structural changes can be created through consistent inputs and pushed through the right approval stages. Tools like Wrike and Smartsheet show how form and record triggers can keep intake, routing, and status updates aligned.
The next tier of evaluation focuses on how each tool handles modeling complexity and governance over time. Oracle HCM Cloud and PeopleSpheres place org maintenance behind delegated authority and audit-friendly controls, while tools like Notion and Asana rely on database templates and task workflows.
Approval routing that launches structured work from forms or record edits
Wrike request forms can launch structured work items into predefined workflow stages with approval routing. Smartsheet automation rules can trigger from form submissions and record edits to route approvals and status updates.
Position or structure-first modeling tied to roles and delegated authority
Oracle HCM Cloud uses position-centric role and approval interactions with RBAC-aware governance for org changes. PeopleSpheres binds structural edits to delegated authority and approval steps in a change workflow engine.
Automation rules that trigger on status and custom field changes
Asana rules can trigger on task and project events to drive approvals, nudges, and status transitions. ClickUp Automations can trigger cross-space actions, including starting review cycles and assigning ownership from status and custom field changes.
Admin governance controls with audit visibility for configuration and content changes
Smartsheet includes admin governance with role-based permissions and activity visibility for configuration changes and content updates. Oracle HCM Cloud pairs RBAC with audit logs to support controlled administration across HR, finance, and IT teams.
API and extensibility for provisioning and cross-system synchronization
Oracle HCM Cloud supports published APIs plus SCIM-based provisioning and SAML SSO integration for identity-managed workflows. Wrike provides an API and extensibility surface that helps connect intake, tasks, and notifications to existing systems of record.
Data-linked org workspaces with reusable templates and consistent views
Notion template-based database views keep org data, workflows, and artifacts linked through a consistent page structure. Wrike and Asana also use templates and views, but Wrike focuses on workflow stages with dependency-aware execution.
Decision framework for selecting the org management tool that matches the approval and structure model
Start by mapping how structural changes are created in the business. Wrike fits when intake happens through structured request forms and needs dependency-aware execution across departments, while Smartsheet fits when ops teams want approvals tied to record deadlines and grid data.
Next choose the modeling philosophy. Oracle HCM Cloud and PeopleSpheres center on position or structure with delegated authority checks, while Asana, ClickUp, and Jira center on execution objects like tasks or issues that can approximate org workflows.
Choose the object that represents org change
If org changes originate as position and assignment edits with controlled access, Oracle HCM Cloud and PeopleSpheres support position-centric or structure-first governance that drives approvals. If org changes originate as requests and need structured routing into workflow stages, Wrike request forms provide that launch point into predefined approval stages.
Pick the automation trigger type that matches operational reality
For intake-driven routing, Smartsheet automation rules trigger from form submissions and record edits to route approvals and status updates. For execution-driven handoffs, Asana rules trigger on task and project events and ClickUp Automations trigger cross-space actions from status and custom field changes.
Decide how governance should be enforced across teams and spaces
For company-wide admin controls with audit logs and RBAC-aware governance, Oracle HCM Cloud and Smartsheet provide governance with audit visibility for admin actions and configuration changes. For teams that can enforce governance through structure and templates, Wrike requires template and naming standards to avoid ambiguity and timing issues.
Validate how org reporting relationships will be audited after custom modeling
If the org workspace relies on many custom properties, Notion can make reporting relationships harder to audit as customization grows. If org reporting views depend on consistent coding practices, Oracle HCM Cloud requires discipline so reporting stays aligned with the position model.
Match extensibility needs to your integration and provisioning requirements
If identity provisioning and SSO are part of org change operations, Oracle HCM Cloud supports SCIM-based provisioning and SAML SSO plus automation-ready APIs. If integration is mainly about pushing work status and notifications, Wrike and Jira provide APIs and webhooks that support custom integrations for workflow transitions and reporting.
Stress-test hierarchy modeling complexity and performance at scale
If matrix responsibility and dotted-line reporting must be precise, PeopleSpheres and Wrike both require careful modeling because matrix-style responsibility can add ambiguity or extra configuration. If complex org modeling is attempted in spreadsheet schemas, Smartsheet requires careful sheet schema design and structured templates to avoid brittle governance and automation rule naming issues.
Which teams should adopt each organizational management approach
Different tools fit different org change lifecycles. The best match depends on whether the workflow starts as a structured request, a record update, or a position-driven HR process.
The following segments map to the best-fit guidance for each tool.
Enterprise org ops that treat org changes as position-controlled, identity-provisioned workflows
Oracle HCM Cloud fits because it centralizes org management with a position model tied to RBAC-aware governance and audit logs. It also supports SCIM-based provisioning and SAML SSO so org changes can be automated through identity-managed access.
Organizations that need governed intake with dependencies and approval stages across departments
Wrike fits because request forms launch structured work items directly into predefined workflow stages with approval routing. Its dependency tracking keeps cross-team schedules tied to execution when multiple workstreams run at once.
Ops and project teams that want approvals and dashboards without building custom workflow apps
Smartsheet fits when teams need spreadsheet-native grid and timeline views plus approvals tied to records and deadlines. Its automation rules trigger from form submissions and record edits so routing stays aligned with the record lifecycle.
Enterprises that need a governance-first org maintenance workflow with delegated authority checks
PeopleSpheres fits because its change workflow engine binds structural edits to delegated authority and approval steps in one operational flow. Permissioning limits who can edit sensitive entities while org views support span-of-control and reporting-line checks.
Cross-functional teams that can represent org processes as task or issue workflows
Asana and ClickUp fit when assignment-level execution and cross-project reporting matter more than formal role hierarchy modeling. Jira fits when issue workflows with conditions, validators, and post-functions drive governance through every transition.
Common implementation pitfalls in org management tools
Org management failures usually come from mismatched modeling discipline or unclear governance boundaries. Tools that rely on templates and custom properties need consistent standards so approvals and reporting stay accurate.
The pitfalls below show where each tool tends to break when org modeling and automation are treated as ad hoc work.
Modeling matrix responsibility without a governance plan for dotted-line ambiguity
Wrike and PeopleSpheres both require careful matrix modeling to avoid ambiguous responsibility, especially for dotted-line scenarios. PeopleSpheres adds extra configuration effort for matrix reporting edge cases, so delegation rules must be designed before automation runs.
Letting templates or naming conventions drift across teams
Wrike can require ongoing governance discipline for template and naming standards so workflow stages stay understandable across departments. Smartsheet advanced automation also needs disciplined rule naming and testing so routing does not degrade over time.
Overbuilding org reports in flexible workspaces without a reporting audit strategy
Notion can make reporting relationships harder to audit when many custom properties exist. Oracle HCM Cloud also depends on consistent coding practices for some org reporting views, so coding drift leads to misaligned reporting.
Treating approval workflows as decoration instead of enforced workflow transitions
Trello keeps workflow depth limited for approvals and role-based delegation, so approvals need stronger workflow coverage than boards alone. Basecamp has no native org chart or position control features, so org approval workflows must be implemented through project conventions rather than directory-grade structures.
Assuming complex org modeling will be native to spreadsheet schemas or task graphs
Smartsheet requires careful sheet schema design for complex org modeling, and role hierarchies can become brittle when schemas vary. Asana and ClickUp fit org processes as execution workflows, but reporting on delegation and hierarchy can be indirect versus dedicated org models.
How We Selected and Ranked These Tools
We evaluated Wrike, Smartsheet, Oracle HCM Cloud, Notion, Asana, ClickUp, PeopleSpheres, Trello, Jira, and Basecamp using three scored areas: features, ease of use, and value. Features carried the most weight at 40 percent, while ease of use and value each accounted for 30 percent of the overall score. Each score reflects criteria-based research from the capabilities described for every tool rather than private product lab testing.
Wrike separated itself because request forms launch structured work items into predefined workflow stages with approval routing, and it also ties cross-team execution to dependency tracking. That standout capability aligns directly with features and governance automation, which lifted it above tools that focus more on boards, tasks, or lightweight coordination.
Frequently Asked Questions About organizational management software
How do Wrike and Asana differ for approval-driven work intake?
Which tools support identity provisioning and SSO for org data access?
How does data migration typically work when moving an existing org chart into a new system?
What admin controls and audit visibility exist for configuration changes?
How do Notion and Trello model organizational relationships without fixed HR modules?
When does a position-based model matter more than a task-based workflow model?
What breaks if automation is driven only by spreadsheets or lightweight boards?
Where does extensibility show up in practice for org management workflows?
How does PeopleSpheres bind structural edits to approvals and delegated authority?
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 Finance alternatives
See side-by-side comparisons of business finance tools and pick the right one for your stack.
Compare business finance 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.