Explore Problems

Sales teams sharing contracts and specs across email attachments, chat and cloud drives end up with conflicting versions and overwritten changes. This risks sending the wrong document to clients and lacks check-in/check-out control.

Coding agents rely on training data that predates renamed or removed APIs, so they confidently write outdated code. Developers also face a heavy research burden choosing safe, relevant skills and MCP servers from thousands of options.

Small businesses find a large CRM hard to learn, expensive, and dependent on extra setup. Customizing reports and workflows takes significant time.

A developer highlights that clipboard history and sync tools routinely capture and persist sensitive data such as API keys copied during normal workflows, requiring software to be built defensively assuming the clipboard is not a safe transit medium. Points to a structural, often-overlooked security exposure in everyday developer tooling.

Developers building with AI agents lack trustworthy, real-world benchmarks to compare how different models perform in different harnesses. Existing benchmarks (like TerminalBench) do not map to actual developer experience, leaving teams to guess at which model+harness combinations work best. The space is moving fast and existing leaderboards are fragmented.

Consumers who submit written requests to stop debt collector contact find their instructions routinely ignored, violating FDCPA protections. The enforcement gap places the burden on individuals to file complaints rather than on collectors to comply. Affected users face ongoing harassment with limited immediate legal relief.

No self-hosted family organizer covers tasks, shopping, meals, calendar, and budget without being SaaS or bloated.

Customer success and operations staff need custom data for customers but must file tickets and wait days for engineering. Direct database access risks exposing PII, so the bottleneck persists.

A Carvana buyer received a vehicle with severely degraded front tires unsafe to drive and undisclosed in the listing, failing a state safety inspection. The case illustrates a structural gap in condition disclosure and pre-delivery inspection for online, no-test-drive vehicle marketplaces.

A customer was charged a $649 non-return fee for a phone that AT&T's own system shows was returned on time, and months of follow-up calls have produced only a partial ($633) credit with no full resolution. This reflects a billing-adjustment process that fails to fully correct known errors even once acknowledged.

A Miro customer reports being moved to a different pricing plan multiple times without clear consent, requiring repeated disputes to reverse. This reflects a broader pattern of SaaS billing changes applied unilaterally, eroding trust and creating recurring support burden for affected customers.

A contractor using Angi's lead platform was charged $200 despite completing no jobs, and continued to be billed even after cancelling and receiving a confirmation number. Support routed calls in circles, and the company noted it isn't monitored by the Better Business Bureau, leaving the customer with no clear recourse.

A 12-year insurance customer was quoted a specific monthly discount over the phone for increasing their deductible, but the issued policy reflected a much smaller reduction. When they asked for the call recording to verify what was promised, the representative refused to escalate or provide access to a manager. This reflects a recurring gap where verbal phone quotes aren't reliably honored or auditable against what customers actually agreed to.

A customer who canceled Allstate home and auto policies after finding a cheaper rate elsewhere was sent to a collections agency, despite never missing a payment or being late. The practice appears to apply broadly whenever a customer switches carriers, punishing departure rather than reflecting any actual delinquency.

A Slack user reports that desktop notifications frequently fail to alert them to new messages, causing missed communications. Stepping away for even a day leaves them buried under a backlog with no efficient way to catch up, turning re-engagement into a tedious manual scroll rather than a guided summary.

A user warns that an app claiming to be Google Docs, distributed outside the official Google Play Store, is actually an AI-generated clone designed to steal user data. This points to a growing pattern of AI-generated counterfeit apps impersonating trusted brands to harvest data from unsuspecting users.

A consumer disputes an auto loan reported by Regional Acceptance because their credit report contains contradictory data: one section shows the account settled with a $0 balance while another lists a $5,700 charge-off. This kind of internally inconsistent furnisher reporting is a recurring credit-report accuracy problem.

A longtime customer's loyalty account, including military discount status and purchase history, was inadvertently deleted after a phone number update, and multiple support agents and departments were unable to locate or restore the data. This shows a structural weakness in customer support tooling: front-line staff lack the access or process to fix account/identity data corruption without escalating to IT, and no such escalation succeeded here.

Developers using Turborepo with Bun workspaces struggle to build a Docker image for a single app without copying the entire monorepo, because bun install fails to resolve workspace dependencies in isolation. Existing guidance like turbo prune --docker is designed around npm/pnpm and is not well documented for Bun.

A long-time Progressive customer's auto-renewal failed because their card was compromised by fraud, causing an 8-hour lapse in coverage; despite a clean payment history, the insurer would not honor the prior renewal rate and offered no exception for the fraud-caused gap. This reflects a broader rigid industry practice of penalizing any coverage lapse regardless of cause.