Explore Problems

ClickUp has silently changed subscription plans and removed features without informing affected customers, causing unexpected account disruptions and eroding trust. Users are left to discover changes on their own.

Existing SAST benchmarks measure only simple single-file taint flows, failing to evaluate whether tools can correlate low-severity findings across multiple files into compound exploit paths. Security engineers and tool vendors lack a statistically rigorous, tool-agnostic way to measure how well static analysis tools detect chained vulnerabilities or resist adversarial evasion techniques. This gap means SAST tools can appear performant on standard benchmarks while completely missing real-world attack patterns.

DevOps teams are frequently asked to find orphaned AWS resources and explain high cloud bills but lack good open-source tooling. Existing FinOps SaaS platforms are expensive, and writing one-off scripts is tedious and error-prone.

Some businesses generate revenue in Stripe that appears earned but is never actually collected, due to failed charges, incomplete billing flows, or dunning gaps. This lost revenue often goes unnoticed until reviewed manually. It matters because uncollected revenue directly erodes margins for subscription and usage-based businesses.

A customer's certificate of deposit was closed by a bank employee without authorization, and despite filing a police report and signed fraud statement, the bank denied the fraud claim without providing an investigation report. Three months later the account remains unresolved.

A State Farm customer's authorized EFT payment was blocked by a shifting documentation requirement, and after weeks of unanswered follow-up with an unavailable broker, the policy was cancelled without proactive notice. The cancellation letter arrived after the effective date had already passed, leaving the customer with a $199 penalty for a coverage gap at their new insurer.

A PODS moving and storage customer had two scheduled deliveries cancelled by the company and was charged a storage fee they had been told would be waived. Ten days after filing a formal complaint, PODS has not followed up, leaving the customer suspecting the delays and charges are not accidental.

A customer's payments failed because Progressive's own accounting staff entered an incorrect card expiration date, triggering two returned-payment events and a delinquent account; despite a representative acknowledging the error, no one could correct it or escalate the issue. The customer paid the disputed amount to avoid a coverage lapse and is now fighting to clear a credit report entry caused entirely by the insurer's mistake.

A driver whose parked car was hit by an Allstate-insured driver spent over 14 hours trying to get repairs approved, was asked to pay for a rental car upfront for later reimbursement, and was pressured to accept recycled parts the body shop deemed substandard. Each additional issue required a two-day approval wait.

A GEICO policyholder reports the insurer finalized an at-fault liability decision against them before reviewing submitted scene photos, and misidentified the other driver's gender despite contrary evidence. A claims director reportedly admitted the decision would not be reversed due to internal corporate concerns.

Progressive added a policyholder's adult son, who already carried his own separate policy, to the household policy and charged $450 extra without clear authorization. Even after confirming the addition was an internal agent error, the company refused to issue a refund.

A small-dollar lender repeatedly texts and calls a disabled borrower with deceptive loan-renewal offers and abusive language, despite the borrower's financial hardship and repeated attempts to end contact.

After a customer's mobile line is cancelled following their death, the carrier reassigns the phone number to a new subscriber but keeps billing the deceased's stored card, then refuses a refund because the estate has no active account to credit.

A borrower describes a credit union rejecting standard loss-mitigation options during a documented family financial hardship, while compounding junk fees and limiting account access through restrictive online banking design. The pattern reflects a structural failure in how lenders handle hardship-driven loss mitigation.

While comparison-shopping loan rates online, a consumer connects their bank account to check eligibility and, without ever accepting a loan agreement, ends up with an active loan carrying roughly 1000% APR — exposing a consent/disclosure gap in online lending eligibility checks.

Consumers taking loans from high-interest online lenders are not given clear disclosure of interest rates and repayment terms at origination. By the time they realize the cost, they are trapped in unaffordable payment cycles. Predatory lending disclosure gaps are structurally pervasive in subprime and tribal lending.

Fraudsters impersonate payment platform representatives to trick consumers into creating accounts that enable unauthorized fund transfers. Victims follow seemingly legitimate instructions before realizing they were scammed. The pattern exploits trust in branded communication channels and is difficult to distinguish from real support interactions.

Configuring ClickUp notifications requires extensive experimentation to get right — users either receive overwhelming noise or miss important updates. The lack of intuitive notification controls is a systemic UX gap that degrades the daily experience for teams.

Non-designers using Canva on mobile face a steep learning curve making the tool feel inaccessible. The gap between desktop and mobile experience is notable. This limits adoption among the broad consumer market of casual creators.

Developers configuring Spring Boot to connect to PostgreSQL running in Docker frequently hit authentication failures because localhost inside a container refers to the container itself, not the host machine. This common Docker networking misunderstanding blocks local development setup. The fix is well-documented but Spring Boot error messages do not surface the root cause clearly.