Commissioned Research
Top 10 Best Working Software of 2026

GITNUXSOFTWARE REVIEW

Business & Finance

Top 10 Best Working Software of 2026

Compare working software options like Asana, monday.com, and ClickUp, covering fit and tradeoffs for teams choosing project tools.

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

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

02Source Research

Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.

Read our full methodology →

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

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Working software platforms shape how teams track tasks, requests, approvals, and delivery artifacts through shared data models and automation rules. This comparison helps analysts and operators weigh configuration depth, API and integration fit, and governance details like RBAC and audit logs across tools built for multi-user execution.

Asana is the best pick for teams that need standardized project execution with automation and outside updates, thanks to its Automation Rules plus webhooks that drive event-based changes between tasks and external systems, while monday.com is a strong alternative for SMBs that want configurable linked boards and flexible automation rules across work views.

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

Asana

Automation Rules plus webhooks enable event-driven updates between Asana tasks and external systems.

Best for: Fits when teams need standardized project execution with workflow automation and integration-driven updates.

2

monday.com

Editor pick

Automation rules can update fields, create items, and route ownership based on changes across related boards.

Best for: Fits when teams want configurable work management with strong views, automations, and integrations.

3

ClickUp

Editor pick

Recurring tasks and automation combine to keep operational work schedules aligned with changing priorities.

Best for: Fits when teams need one configurable system for tasks plus automation and reporting across functions.

Comparison Table

1
AsanaBest overall
enterprise
9.1/10
Overall
2
8.9/10
Overall
3
8.6/10
Overall
4
enterprise
8.4/10
Overall
5
8.3/10
Overall
6
7.8/10
Overall
7
enterprise
7.4/10
Overall
8
vertical specialist
7.2/10
Overall
9
API-first
6.8/10
Overall
10
6.7/10
Overall
#1

Asana

enterprise

Asana manages projects, tasks, goals, workflows, and team dependencies.

9.1/10
Overall
Features9.1/10
Ease of Use9.2/10
Value9.0/10
Standout feature

Automation Rules plus webhooks enable event-driven updates between Asana tasks and external systems.

Asana supports work tracking with task-centric planning, timelines, and portfolio views that connect projects to outcomes. Teams can standardize execution using reusable templates, forms, and rules that route work based on assignees, dates, and fields.

Asana also provides an automation surface through its API and webhooks, plus admin controls for user provisioning and content permissions. Reporting and workload views help teams manage dependencies and status across multi-project workstreams.

Pros
  • +Task templates and project templates reduce repeated setup for recurring work
  • +Rules can auto-assign, set due dates, and update fields from triggers
  • +API and webhooks support custom integrations and event-driven workflows
  • +Portfolios and reporting track cross-project progress with clear rollups
Cons
  • –Complex cross-team governance needs careful permission design
  • –Automation rules can become difficult to reason about at high volume
  • –Dependency management stops short of full delivery pipeline instrumentation
  • –Advanced custom workflows often require API integration effort
Use scenarios
  • Architecture and design teams

    Track design milestones across collaborators

    Tracked design plan and dates

  • Project managers and delivery teams

    Plan execution timelines from tasks

    Schedule tied to task progress

Show 2 more scenarios
  • Innovation and program teams

    Manage stage-gate initiative progress

    Shared initiative status view

    Teams coordinate idea intake and stage-gate tasks with ownership and next-step status.

  • Product and software teams

    Run sprint planning and feature tracking

    Visible ownership and status

    Teams assign sprint work and track feature progress using project views across sprint cycles.

Best for: Fits when teams need standardized project execution with workflow automation and integration-driven updates.

#2

monday.com

SMB

monday.com provides configurable boards for projects, processes, sales, and operations.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Automation rules can update fields, create items, and route ownership based on changes across related boards.

monday.com coordinates work by letting teams build boards that represent tasks, timelines, and files, then connect them with automations. Core capabilities include views for Kanban, calendar, timeline, workload, and dashboards, plus form intake that writes records into boards.

Teams can standardize execution with templates, item-level permissions, and structured status changes. monday.com also supports integration via APIs and marketplace apps so work data can flow between systems.

Pros
  • +Board-based data model supports multiple linked views without redesigning workflows
  • +Built-in automation rules trigger on item changes and field values
  • +Marketplace integrations cover common tools for docs, chat, and reporting
  • +Workload and timeline views make capacity and sequencing visible
Cons
  • –Deep workflow governance requires careful permission and template discipline
  • –Large-scale reports can feel slower when many boards and complex formulas grow
  • –Fine-grained API workflows need more design than click-based configuration
  • –Structured development artifacts like pull requests need external tooling
