What is Real Problem AI?

Real Problem AI is a curated directory of 200+ real problems worth building an AI startup around. Each problem is scored honestly on severity, AI feasibility, market signal, and competition gap. We're for builders looking for what to build, not for ethics debates about AI.

What is the difference between Real Problem AI and AI ethics or AI risks indexes?

Real Problem AI catalogues problems AI can solve — productive, commercial opportunities for builders. AI ethics indexes catalogue problems with AI itself (bias, environmental cost, copyright, consciousness). Different intent, different audience: founders and indie hackers vs researchers and policy folks.

What should I build with AI in 2026?

Look for problems with high severity (it costs people hours, sleep, or revenue every week), high AI feasibility (LLMs, vision or voice are great at this today), strong market signal (Reddit threads + willingness to pay), and a clear competition gap (incumbents miss the same obvious thing). Real Problem AI scores 200+ such problems for you on those four axes.

Where do Real Problem AI's startup ideas come from?

From three sources, scanned each cycle: 1) Reddit threads where people describe a real friction in their own words, 2) podcasts and talks of founders young builders trust (Nikhil Kamath, Aman Gupta, Ankur Warikoo, Raj Shamani, Andrej Karpathy, Greg Isenberg), and 3) a continuous 1,000+ source scan covering forums, app store reviews, regulator filings, and field interviews.

Is Real Problem AI free?

Yes. Browsing every problem, opening every score breakdown, raising your hand on a co-founder match, and the founder vault are all free. There is no paywall.

How is each problem scored?

Four axes, each 1-10, weighted: Problem Severity (30%), AI Feasibility (25%), Market Signal (25%), Competition Gap (20%). Weighted average is the Opportunity Score on each card. Only problems clearing 7.0+ make the live list.

Why do agency PMs still hand-write client status reports from Asana, Slack, and Harvest every Friday?

Agency account managers spend 3 to 5 hours every Friday assembling a client update by copy-pasting Asana task status, Slack threads, and Harvest hours into a Google Doc, because no tool joins all three with context.

Category: Marketing, Sales & CRM · Trend: Agents · Opportunity score: 7.8 / 10

What is the “Why do agency PMs still hand-write client status reports from Asana, Slack, and Harvest every Friday?” problem in 2026?

Who has this problem?

Account manager at a 10 to 50 person digital marketing agency.

Evidence this problem is real

“I literally spend my entire Friday afternoon copy pasting from Asana into a Google Doc and then rewriting it so the client does not see jira-speak.”

Sourced from r/agency threads on weekly client reporting workflows.

Existing players in this space

Status Hero — Team standup digest, not client-facing tone.
Range — Internal updates only, no Harvest/Asana joint pull.
Asana Status Updates — Single-tool view, no Slack or Harvest context.

What existing players are missing

An agent that connects Asana plus Slack plus Harvest plus Figma, drafts a client-tone weekly update with screenshots, and lets the AM approve in 15 minutes instead of 4 hours.

How Real Problem AI scores this opportunity

Aggregate score: 7.8 / 10. Four-axis rubric:

Problem severity: 7 / 10
AI feasibility today: 9 / 10
Market signal: 7 / 10
Competition gap: 8 / 10

How to build a solution: stack hints

Asana API
Slack API
Harvest API
Claude Opus for tone-shifted summarization

Why this problem is archived

Capped at 100 per editorial policy; lower-score entries rotate to archive.