Explore Problems

After 46 years as customers, a couple experienced increasing claim denials, large rate increases, and an unhelpful AI-driven support system. The breaking point came when the insurer refused to let a family member briefly drive the insured vehicle without first submitting his personal identifying information, despite decades of loyalty and no prior issues.

A T-Mobile customer reports being unable to make calls or watch TV due to service outages following a merger with US Cellular, attributing the degradation directly to the merger. The reliability issue is prompting the customer to consider switching to a competing carrier despite continuing to pay for service.

Customers of portable storage/moving container services report being billed for additional months while waiting weeks for a scheduled pickup that the company itself delayed, with no compensation or expedited resolution offered. This creates a situation where customers pay for service they can no longer use due to the providers own scheduling failures.

A customer describes repeated last-minute scheduling changes by a container moving company - including repositioning errors and pickup/delivery date shifts - while being charged fees for changing dates themselves but receiving no refund when the company changed dates on them. This asymmetric change-fee practice made planning the move unreliable and ultimately drove the customer to a different mover.

A customer signed a binding proposal for kitchen countertops at a specific measurement and price, but the installing subcontractor returned a measurement 33 percent larger, inflating the cost by roughly $2,150. The gap between retailer-provided estimates and installer-verified measurements exposes customers to unexpected price increases after signing.

A customer reports that PODS ruined newly installed sod on their driveway during service, and despite multiple attempts to reach the company for resolution, no one has called back. This reflects a recurring pattern of unresponsive follow-through on property-damage claims after a move.

A customer's rented storage POD was not watertight, allowing nearly two inches of standing water to accumulate inside after a rain shower, forcing them to tarp the unit and run a dehumidifier to protect their furniture and belongings before pickup was possible. Delivery and pickup crew service was rated highly, but the unit's physical quality was not.

A payroll and HCM company posted a paid job to automate manual workers' compensation policy lookups on the New Jersey Compensation Rating & Inspection Bureau website. This reflects a recurring, tedious compliance task that currently has no API and requires browser automation to eliminate manual lookups.

Merchants report being unable to fully access the underlying control panel or HTML needed for SEO and custom updates on Shopify, and frame this alongside the broader frustration of perpetual SaaS fees without ever owning the underlying software. This limits how much technical control store owners have over their own storefront.

Users with a clear mental image struggle to translate it into an effective prompt for image generators like Midjourney, DALL-E, or Gemini, since each model responds differently to the same wording. The friction spans initial prompt-writing, refining a rough prompt, and reverse-engineering a prompt from a reference image.

A long-distance mover's container arrived four business days after the scheduled date, with only a single delay notification and no follow-up communication even when the customer's own representative could not say where the shipment was. The lack of proactive status updates forced the customer to repurchase items and disrupted their moving timeline.

A customer spent over three hours on the phone across multiple calls trying to get a storage container picked up after two reschedules, with front-line phone agents stating a manager or supervisor was never available to speak with. This reflects a structural gap in escalation options when scheduling commitments are repeatedly broken.

Users who want to track what they watch and read across films, TV, and books find existing single-purpose apps (e.g. Letterboxd, Goodreads) fragmented, ad-cluttered, and clunky to use, forcing many back to generic notes apps. The problem matters because there is no simple, unified, low-friction home for cross-media tracking and discovery.

A credit card customer facing financial hardship was told to contact the credit card department for help, but representatives repeated a fixed script and could not explain the underlying issue when pressed. A complaint was later opened on their behalf without full context of the hardship.

A credit card recently migrated between issuers was closed shortly after an annual fee was charged, with no prior warning or credit issues, suggesting a backend data-migration error. This illustrates the risk of account disruption when card portfolios move between issuers without adequate data reconciliation.

Travelers wanting to explore where they can afford to go must manually compare flights, hotels, and total costs across many possible destinations to find options that fit a fixed budget. A budget-first search flips the usual flow, ranking destinations by estimated total cost and remaining budget instead of starting from a chosen place.

Home users who switch ISPs or routers often find that consumer routers, across multiple brands, do not offer a simple way to map a local IP address to a custom hostname. Existing options are either absent, undocumented, or require heavier tools like DDNS or custom firmware rather than a plain local DNS record editor.

A user cancelled their Canva subscription days before the renewal date but was still auto-charged, highlighting a lack of self-serve, non-auto-renewing payment options for subscription services.

A founder describes their landing page receiving 4.5 million views after an investor shared a screenshot, yet the surge converted only a single paying subscriber. It highlights the gap between attention and virality versus actual monetized conversion for early-stage products.

Developers who expose an MCP server have no way to see the full agent session behind incoming tool calls -- what the user originally asked, what the agent reasoned, or where it got stuck -- because that conversation lives entirely inside the end user's AI client. This makes it nearly impossible to know which use cases are popular or where users are frustrated.