The Pain Points Project← Back to Stream
About the project

Real problems. Worth solving.

Builders need ideas. Operators have headaches. The Pain Points Project is a public database that bridges the two.

What this is

A central place for people to log problems that have. This could be anything from broken workflows, missing features, manual loops, and "why is this still a thing?" annoyances that would have a measurable payoff if someone built a fix. We keep them in one searchable list so builders can find ideas worth their time, and the people stuck living with the friction can actually see it solved.We want to make the world a better place by helping to solve problems faster.

For builders & founders

Skip the "idea void." Browse verified frictions logged by people who actually face them. Every entry already has built-in demand.

For everyone else

Stop tolerating clunky tools. Log the thing that wastes your time once. Let the people who can fix it find it.

Looking for a co-founder?

Drop into our Matrix space. This is where builders can meet to talk through the problems they're seeing on the site and team up to fix them. Open chat, free, no commitment.

Open the project space ↗

What belongs here

Great fits

  • When you save a CSV from Excel, formatting metadata is lost — no easy way to keep it side-loaded.
  • Bookkeepers re-type the same invoice numbers into four separate systems every day.
  • There's no clean way to share a multi-step form's state via URL.
  • Pharmacy stock counts still rely on weekly manual audits because no system reconciles supplier feeds.

Not a fit

  • Personal life dilemmas ("my boyfriend never does the dishes").
  • Problems too broad to ever ship a solution to ("end world hunger").
  • Pure venting with no measurable cost or audience.
  • Feature requests aimed at a single specific product team.

The test: could a small team plausibly ship a fix in 6–12 months, and would real people notice the difference? If yes, it belongs here.

How it works

STEP 01

Log it

Describe the friction, tag the industry, optionally flag what kind of expertise it would take and add any other comments.

STEP 02

We review

A human checks each submission so the database stays high-signal - no spam, no rants.

STEP 03

Builders find it

Approved entries appear in the public stream where anyone scouting for ideas can pick one up.

Ready to dig in?

Browse the database for problems worth solving, or share one of your own.

Browse the databaseLog a pain point →