Use scenarios
  • Organizational change teams

    Track initiatives across stakeholders

    Structured change program execution

  • Scrum teams and engineering

    Model backlog and sprint stages

    More visible sprint progress

Show 2 more scenarios
  • Operations managers and teams

    Coordinate approvals and recurring work

    Clear ownership for handoffs

    Teams run request handoffs and approvals on shared boards with automated status changes.

  • Portfolio leaders

    Roll up milestones into dashboards

    Cross-project execution visibility

    Teams combine milestone and timeline data from multiple projects into shared dashboards for reporting.

Best for: Fits when teams want configurable work management with strong views, automations, and integrations.

#3

ClickUp

SMB

ClickUp combines tasks, documents, goals, whiteboards, and project planning in one workspace.

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

Recurring tasks and automation combine to keep operational work schedules aligned with changing priorities.

ClickUp provides task tracking with dependencies, recurring work, and custom fields that map to different operational models. Multiple view types and a unified space structure help keep work organized for teams that manage mixed streams like projects, support queues, and recurring ops.

A key tradeoff is that deeper workflow consistency depends on careful configuration of custom fields, templates, and automation rules. ClickUp works best when a team can standardize statuses and templates, then iterates on automation for handoffs and reporting in one place.

Pros
  • +Task customization with custom fields and multiple structured view options
  • +Automation rules that trigger on status and field changes for handoffs
  • +Workload reporting to visualize capacity and bottlenecks across teams
  • +Docs and comments stay attached to tasks for contextual collaboration
Cons
  • –Workflow standardization takes disciplined configuration to avoid inconsistent statuses
  • –Advanced reporting can require more setup than simple single-team trackers
Use scenarios
  • Product delivery teams

    Track releases with custom status workflows

    Faster coordination across squads

  • IT service and operations teams

    Run a unified work queue

    More predictable operational cadence

Show 1 more scenario
  • Revenue operations teams

    Coordinate cross-team process steps

    Fewer missed handoffs

    Rules trigger on field edits to route tasks through defined stages and generate reports.

Best for: Fits when teams need one configurable system for tasks plus automation and reporting across functions.

#4

Wrike

enterprise

Wrike coordinates projects, requests, resources, approvals, and portfolio reporting.

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

Wrike includes request intake workflows that route work through configurable statuses with role-based visibility controls.

Wrike supports workspaces, projects, tasks, and requests with customizable statuses and due dates, which helps teams standardize delivery tracking without forcing a single rigid project model. Multiple views support planning and execution, including list-style task work, timeline-style planning, and reporting dashboards that reflect real workflow status. Dependency management and reusable templates help teams coordinate work across functions and reduce setup time for recurring initiatives.

Pros
  • +Workflow states and statuses support consistent execution across many projects
  • +Dependency tracking helps coordinate downstream work and reduce scheduling drift
  • +Admin permissions plus audit history support controlled collaboration
  • +API and integrations enable automated updates from external tools
Cons
  • –Workflow and permission design takes effort in large, multi-project setups
  • –Some advanced configuration features can add admin overhead
  • –Custom reporting can require deeper configuration than teams expect
  • –Complex dependency graphs can be harder to interpret in timeline views
Use scenarios
  • Program management teams

    Coordinate parallel delivery with dependencies

    Fewer missed handoffs

  • Operations and PMO

    Standardize intake for recurring requests

    More predictable throughput

Show 2 more scenarios
  • IT and automation teams

    Sync work data with external systems

    Less manual coordination

    The API supports automated creation and updates of tasks and records from upstream tools.

  • Enterprise project portfolios

    Control access and trace changes

    Improved compliance posture

    Permissions and audit trails support governed collaboration across teams with different visibility needs.

Best for: Fits when cross-team execution needs workflow governance and dependency-aware planning.

#5

Todoist

SMB

Todoist manages personal and team tasks with projects, priorities, labels, and due dates.

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

Rules that move, label, and reassign tasks based on due dates and task metadata.

Todoist organizes work around tasks, projects, and recurring schedules, which makes it suitable for day-to-day delivery and ongoing operations. Filters can combine criteria like due dates, labels, and project membership to create focused views for planning and review. Task details support comments and file attachments, which reduces the need to jump between tools for context.

Pros
  • +Recurring tasks reduce manual scheduling for routine operations
  • +Filters and saved views keep planning centered on actionable work
  • +Rules automate task routing based on labels, projects, and dates
  • +Comments and assignments keep context attached to each task
Cons
  • –Task dependencies and release artifacts require external tooling
  • –Automation via rules is limited compared to full workflow engines
