.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
How Do Modern Project Management Tools Like Linear Challenge Legacy Pricing Models
Project management software has changed faster than the way it is priced. The user experience has moved from configurable systems built around administrators towards fast, opinionated products that product managers and engineers can start using in minutes. Yet the commercial unit remains remarkably familiar: in most products, another person using the software still means another paid seat.
Linear makes the tension unusually visible. Its Free plan allows unlimited members while limiting teams and issues; its paid plans then move to a per-user price and progressively unlock more organisational depth. As of August 2026, Basic is $10 per user per month billed yearly, Business is $16, and Enterprise is custom-priced. Business also opens private teams, guest accounts, Linear Insights and Linear Asks, while Enterprise adds SAML, SCIM, more administrative control and onboarding support.
The stakes go beyond whether $10 or $16 is a fair price. Modern project management products become more valuable when information reaches more people, but traditional seat pricing becomes more expensive for the customer for exactly the same reason. A product team may have 40 people actively creating and managing work, yet another 60 executives, designers, support staff and salespeople may need to read, comment or submit requests.
Monetizely's position is that Linear challenges legacy project-management pricing mainly by exposing how blunt the traditional all-user seat has become. Linear should keep the paid seat as its primary meter, but redefine that seat around people who actively build and manage work, make low-intensity participation free, and recover enterprise value through a fixed workspace fee rather than charging every participant as if they were a full-time operator.
Linear has modernised the offer faster than the bill
A pricing model is not just the number printed on the website. Monetizely's 5-Step Pricing Framework treats monetisation as a chain of linked decisions. Goals and Segmentation defines the commercial objective and identifies buyers whose needs differ enough to justify separate offers. Packaging decides which capabilities belong together and what should trigger an upgrade. Pricing Metric determines what unit the customer's bill should grow with. Rate Setting establishes how much to charge for each unit against willingness to pay, alternatives and value. Operationalization makes those decisions work in quoting, entitlements, billing, expansion and renewal. As discussed in Monetizing Agentic AI, the sequence matters because changing a price without fixing the package or metric can merely move friction from one part of the buying journey to another.
Linear has made meaningful progress on rate setting without changing the underlying paid metric. Archived pricing from April 2026 showed Basic at $8 per user per month and Business at $14; by August the public prices had moved to $10 and $16. That represents a 25% increase for Basic and roughly 14% for Business, while both remain priced per user. The live page also shows that Linear increasingly uses product complexity rather than headcount to separate the packages.
The pricing history and current package structure make that distinction easier to see.
| Exhibit: Linear's pricing moved, but the primary paid meter did not | April 2026 archived price | August 2026 public price | Price movement | Current package fence |
|---|---|---|---|---|
| Free | $0 | $0 | None | 2 teams, 250 issues, unlimited members |
| Basic | $8/user/month | $10/user/month | +25% | 5 teams, unlimited issues, admin roles |
| Business | $14/user/month | $16/user/month | +14% | Unlimited teams, private teams and guests, Insights, Asks |
| Enterprise | Custom | Custom | Not disclosed | SAML, SCIM, advanced admin, security, onboarding and account support |
Sources: Linear pricing page, reviewed August 2026, and April 2026 Wayback captures. Current package details are confirmed on Linear's live pricing page.
The table shows the central issue: Linear has become more sophisticated about what customers buy, but not about whom customers pay for.
That does not make the seat wrong. Product managers, engineers and other people who spend their working day creating issues, triaging work, managing projects and updating roadmaps are sensible units of value. Their number often scales with the amount of work that a customer entrusts to Linear.
Trouble starts at the edge of the workflow. Linear Asks is designed to bring requests into the system, Business supports guest accounts, and higher tiers expand reporting and organisational visibility. Those features make Linear useful to people beyond the core product-development team. When the product is designed to widen participation but the commercial model keeps treating every paid user alike, adoption and monetisation begin pulling in opposite directions.
Strong packaging cannot fully compensate for a blunt paid seat
Linear performs well on two of the three parts of the 5-Step Pricing Framework that matter most in this teardown. Its packages follow a recognisable maturity curve: try the product broadly for free, remove work limits in Basic, add cross-team capabilities in Business, and move enterprise administration and security into the negotiated tier.
The pricing metric is where the model lags the product.
| Exhibit: Linear's pricing scorecard | Grade | Monetizely's rationale |
|---|---|---|
| Packaging | A- | Limits shift logically from issues and teams towards coordination, reporting and organisational control as the buyer matures. |
| Pricing Metric | C+ | Per-user pricing remains simple for active builders, but the public paid model does not distinguish them from lighter participants as collaboration broadens. |
| Operationalization | B | Transparent self-service pricing leads into an annual-only Enterprise offer with invoice/PO support, but enterprise security and role complexity arrive largely through the sales motion. |
Source facts underlying the assessment are Linear's public pricing and feature entitlements as of August 2026. The grades are Monetizely's assessment.
Linear gets packaging right, gets the paid-user definition wrong, and has an operational model that remains workable largely because the metric itself is simple.
The strongest choice is the Free package. Unlimited members combined with a 250-issue and two-team limit means Linear can let a group experience collaboration before charging according to headcount. That is a much better product-led gate than a low user cap because the point of upgrade arrives when the customer is doing more real work.
The weakest choice appears one step later. Basic and Business still quote one price “per user/month”. A product manager who owns a roadmap can therefore sit on the same commercial axis as a colleague whose main need is visibility, even though the product value and usage intensity differ sharply.
Enterprise packaging adds another pressure point. SAML and SCIM appear only in Enterprise, alongside granular administration, advanced security, migration help and account management. Monetizely's position is that these capabilities should support a workspace-level enterprise charge. Security and central administration are benefits purchased by the organisation, not something whose value rises neatly every time a low-frequency participant is added.
The market is already separating people who run work from people who participate in it
Linear is not operating in a vacuum. Several project-management vendors are already weakening the assumption that every person who touches the product should carry the same economic weight.
Atlassian provides the clearest evidence because two products inside the same company use very different approaches. Core Jira still defines a user broadly as someone who can log in, charges monthly customers according to the exact user count and bills annual customers according to the tier closest to that count. Jira Product Discovery, by contrast, explicitly charges creators while allowing contributors to participate for free. Its current page lists Standard at $10 per creator per month and Premium at $25.
The contrast across the category is instructive.
| Exhibit: Project-management vendors increasingly distinguish participation from full paid use | Public starting paid price reviewed August 2026 | Primary listed meter | Treatment of lighter participation |
|---|---|---|---|
| Linear Basic | $10/user/month, annual | User | Business adds guest accounts, but listed paid pricing remains per user |
| Jira Product Discovery Standard | $10/creator/month | Creator | Contributors are explicitly free |
| Asana Starter | $10.99/user/month, annual | User | Unlimited free guests |
| monday.com Standard | $12/seat/month, annual | Seat | Read-only viewers exist alongside paid seats |
| Smartsheet Pro | $9/member/month, annual | Member | Unlimited Contributors |
| ClickUp Unlimited | $7/user/month, annual | User | Guest access with permission controls |
Sources are official vendor pricing pages reviewed in August 2026. Linear:; Atlassian:; Asana:; monday.com:; Smartsheet:; ClickUp:.
The market is not abandoning seats. It is becoming more precise about which type of user deserves one.
Atlassian's own public filings help explain why the older approach became so powerful. Its fiscal 2024 10-K describes a product-led model designed to begin with easy self-service adoption and then expand relationships inside customers, including Fortune 500 companies using its products across thousands of users. Seat expansion was therefore not merely a billing convenience. It was deeply connected to the SaaS growth engine.
Yet Atlassian now charges only creators in Jira Product Discovery. A company with decades of experience monetising broad user expansion has concluded that, for at least one modern collaborative workflow, charging every participant is not necessary.
Asana provides even stronger operating evidence. On its 10 March 2025 earnings call, then-CEO Dustin Moskovitz argued that SaaS pricing requires the “right menu of options to align price to value.” COO Anne Raimondi reported that geographic pricing tests had produced a “positive trade-off between price and seat volume” and said 25% of view-only users introduced since 2023 had subsequently converted to paid licences.
That conversion rate matters. Free or cheaper participation does not automatically destroy monetisation. In Asana's reported experience, putting the product in front of more people created a route into paid usage.
monday.com reaches the same problem from a different direction. Co-founder Roy Mann described the company's “adaptable product suite and scalable pricing” on its 12 May 2025 earnings call. Three months earlier, CFO Eliran Glazer said large customers tended to expand after they “unlock the value of the platform”, sometimes consolidating other vendors onto monday.com.
Taken together, these operators are describing a market where expansion still matters, but simple multiplication of one price by every person is no longer the only route to that expansion.
The seat still works when it represents somebody doing the work
Moving away from all-user billing should not be confused with moving away from seats.
A project-management product remains deeply tied to human work. Engineers close issues. Product managers manage projects and cycles. Team leads triage priorities. Unlike a database measured in queries or an infrastructure product measured in compute, a Linear workspace still creates much of its value through people actively coordinating work.
That makes the active builder a strong primary meter. The question is not whether Linear should charge per seat. The question is whose seat should count.
A role test makes the boundary clear.
| Exhibit: The paid seat should follow active work, not simple access | Typical use of Linear | Relationship to customer value | Monetizely's proposed treatment |
|---|---|---|---|
| Builder | Creates and owns issues, projects, cycles and roadmaps; triages work | Direct and frequent | Full paid seat |
| Contributor | Comments, supplies context, updates occasional work | Improves execution but does not run the system | Free participation |
| Requester / viewer | Submits requests, reads status, follows progress | Expands visibility and data flowing into Linear | Free participation |
| Workspace administrator | Controls access, security and organisation-wide settings | Organisation-level value | Covered by enterprise workspace fee |
Under this design, the bill scales with the people who run the work while participation around them can grow without forcing a budget decision every time another stakeholder needs access.
The distinction also improves packaging. Linear can continue selling Basic to small builder teams, Business to groups needing deeper coordination, and Enterprise to organisations requiring security and control. What changes is the relationship between the package and the number of users.
A fixed enterprise workspace fee would pay for the capabilities that Linear currently places in Enterprise: SAML, SCIM, central administration, advanced security, migration and account support. The builder seat would remain the primary meter. That is a deliberate architecture, not a compromise between two incompatible models.
Linear's next reset should remove the penalty for widening adoption
The recent move from $8 to $10 for Basic and $14 to $16 for Business shows that Linear can raise list price. Another conventional increase would miss the larger opportunity.
Its next reset should instead be a role-based seat model anchored on paid builders, with unrestricted low-intensity participants and a fixed Enterprise workspace fee.
The economic case becomes clearer in a simple adoption scenario. Consider an organisation with 100 people who need visibility into product work, but only 45 who actively create and manage it. At the current Business list rate of $16 per user per month, an all-user price reference would be $19,200 a year.
The proposed architecture can preserve or improve that revenue while making the 55 lighter participants inexpensive to add.
| Exhibit: Role-based pricing can preserve revenue while removing expansion friction | Paid builders | Other participants | Annual price reference |
|---|---|---|---|
| Current all-user Business reference | 100 | 0 separately classified | $19,200 |
| Builder seats only, no workspace fee | 45 | 55 free | $8,640 |
| Recommended architecture | 45 at $16/month | 55 free | $18,640-$23,640, including a modelled $10,000-$15,000 Enterprise workspace fee |
| Recommended architecture after 50 more non-builders join | 45 at $16/month | 105 free | $18,640-$23,640 |
The scenario is modelled, not Linear guidance. Full assumptions appear at the end.
The point is not the proposed $10,000-$15,000 fee itself. The important change is that Linear could preserve roughly the same contract value while making the marginal cost of broad organisational participation close to zero.
Now consider the purchasing behaviour that creates. Under an all-user model, adding 50 people at the Business list rate represents another $9,600 of annual list-price exposure. Under the recommended structure, adding 50 viewers or requesters does not change the bill unless the number of active builders changes.
Procurement therefore stops asking, “Does this person really need a licence?” Product leadership can instead ask, “Would giving this person access make the workflow better?”
That change has strategic value. More requesters can feed work into the system. More executives can see progress without asking product managers for separate status updates. More support and go-to-market staff can supply context around customer needs. Linear's own move towards guest access and request intake already points towards broader participation. Pricing should help that behaviour rather than meter it indiscriminately.
For Linear, the reset would also sharpen its competitive story against Jira. Atlassian's core Jira billing still carries user-count tiers for annual subscriptions, while Jira Product Discovery already proves Atlassian can separate paid creators from free contributors. Linear can take the cleaner principle across the broader product-development workflow.
Modern project-management software does not win because it is a few dollars cheaper per seat. It wins when teams can spread it through the organisation without recreating the administrative and purchasing friction that drove them away from legacy tools in the first place.
Pricing leaders should design for participation before pushing ARPU higher
The wider lesson is not that per-seat SaaS pricing is dead. For products centred on human work, the seat remains one of the cleanest meters available. The mistake is assuming that every human interacting with the product represents the same amount of value.
Linear is close to the right answer because its product architecture already distinguishes deep work from broad participation. Its commercial architecture now needs to catch up.
For operators designing or resetting pricing in this category, we recommend five moves:
Make expansion through participation a board-level growth hypothesis. Measure whether accounts that expose more non-builders to the product subsequently add more active users, teams and paid workflows. Asana's reported view-only conversion provides a useful benchmark for what such a loop can look like.
Run the new meter against real customer histories before changing the public page. Re-rate a representative set of small, mid-market and enterprise accounts using active builders rather than total users, then determine the workspace fee required to keep the transition commercially neutral.
Judge the reset by net revenue retention, not by price per user. A lower average charge per visible participant is acceptable if customers invite more stakeholders, builders expand faster and account revenue grows.
Give sales one commercial sentence that a buyer can repeat internally: pay for the people who run the work, invite everyone who helps the work move. Complexity should live in the entitlement system, not in the explanation.
Use the metric change as product strategy, not discounting. A model that lets a 50-person product team involve hundreds of colleagues without hundreds of additional licences creates a competitive difference that another 10% promotional discount cannot match.
Linear has already demonstrated that modern project-management software can strip considerable friction out of the work itself. Its next pricing advantage should come from doing the same to the bill.
Assumptions
All public prices are USD list prices reviewed on or around 13 August 2026 unless another date is stated; taxes, negotiated discounts, minimum commitments and private Enterprise terms are excluded. The historical Linear comparison uses April 2026 Internet Archive captures. The 100-person scenario assumes 45 active builders, 35 contributors and 20 viewers/requesters, with a modelled $10,000-$15,000 annual Enterprise workspace fee; it is not Linear pricing guidance. No Linear 10-K or public earnings-call transcript was available in our source review, so the brand-specific teardown uses Linear's official pricing and archived pages, while public-company filings and official earnings transcripts from Atlassian, Asana and monday.com provide market triangulation.
Footnotes
Monetizing Agentic AI, Ajit Ghuman and Akhil Gupta, Monetizely, 2026: https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
Linear, official pricing page, current review August 2026: https://linear.app/pricing
Internet Archive, Linear pricing page, April 2026 captures: https://web.archive.org/web/202604*/https://linear.app/pricing
Atlassian, Jira official pricing and billing documentation: https://www.atlassian.com/software/jira/pricing
Atlassian, Jira Product Discovery official pricing: https://www.atlassian.com/software/jira/product-discovery/pricing
Atlassian Corporation, Form 10-K for fiscal year ended 30 June 2024: https://d18rn0p25nwr6d.cloudfront.net/CIK-0001650372/c6c36f27-7140-452e-a8e7-e711234d3427.pdf
Asana, official pricing page: https://asana.com/pricing
Asana, Q4 fiscal 2025 earnings-call transcript, 10 March 2025: https://investors.asana.com/static-files/93dde8b3-8e59-48f8-bc87-945a6c34b2ed
monday.com, official pricing page: https://monday.com/pricing
monday.com, Q1 2025 earnings-call transcript, 12 May 2025: https://s29.q4cdn.com/881027206/files/docfinancials/2025/q1/MNDY-USQTranscript_2025-05-12.pdf
monday.com, Q4 2024 earnings-call transcript, 10 February 2025: https://s29.q4cdn.com/881027206/files/docfinancials/2024/q4/MNDY-USQTranscript_2025-02-10.pdf
Smartsheet, official pricing page: https://www.smartsheet.com/pricing
ClickUp, official pricing page: https://clickup.com/pricing