Top 10 Best Faster Software of 2026

GITNUXSOFTWARE ADVICE

General Knowledge

Top 10 Best Faster Software of 2026

Compare Faster Software tools with a top 10 ranking of speed-focused picks like Notion, monday.com, and Linear. Explore options fast.

10 tools compared25 min readUpdated 5 days agoAI-verified · Expert reviewed
How we ranked these tools
01Feature Verification

Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.

02Multimedia Review Aggregation

Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.

03Synthetic User Modeling

AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.

04Human Editorial Review

Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.

Read our full methodology →

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

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

This ranked list focuses on software that reduces cycle time through automation, fast collaboration, and streamlined execution workflows. Readers can compare top options for planning, documentation, and issue tracking, then pick the platform that matches team speed requirements without building a complex process.

Editor’s top 3 picks

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

Editor pick
1

Notion

Relational databases with multiple synced views and powerful query-style filtering

Built for teams building structured knowledge bases and lightweight project systems.

2

monday.com

Editor pick

Automation recipes that update fields, create tasks, and notify stakeholders across boards

Built for teams standardizing workflows with visual automation and cross-project reporting.

3

Linear

Editor pick

Cycle view for planning work around milestones and iterative delivery

Built for engineering teams managing roadmaps, releases, and GitHub-linked execution.

Comparison Table

This comparison table maps Faster Software tools across workflow and documentation needs, including Notion, monday.com, Linear, Jira Software, and Confluence. It highlights how each platform structures project planning, issue tracking, team collaboration, and knowledge capture so readers can match tool capabilities to their operating model.

1
NotionBest overall
workspace
9.2/10
Overall
2
work management
8.9/10
Overall
3
issue tracking
8.6/10
Overall
4
agile platform
8.3/10
Overall
5
team knowledge
7.9/10
Overall
6
team messaging
7.6/10
Overall
7
collaboration suite
7.3/10
Overall
8
productivity suite
6.9/10
Overall
9
kanban boards
6.6/10
Overall
10
task management
6.3/10
Overall
#1

Notion

workspace

Provides fast, flexible workspace pages, databases, and team collaboration features for knowledge management and lightweight project tracking.

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

Relational databases with multiple synced views and powerful query-style filtering

Notion stands out for combining docs, databases, and lightweight project tracking in one shared workspace. Core capabilities include customizable pages, relational databases with filters and views, and collaborative editing with comments and mentions. Users can build templates and automate workflows using Notion Automations and embedded integrations. Shared portals and permission controls support team knowledge bases and structured operations.

Pros
  • +Relational databases with views for boards, tables, and calendars
  • +Fast page templating with reusable blocks and databases
  • +Real-time collaboration with mentions and threaded comments
  • +Granular sharing and workspace permissions for teams
  • +Automations to trigger actions across common workflows
Cons
  • Complex database modeling can become difficult to maintain
  • Performance can degrade with very large databases and heavy embeds
  • Offline editing is limited compared with dedicated offline apps
  • Advanced rollups and formulas can require steep setup effort
  • File-heavy use cases can feel less structured than DAM tools

Best for: Teams building structured knowledge bases and lightweight project systems

#2

monday.com

work management

Offers configurable work management boards for projects, operations, and workflows with automations and real-time team visibility.

8.9/10
Overall
Features9.2/10
Ease of Use8.7/10
Value8.8/10
Standout feature

Automation recipes that update fields, create tasks, and notify stakeholders across boards

monday.com stands out for highly customizable work boards that connect tasks, owners, and timelines into one shared view. Teams build workflows with visual status updates, automations, and dashboards that summarize progress across projects. Reporting and integrations support cross-tool coordination for operations, product, and delivery work. Permission controls and templates help standardize execution while keeping per-team flexibility.

Pros
  • +Flexible board layouts with multiple field types for task detail capture
  • +Powerful automation rules that trigger updates across boards and workflows
  • +Dashboards with real-time KPIs for tracking progress without manual reporting
  • +Strong project views including timelines and workload-style summaries
  • +Integrates with common work tools to reduce context switching
