Explore Problems
Showing 4,118 of 9,994 problems · matching your filters
ISPs Continue Billing for Equipment Months After It Was Returned
Internet service providers charge customers for equipment for over a year after it has been returned and the return confirmed via UPS tracking. When customers dispute the charges, the burden is placed on them to prove the return rather than on the ISP to verify against serial number records. The process is designed to favor the ISP and exhaust consumers into paying unjust fees.
Opaque and Disproportionate Insurance Surcharges for Young Drivers
Parents adding young drivers to auto insurance policies face massive, unexplained premium increases that require persistent negotiation to partially resolve. The process repeats with each new young driver added, with no consistent pricing formula disclosed. Customers only discover they are being overcharged by comparison shopping with competitors.
Ambulance Debt Collectors Pursue Patients Who Never Chose the Provider
Patients transported by ambulance dispatched by a third party receive large collection demands for services they never selected or authorized, with no in-network choice available in the emergency. Debt collectors continue pursuing payment through repeated calls even when the patient explains they had no ability to choose the provider and cannot afford the bill.
Xfinity account settings changed without customer authorization or notification
A Comcast customer discovered their internet package, billing method, and statement preferences were all modified on a specific date without their knowledge or consent. Five transfers over one hour produced no explanation of how the changes were made or whether the account was compromised.
HubSpot tier jumps create unaffordable cost cliffs for growing teams
Moving between HubSpot pricing tiers involves sudden, steep cost increases that are difficult to justify or budget for during growth phases. The gap between tiers is not proportional to the incremental value received. Teams that hit these cliff points are forced to overpay, delay capability, or migrate away.
Zendesk workflow configuration stops non-technical teams at install
Teams without dedicated ops or technical staff cannot progress past initial Zendesk setup — the workflow builder requires enough configuration expertise that many users stall after installation and never activate core automation features. This creates a gap between what teams purchased and what they actually use.
Solo SaaS Builders Stall Near Completion Without Co-Founder or Collaborator
Indie developers frequently reach 70-90% project completion but lack complementary skills in marketing, design, or backend to ship. Finding trustworthy collaborators willing to work for equity or revenue share rather than cash is a persistent structural gap. Existing platforms like LinkedIn and co-founder networks are too generic for this specific need.
Small business owners cannot execute consistent marketing without significant time investment
Small business owners lack the time and marketing expertise to maintain consistent, effective marketing activities. Existing tools require significant learning curves or ongoing manual effort that owners cannot sustain alongside running their business. There is strong demand for solutions that deliver marketing outcomes without requiring owners to become marketers themselves.
No credible open-source bot for automating data-broker removal requests
Paid services exist for opting consumers out of data brokers but feel overpriced or scammy. The repetitive request flow looks well suited to AI automation, yet there is no widely-adopted open-source alternative.
AI Coding Agents Lose Context on Session Reset and Make Opaque Decisions
AI coding assistants forget all reasoning, design decisions, and open TODOs when a session ends, forcing developers to re-explain context from scratch. Compounding this, AI-generated code changes are opaque — it is unclear which prompt or reasoning step caused any given edit. These two gaps block AI agents from functioning as reliable, auditable collaborators in real development workflows.
Long-running coding agents lose task state when context windows overflow or sessions end
Coding agents handling multi-phase tasks store all intermediate state in volatile session context. When context overflows or sessions terminate, the agent loses the full decision history, leading to repeated mistakes and failed handoffs across phases. There is no standard mechanism for externalizing agent workflow state to durable structured storage.
AI Applications Lack Built-in Prompt Injection and Data Leak Detection
Teams building AI apps and agents have no easy way to screen inputs, files, URLs, or MCP server responses for prompt injection attempts and data leakage before that content reaches their models. This creates a security blind spot as more products wire untrusted content directly into LLM context windows.
Auto lenders report conflicting delinquency histories across credit bureaus despite formal disputes
Consumers dispute inaccurate and inconsistent credit report entries from an auto lender, only to have the tradeline reappear with materially different delinquency data across the three major bureaus. Furnishers reportedly fail to provide documentation proving what was actually verified, leaving consumers without a clear channel for resolution even after formal FCRA dispute procedures.
Account Termination Revokes the Support Access Needed to Dispute It
A remote worker arranged with an agent to keep internet running until a specific date before a move, had the date confirmed several times, and came home to find service already cut. Attempting to reach support was impossible because the assistant now classified them as a former customer and refused contact. Disconnection simultaneously creates the dispute and removes every channel for raising it.
Consumer Apps Rely on Billing Dark Patterns and Forced Gamification
Mining thousands of 1-3 star reviews across 15 competitor apps in a niche revealed the top complaint by volume was billing dishonesty: charges immediately after onboarding, refused refunds, and hidden cancel buttons. A close second was fatigue with forced gamification (mascots, streaks, pop-ups), with no honest-pricing, non-gamified alternative available in the category.
Prepaid Card Providers Close Accounts and Block Access to Direct-Deposited Benefits
Recipients of Social Security and disability direct deposits report prepaid card providers closing their accounts without cause immediately after a deposit lands, cutting off access to funds they depend on for essential living expenses. No clear process exists to recover the money once the account is closed.
LLMs Produce Inconsistent, Off-Style Frontend UI Code
Developers report that while LLMs generate strong backend code, frontend output ignores existing design systems, introduces redundant custom CSS/JS, and picks inconsistent colors, fonts, and alignment. The community workaround is strict prompting rules plus pointing the model at specific component libraries or MCP-exposed design systems.
Banks give no usable detail on unrecognized card transactions
A cardholder who spotted an unrecognized transaction found the bank chatbot and phone support unable to provide merchant location, time, or cardholder details, and was even given a wrong merchant contact. The gap forces customers into slow manual dispute processes for something a merchant-enrichment layer could resolve automatically.
SaaS Vendors Use Dark-Pattern Cancellation Flows to Trap Subscribers
Business software vendors design cancellation flows that mislead users into believing they have cancelled when they have not, resulting in continued charges. HubSpot and similar platforms use multi-step confirmation gaps that exploit user assumptions. This is a structural problem affecting millions of SaaS subscribers who discover unwanted renewals only after billing.
AI Writing Tools Lack Persistent Default System Prompts
Users of AI copilot and prompt tools cannot set a persistent default system prompt or brand voice that automatically applies to every new chat session. Each session requires manual re-setup, breaking workflow continuity for teams and individual creators who rely on consistent tone and context.