Use scenarios
  • Product managers

    Track weekly delivery tasks

    Fewer missed next steps

  • Operations teams

    Run recurring compliance routines

    Consistent recurring execution

Show 2 more scenarios
  • Customer support teams

    Triage and follow up on issues

    Faster issue closure

    Support leads can assign tasks, add comments, and keep resolution steps visible through filtered views.

  • Freelancers and consultants

    Plan client deliverables consistently

    Lower planning effort

    Freelancers can use templates and recurring tasks to repeat onboarding and recurring reporting workflows.

Best for: Fits when small to midsize teams need shared task execution with low setup overhead.

#6

Zoho Projects

SMB

Zoho Projects provides task management, milestones, timesheets, documents, and automation.

7.8/10
Overall
Features7.8/10
Ease of Use7.8/10
Value7.8/10
Standout feature

Workflow rules that change task status and notify stakeholders from project events without custom code.

Zoho Projects runs work management with Gantt planning, Kanban boards, and task-level assignment tied to milestones. It adds roadmap and portfolio-style views plus time tracking and workload reporting for execution visibility.

Pros
  • +Gantt, Kanban, and milestone views stay consistent across the same project model
  • +Time tracking and workload reporting support staffing and delivery forecasting
  • +Workflow rules can drive status changes and notifications from project events
  • +Zoho suite integration enables cross-app identity and data handoffs
Cons
  • –Setup depth increases when projects need multiple custom fields and permissions
  • –Automation coverage depends on available trigger and action types per workflow
Use scenarios
  • Project delivery and support teams

    Track issues inside project work

    Issues stay visible with progress

  • Project teams handling documents

    Share documents with approval flows

    Documents connected to delivery activity

Show 2 more scenarios
  • Project managers and delivery teams

    Plan milestones and task dependencies

    Coordinated project plan

    Managers break delivery plans into tasks, milestones, dependencies, and schedules with clear relationships.

  • Operations teams and admins

    Automate status updates and operations

    Less manual coordination

    Teams apply workflow automation and programmatic updates to reduce repetitive project administration.

Best for: Fits when teams need structured planning, time tracking, and cross-module automation in a Zoho-centered environment.

#7

Smartsheet

enterprise

Smartsheet uses spreadsheet-style workspaces for projects, portfolios, forms, and automation.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Row-scoped approvals and workflow actions that operate directly on sheet records and related items.

Smartsheet fits teams that need spreadsheet-like planning with a stronger control layer than ad hoc docs. It supports structured sheets, report builders, and workflow-style approvals tied to specific records.

Pros
  • +Spreadsheet-native UI with reliable structured record tracking
  • +Approval workflows can gate changes at the row and item level
  • +API and automation enable data sync with external systems
  • +Templates speed up repeatable program and department tracking
Cons
  • –Advanced automation can require careful design to avoid brittle dependencies
  • –Reporting limits complex multi-dimensional analysis compared with BI-focused tools
  • –Some workflow logic is harder to version and govern at scale than issue trackers
  • –Large sheet performance depends on how formulas, attachments, and cross-links are used
Use scenarios
  • Program managers and portfolio leaders

    Consolidate cross-initiative status

    Consistent multi-project status visibility

  • Program and delivery teams

    Govern milestones and acceptance gates

    Centralized milestone tracking

Show 2 more scenarios
  • Project managers and delivery teams

    Run linked planning with timeline views

    Shared plan with visible progress

    Teams manage tasks, owners, dates, dependencies, and status in linked sheets with timeline views.

  • Operations managers and service teams

    Intake requests into assigned queues

    Consistent intake and process tracking

    Forms collect request details and route them into work queues and follow-up workflows.

Best for: Fits when teams need controlled work tracking using spreadsheet-style workflows and integrations.

#8

Teamwork.com

vertical specialist

Teamwork.com manages client projects, budgets, resources, milestones, and profitability.

7.2/10
Overall
Features7.2/10
Ease of Use7.3/10
Value7.1/10
Standout feature

Client portal workspaces that mirror internal task tracking, so external stakeholders see the same delivery objects.

Teamwork.com fits organizations that run work across projects and client delivery with shared tasks, files, and status tracking. Its project workspaces support kanban-style boards, timesheets, and workload visibility built around task-level assignments and due dates.

Pros
  • +Client portals keep delivery artifacts and task updates in one place
  • +Workload charts tie assignments to capacity and highlight over-allocation
  • +Rule-based automation can update fields and notify teams after task events
  • +Timesheets connect effort reporting to the same task records as delivery work