Cons
  • Complex boards can become hard to maintain without clear standards
  • Some advanced workflows require deeper configuration to scale cleanly
  • High customization can increase user training and onboarding time
  • Large boards may feel slower with heavy automation and many updates

Best for: Teams standardizing workflows with visual automation and cross-project reporting

#3

Linear

issue tracking

Delivers fast issue tracking with planning, issue workflows, and integrations that streamline product and engineering execution.

8.6/10
Overall
Features8.4/10
Ease of Use8.8/10
Value8.5/10
Standout feature

Cycle view for planning work around milestones and iterative delivery

Linear focuses on fast issue tracking with a lightweight interface and keyboard-first workflows. Teams manage software delivery through custom fields, milestones, and issue views that stay tightly connected to statuses. Roadmaps and cycle-based planning tie work items to releases, while integrations connect issues to GitHub workflows. Collaboration features like mentions, comments, and shared filters make triage and handoffs smoother across engineering teams.

Pros
  • +Keyboard-first issue creation and updates accelerate everyday triage
  • +Cycle-based roadmap planning keeps milestones aligned to delivery timelines
  • +GitHub integration links commits and pull requests to issues
  • +Custom issue fields improve reporting across different project types
Cons
  • Advanced reporting requires more setup than basic dashboard needs
  • Non-development workflows need extra modeling to fit issue-first structure
  • Some enterprise governance features are limited for large organizations

Best for: Engineering teams managing roadmaps, releases, and GitHub-linked execution

#4

Jira Software

agile platform

Provides advanced agile planning and issue workflows with dashboards, automation, and a large ecosystem of integrations.

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

Configurable issue workflows with automation rules for status and field-driven transitions

Jira Software stands out with tightly structured workflows built around issue types and status transitions. It enables teams to plan with Scrum boards and track work with Kanban boards backed by configurable fields and automation rules. Reporting tools such as dashboards and advanced roadmaps help connect delivery progress to epics and releases.

Pros
  • +Configurable issue workflows with granular statuses and transitions
  • +Scrum and Kanban boards support sprint and continuous delivery tracking
  • +Powerful automation rules reduce manual updates across projects
  • +Dashboards and roadmaps visualize progress from epics to releases
Cons
  • Workflow complexity increases admin overhead for large project setups
  • Cross-project reporting can require careful hierarchy and naming conventions
  • Advanced analytics depend on consistent issue hygiene by teams
  • UI can feel heavy with many custom fields and gadgets

Best for: Teams tracking software delivery with structured workflows and agile boards

#5

Confluence

team knowledge

Enables team documentation and knowledge bases with collaborative editing, structured spaces, and seamless linking to Jira work.

7.9/10
Overall
Features7.8/10
Ease of Use8.0/10
Value8.0/10
Standout feature

Page templates with macros like Jira Issue and decision logs for reusable documentation blocks

Confluence stands out for team knowledge building with highly structured pages, shared spaces, and strong collaboration across organizations. It supports real-time co-editing, page templates, and search across content and attachments. Built-in permissions enable space-level access control, while integrations with Atlassian tools connect documentation to issues, sprints, and releases. Automation through Atlassian workflows and add-ons helps keep documentation aligned with ongoing work.

Pros
  • +Structured spaces organize documentation by team, project, and program
  • +Fast search finds pages and attachments across spaces
  • +Real-time editing supports smooth collaboration and version history
  • +Granular permissions control who can view and manage spaces
  • +Integrates with Jira to link requirements, bugs, and releases
Cons
  • Large knowledge bases can feel complex to navigate without strict conventions
  • Advanced customization often depends on additional apps or administrators
  • Permissions changes can be error-prone across linked content
  • Content governance requires active ownership to prevent stale pages

Best for: Teams maintaining living documentation with Jira-linked knowledge and shared governance

#6

Slack

team messaging

Delivers real-time team messaging, channels, search, and workflow integrations to reduce time-to-decision and handoffs.

