Explore Problems

Developers building toolchains in Zig have no performant spec-compliant JavaScript parser available as a native library, forcing them to use slower Node.js bindings or reimplement parsing. This limits the Zig ecosystem's ability to compete with Rust-based tooling like Oxc.

People doing repetitive research or content-assembly tasks across many web pages, screenshots, and files have to redo the same manual sequence of steps each time, since browsers offer no built-in way to capture and rerun a multi-step workflow. This creates recurring time cost for tasks that follow a repeatable pattern.

A customer confirmed in writing via chat that a phone upgrade would involve no trade-in and no bill changes, only to be told in a later chat that this was wrong and dismissed as a 'miscommunication' despite screenshots proving otherwise. This highlights a lack of accountability and record-keeping when customer service commitments made in one interaction are contradicted in the next.

In project and task management tools, marking a task complete does not guarantee that the decision it represented was actually finalized, communicated, or acted upon. This gap between task-completion status and decision-closure creates ambiguity in team workflows.

Consumers are subjected to illegal debt collection tactics including impersonation of attorneys or government officials, causing fear and coerced payments.

Writers and developers who want to publish formatted Markdown documents publicly must set up a CMS, static site generator, or deal with platform-specific formatting conversions. There is no frictionless Markdown-to-shareable-URL path without account registration or infrastructure. The gap is small but real for technical writers and documentation maintainers.

A customer traded in four phones when switching carriers but only three lines received the promised credits, with store staff wrongly accusing the customer of not returning a device until security footage proved otherwise. The dispute highlights how in-store trade-in processing errors can leave customers fighting for months to get promised credits honored.

When a retailer routes a product return through a third-party vendor for processing, customers report the vendor claiming the item was never received even after drop-off, leaving no independent proof of delivery to resolve the dispute. This reverse-logistics tracking gap leaves the customer without their refund or replacement.

A builder describes being frustrated by needing separate apps for prayer times, the Quran, and tasbih, none of them well-designed, and by the risk of an AI answering religious questions incorrectly. They built a single offline-capable app with a Quran/Sunnah-sourced assistant that cites its sources for every claim and explicitly is not a substitute for a scholar.

A kitchen using Asana for scheduling still can't go fully paperless because staff without smartphones, or uncomfortable using the app, need printed schedules anyway. Highlights an adoption gap between digital-first PM tools and frontline workforces in industries like food service.

A Gusto user reports experiencing long wait times for email responses when asking complex tax-related questions, expressing a desire for faster turnaround. Delayed support responses for time-sensitive tax matters add friction and uncertainty to payroll administration.

Small independent clothing brands running limited-quantity product drops need to handle listing, per-size stock tracking, payment collection, and shipping label purchase, currently requiring them to combine multiple disconnected tools or manual processes. A platform-fee model is proposed as an alternative to subscription software for this workflow.

A user expresses that Canva's growing emphasis on AI-generated content has diminished the app's appeal, longing for the more human-driven creative experience it used to offer. Reflects a broader sentiment of AI-fatigue among design-tool users.

A customer reports that their autopay setting is repeatedly reverted, causing a recurring $15 monthly surcharge for not paying via autopay. The pattern suggests a systemic account-settings reliability issue rather than a one-time billing error.

A customer who used their insurance for a small glass chip repair found the incident recorded as a formal claim, which they fear affects future premiums or risk profile. This makes customers wary of using coverage even for minor, clearly-covered repairs.

A customer requested full account cancellation a month before the next billing cycle but was told active lines would still be charged regardless, and phone/in-person escalation attempts led nowhere with contradictory phone numbers and disconnected transfers. This reflects a structural gap between customer-initiated cancellation requests and how billing systems actually process them.

A Canva user believed they had signed up for a free trial but was unexpectedly charged, and is requesting a refund.

Wells Fargo fraud department asked the customer to confirm unauthorized activity, but did not cancel the compromised card number as required. Creates ongoing fraud exposure after customers report incidents.

Consumers face harassment and credit damage from collectors attempting to collect debts that have already been paid in full.

Technical co-founders take less equity for idea-stage startups, then realize their network and execution ability far exceeds the original idea value.