Explore Problems

Customers who signed up for Asana's original Enterprise tier found some of those features later moved behind a new, higher-priced Enterprise tier. Users also feel Asana has prioritized AI investment over longstanding requests, such as the ability to assign a task to multiple people.

Independent hosts and small short-term-rental managers coordinate reservations, availability, housekeeping, maintenance, staff, and expenses across spreadsheets, chat threads, and disconnected tools. Hotel-grade property management systems are too heavy and costly for their size, leaving a gap between manual process and enterprise software. It matters because operational slippage in this segment directly costs bookings and reviews.

Freelancers and small teams lose track of client threads and forget to reply for days. Full CRMs are overkill and priced per seat, leaving a gap for lightweight follow-up tracking.

Hosts running vacation rentals answer the same guest questions and brief cleaners before every changeover, with no shared system connecting booking tools, guidebooks, and cleaning staff, leaving them uncertain whether a property is truly ready and without any record of what was done.

After downgrading from Canva Pro, a user found that designs created and paid for while subscribed became watermarked and undownloadable, effectively locking previously accessible content behind a renewed subscription. This reflects a broader pattern in subscription design tools of restricting access to content created under a prior paid tier.

Parents supporting adult "boomerang kids" who move back home often lack a clear, unemotional way to calculate the real monthly cost of support, agree on ground rules, and track whether money given is a gift or a loan. Without structure, these informal arrangements risk ambiguity and family conflict.

Users who need to split large Excel files (10k+ rows) into multiple files by a column value find VBA macros take hours to complete. This performance bottleneck affects finance and data teams doing routine bulk data segmentation, pushing them to seek faster automation methods.

Manufacturing maintenance technicians using SAP Plant Maintenances mobile front end frequently produce incomplete or incorrect data entries and failure-code captures, creating high manual effort to compile recurring reports. The poster is soliciting automation demos to address these recurring inefficiencies.

A developer in India had payment cards fail more than ten times when purchasing AI API credits and ended up building their own gateway. It points to payment friction for developers outside major card markets.

A customer paying for phone protection was told a damage claim was a pre-existing condition, and separately learned that promised insurance on an upgraded phone was never actually active despite being charged for it monthly. Follow-up calls produced dropped calls, conflicting information, and an accusation of fraud, pointing to a gap between sold protection plans and what is actually enrolled in AT&T's systems.

A used electric vehicle buyer experienced repeated charging failures and a sudden loss of power after purchase, and after multiple failed repair attempts the dealership declared the vehicle no longer its responsibility and refused further service. The case highlights gaps in how used-EV dealers diagnose and stand behind battery/charging issues, leaving buyers stranded with unresolved safety risks and no clear service path.

A Shopify merchant reports that Shopify Payments held their funds without a clear explanation, blocking withdrawals, charges, and transfers, while support repeatedly deferred resolution with no timeline. The merchant lost customers and sales during the freeze, illustrating the risk merchants face when a single payment processor controls access to their revenue.

Mid-size SaaS ops teams connect CRM, sales and chat tools, but handoffs between systems stay messy and break. When the builder leaves, nobody understands or dares to touch the automation, and failures are hard to diagnose.

Product managers tasked with modernizing legacy enterprise software (e.g., COBOL, PowerBuilder stacks) face declining customer bases, leadership visions detached from technical reality, and development teams lacking modern skills. This creates a structural mismatch between business modernization goals and the team's technical capacity to deliver them.

A customer with a paid six-year warranty on a water heater experienced a malfunction but made over ten calls without reaching anyone who could arrange a technician visit or explain the warranty process. The case shows how retail extended-warranty programs can lack a clear escalation path or contracted service providers, leaving customers unable to redeem paid coverage.

A customer ordered moving containers from PODS and was charged for units they returned, resulting in a documented overcharge of roughly $4,800. Despite four separate refund requests across several months, the correct refund has not been issued, exposing gaps in billing reconciliation and refund follow-through.

Enterprise HCM consultants and admins repeatedly face the same technical issues (payroll cluster mismatches, time evaluation quirks, integration replication errors) but the fixes exist only in individual experts' heads or scattered documents. This creates slow, inconsistent troubleshooting across SAP HCM, SuccessFactors, Workday, Oracle HCM, ADP, and Dayforce.

International students planning to study in Italy, particularly from India, lack a single clear source explaining what steps to take, in what order, and what mistakes to avoid. Instead the process is scattered across university sites, government portals, consulates, scholarship pages, forums, and paid consultants.

Project management software like Asana only delivers value when every team member consistently updates tasks and checks notifications; when adoption is inconsistent, boards become cluttered and effectively untracked. Teams managing many projects, subtasks, and due dates report feeling overwhelmed without clear usage rules.

Group trips often require juggling a separate notes document, a cost-splitting app, and a group chat thread, causing itinerary and payment details to get lost. Travelers experience recurring friction and disputes over shared expenses and disorganized planning.