Explore Problems

A Shopify app user reports that an app advertised as a free 3-day trial began charging $1/month without clear upfront disclosure, prompting an immediate uninstall. The complaint reflects a recurring trust problem in app-store billing transparency around trial-to-paid conversions.

A developer scraping Shopee product data repeatedly hits a verify-traffic anti-bot error that redirects requests to a login wall, even when using ISP or premium residential IPs with Playwright. This reflects the broader difficulty of reliably bypassing e-commerce anti-scraping defenses, which persists despite paying for higher-quality proxy infrastructure.

A buyer newly purchased certified vehicle developed a check-engine fault within a week, caused by the dealer own service overfill, followed by a second failure with nine warning codes just after 30 days. Repeated corporate escalation attempts went unreturned, with the earliest inspection slot offered 17 days out.

A small company using a customer service platform notes that the product design assumes large teams of agents working around the clock, an assumption that does not hold for small businesses without dedicated or continuous support staff. This mismatch between platform design assumptions and small-team realities limits usability for smaller customer service operations.

A customer who switched auto insurance policies for a car purchase that fell through within the same day saw their rate jump $800 after reinstating the old policy, with no advance warning that mid-cycle changes would trigger a full rate recalculation. This reflects a structural gap in how insurers communicate the pricing consequences of policy changes before customers make them.

Companies knowledge about their customers lives fragmented across many disconnected documents and systems, so teams cannot easily answer relational questions like what is driving churn or why customers adopt or abandon a feature. A launch post (136 upvotes) addressing this drew strong engagement, though customer-intelligence tooling is an already competitive space.

Salesforce Sales Cloud has so many functions that new users cannot work in it without formal training. This slows adoption for sales teams.

Accountants using QuickBooks Online report recurring price increases and unnecessary interface or format changes that appear aimed at justifying higher fees. They feel the vendor undervalues accountant relationships. This erodes trust among the professionals who recommend the tool to clients.

An experienced engineer spent six months finding no customers because the problem was not validated up front. He struggles to find and validate small, specific problems with a cohort before building, and Reddit mining has not worked.

A small support team reports that adding a third agent account or a second departmental helpdesk requires upgrading to a paid subscription, regardless of ticket volume. The customer accepts that vendors must monetize but experiences the gate as arriving before the usage that would justify it. This matters because seat-and-workspace gating prices out teams whose structure, not their scale, crosses the threshold.

Event suppliers in the UK manage inquiries, proposals, contracts, and deposits either manually or through platforms that charge per-lead fees, adding cost and friction to closing bookings. This creates demand for booking software that turns an inquiry into a signed contract and deposit without lead-fee overhead.

Teams using separate apps for chat, planning documents, and task tracking lose the reasoning behind decisions when work moves between tools, since each handoff strips away the originating conversation. This fragmentation makes it hard to trace why a task exists or what discussion produced it.

A U-Haul customers local store refused to honor an online reservation that had explicitly declined optional insurance, refused to fulfill a prepaid supply order and substituted a costlier combination instead, and issued a vehicle with a broken window and low fuel. The complaint frames this as a franchise location disregarding corporate policy during a time-sensitive move, leaving the customer to pay more than agreed.

An AT&T customer was repeatedly told a new phone came at no cost and without a contract, only to discover after returning their old device that they were enrolled in 36 months of installment payments. Despite AT&T recording all calls, the company could not produce the original conversation and multiple representatives and a supervisor refused to correct the error.

Building and deploying backend systems on cloud platforms typically requires maintaining a traditional server or container layer separate from infrastructure-as-code definitions, adding operational overhead like keeping containers warm and babysitting servers. This split forces developers to reason about two systems instead of describing the whole system in one place.

Teams using AI-powered pull request review tools must send source code, diffs, and sometimes model API keys to external SaaS platforms, raising data exposure concerns for organizations with proprietary or regulated codebases. This creates demand for review tooling that runs entirely within the user's own environment.

People managing a work calendar, a personal calendar, and a separate task list must manually reconcile them each day to figure out what matters next, with no unified view or daily summary. This fragmentation persists across the many standalone calendar and task apps in common use.

A customer's online patio set order arrived missing a box of hardware, cushions, and wicker pieces, and Lowe's could only provide a non-working phone number for the drop-ship vendor to resolve it. This reflects a structural accountability gap between marketplace retailers and third-party fulfillment vendors when shipments are incomplete.

Podcast listeners often can't quickly locate the specific segments they care about without listening through entire episodes, making it hard to keep up with the volume of new content. An AI pipeline that transcribes, summarizes, and makes podcast content searchable addresses this time-consuming discovery problem.

A builder describes creating a tool that lets multiple local and cloud LLM agents run structured dialogues with shared memory from one app, and is polling whether people would pay for it. The underlying problem is that AI power users must juggle separate agent tools, API keys, and subscriptions with no unified interface or shared context.