ClickUp pricing when your operations team outgrows Free

Your operations team has settled into ClickUp, but the weekly request export and assignment rules now matter more than the first task list did. ClickUp pricing should follow those recurring jobs. Stay on Free if its limits still fit the workflow. Evaluate Core for the documented increase in capacity, and Business when recurring exports or the required automation behavior justify it.

The current public plans differ from older Unlimited pricing you may find elsewhere. Kartik Deshpande checked official pricing and help pages on October 29, 2026. This is documented research with a hypothetical workload, not a hands-on review or customer quote. Confirm which plan generation your workspace uses before comparing its invoice with the public page.

Start with the current plan and billing term

The ClickUp pricing page currently displays Free Forever, Core, and Business among its options. Core shows $9 per user per month billed yearly, beside a crossed-out $12 regular rate. Business shows $17 beside $25. The displayed discount does not establish your renewal rate or its duration.

The public Free listing includes unlimited tasks and members, but only 60 MB of storage and one form. A team can therefore fit the member count while exceeding a different allowance. Inventory attachments, request intake, and recurring outputs before deciding that another paid seat is the problem you need to solve.

Existing workspaces may still use older plans. ClickUp’s add-on documentation says workspaces are being upgraded and distinguishes older AI add-ons from the new plans. Record the plan name and included features from your own billing screen, then verify the proposed change before approving it.

Price eight paid users for the same year

Use a hypothetical team of eight internal people, including the workspace owner and administrators. All eight need paid member access in the upgraded workspace. The team handles 200 operational requests a month, assigns an owner and due date, and sends a weekly export to a manager. Keep that workload constant when comparing Core and Business.

At the displayed rates, Core is 8 × $9 × 12 = $864 for a year. Business is 8 × $17 × 12 = $1,632, a $768 difference. At the regular rates shown alongside them, the same calculation gives $1,152 and $2,400. Those regular-rate calculations are comparison scenarios, not a prediction of the amount you will renew at.

These are USD seat subtotals for twelve months, excluding taxes, additional credits, implementation, and other services. Ask checkout or sales to confirm the committed total, discount period, and renewal terms. If a feature requires a different plan, revise the calculation rather than keeping the cheaper subtotal as the budget.

ClickUp’s role-pricing documentation includes owners, administrators, members, and limited members among subscription roles. Permission-controlled guest allowances depend on the plan and member count; exceeding the allowance can add a paid member seat. Do not assume that someone called a guest is free just because they are outside your company.

The monday.com pricing comparison examines another team-workspace budget. Carry the same eight editors and weekly reporting job into that evaluation. Compare complete configurations, including any required extras, rather than treating each vendor’s lowest rate as the price of the same work.

Count actions and specify the export you need

ClickUp’s automation limits list 100 monthly actions for Free, 1,000 for Core, and 10,000 for Business. The documentation says automations pause for the month after the limit is exceeded. Conditions and automation integrations also have plan restrictions, so volume alone does not establish that a rule will run on Core.

For the sample workload, suppose each of 200 requests causes two counted actions. That produces 400 actions before reminders, corrections, or other workspace activity. It exceeds the stated Free allowance and sits below Core’s action allowance, but you still need to verify how the configured rule is counted and whether its conditions are available. Keep a record of actual pilot usage before committing to an allowance.

The export documentation distinguishes location exports from exporting workspace task data. On the new plans, Core has trial List exports and excludes Table and Form view exports; Business includes unlimited List exports. A weekly List export therefore needs more than a trial entitlement. Confirm the exact export format and access required by the manager.

Separate AI credits from the base workflow

ClickUp’s AI-credit documentation assigns new Core plans 1,000 credits per seat per month and Business 1,500. Credits are pooled across the workspace, and unused monthly credits do not roll over. Additional credits can be purchased on the new paid plans; the older Brain AI and Everything AI add-ons are not purchased separately on those plans.

Do not treat an AI-credit allowance as unlimited model usage. ClickUp documents separate Brain model allowances, with trial usage on Core. Specify whether the team needs a request summary, an automated action, or neither, then check the relevant usage measure. The sample seat budget includes no purchased extra credits.

Rehearse a request through assignment and export

Create a permitted sample request with an identifier, department, owner, due date, status, and attachment. Add a second request that the first reviewer should not see. Configure the intended intake and assignment rule, then process a request through completion. The expected result is the correct owner and status, with the supporting file still tied to its identifier.

ClickUp’s Space documentation describes location structure and permissions beneath Spaces. Use the planned member and guest roles when testing access. Try the other request’s direct link, then repeat after access is removed. A filtered task view does not by itself prove the underlying request is private.

Generate the weekly export using the role that will own the job. Check field values, excluded requests, and attachment handling. The export documentation requires both workspace and location permissions for view exports and gives owner/admin workspace exports a separate permission path. Record the observed output; the checks here are proposed, not completed test results.

Keep an exit copy and rebuild configuration deliberately

Before importing active work, agree how the old statuses and identifiers map to ClickUp. Transfer a sample first, reconnect approved integrations, and test notifications and access. Count open requests in both locations and decide which system accepts updates during the move. A matching row count alone does not establish that responsibility and evidence transferred.

For an exit rehearsal, ClickUp documents workspace task exports to CSV. Inspect the selected locations and preserve needed files and documents separately where required. Rebuild and test automation rules and permissions in the destination; a data file does not establish that application behavior moved with it.

If shared reference records drive your workflow more than assignments do, the Airtable vs monday comparison provides a related evaluation. Keep the same request and reporting fixture when considering a different structure, and include the migration effort in the decision to leave.

Where Permute fits: business evidence behind request reports

Permute sells connected business data and custom applications. This comparison reflects our commercial interest. A task workspace can coordinate work while its customer or supplier references disagree with accounting records. We connect supported sources and reconcile identifiers so reports and applications can reuse the agreed business record.

Your team defines when a request counts as complete and which source establishes the amount. We can reuse that definition with source evidence, freshness, and current permissions. An operations manager reviewing outstanding work can inspect the supporting records and unresolved differences. That is a separate scope from choosing where colleagues assign tasks.

Verify the source path before extending the workspace

We do not supply ClickUp subscriptions or promise a native connector, automatic migration, or equivalent task-management features. Source access and custom application work require a defined scope. External actions need supported operations, permissions, and approval. Keep ClickUp when it handles the team’s work; evaluate connected-data work where reporting evidence remains unresolved.

Upgrade for the recurring job that exceeds Free

Stay on Free while the team’s storage, intake, and recurring work fit its allowances. Compare Core and Business using the same people, action counts, and export requirements. Confirm the displayed discount and renewal terms before approving the annual subtotal. Accept the upgrade after the request, permission, and reporting checks match the job you need to run.

Questions about upgrading from ClickUp Free