Explore Problems

People running self-hosted services want to know immediately when something breaks overnight rather than discovering it the next morning, but existing monitoring options are seen as either too heavyweight or not worth paying for. The result is a preference for quick, ad-hoc scripts over adopting a dedicated monitoring product.

A user describes Asana as overly complex for simple projects, notes that important features like timelines and custom rules are locked behind premium plans, and finds the notification system becomes cluttered without manual tuning. This reflects a common tension in project management tools between power-user features and simple-use-case usability.

An indie maker describes being frustrated by paying recurring subscription fees for screen-recording/demo-video tools that lacked the draw-on-screen annotation features he needed, prompting him to build and open-source an alternative. Highlights a gap around affordability and specific editing features in the demo-video tool space.

Developers building B2C financial-aggregation products face a near-duopoly (Plaid and MX) for bank account data access, with multi-week waits for production API approval and no way to reach support until a paid "production access" tier is granted -- only a sales team that cannot resolve technical blockers. Building an alternative or working around this is a structural pain point for any team building on top of US bank data.

Notion users want to write and own their notes in an open, portable format such as markdown instead of being locked into Notion's proprietary storage, especially as that data may be used to train Notion's AI. This raises data ownership and privacy concerns for users who prefer tools like Obsidian.

A PODS customer describes a multi-container move where a driver blocked access to a container awaiting pickup, and support then failed to reschedule properly due to insurance and liability constraints. The breakdown in logistics coordination between deliveries cost the customer hours of unresolved support calls.

A Slack user describes performance continuously dropping over several months: the app has become glitchy and unreliable, files take much longer to load, messages don't sync until a channel is opened, and notifications arrive late.

Zendesk only groups tickets from a matching requester identity, so when the same customer emails once from a personal address and later from a work address about the same issue, the tickets stay unlinked. Agents must manually notice matching subject lines to catch the duplication, adding avoidable support workload.

A homeowner requested cancellation of an Allstate policy after discovering coverage misrepresentation, but the insurer created duplicate policies and continued billing through the mortgage escrow account despite internally confirming the cancellation request. Conflicting information from support reps left the customer unable to get the erroneous charges corrected across multiple contacts.

When a lender switched the payment processor handling a customer's installment loan mid-contract, the customer was charged again after the loan was already paid off in full. Support could not produce proof that a promised refund had actually posted, leaving the customer to independently verify with their own bank.

Insurers cancel policies citing overall claim activity even when the claims in question were denied or paid zero dollars. Consumers have no clear way to get these non-paying claims removed from shared industry databases like CLUE before they affect future coverage.

Finding a specific message from months ago is hard when the exact wording is not remembered. During incidents, thread notifications pile up fast as many customers report the same issue and many people reply at once. This affects support and operations teams working in chat.

Muslims who have missed prayers over time need to calculate their outstanding "kaza" debt and work through it with a realistic daily plan, but most existing prayer apps focus on prayer times and reminders rather than debt tracking. This creates demand for a calm, structured way to quantify and chip away at a backlog of missed religious obligations.

Support teams find that most adjacent capabilities in their helpdesk suite are sold as separately priced modules, so effective cost per agent climbs quickly as the team adopts more of the platform. Buyers report no dissatisfaction with the core product itself, only with how quickly the total bill compounds. The pattern makes budgeting unpredictable as headcount and tooling needs grow.

Product teams see users vanish without complaint, with two thirds leaving at the same step. Without feedback, they cannot tell why users abandon, so the cause of churn stays hidden.

Parents currently must either ban AI tools outright or let children use them without guidance, with no structured middle path. This creates a gap for a mastery-based way to teach kids (5+) how AI works and how to use it safely, while keeping parents in control.

A customer's order for two items was never delivered because it was returned to the merchant mid-shipment, yet no refund was issued automatically and the customer had to request one directly. This points to a gap in retailer fulfillment systems where a shipment's return-to-sender status does not reliably trigger a refund, leaving customers to chase money back themselves.

Developers reviewing large code changes produced by coding agents face walls of unstructured file diffs that are hard to parse and give feedback on. Existing terminal-based review tools address pieces of this but lack a narrated, chaptered walkthrough that breaks a large change into a guided, commentable tour.

A homeowner filing a covered claim found Allstate's internal repair estimate came in at roughly a third of the bid from an Allstate-preferred contractor, and was told to find a contractor matching the lower number themselves. This reflects a broader pattern where insurer estimates diverge sharply from real contractor pricing, shifting the cost gap onto policyholders.

Small business owners researching how competing accounts structure their content resort to scrolling feeds and screenshotting individual posts, then reassembling the picture by hand. The raw material is public but arrives in a form that resists comparison across accounts, posting cadence, or collaboration partners. The manual pass costs hours per planning cycle and has to be repeated whenever strategy is revisited.