Code is an expensive way to discover that a problem was only interesting in theory. Before opening an editor, I look for evidence that already exists in the world.

A repeated workaround

One workaround can be personal taste. A repeated workaround is a pattern. Look for copied templates, private spreadsheets, calendar reminders, and awkward chains of messages that people keep rebuilding.

An unprompted complaint

The strongest language appears when no one is pitching a solution. Support forums, community threads, search queries, and interview stories reveal how people naturally describe the friction.

A meaningful commitment

Attention is cheap. A useful signal costs something: time for a second conversation, access to a real document, an introduction to a colleague, a deposit, or a return visit without a reminder.

Before code
  1. Find the workaround.
  2. Capture the exact words.
  3. Ask for one meaningful next action.

You do not need certainty. You need enough evidence to make the next investment honest.