Turn scattered customer signal into one prioritized spec

As a founder you're the highest-bandwidth sensor in the company — you hear it on calls, in Slack, in the churn note, in the investor's offhand comment. The problem isn't a lack of signal; it's that the signal is scattered across a dozen surfaces and lives mostly in your head. This flow collects it in one place, finds where it concentrates, and turns the densest cluster into a spec the team can act on — so a real pattern beats whatever you happened to hear last.

The input

Whatever you've collected, in any mix:

• A sales or customer call summary
• A couple of Slack threads
• A churn or cancellation email
• Your own running notes

No format requirements. The messier the pile, the more this helps.

The flow

1. Dump it all into the Evidence Board. Open the Evidence tab and paste each source. Each becomes an evidence item with its quote, type, and origin preserved — call vs. Slack vs. email — so you keep track of where things came from.

2. Cluster to see where the signal concentrates. Generate clusters. The point isn't to organize neatly — it's to see which problem shows up across the most independent sources. Three different customers hitting the same wall outranks one loud complaint.

3. Rank by evidence weight. The cluster with the heaviest, most varied, most recent evidence is your candidate. This is the founder's edge made explicit: prioritizing by where reality concentrates, not by recency or volume.

4. Synthesize the top cluster into a spec. Select its items and click Synthesize Intent. You get a spec anchored to specific quotes from specific sources — defensible to the team, the board, and future-you.

The output

One artifact out of a dozen fragments:

• A single prioritized spec, not a backlog of half-thoughts
• Ranked by evidence concentration, so the loudest voice doesn't win by default
• Sources preserved, so "why this?" has a real answer
• Out of your head and into the workspace, where the team can act without a meeting

Why this beats a founder backlog doc

A founder backlog is a list of everything you've ever noticed, in the order you noticed it. It has no notion of weight — the one-off and the recurring crisis sit at the same indent. Clustering the actual evidence surfaces the pattern instead of the recency, so the team builds against where the signal piles up, not against what you remembered this morning.

Try it yourself

1. Collect 5–10 recent bits of customer signal from wherever they live
2. Open Pathmode → product → Evidence tab and paste each one
3. Generate clusters and find the one spanning the most sources
4. Select it and click Synthesize Intent

Related

• Use case: Convert a Slack thread into an evidence item
• Use case: Decide what the team builds next — without a roadmap meeting
• Playbook: Prioritizing Intents