Cons
  • –Workflow customization is limited compared with tools built around deeper custom statuses
  • –Cross-tool process automation depends heavily on connected apps and external systems
  • –Reporting is strong for status and workload but thin for workflow analytics
  • –Permission granularity can feel coarse for complex org-wide RBAC patterns
Use scenarios
  • Agency and client-service teams

    Coordinate delivery across client projects

    Shared view for client delivery

  • Cross-functional project teams

    Combine boards with project timelines

    Shared schedules with task progress

Show 2 more scenarios
  • Teams sharing project documents

    Share files with workspace-controlled access

    Files shared with selected participants

    Teams attach documents to tasks and apply project and client workspace permissions for visibility control.

  • Creative and design teams

    Coordinate creative intake and approvals

    Handoffs stay connected to work

    Teams move creative work through intake, production, review, and approval using task statuses and feedback.

Best for: Fits when delivery teams need client-facing project management with timesheets and lightweight automation.

#9

Airtable

API-first

Airtable combines relational databases, interfaces, automations, and collaborative work tracking.

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

Record-level automations that evaluate formulas and trigger chained actions across linked tables.

Airtable turns spreadsheets into configurable work systems with linked tables, custom views, and form-style data entry. Its core workflow strength comes from automations that trigger on record changes, plus an API for syncing records between Airtable and external systems.

Pros
  • +Relational tables with bidirectional linking support trackable workflows
  • +Automation rules react to field changes across records and formulas
  • +REST API enables reliable record-level sync with external systems
  • +RBAC and workspace settings support controlled collaboration on shared bases
Cons
  • –Large bases can feel slower when many linked records and heavy views are used
  • –Automation complexity can become hard to debug without systematic logging
Use scenarios
  • Small business sales teams

    Track clients and deal activity

    Configurable client database

  • Operations specialists

    Build lightweight internal databases

    Shared database with tailored views

Show 2 more scenarios
  • Project managers and cross-functional teams

    Manage tasks using multiple views

    Shared tasks with ownership and dates

    Teams manage structured work items using Kanban, grid, calendar, timeline, and filtered dashboard views.

  • Teams with recurring process stages

    Track card-based process work

    Process tracking with richer context

    Teams track work items as structured cards with fields, linked records, attachments, and automated status changes.

Best for: Fits when teams need a configurable, relational tracker with automation and API access.

#10

Basecamp

SMB

Basecamp organizes team projects with message boards, to-dos, schedules, files, and check-ins.

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

Message boards and announcements are designed for durable, threaded team communication tied to each project workspace.

Basecamp centers on threaded discussions, file sharing, and simple project messaging in a single workspace per team. It provides built-in to-do lists, calendars, and milestone-style planning with fewer workflow constructs than issue trackers.

Pros
  • +Threaded message boards keep decisions and updates in one place
  • +Built-in to-do lists and due dates reduce reliance on external task tools
  • +Calendar and docs consolidate planning artifacts alongside team chat
  • +File storage with per-project organization supports everyday collaboration
Cons
  • –Limited automation and workflow tooling for sprint and release ceremonies
  • –APIs and integration depth lag behind tools built for engineering workflows
  • –No native issue fields and board tooling match dedicated trackers
  • –Governance controls for scale are thinner than enterprise work management suites
Use scenarios
  • Agencies and external partners

    Collaborate with guest access

    Contained partner communication

  • Product and department teams

    Communicate roadmap milestones

    Readable plan with responsibilities

Show 2 more scenarios
  • Architecture studios

    Run lightweight client project hub

    Lightweight delivery hub

    Studios manage shared messages, tasks, schedules, and documents for client or internal delivery tracking.

  • Marketing teams and agencies

    Coordinate campaign execution in one place

    Coordinated campaign delivery

    Teams organize campaign tasks, review discussions, schedules, and supporting files in a single project space.

Best for: Fits when teams want a shared workspace for decisions, tasks, and documents without engineering-grade workflow automation.

Conclusion

After evaluating 10 working software, Asana 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
Asana

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Working Software

