Quick Verdict: ClickUp 3.0 was announced February 28, 2023, reached general availability November 17, 2023, was deprecated March 27, 2026, and superseded by ClickUp 4.0 — a roughly 28-month flagship lifespan, unusually short for a major SaaS release. Between 2023 and 2026, five specific bets ClickUp placed during the 3.0 cycle drew sustained pushback in r/clickup and on the ClickUp Feedback Portal. None of these bets means ClickUp is unusable today; each shifts a different trade-off for a different group of paying users.
The five bets, in unpack order:
- “On-time delivery” — announced February 2023, phased rollout stretched 8.5 months to GA.
- “Performance first” — 3.0 GA promised “2x, 3x, 5x faster”; early adopters called it “unusably slow”; a Feedback Portal performance thread still carries 1,100+ votes in 2026.
- “AI-first roadmap” — aggressive AI shipping while a 174-vote “Fix existing bugs rather than add new features” thread sat at the top of the request board.
- “Stable pricing” — grandfathered Plus pricing rolled forward, guest seats reclassified, several 2025 renewal threads documenting 2x to 8x billing changes.
- “Customer success” — forced default changes, escalation-only support, and the April 27, 2026 feature-flag data incident.
| If you are a… | Should you care? |
|---|---|
| Heavy power user / long-tenured | Yes — bets #2, #3, and #5 most likely affect daily workflow. |
| SMB on Business plan with guests | Yes — bet #4 (pricing reclassification) is the largest dollar exposure. |
| Large enterprise admin | Yes — bets #2 (large-workspace performance) and #5 (support, incident) matter. |
| New prospect evaluating ClickUp | Read all five — none blocker in isolation, but they set context for 4.0. |
We do not recommend leaving ClickUp; we do not recommend doubling down. We lay out evidence so you can decide.
How We Researched This
We built this analysis from primary discussion sources rather than secondary tech-press summaries.
What counted as a primary source: Reddit user posts on r/clickup — thirteen high-upvote threads spanning November 2022 to March 2026 — vote-weighted feature requests on the ClickUp Feedback Portal (where ~2,400 cumulative votes across the performance, bugs, and pricing threads were counted), the official ClickUp blog (3.0 announcement, 3.0 GA post, 4.0 launch post, April 27 incident post-mortem), the ClickUp 4.0 changelog and Help Center, the BusinessWire 4.0 GA press release for the official “Craft & Quality” launch theme and CEO statement, and the ZenPilot 4.0 review by an eight-year ClickUp partner.
What we treated as secondary: general SaaS round-ups, comparison blogs, and unverified Twitter / LinkedIn commentary. Useful for context but not counted toward our “≥1 primary source per bet” requirement.
What we deliberately excluded: G2 and Capterra rating time-series — these require paid review tools to reconstruct historically. We cite the current G2 snapshot (4.7/5 across 11,176 reviews) for scale only, not for trend.
Two-sided requirement: Every bet section pairs a critical user quote with either an on-record ClickUp response or a third-party defending voice. Where the official defense is limited to general announcements, we flag it explicitly rather than paraphrase.
Source Bias Disclosure
Pricing changes, deprecation dates, and official defenses in this article are primarily sourced from ClickUp’s own announcements and Help Center pages. Independent third-party verification of precise numbers — what exact day a feature was deprecated, what the official “before” price was — is structurally limited because these facts are originated by ClickUp itself.
User-side narratives, in contrast, are sourced from r/clickup and the ClickUp Feedback Portal, where roughly 2,400 verified paying-user votes carry more weight than anonymous social comments. Reddit posts are subject to selection bias toward users who are vocal enough to post; quiet satisfied customers are under-represented by definition. We balance both sides per bet, and where the ClickUp side is publicly thin we say so directly rather than inventing parity.
Bet #1: The “On-Time Delivery” Promise (Missed by 8.5 Months)
What ClickUp promised
On February 28, 2023, ClickUp published “ClickUp 3.0 is here” — the company’s announcement that a rebuilt ClickUp 3.0, with a new architecture and overhauled UI, was beginning to roll out. The framing in the announcement and in adjacent CEO communication was that 3.0 was actively shipping in 2023, with paying customers expected to be migrated within the year. For many existing customers, that announcement was read as a near-term delivery commitment.
What actually happened
3.0 did not become generally available in spring 2023. It did not become generally available in summer 2023. The official “ClickUp 3.0 is now available for everyone” post landed on November 17, 2023 — roughly 8.5 months after the February announcement. Across that window, r/clickup ran a recurring genre of “where is 3.0” posts that mixed dark humor with mounting frustration about missed dates.
In April 2023, a thread titled “Waiting for Clickup 3.0 like…” reached 72 upvotes with an OP that mocked the wait using a string of emoji aging from baby to elder. The comment thread was a mix of genuine frustration and resigned humor — paying customers checking back week after week without a delivery date.
A month later, “I think I know why ClickUp 3.0 is taking so long” surfaced a more pointed theory: ClickUp’s own internal performance problems were slowing the team. The OP wrote that ClickUp “must be using ClickUp 2.0 to run their own business and it’s dammmmn slow,” framing the delivery delay as a symptom rather than a discrete schedule miss.
By June, “3.0 — Where are you?” had reached 55 upvotes and surfaced what became one of the more cited comments of the cycle. A user named italicizedmeatball wrote, in a 13-upvote reply:
ClickUp is scraping bottom on integrity as a company for behaving this way, I’m actively looking at other options.
— italicizedmeatball, r/clickup comment, June 2023
That comment captures the specific complaint: not that 3.0 was late, but that communication around being late was opaque. By August, the thread “When the product (Clickup 3.0) is not ready but we have to deliver something” reframed the delay as forced-shipping — the OP described the launch as ClickUp having “overpromised and missed the ETA by months multiple times” before delivering anyway.
Timeline
| Date | Event |
|---|---|
| 2023-02-28 | ClickUp publishes “ClickUp 3.0 is here” announcement, signaling 2023 rollout. |
| 2023-04-11 | r/clickup “Waiting for Clickup 3.0 like…” (72 upvotes). |
| 2023-05-26 | r/clickup “I think I know why ClickUp 3.0 is taking so long” (52 upvotes). |
| 2023-06-07 | r/clickup “3.0 — Where are you?” (55 upvotes). |
| 2023-08-31 | r/clickup “Clickup 3.0 is not ready but we have to deliver something” (40 upvotes). |
| 2023-11-17 | ClickUp publishes “ClickUp 3.0 is now available for everyone” — GA. |
Data points
The hardest single number from Bet #1 is the announcement-to-GA gap: roughly 8.5 months from February 28, 2023 to November 17, 2023. For a flagship SaaS release that was framed as already shipping, an 8.5-month difference between announcement and “available for everyone” is the headline data point. Four high-upvote r/clickup threads (72 + 52 + 55 + 40 = 219 cumulative upvotes) tracked the wait across that window — not a viral spike but a sustained drumbeat of public frustration.
The defense
ClickUp’s official communication frames the 3.0 timeline as a phased rollout, not a missed launch — the February 28 post used “here” language about early access and beta cohorts, and the November 17 post explicitly called itself “available for everyone,” signalling the difference between early-access shipping and general availability.
Limited public defense beyond official communication. We did not find a contemporaneous ClickUp engineering blog or executive interview that publicly addressed the 8.5-month gap as a missed schedule; the framing has consistently been “phased rollout completed.” Independent customer voices defending the delay specifically — as opposed to defending ClickUp generally — were rare in the same r/clickup threads.
4.0 era status
ClickUp 4.0 was announced and made generally available on December 9, 2025 per the BusinessWire press release. Unlike 3.0, the 4.0 cycle did not produce a recurring “where is it” genre on r/clickup — the announcement and the GA were the same event, which closes this specific pattern.
Primary impact: entire customer base during 2023, with the strongest signal from existing paying customers who were waiting on the new architecture.
Bet #2: The “Performance First” Promise (3.0 Launched Slower, 4.0 Still Sluggish for Some)
What ClickUp promised
The “ClickUp 3.0 is now available for everyone” GA post on November 17, 2023 led with performance. Across the announcement and adjacent ClickUp marketing, the new version was framed as “2x, 3x, 5x faster” than 2.0 — speed was positioned as the primary justification for the rewrite. For users who had been told the rollout would deliver a faster ClickUp, performance was the headline promise.
What actually happened
Performance problems on the ClickUp web app predate 3.0. A November 2022 r/clickup thread, “Why is ClickUp so slow?,” reached 48 upvotes a full year before the 3.0 rollout, surfacing load-time and dragging issues on what was still 2.0. The 3.0 launch did not reset that signal — it added new ones.
The clearest user description of the post-launch experience came in a January 2026 r/clickup discussion. In a 63-upvote thread titled “You should not add any new features for the next 6 months,” commenter Naive-System1940 — defending ClickUp on net — wrote:
When 3.0 first came out it was unusably slow. They did a lot of invisible work to speed it up.
— Naive-System1940, r/clickup comment, January 2026
That comment is a balanced data point: it confirms the early-launch performance failure (“unusably slow”) and credits subsequent invisible work (“a lot of invisible work to speed it up”). It is the kind of nuance that does not show up in headline metrics.
The ClickUp Feedback Portal — where voting requires a logged-in paying account — preserves the longer-tail signal. The thread “3.0 is slow” reached 461 votes and was eventually marked Completed by ClickUp staff, even as users continued to comment about ongoing slowness into 2026. A separate older thread titled “Web app performance and speed issues” — open since 2020 and still active in 2026 — sits above 1,100 votes, the single largest performance complaint in the portal. A third thread, “Make it faster,” collected 371 votes and includes 2026 comments from paying customers who say they are reconsidering renewal:
The app is painfully slow! It is unresponsive and dragging tasks in a sheet is just a waste of human resources.
— Sybren, ClickUp Feedback voter, January 2026
I can’t deal with the load times, hang-ups and crashes. This might be our last year using Clickup.
— Matt Adkins, ClickUp Feedback voter, March 2026
The pattern across all three threads is that performance complaints did not stop at 3.0 GA in November 2023 — they continued through the 3.0 lifespan and into the 4.0 transition window.
Timeline
| Date | Event |
|---|---|
| 2022-11-05 | r/clickup “Why is ClickUp so slow?” (48 upvotes, pre-3.0). |
| 2023-07-15 | ClickUp Feedback Portal “3.0 is slow” thread opens; eventually reaches 461 votes. |
| 2023-11-17 | ClickUp 3.0 GA; marketing promises “2x, 3x, 5x faster.” |
| 2025-10-27 | r/clickup “ClickUp 4.0 is very slow — especially Doc.” |
| 2025-12-09 | ClickUp 4.0 GA; BusinessWire launch positioned around “Craft & Quality” theme. |
| 2026-01-18 | r/clickup “You should not add any new features…” — Naive-System1940 confirms early 3.0 was “unusably slow.” |
| 2026-03-19 | Feedback Portal “Make it faster” commenter says “This might be our last year using Clickup.” |
Data points
The most-cited hard numbers in Bet #2 are the vote totals: 461 votes on “3.0 is slow,” 1,100+ votes on “Web app performance,” and 371 votes on “Make it faster.” That is roughly 1,900 paying-customer votes concentrated on performance alone, across three threads. On the ClickUp side, the 3.0 GA “2x, 3x, 5x faster” claim is the official 3.0-era performance benchmark; the 4.0 GA messaging shifted away from speed multiples to the “Craft & Quality” theme — itself an implicit concession that the 3.0-era speed framing did not match user experience for large workspaces.
The defense
ClickUp’s most direct on-record response is the 4.0 launch itself. The BusinessWire 4.0 GA post led with “Craft & Quality” as the version theme and quoted CEO Zeb Evans saying, “Every pixel of ClickUp 4.0 reflects our obsession with craft and quality. We’ve listened to our users, sweated every detail, and poured our love for productivity into this release.” Branding the next release around craft and quality — rather than another set of speed multiples — is itself an implicit acknowledgement that the prior cycle did not deliver on that axis.
On the user side, the strongest defense of ClickUp’s invisible engineering work came from Naive-System1940’s January 2026 r/clickup comment quoted above (“They did a lot of invisible work to speed it up”) — a paying customer crediting ClickUp for measurable improvement even while flagging the launch as initially unusable.
4.0 era status
Partially fixed for many workspaces, still ongoing for some. ZenPilot founder Gray MacKenzie — whose firm has worked with ClickUp implementations for eight years — wrote in his ClickUp 4.0 review that 4.0 is “the most stable major ClickUp release I’ve seen in 8 years,” a strong third-party signal that 4.0 narrowed the gap. At the same time, r/clickup thread “ClickUp 4.0 is very slow — especially Doc” from October 2025 documents that 4.0 has not fully closed the speed complaint for all workloads, particularly Docs-heavy ones.
Primary impact: large workspaces and power users with heavy data loads. Lighter workspaces report a smaller performance gap.
Bet #3: The “AI All-In” Bet (Users Asked for Bug Fixes, Got More AI Features)
What ClickUp promised
ClickUp’s product roadmap from 2024 through early 2026 leaned heavily into AI as the company’s primary differentiator. Successive releases shipped AI Tasks, AI Notetaker, AI knowledge agents, and AI-powered automation — each launched with marketing language framing AI as the path to faster project workflows. The implicit promise was that AI investment would compound into productivity gains for existing customers while opening new top-of-funnel positioning against AI-native competitors. The bet was that customers would absorb new features faster than they would notice deferred bug work. The Feedback Portal record suggests the opposite happened.
What actually happened
The clearest signal that ClickUp’s AI-first roadmap collided with user priorities is a Feedback Portal request titled “Fix existing bugs rather than add new features”, opened June 26, 2023 and still gathering votes through 2026 — 174 verified paying-user votes by spring 2026. The title states the priority inversion in five words. The comment thread documents how the gap widened across the AI-rollout period. On April 3, 2025, voter Steven Thiel summarized the position that recurs throughout the thread:
They have 10x features and 100x glitches…we need them but they suck.
— Steven Thiel, Feedback Portal commenter, 2025-04-03 source
Joshua Petrie’s earlier comment from July 5, 2023 quantified the user-side experience of the bug backlog: an “average turnaround time of ~8 months on bug fixes” — drawn from his own tracking rather than a ClickUp-published metric, but quoted across the thread for nearly three years.
Two 2026 Reddit threads escalated the same priority concern with substantial vote weight. On January 18, 2026, r/clickup post 1qgdr84 — title “You should not add any new features for the next 6 months” — collected 63 upvotes and dozens of comments arguing release cadence had outpaced ClickUp’s ability to stabilize what shipped before. Two months later, on March 18, 2026, r/clickup post 1rxbtla by michaeldrosenberg drew 120 upvotes for a longer post that connected the AI push directly to stability regressions:
baseline features and functionality break
— michaeldrosenberg, r/clickup, 2026-03-18 source
Commenters in both threads named specific AI-era regressions — task drag latency, Doc rendering hiccups, view rebuild times — that overlapped with the Bet #2 performance evidence and underscored that the two bets compounded rather than ran in parallel.
Timeline
The chronology stretches across nearly three years:
- 2023-06-26: Feedback Portal “Fix existing bugs rather than add new features” opens; 174 votes by spring 2026.
- 2024 through 2025: ClickUp ships successive AI releases — AI Tasks, AI Notetaker, AI knowledge agents, AI automation — each promoted as a flagship capability.
- 2025-04-03: Steven Thiel posts the “10x features and 100x glitches” comment that becomes a frequently quoted summary of the thread.
- 2026-01-18: r/clickup post 1qgdr84 — “You should not add any new features for the next 6 months” — collects 63 upvotes.
- 2026-03-18: r/clickup post 1rxbtla — 120 upvotes — connects baseline-feature breakage to the AI-first release pattern.
By the time the 2026 posts landed, the original 2023 Feedback Portal request had been live for more than 32 months without a status change.
Data points
- 174 Feedback Portal votes on “Fix existing bugs rather than add new features,” verified paying-user accounts, persistent across 2023–2026.
- 63 upvotes on the January 2026 “stop new features” Reddit post.
- 120 upvotes on the March 2026 “baseline features break” Reddit post.
- ~8 months average bug-fix turnaround per user tracking, per the most-quoted Feedback Portal comment from July 2023.
- “10x features and 100x glitches” — a phrase quoted in third-party reviews and other r/clickup threads since April 2025.
The Feedback Portal vote count rose steadily across three years, Reddit threads accumulated upvotes within days, and the complaint pattern recurred under different post titles — continuity is the strongest signal that the bet has not been quietly resolved.
The defense
ClickUp has not published a direct public response to the “stop new features” framing. The closest thing to a defense in the public record is a counter-comment from a long-time user inside the January 2026 Reddit thread, acknowledging stabilization work that did not show up in marketing materials:
When 3.0 first came out it was unusably slow. They did a lot of invisible work to speed it up.
— Naive-System1940, r/clickup, 2026-01-18 source
That is not a ClickUp employee speaking, but it captures real tension: a company can be doing significant stability work and still leave users feeling the AI push is louder than the fix push. The 4.0 “Craft & Quality” tagline in December 2025 is the closest thing to an indirect strategic-direction defense — read most naturally as an acknowledgment that the 3.0 era skewed toward velocity at the expense of polish.
4.0 era status
Partially fixed. The “Craft & Quality” tagline at the December 2025 4.0 launch signals an explicit strategic rebalance toward stability over feature velocity. ZenPilot Founder Gray MacKenzie’s 4.0 review described the release as “the most stable major ClickUp release I’ve seen in 8 years” — a strong industry endorsement that the bet’s stability cost was being addressed. That said, the 174-vote Feedback Portal request remained without a “Resolved” status as of spring 2026, and 4.0 continued to add AI capabilities alongside stability work rather than freezing feature development.
Primary impact: active users across all plan tiers — particularly paying customers and power users who tracked specific recurring bugs and watched AI announcements ship in front of fixes for those bugs.
Bet #4: The “Stable Pricing” Promise (Grandfathered Plans Broken, Bills 8x Up)
What ClickUp promised
Like most maturing SaaS products, ClickUp historically positioned itself around grandfathered pricing for existing customers — the implicit promise that paying customers locked in at one price would not be moved to a more expensive structure without notice. Public-facing marketing emphasized predictability and the ability for teams to plan budgets year over year. Sales conversations frequently included grandfathered-rate language for early customers. The bet was that ClickUp could refresh its pricing for new customers without disrupting existing customer trust. Three Reddit threads from 2025 indicate that, at least for a subset of customers, the disruption was substantial enough to land in r/clickup with high vote counts.
What actually happened
The most-shared example came on January 9, 2025, when r/clickup user rhodesbrosky posted “Bill went from $144 to $1200” — collecting 53 upvotes and a thread of similar experiences from agencies and SMBs working with guest collaborators. The cause was a structural change in how ClickUp billed for guest users:
ClickUp changed their pricing structure without warning and now charges full member fees for guests (unless they’re view-only).
— rhodesbrosky, r/clickup, 2025-01-09 source
For agencies and consultancies whose workflow involved inviting many client-side editors as guests — historically a low- or no-cost seat — the change meant guests crossed an invisible line into paid-member billing. A $144 monthly bill becoming $1,200 monthly is an 8.3x jump; for a small agency on tight project margins, that math forces a renegotiation with clients, a switch to view-only access (which often defeats the collaboration use case), or migration off the platform.
The pattern repeated on February 27, 2025, when r/clickup user ryanoburch posted “Warning for anyone evaluating ClickUp”, drawing 77 upvotes — the highest-voted post in this cluster:
Upon this year’s renewal … our price would essentially double.
— ryanoburch, r/clickup, 2025-02-27 source
Multiple comment replies reported the same renewal pattern: workspaces priced consistently for years suddenly faced roughly 2x increases at renewal time.
By June 1, 2025, the grandfathered-pricing question itself became the headline. Several_Guava_1992 posted “ClickUp just chicken out from their grandfathered” with a direct account of a written commitment going unhonored:
We had an email before that they will grandfathered our price at $9 … we are now billed at $12 without notice.
— Several_Guava_1992, r/clickup, 2025-06-01 source
The dollar amount is smaller than the 8x agency bill, but the complaint is sharper: a written commitment about a held rate was followed by a billing change without further notice. For customers whose primary trust criterion is “the company keeps written promises,” that example carries the most weight.
Timeline
The 2025 pricing-disruption cluster fits a compact six-month window:
- 2025-01-09: rhodesbrosky posts “Bill went from $144 to $1200” — 53 upvotes — documenting the guest-seat billing change.
- 2025-02-27: ryanoburch posts “Warning for anyone evaluating ClickUp” — 77 upvotes — documenting renewal-time roughly-2x increases.
- 2025-06-01: Several_Guava_1992 posts the explicit grandfathered-commitment breakage — 17 upvotes but unusually specific evidence — a written email about a held $9 rate followed by $12 billing.
The three posts span agency billing, renewal pricing, and grandfathered commitments — three distinct dimensions of the same underlying bet that “stable pricing” would not produce visible churn signal.
Data points
The numerical record on this bet is unusually concrete because users posted exact dollar amounts:
- $144 → $1,200 = 8.3x billing jump for an agency hit by the guest-seat rule change (January 2025).
- Roughly 2x renewal pricing at year-over-year contract renewal, per the most-upvoted thread (February 2025, 77 upvotes).
- $9 → $12 per seat = 33% increase against an explicit grandfathered email commitment (June 2025).
- 53, 77, and 17 upvotes across the three Reddit posts — the 77-upvote post in particular is one of the higher-voted ClickUp pricing posts in r/clickup’s recent history.
For the agency case, the 8.3x multiplier is the headline number, but the underlying mechanism — a billing rule change that reclassified guest seats — is the durable signal. Pricing tables that change the meaning of an existing seat category can produce dramatic bill changes even when the per-seat list price has not moved.
The defense
ClickUp’s public position on the 2025 pricing transitions, reflected in the pricing page and customer communications, frames the changes as routine product evolution. No standalone announcements explained the structural rationale for the guest-seat reclassification or the grandfathered-rate transition — those were treated as commercial mechanics, not communications events.
The internal logic is real: companies routinely refresh pricing for new customers, adjust seat definitions as capabilities expand, and let grandfathered customers age off through renewal. The user side reads the same mechanics differently — particularly when a written commitment is followed by a billing change. That gap between commercial logic and the trust framework customers thought they bought into is what made the 2025 posts land with the vote counts they did.
4.0 era status
Unresolved at the policy level; case-by-case at the customer level. ClickUp’s pricing page reflects the post-2025 structure, with no public statement committing to held rates for new cohorts. Individual support escalations produced negotiated outcomes during 2025–2026 — typically when customers cited reddit threads or filed billing disputes — but no published policy has changed.
Primary impact: paying customers, particularly SMBs and agencies with significant guest-user footprints, plus customers holding a grandfathered-rate commitment from earlier years.
Bet #5: The “Customer Success” Promise (Forced Defaults, Support Backlog, Feature-Flag Data Incident)
What ClickUp promised
ClickUp positioned customer success as a structural advantage — feature-rich enough to consolidate categories, responsive enough to support large rollouts. The pitch worked: by late 2025 the company reported 20M users, 4M teams, ~$300M ARR. The implicit promise was a reliable customer experience — predictable defaults, working support, safe handling of customer data.
What actually happened
Three distinct customer-experience signals stacked up across late 2024, 2025, and early 2026, ending in a security incident.
The first signal was forced default changes. In a March 2026 r/clickup thread titled “I’m so tired ClickUp” — 120 upvotes — original poster michaeldrosenberg wrote:
I’ve complained, endlessly, about default behavior being changed on users, forcing users to come into work one day and re-learn or re-configure their way of life.
— michaeldrosenberg, r/clickup, March 2026
That post drew an unusually direct reply. In the same thread, ClickUp’s product strategy lead — posting under the verified u/DeanPhillipsCU handle — wrote a four-word acknowledgement that received 32 upvotes on its own:
you’re not wrong on any of it.
— Dean Phillips, ClickUp product strategy, March 2026 r/clickup comment
The second signal was support response time. The February 2025 r/clickup warning thread (77 upvotes) is best known for its pricing message, but in the comments user FestiveFerret described a different problem:
got my problem escalated by reddit (the only way to get support to write you back).
— FestiveFerret, r/clickup comment, February 2025
Longer-tenured customers echoed the pattern. A January 2025 thread titled “Seriously regretting implementing ClickUp at my company” reached 79 upvotes, and an October 2024 post titled “Thinking about leaving ClickUp after almost 5 years” (43 upvotes) captured the kind of long-horizon churn signal that is rare in product subreddits.
The third signal was a confirmed security incident. On April 27, 2026, security researchers disclosed that ClickUp had been storing some customer data inside its feature flag configuration system — a non-customer-facing internal tool. The next day, ClickUp published a public post-mortem confirming the exposure: 893 customer email addresses and one API token, sitting within a configuration table of roughly 4,809 feature flags. The post-mortem also confirmed that the data should never have been there.
Timeline
| Date | Event |
|---|---|
| 2023-09-05 | Feedback Portal “3.0 update for whole teams” opens — 306 votes; admins flag version-split friction during 3.0 rollout. |
| 2024-10-14 | r/clickup “Thinking about leaving ClickUp after almost 5 years” (43 upvotes). |
| 2025-01-23 | r/clickup “Seriously regretting implementing ClickUp at my company” (79 upvotes). |
| 2025-02-27 | r/clickup “Warning for anyone evaluating ClickUp” — support-via-reddit comment surfaces. |
| 2026-03-18 | r/clickup “I’m so tired ClickUp” (120 upvotes) + Dean Phillips on-record acknowledgement. |
| 2026-04-27 | Security researchers disclose feature-flag data exposure. |
| 2026-04-28 | ClickUp publishes post-mortem and apology. |
Data points
The bet #5 numbers concentrate in two columns. On the user side: 120 upvotes for the March 2026 defaults complaint, 79 for the January 2025 regret thread, 43 for the October 2024 five-year-tenure churn signal, and 306 votes on the 2023 rollout-split Feedback Portal thread. On the company side: 893 customer email addresses and one API token exposed inside a 4,809-row feature flag table — the specific incident that produced the 2026-04-28 post-mortem.
The defense
This is the only bet where ClickUp’s own voice is on the record at scale, and that matters for the balance of evidence. Dean Phillips’s four-word reply to a 120-upvote critique is a rare on-the-record concession from a vendor product lead; the post-mortem the company published one day after the security disclosure goes further. The April 28 post opens with a direct acknowledgement:
We should have caught this sooner. We didn’t, and we owe you a clear explanation of what happened, why, and what we’ve done about it now and how we’re improving moving forward.
— ClickUp, official post-mortem opening, April 28, 2026
In a later “Where our process failed” section of the same post, ClickUp names the structural mistake explicitly:
None of these excuse the core issue: customer data should never have been in our feature flag configurations in the first place.
— ClickUp, post-mortem “Where our process failed” section, April 28, 2026
Two things stand out. The language across both passages is unusually direct for an incident disclosure — naming the structural mistake rather than minimizing scope. And the timing — a same-week named Reddit response, then a public post-mortem within 24 hours — represents a different operating tempo from bet #3 bug-fix delays. Whether that tempo persists is the open question.
4.0 era status
Still in progress. ClickUp 4.0’s “Craft & Quality” positioning, launched in December 2025, predates the April 2026 security incident, so 4.0 cannot itself be credited with the response — the response is post-4.0 operations. The Dean Phillips Reddit reply and the same-week post-mortem are the visible signals that customer-success operations are getting more attention; the durability of that posture is something only the next twelve months of incidents and support response times can confirm.
Primary impact: enterprise customers and five-plus-year tenured accounts. Newer, smaller customers experienced fewer touch points with the changing defaults and the support backlog.
What 4.0 Learned: The “Craft & Quality” Pivot
ClickUp 4.0 shipped on December 9, 2025, 25 months after the 3.0 GA and four months before 3.0 itself was deprecated. The official theme — “Craft & Quality” — is the clearest evidence ClickUp internally absorbed the 3.0-era pattern. Each word does work: “craft” answers bet #3 feature-density complaints; “quality” answers bet #2 performance and bet #5 default-change friction. A version theme is a strategic signal — the signal here is concession.
The strongest third-party endorsement: Gray MacKenzie, ZenPilot founder, called 4.0 “the most stable major ClickUp release I’ve seen in 8 years” in his 4.0 review — a comparative claim from a practitioner who has watched the platform across versions.
The user side is more mixed. Naive-System1940’s January 2026 comment (bet #2) credits “a lot of invisible work” speeding things up between 3.0 GA and 4.0. The October 2025 r/clickup “ClickUp 4.0 is very slow — especially Doc” thread shows the gap has not closed for every workload, particularly document-heavy ones. The April 27 security incident, post-dating 4.0 GA by four months, is a reminder that platform engineering and customer-success operations move on different timelines.
Two open questions follow. First, whether the “Craft & Quality” theme produces measurable improvements on the workloads that drove the original 461- and 1,100-vote performance complaints — third-party reviewers and individual user threads disagree on the magnitude, and ClickUp has not published 4.0 benchmark numbers. Second, whether the April 28 post-mortem tempo — direct, named, fast — becomes operating norm or stays a one-off. Neither has a settled answer.
What This Means for You
The retrospective above is descriptive, not prescriptive. The five bets are documented because they happened, not because they predict where your team should land. We frame guidance as one of three options — continue (keep current setup), observe (delay the decision while watching specific signals), or consider alternative (begin pricing replacement options) — three paths rather than a binary, with the right path depending on which user group describes you most.
Heavy power users and agencies — observe. You absorbed the most concentrated impact from bets #2, #3, and #5. If your renewal is more than 90 days out, keep watching 4.0 stability for two billing cycles before committing to a multi-year. The ClickUp review page tracks current performance with 4.0 improvements applied; cross-check against your daily workflow rather than any aggregate score. Signal to watch: whether the April 28 post-mortem tempo persists across the next two incidents.
SMB and small teams — observe for now, consider alternative if pricing math has drifted. Bet #4 has the highest direct dollar impact on you. Download your last twelve months of invoices and confirm the per-seat, per-guest, and renewal-rate math against the original quote. If the math has drifted more than 30%, the comparison with Asana and the broader alternatives roundup are worth pricing against during renewal week — to have a credible alternative quote in hand, not necessarily to switch.
Large enterprise — observe pending procurement-and-security review. Bet #5 maps to your risk model. The questions worth raising with ClickUp’s enterprise team: what changed in feature-flag data handling after April 27, what SLA covers support response for your tier, whether “Craft & Quality” extends to a documented change-management policy on defaults. Whether the answers suffice is a procurement-and-security call — continue if the answers move, consider alternative if they do not.
New prospects — continue evaluation with a hard trial. None of the five bets disqualifies the platform; together they describe a platform that shipped fast, accumulated debt, and is now in a published correction cycle. Run a fourteen-day trial against your most demanding workflow (high-cardinality database, Docs-heavy use case, or whichever pattern matches daily reality). The trial is more informative than the retrospective.
ClickUp’s #1 ranking on the 2026 PM tools comparison reflects price-to-feature for budget-conscious teams — an axis unchanged by this retrospective.
Frequently Asked Questions
What happened to ClickUp 3.0?
ClickUp 3.0 was announced February 28, 2023, reached GA November 17, 2023 (8.5 months late), and was deprecated March 27, 2026 — a roughly 28-month flagship lifespan, unusually short for a major SaaS version. Across that window, 3.0 absorbed five bets: delivery delay, performance complaints, an AI-feature push that pulled engineering attention from bug fixes, pricing-structure changes that broke grandfathered plans, and a customer-success backlog ending with the April 2026 feature-flag data incident.
Is ClickUp 4.0 stable now?
Partially. ZenPilot’s Gray MacKenzie called 4.0 “the most stable major ClickUp release I’ve seen in 8 years,” and the BusinessWire launch positioned 4.0 around a “Craft & Quality” theme — an explicit posture reset. An October 2025 r/clickup thread documents 4.0 latency in document-heavy workloads, and the April 2026 security incident post-dated 4.0 GA. The honest read: 4.0 closed the largest gaps but has not been observed long enough to confirm the posture persists across release cycles.
Should I switch from ClickUp after these issues?
Probably not on this retrospective alone. The retrospective is descriptive; switching is forward-looking and depends on your renewal date, alternatives, and what 4.0 looks like for your workflow. A defensible step: run your real workload on 4.0 for two billing cycles, while maintaining at least one credible alternative quote.
Why did ClickUp deprecate 3.0 so quickly (28 months)?
ClickUp did not publish a single explanation, but the 4.0 launch theme — “Craft & Quality” — frames 4.0 as a deliberate posture reset rather than incremental update. The 25-month gap between 3.0 GA and 4.0 GA, plus the 4-month deprecation window after 4.0 shipped, is consistent with cutting losses on 3.0-era decisions documented in bets #2 and #3 rather than continuing to patch them.
Did ClickUp’s pricing change break grandfathered deals?
In multiple documented cases, yes. The January 2025 “Bill went from $144 to $1200” thread describes an 8.3x jump after ClickUp began charging full member fees for non-view-only guests. A June 2025 thread documents a $9 grandfathered seat rate being billed at $12 without prior notice. A February 2025 warning thread reports renewals “essentially doubling.” Whether your account was affected depends on the original quote and billing period — compare your last 12 months of invoices against the quoted rate.
What was the April 2026 security incident?
On April 27, 2026, security researchers disclosed that ClickUp had stored 893 customer email addresses and one API token inside its internal feature flag configuration system — a tool not intended for customer data (roughly 4,809 feature flag entries total). On April 28, ClickUp published a public post-mortem stating that the data “should never have been in our feature flag configurations in the first place,” that the company should have caught it sooner, and that customers were owed a clear explanation. The post-mortem did not document downstream misuse.
How does this compare to other PM and workspace tools’ rollout history?
Major SaaS versions produce friction, but this specific pattern — eight-month delivery slip, performance regression, an AI push during a stability window, grandfathered-plan disruption, and a security incident — is more concentrated than typical. For a parallel retrospective on a comparable platform, the Notion 2026 controversy roundup documents a different but overlapping set of vendor decisions over the same window. Reading the two together is the easiest way to calibrate which patterns are vendor-specific and which are category-wide.