Explore Problems

Teams needing daily view-count tracking for hundreds to thousands of their own public Facebook video and reel URLs cannot use the Graph API due to app approval and token restrictions. Workarounds like metadata scraping and headless browsers return stale or inaccurate counts and break down at scale due to bot detection and fragile page structures.

Groups sharing recurring or one-off date plans, a school calendar shared with hundreds of families, a sales kickoff agenda shared with dozens of colleagues, currently juggle that information across documents, spreadsheets, PDFs, and email threads with no dedicated, easy way to plan and share it. This launch post drew unusually high engagement for the resonance of the underlying pain.

Users save location-tagged reels (e.g., restaurant or travel recommendations) to themselves but rarely return to them because they are buried in a flat DM or bookmark list. The problem is retrieval and actionability of saved content, not the saving itself.

A developer needs to run a Python-trained neural network on an embedded controller with no Linux, limited CPU/memory, minimal runtime dependencies, and predictable real-time behavior, but existing frameworks like ONNX Runtime mostly target desktop or embedded-Linux environments. This points to a broader gap in tooling for generating standalone, dependency-light C code from trained models for bare-metal or RTOS embedded targets.

As coding agents increasingly write and review code alongside humans, traditional Git hosting platforms were not designed for agent-native workflows like agent-initiated PRs, in-agent code browsing, or agent access management. Developers need code hosting that treats agents as first-class collaborators rather than bolted-on API consumers.

A user reports Canva's mobile app stays hard to use even after watching multiple tutorials, with the on-screen keyboard obstructing the interface whenever text size is adjusted. The user also expresses frustration that the app marketed as free pushes toward paid features they cannot currently afford.

A customer filing an Allstate SquareTrade electronics warranty claim for an unfixable streaming device found the claims process confusing and slow, requiring the device be shipped away for evaluation and leaving the family without service for weeks.

Merchants needing B2B logic, ERP/PIM/POS integrations, international markets, and custom UX find Shopify is not a simple plug-and-play platform at that complexity tier, requiring a clear strategy and an implementation partner to get right. This creates a significant hidden services/expertise cost for merchants scaling beyond basic storefront needs.

Users of AI-powered work platforms report that AI-generated answers are only as reliable as the underlying data, and messy or inconsistent boards produce weak results. This reflects a structural limitation of AI features layered on top of unstructured or poorly maintained user data.

A utility customer found their bill listed jointly in her name and her son's name after a chaotic relocation, and once the resulting high balance was noticed, the utility refused to help correct the account. This highlights how utility billing systems can create account errors during life disruptions and offer limited recourse to fix them.

A user describes a communication or design tool as unusable outside of a traditional desk setup, highlighting that the product is built around people sitting at a computer screen. This points to a broader accessibility gap for workers who are mobile or not desk-bound but still need to collaborate.

A State Farm customer received a refund check from corporate that bounced, delaying a $2,100 refund. Attempts to reach corporate customer service during the week are automatically rerouted to an unresponsive local agent instead, leaving the customer with no path to escalate a billing error.

Users of helpdesk platforms like Freshdesk report that configuring automation features takes longer than expected and that advanced options are not intuitive to use. This creates friction when trying to set up more sophisticated workflows beyond basic automations.

A user reviewing helpdesk software reports the interface is convoluted, key functionality is hard to locate, and custom automation rules behave inconsistently. This usability and reliability gap makes day-to-day support operations harder than expected.

Users repeatedly identify QuickBooks Online's customer service as its weakest aspect, a friction point in an otherwise dominant accounting platform. This signals an opening for competitors or complementary support tools focused on responsive, accessible service.

A two-decade policyholder discovers that a previously included benefit (free windshield replacement) had silently required an opt-in checkbox he was unaware of, resulting in unexpected out-of-pocket costs. This illustrates how opaque policy terms and unexplained coverage changes erode long-term customer trust and drive churn.

A long-tenured policyholder living abroad describes five separate calls needed to obtain a correct letter of insurance experience, with the insurer repeatedly sending incomplete letters, misnaming the policyholder, or failing to send anything after promising to. This points to gaps in self-service document generation and international customer support.

A small-business Pipedrive user wants to use additional CRM features but finds their budget cannot cover the cost of upgrading to a higher plan. This reflects a broader affordability gap between CRM feature tiers and what budget-constrained small teams are able to pay.

Product managers and engineers without design backgrounds find it hard to describe what they want an interface to look like (e.g. "make it feel like Stripe") in terms an LLM can act on, and end up repeating the same style instructions across sessions. The author built a lightweight skill that captures and reuses these design preferences, but frames UI polish as a lower-priority concern compared to features and bugs.

Creators who release music or games receive batches of redemption codes from labels or distributors and must manually hand them out to fans, reviewers, and curators using spreadsheets or email threads. This ad hoc process makes it easy to accidentally give the same code to multiple people, lose track of which codes have been claimed or failed, and lets bots drain codes without protection.