How do Airtable and ClickUp differ in how automation connects data and tasks?
Airtable triggers automations on record changes in linked tables and can chain actions based on formula results. ClickUp runs automation rules on task and status changes inside its work hub, with triggers that react to edits across items, not linked spreadsheet-style records.
When should a team choose Jira over ClickUp for workflow governance?
Jira fits teams that need explicit issue workflows, dependency tracking, and admin-controlled state transitions across many delivery teams. ClickUp supports configurable views and automation, but Jira’s project and workflow model typically aligns better with engineering-style delivery patterns and definition-of-done tracking.
Which tool supports request intake routing with role-based visibility controls?
Wrike supports request intake workflows that route work through configurable statuses with role-based visibility controls. Basecamp can route requests through message boards and announcements, but it does not provide the same status-driven intake governance model.
How do Jira and Asana handle event-driven updates to external systems?
Asana exposes automation via its API and webhooks so external systems can update task state and fields when events occur. Jira also integrates through APIs that support event-based synchronization, but Asana’s automation surface is designed to connect task events directly to external workflows.
What breaks if an organization relies on RBAC alone for auditability in Smartsheet or Airtable?
RBAC limits who can view or act on records, but neither Smartsheet nor Airtable replaces the need for a complete audit log strategy around record-level changes and approvals. Smartsheet includes activity history for controlled workflows, while Airtable’s governance depends on workspace roles plus admin settings for access to records and automations.
How should data migration be planned when moving from spreadsheets to Airtable or Smartsheet?
Airtable maps spreadsheet columns into linked tables and then rebuilds the relationships so automations can evaluate record changes. Smartsheet migration usually restructures rows into sheets and then reattaches workflow approvals to specific records so status and approvals remain consistent.
When do ClickUp and monday.com become harder to operate due to configuration sprawl?
ClickUp can become complex when many status changes, fields, and automation rules interact across multiple views and reporting dashboards. monday.com can become harder to govern when item-level permissions, board templates, and cross-board automations multiply, especially across many teams and boards.
Which platform best supports extensibility through APIs and scripting for relational work models?
Airtable combines a relational data model with an API and extensibility options like scripting and marketplace apps. Smartsheet also offers an API and custom integrations, but Airtable’s linked-table model more directly represents multi-entity workflows in a single system.
How do Basecamp and Teamwork.com differ for teams that need client-facing work objects?
Teamwork.com provides client portal workspaces that mirror internal task tracking so external stakeholders see delivery objects tied to projects. Basecamp emphasizes threaded communication and milestone-style planning in project workspaces, so external visibility depends more on invitations and shared discussions than mirrored task objects.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Working Software

We focus on what keeps teams moving after the first setup: integration depth, a trustworthy data model, and automation that actually runs. The biggest differences show up in integration depth, audit log behavior, and how configuration changes flow into daily work—so the product stays “working software” instead of just “installed software.”

Integration depth via APIs and webhooks

Why it matters

Integration depth via APIs and webhooks determines whether other tools can exchange data without manual copy steps. For working software, that reduces handoff friction and makes workflows repeatable.

How to check

In a demo, ask how the system sends and receives events (for example, when a record changes) and show the exact payload fields. Then test a webhook-style automation or an API call that creates/updates an object and verify the result appears in the UI.

Data model matches real workflow objects

Why it matters

A workable data model prevents constant workarounds and brittle mappings. When objects fit your process, teams spend time on outcomes instead of translating between fields and statuses.

How to check

Ask for a sample workspace built around a common workflow in your industry, then show how states, ownership, and attachments are represented. During evaluation, try creating one record end-to-end and confirm you can search, filter, and report on key fields without hidden transformations.

Automation and scheduling are first-class

Why it matters

Working software needs automation that runs on real schedules and triggers, not only on demand. Automation surface depth also signals whether teams can move from “do it once” to “run it every time.”

How to check

Request a live scenario: set up a rule that triggers on a specific field change and another that runs on a schedule. Confirm you can test, preview, and view execution history for each run, including any failures.

Admin governance with RBAC and audit log

Why it matters

Admin governance with RBAC and audit log protects daily operations as more people and integrations join. It also helps you understand what changed when something breaks.

How to check

In the admin area, show how roles limit actions (view, edit, approve) and how permissions apply to embedded automation and API access. Then demonstrate the audit log by performing a controlled change and checking that the who/what/when trail appears.

Configuration changes are controlled and reversible

Why it matters

Configuration change flow determines whether your system remains working software after adjustments. If changes are hard to trace or undo, teams hesitate to improve the workflow.

How to check

Ask the demo team to change a field mapping, rule, or workflow step, then show how the system validates the update. Try rolling back (or restoring prior settings) and verify the business objects return to the prior behavior you can confirm in the UI.

Red flags

  • Integrations require manual export/import for common events
  • Core objects don’t align with your workflow states and ownership
  • Admin actions don’t leave a clear audit trail or permission enforcement

Fit by situation

  • If you connect several existing tools and need data to move automatically, prioritize integration depth via APIs and webhooks.
  • If your team constantly re-labels fields or statuses to make the product fit, prioritize data model matches real workflow objects.
  • If multiple roles manage setups and rules, prioritize admin governance with RBAC and audit log.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

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

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

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

  • Editorial write-up

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

  • On-page brand presence

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

  • Kept up to date

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