7.6/10
Overall
Features7.7/10
Ease of Use7.4/10
Value7.6/10
Standout feature

Slack Connect for controlled external collaboration across organizations

Slack stands out with organization-wide communication centered on channels, threads, and searchable message history. The platform supports file sharing, direct messaging, and structured collaboration through app integrations and workflow automation. Slack Connect enables controlled cross-company collaboration with external teams. Enterprise administration tools add governance features like message retention controls and user management.

Pros
  • +Channel-based communication scales teams without losing context
  • +Threaded replies keep discussions readable and searchable
  • +Slack apps integrate tools like Jira, GitHub, and Google Drive
  • +Slack Connect supports secure collaboration with external organizations
Cons
  • Large channels can become noisy without strong channel hygiene
  • Thread usage varies by team, reducing consistent organization
  • Some advanced governance features require deeper admin configuration
  • Automation often depends on third-party apps for full coverage

Best for: Teams needing channel-based collaboration with strong integrations

#7

Microsoft Teams

collaboration suite

Combines chat, meetings, file collaboration, and app integrations to centralize team communication and execution.

7.3/10
Overall
Features7.6/10
Ease of Use7.0/10
Value7.1/10
Standout feature

Teams channels combined with SharePoint-backed file collaboration

Microsoft Teams distinguishes itself by tightly integrating chat, meetings, and collaboration with Microsoft 365 productivity tools. It supports scheduled and on-demand video meetings, persistent team chat, file sharing in SharePoint and OneDrive, and structured collaboration through Teams channels. Automation and coordination are strengthened by workflow options like approvals and task tracking, with extensibility via bots and Power Platform apps. Enterprise administration features include role-based access controls and audit capabilities designed for governed organizations.

Pros
  • +Video meetings with screen sharing, recording, and live captions
  • +Persistent channels for topic-based chat and announcements
  • +Deep Microsoft 365 integration with Word, Excel, and PowerPoint collaboration
  • +Robust permissions via Azure AD and granular team controls
Cons
  • Channel sprawl can make searching conversations and context difficult
  • External sharing requires careful configuration to avoid overexposure
  • Large organizations may face governance overhead for many connected apps
  • App customization can lead to inconsistent experiences across teams

Best for: Organizations standardizing collaboration around Microsoft 365 for team communication

#8

Google Workspace

productivity suite

Provides Gmail, Google Drive, Docs, Sheets, and shared collaboration workflows that support fast team execution.

6.9/10
Overall
Features7.1/10
Ease of Use6.7/10
Value7.0/10
Standout feature

Shared Drives with granular permissions and centralized ownership for teams

Google Workspace unifies Gmail, Calendar, Drive, Docs, Sheets, and Meet into one admin-managed productivity suite. Team collaboration is built into shared documents with real-time editing, version history, and permission controls. Centralized identity and device management support secure access for users and endpoints. Meet and Chat integrate with email and calendar scheduling to connect communication and work artifacts.

Pros
  • +Real-time Docs and Sheets co-editing with change history and activity tracking
  • +Shared Drive structures access across teams without manual folder micromanagement
  • +Meet supports scheduled video meetings tied to Calendar invites
  • +Strong admin controls for user provisioning, security settings, and audit logs
  • +Gmail search and filters make high-volume inbox operations faster
Cons
  • Advanced workflow automation relies heavily on separate Google automation components
  • Drive permissions can be confusing when mixing shared drives and personal drives
  • Offline editing support is limited for complex file types and workflows
  • Reporting depth for some admin events requires careful configuration

Best for: Teams needing secure cloud collaboration with email, docs, and meetings

#9

Trello

kanban boards

Uses simple kanban boards with cards, checklists, automation, and collaboration to move work quickly.

6.6/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.8/10
Standout feature

Power-Ups and Butler automation trigger actions based on card and board events

Trello stands out with its card-and-board interface for visual planning, tracking, and lightweight workflow management. Boards, lists, and cards support tasks with checklists, due dates, attachments, comments, and labels. Teams can add collaboration features like mentions, activity history, and board permissions for shared execution. Power-ups extend boards with integrations such as calendar views, automation, and form intake to reduce manual coordination.

