Explore Problems
Showing 799 of 4,293 problems · matching your filters
T-Mobile Charges Thousands After Cancellation Despite In-Store Confirmation
T-Mobile Home Internet continued billing months after a documented cancellation, with in-store staff confirming the account was fully disconnected yet charges continuing and escalating. Equipment return instructions were delayed for months. The pattern mirrors industry-wide post-cancellation billing fraud affecting thousands of customers.
Insurance Premium Spikes After Adding Drivers With Minority-Sounding Names
A policyholder experienced an unexplained premium increase after adding a driver with a Hispanic name, with the increase persisting even after removing that driver entirely. The insurer deleted previous lower quotes without notice and refused to honor them. The pattern suggests possible proxy discrimination in underwriting algorithms that is difficult for consumers to detect or prove.
Insurers Raise Premiums Sharply on Long-Term Loyal Customers After Minor Claims
Long-term policyholders with clean histories face steep premium increases after minor covered incidents like pipe breaks or roadside assistance. Loyalty provides no protection against rate hikes, and insurers use any claim as justification for significant increases. This punishes customers for using the coverage they paid for.
State Farm Raises Rates After Covered Roadside Assistance Use Customers Paid For
State Farm increases premiums after customers use covered roadside assistance for a flat tire, treating a basic covered service as a chargeable claim. Customers who followed policy terms find themselves penalized with rate hikes exceeding $100 per month. This creates a perverse incentive where using insurance coverage actively harms the policyholder.
AI-generated UI code quickly becomes inconsistent and unmaintainable
Developers using AI coding agents like Cursor or Claude Code to build UIs find that generated components ignore existing design systems, mix inline styles, and produce hallucinated code that becomes inconsistent and production-unready after a few iterations. This structural limitation of context-unaware AI code generation is a major pain point as AI coding adoption accelerates.
QA Cannot Keep Up With AI-Agent-Generated PR Volume
Engineering teams using AI coding agents are producing far more pull requests than QA can review, particularly where testing requires physical devices or complex workflows. The mismatch between AI-generated output velocity and fixed human review capacity creates a structural bottleneck that worsens as agentic tooling matures. Existing CI and code review tooling was designed for human-paced output and does not address the volume problem.
No Unified Development Environment for Running Multiple AI Agents in Parallel
Developers building with multiple AI models lack a single workspace to orchestrate parallel agents, browser, and IDE simultaneously, forcing constant context switching. Multi-agent coordination tooling represents an emerging infrastructure gap as agentic AI workflows become standard practice.
AI Invalidates Traditional Technical Hiring Assessments for Engineers
Engineering hiring teams are struggling to design assessments that meaningfully evaluate candidates now that AI tools are a normal part of how engineers work. Banning AI makes assessments feel artificial while allowing it without redesigning the evaluation produces noisy signals that conflate prompt skill with engineering ability. There is a clear and growing market need for AI-native technical assessment frameworks and tooling.
No Independent Low-Latency Search API Purpose-Built for AI Agents
AI agents relying on web search face latency and dependency issues with incumbent providers not designed for programmatic agent use. The need for a custom-built search API with own crawler and retrieval models indicates a clear market gap as agent workloads scale.
AI Agent Benchmarks Fail to Predict Real-World Performance
Teams building AI agents find that standard benchmarks are poor predictors of real-world performance, making it difficult to evaluate and compare agents reliably. This creates a gap in the evaluation tooling ecosystem as multi-agent architectures become more common.
LLM Agents Lose Goal Coherence in Long-Running Sessions
Developers building multi-step LLM agents report that models drift from their original task framing over extended sessions, abandoning planned workflows or producing outputs that deviate from agreed specifications. The problem is particularly acute with architect-style sub-agents expected to maintain consistent behavior across many turns. No reliable mechanism exists to detect or correct drift without full session restarts.
Global Remote Teams Lack Portable Group Health Insurance Without Multi-Country Entity Setup
Founders running multi-country remote teams from a single registered entity cannot easily procure group health insurance that covers employees across borders without establishing local legal entities in each country. International Private Medical Insurance (IPMI) providers exist but require navigating provider selection, compliance with mandatory national coverage mandates, and EOR considerations — a process most small ventures lack HR expertise for. The complexity creates a compliance gap and benefits inequality across the team.
Auto Lender Reports Contradictory Payment Status Across Credit Bureaus
An auto lender's official CFPB response contains internal contradictions, showing the same account as both delinquent and current simultaneously across different credit bureaus. The FCRA's maximum-possible-accuracy standard is unenforceable in practice when lenders can close complaints with inconsistent documentation. Consumers face damaged credit with no effective correction mechanism.
Developers Unsure Whether to Use AI-Native IDEs or VSCode Plus Claude for Building
Non-traditional developers and indie hackers building with AI assistance are confused about which environment yields better results — specialized AI builders or VSCode with Claude. Output quality inconsistency in AI-native IDEs is driving this uncertainty.
Landing Page Copy Fails to Resonate With Target Buyers
Marketers and founders lack reliable ways to validate whether their landing page messaging connects with ideal buyers before launch, leading to poor conversion rates. Simulated audience feedback tools address this gap by giving copy writers immediate signal from synthetic buyer personas.
AI Writing Tools Generate Generic Content That Lacks Authentic Voice
Content creators find that AI writing assistants produce bland, formulaic output that undermines authenticity and brand voice. There is demand for tools that help write with AI while preserving originality and avoiding the tell-tale signs of AI-generated content.
AI Image Generators Have No Memory of Project Style or Direction
Creative professionals cannot lock in consistent art direction across AI image generation sessions — each generation starts fresh with no awareness of prior creative decisions.
Tax tools fail workers with multiple W-2 jobs on combined withholding and 401k limits
Workers with two or more W-2 employers face a gap in tax software where no tool automatically combines federal withholding across employers, catches excess 401k deferrals before correction deadlines, or generates correct W-4 values per employer. This structural gap in multi-employer tax optimization affects a growing segment of workers with multiple jobs.
AI code review tools lack context about the full codebase they are reviewing
Generic AI code review tools only analyze diffs and have no awareness of the broader codebase, missing reinvented utilities, security gaps, and AI-generated code that only makes sense with knowledge of project patterns. This contextual blindness is a structural limitation of current diff-focused review tools in a fast-growing market.
No Unified Visibility Across Multiple Concurrent AI Coding Agents
When multiple AI coding agents run concurrently — including nested subagents spawned by parent agents — developers lose track of what each agent is doing, what tools it called, and whether it completed its assigned scope. There is no standard interface to correlate events across different agent runtimes operating on the same codebase. Without cross-agent observability, debugging unexpected changes or auditing agent behavior requires manually reconstructing session history.