Explore Problems

Notion users experience persistent bugs that delay and disrupt their workflows, particularly for teams who have centralized their documentation and project management in the platform. The instability undermines trust in Notion as a mission-critical tool and forces teams to maintain redundant systems as backup.

Power users of Claude report the AI starts recommending session termination well before they approach their usage limits, disrupting long-running work. The behavior is opaque — users cannot tell whether it is triggered by context window usage, server load, or some other threshold. This undermines trust in the tool for extended technical tasks.

Banks deny unauthorized transaction claims on checking accounts while refusing to share the evidence used in their determination. Consumers have no way to challenge findings or understand what criteria were applied, even when they report transactions immediately.

Users report Notion now requires constant internet connectivity even to access previously synced tables and notes, reversing prior offline functionality. The app has also become noticeably heavier and slower over successive updates. These regressions push power users toward local-first alternatives that prioritize performance and offline access.

Node.js and Deno are too large and slow to cold-start for CLI distribution and lightweight container workloads. A 9MB custom JS runtime with 5ms cold start solves the overhead problem for edge and embedded deployments. This fills the gap between full-featured runtimes and minimal sandboxes.

Asana users find that getting full value from advanced features requires attending dedicated training sessions, as the UI does not make capabilities discoverable on its own. The learning curve is steep enough that teams underuse the platform without formal onboarding investment.

Consumers with excellent payment histories face sudden credit card cancellations triggered by algorithmic review of temporary income decreases caused by medical or life events. Despite meeting all payment obligations, banks cite superficial risk signals with no human review or appeal process. This structural problem with automated credit risk systems causes significant consumer harm.

A consumer made a single payment that was duplicated by the bank's system, and when the bank reversed payments they cancelled the original rather than the duplicate while adding a late fee. Despite assurances from customer service, the error remained unresolved. This reflects systemic payment processing reliability and customer service failures at major banks.

Teams with many active Slack channels experience notification overload that buries important messages. The lack of offline message persistence and no native way to pin or save critical messages compounds the problem. This affects distributed teams who rely on async messaging as their primary coordination tool.

Homeowners cannot get consistent information from mortgage servicers about who owns their loan or the history of servicing transfers, making it impossible to verify payment history or enforce rights related to specific servicer agreements. RESPA requires servicers to provide loan ownership information on request but servicers routinely give incomplete responses. MERS registry lookup tools could help consumers independently verify ownership.

Auto dealers verbally represent trade-in terms that differ from what is actually written into lease agreements, leaving consumers locked into unfavorable terms they did not knowingly accept. The time pressure of dealership signings prevents careful review. Pre-signing contract analysis tools that flag common dealer misrepresentation patterns could protect consumers.

Citibank credits corrections to statements but excludes these credit entries from year-end transaction downloads and ledger views, making it impossible to reconcile accounts when the bank has made errors. The data omission is selective — only bank-initiated corrections are hidden — giving consumers no complete record for dispute documentation. Account transparency tools cannot fix this without bank cooperation.

Transferring photos and videos from iPhones to Windows or Linux machines involves HEIC format incompatibility, duplicate files, missing folder structures, and too many manual steps. Existing command-line tools lack user-friendly interfaces for non-technical users. A local-only GUI tool addresses privacy concerns while making the process accessible.

Consumers discover unexpected recurring charges for Google Drive storage they did not knowingly activate, with no proactive notification before billing begins. The subscription transparency gap affects users who miss the sign-up flow. A subscription audit and alert tool for unknown recurring charges would address this.

Banks reject international wire transfers without providing any reason and then refuse to return the funds to the originating institution. Consumers are left without their money and without explanation, unable to understand or remedy the block. The lack of transparency requirements for wire rejections creates financial paralysis with no appeal path.

Payroll administrators using Gusto face delays between timesheet submissions and payroll run visibility, creating uncertainty during payroll processing windows. The inability to bulk edit payroll entries across employees forces repetitive manual updates that scale poorly with team size. These gaps most impact companies with large hourly workforces where payroll accuracy and speed are operationally critical.

Hardware startup founders receive prototypes with undisclosed design changes made for manufacturing convenience. Lack of supplier transparency tools means problems only surface late in the production cycle. No standardized platform enforces change notifications between founders and manufacturers.

Teams managing large numbers of Trello boards struggle to locate the right board or card efficiently. The search function requires exact keyword matching rather than supporting natural language queries, creating significant navigation overhead as workspaces grow.

Banks apply right of setoff to checking accounts containing court-ordered spousal support arrears, redirecting protected funds to pay unrelated credit card debt. This practice potentially violates state exemption laws protecting support payments from creditor seizure. Vulnerable consumers receiving court-mandated support payments are left without access to protected funds.

Student loan servicers create payment processing errors that result in misapplied or lost payments, often without proactive notification to borrowers. Borrowers discover problems only after receiving delinquency notices, at which point credit damage may already have occurred. Servicer customer service is difficult to reach and slow to resolve disputes for an obligation borrowers cannot easily transfer.