Pros
  • +Boards and cards deliver fast, visual task tracking for teams.
  • +Checklists, due dates, labels, and attachments keep work organized.
  • +Comments and mentions centralize collaboration on each card.
Cons
  • Complex workflows become hard to manage with basic columns.
  • Native reporting is limited without added integrations.
  • Activity history and audit depth are less robust than enterprise tools.

Best for: Teams needing visual task tracking and simple workflow automation without code

#10

Asana

task management

Supports task management, timelines, and team coordination with automation and reporting for faster delivery.

6.3/10
Overall
Features6.3/10
Ease of Use6.5/10
Value6.0/10
Standout feature

Portfolios with progress and custom field rollups across multiple projects

Asana stands out with flexible work views that connect tasks to projects, goals, and timelines in one place. It supports task assignments, due dates, dependencies, and comments so teams can track execution without switching tools. Automation rules route work, update fields, and move items across projects when conditions match. Portfolios and dashboards provide rollups for project status and progress across many workstreams.

Pros
  • +Task dependencies and timeline views keep cross-team work sequenced
  • +Automation rules move and update tasks based on defined triggers
  • +Portfolios roll up progress across multiple projects
  • +Goals connect work to outcomes with measurable tracking
  • +Workload and timeline views highlight resourcing bottlenecks
Cons
  • Complex portfolio and automation setups can become hard to audit
  • Permission management across many projects may feel administratively heavy
  • Reporting depth depends on consistent field hygiene

Best for: Teams coordinating projects with multiple views, automation, and portfolio rollups

How to Choose the Right Faster Software

This buyer's guide explains how to pick the right Faster Software tool for faster execution, smoother collaboration, and less manual coordination. It covers Notion, monday.com, Linear, Jira Software, Confluence, Slack, Microsoft Teams, Google Workspace, Trello, and Asana using concrete capabilities like automations, issue workflows, and structured views.

What Is Faster Software?

Faster Software tools help teams move work forward with fast capture, clear status visibility, and automation that reduces manual updates. This category usually combines structured workflows such as boards or issue tracking with collaboration tools like mentions, comments, and real-time editing. Notion shows what this looks like as a shared workspace that combines relational databases and lightweight project tracking. Linear shows another common pattern with keyboard-first issue tracking tied to cycle planning and GitHub integrations.

Key Features to Look For

These features matter because the fastest tools reduce coordination overhead by keeping work items, context, and approvals connected in one place.

  • Relational data with multiple synced views and query-style filtering

    Notion supports relational databases with multiple synced views like boards, tables, and calendars plus powerful query-style filtering. This structure keeps knowledge and project tracking consistent, but it needs careful database modeling to avoid maintenance complexity. Teams that want structured systems for work and documentation often reach for Notion.

  • Automation recipes that update fields, create tasks, and notify stakeholders

    monday.com is built around automation recipes that update fields, create tasks, and notify stakeholders across boards. Trello adds Butler automation to trigger actions based on card and board events. Asana moves items across projects and updates fields through automation rules when conditions match.

  • Cycle or milestone planning that stays tied to delivery

    Linear provides a cycle view that plans work around milestones and iterative delivery. This keeps planning aligned with execution for engineering teams that work in release cycles. Asana also supports timeline views and workload views to show sequencing and resourcing bottlenecks.

  • Configurable issue workflows with status transitions and rule-driven movement

    Jira Software delivers configurable issue workflows with granular statuses and transitions backed by automation rules for status and field-driven transitions. This model connects execution to agile boards like Scrum boards and Kanban boards. It works best when teams maintain consistent issue hygiene so dashboards and roadmaps remain accurate.

  • Living documentation blocks that link to work items

    Confluence offers page templates and macros such as Jira Issue and decision logs for reusable documentation blocks. This supports consistent decision capture and requirement or bug context tied to Jira work. Confluence also uses structured spaces and page-level templates to keep large knowledge bases organized.

  • Collaboration channels with searchable context and enterprise governance

    Slack organizes communication by channels and threads so discussions remain searchable and tied to the right topics. Slack Connect supports controlled external collaboration with other organizations. Microsoft Teams combines persistent channels with SharePoint-backed file collaboration and includes enterprise administration features like role-based access controls and audit capabilities.

How to Choose the Right Faster Software

Selecting the right tool starts with mapping the workflow type, the automation depth needed, and the collaboration surface required for day-to-day execution.

  • Match the workflow model to how work actually moves

    Choose Notion when teams need a structured knowledge base plus lightweight project systems inside one shared workspace with relational databases. Choose monday.com when work starts as tasks on configurable boards and needs dashboards with real-time KPIs. Choose Jira Software or Linear when work is best represented as issues with statuses tied to delivery, with Jira covering agile boards and Linear adding cycle-based planning.

  • Decide how automation should behave across your workflow

    Select monday.com for automation recipes that update fields, create tasks, and notify stakeholders across boards. Select Asana for automation rules that route work, update fields, and move items across projects based on conditions. Select Trello when automation should trigger on card and board events through Butler to keep simple workflows moving without heavy configuration.

  • Pick reporting and planning views that reduce manual status work

    Choose Linear when milestone-based cycle planning and GitHub-linked execution reduce triage time for engineering teams. Choose Jira Software when Scrum and Kanban dashboards plus advanced roadmaps connect epics to releases through issue relationships. Choose Asana when Portfolios roll up project status and progress across multiple workstreams with timeline and workload views.

  • Ensure documentation and decisions connect to execution

    Choose Confluence when documentation needs structured spaces and reusable templates with macros like Jira Issue and decision logs. Choose Notion when documentation and project tracking can share the same relational database backbone with synced views. Choose Confluence alongside Jira Software when the most critical requirement is linking requirements, bugs, and releases to documentation.

  • Confirm the collaboration surface and governance fit

    Choose Slack when channel-first collaboration and searchable threads must reduce context switching across engineering, product, and operations teams. Choose Microsoft Teams when teams require scheduled and on-demand video meetings plus SharePoint-backed file collaboration inside Teams channels. Choose Google Workspace when teams need Gmail and Calendar tied to Docs, Sheets, and Meet with Shared Drives for structured access control.

Who Needs Faster Software?

Faster Software tools benefit teams that move work through structured workflows, share context continuously, and rely on automation to reduce manual follow-up.

  • Teams building structured knowledge bases and lightweight project systems

    Notion fits teams that want relational databases with multiple synced views plus real-time collaboration with mentions and threaded comments. Notion also supports Fast page templating with reusable blocks and Automations to trigger actions across common workflows.

  • Teams standardizing workflows with visual automation and cross-project reporting

    monday.com fits teams that need board-based work management with flexible field types and real-time dashboards for tracking progress. monday.com automation recipes can update fields, create tasks, and notify stakeholders across boards so reporting stays current without manual updates.

  • Engineering teams managing roadmaps, releases, and GitHub-linked execution

    Linear fits teams that want keyboard-first issue creation and updates plus cycle view planning around milestones. Linear connects issues to GitHub workflows so commits and pull requests remain linked to issue execution during delivery.

  • Organizations standardizing collaboration around Microsoft 365 and governed execution

    Microsoft Teams fits organizations that rely on Microsoft 365 for file collaboration and meetings with screen sharing, recording, and live captions. Teams channels paired with SharePoint-backed files keep topic-based chat organized while enterprise administration supports role-based access and audit capabilities.

Common Mistakes to Avoid

Common failure patterns come from choosing the wrong workflow model, underestimating setup effort for complex configurations, or allowing structure to decay at scale.

  • Building complex database models without ongoing governance

    Notion can become hard to maintain when relational database modeling grows complex and requires careful design discipline. Notion also shows performance degradation with very large databases and heavy embeds, so database growth must be managed with practical limits.

  • Allowing board or workflow customization to sprawl without standards

    monday.com workflows can become difficult to maintain when boards get highly customized without clear standards. Asana automation and portfolio setups can also become hard to audit when conditions and custom fields proliferate.

  • Treating structured issue reporting as optional

    Jira Software reporting depends on consistent issue hygiene, because advanced analytics require teams to maintain accurate statuses, fields, and relationships. Linear also requires some setup for advanced reporting beyond basic dashboard needs.

  • Letting collaboration channels and knowledge spaces degrade into unsearchable clutter

    Slack channels can become noisy without strong channel hygiene, which makes threaded discussion less consistently organized. Confluence large knowledge bases can feel complex to navigate without strict conventions for spaces and page templates.

How We Selected and Ranked These Tools

We evaluated every Faster Software tool on three sub-dimensions: features with a weight of 0.4, ease of use with a weight of 0.3, and value with a weight of 0.3. The overall rating is a weighted average computed as overall = 0.40 × features + 0.30 × ease of use + 0.30 × value. Notion separated itself from lower-ranked tools through feature depth and usability aligned with that scoring model, specifically by combining relational databases with multiple synced views and powerful query-style filtering while keeping collaborative editing with mentions and threaded comments fast for everyday work.

Frequently Asked Questions About Faster Software

Which Faster Software is best for engineering issue tracking with release planning?
Linear fits engineering delivery because its lightweight interface keeps statuses, milestones, and custom fields closely tied to work items. Linear also supports roadmap and cycle-based planning and integrates with GitHub workflows for tighter execution.
How does Faster Software compare for teams that need structured agile workflows?
Jira Software supports structured agile delivery with Scrum boards and Kanban boards backed by configurable fields and automation rules. monday.com also supports workflow standardization but emphasizes visual boards and cross-project dashboards with automation recipes that update fields and notify stakeholders.
Which tool handles living documentation tied to engineering workstreams?
Confluence fits teams that maintain documentation because it provides structured spaces, page templates, and search across content and attachments. It also integrates with Atlassian tools so Jira-linked macros like Jira Issue and decision logs can embed operational context directly into documentation.
What Faster Software works best for a team knowledge base and lightweight project tracking in one place?
Notion combines docs, databases, and lightweight project tracking in a shared workspace. It supports relational databases with multiple synced views and query-style filtering, which makes it practical for building a structured knowledge base and a simple operating system without switching tools.
Which option is strongest for cross-functional task execution using automations across multiple projects?
Asana fits cross-functional execution because automation rules can route work, update fields, and move items across projects based on conditions. Portfolios and dashboards then roll up status and progress across workstreams so teams can track execution without manual coordination.
How do teams typically connect faster communication to work execution in the same system?
Slack connects channel-based communication to work execution through app integrations and workflow automation, and it keeps collaboration searchable through message history. Microsoft Teams ties chat and meetings to Microsoft 365 productivity tools, using Teams channels with SharePoint-backed file collaboration to link discussions to stored artifacts.
What Faster Software is best for visual task planning and simple workflow automation without complex setup?
Trello fits visual planning because boards, lists, and cards support checklists, due dates, attachments, comments, and labels. Power-Ups and Butler enable automation triggered by card and board events, which reduces coordination overhead for lightweight workflows.
Which tool supports governed enterprise collaboration and audit-oriented administration?
Microsoft Teams supports governed organizations with role-based access controls and audit capabilities. Slack also supports enterprise administration features like user management and message retention controls, and it can extend collaboration through Slack Connect with controlled external communication.
How do roadmaps and release planning differ across Faster Software options?
Linear ties planning to releases using roadmap and cycle views that align work items to milestones. Jira Software supports release alignment through advanced roadmaps that connect delivery progress to epics and releases, while Confluence can centralize release decisions through templates and decision logs tied to ongoing work.

Conclusion

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

Our Top Pick
Notion

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.

Logos provided by Logo.dev

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

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

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

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

  • Editorial write-up

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

  • On-page brand presence

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

  • Kept up to date

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