Turn scattered customer signal into one prioritized spec

As a founder you are 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 is not a lack of signal. The signal is scattered across a dozen surfaces and lives mostly in your head, and none of it is written down in a form the team can check.

This flow collects it in one place, keeps each piece honest about its own trust state, and ends with a spec where every claim shows its basis.

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. Capture it all. Open the Evidence tab and paste each source into the composer. A short paste becomes one signal. A longer paste is extracted into rows you keep or drop. Everything you keep lands in the Inbox as Unreviewed, with its quote, type, and source preserved, so you always know whether it came from a call, Slack, or an email.

2. Write the spec you are considering. Start an intent for the problem you think is real. Name the objective, the outcomes you would have to see, the constraints, and the edge cases. These are the claims your evidence has to answer for.

3. Judge one signal at a time. In the Inbox, each signal gets Use as backing, Keep unreviewed, or Dismiss. There is no bulk shortcut, and that is the point: a founder hunch and three independent customers saying the same thing should not enter the record the same way.

4. Back the exact claim. Use as backing asks which claim the signal supports, then reviews and anchors it in one action stamped with your name and the time. Signals you keep unreviewed stay visible and stay unreviewed.

5. Read the spec back. Each claim shows Backed, Unreviewed, Assumption, or No evidence. The claims backed by several independent sources are the ones to build first. The claims sitting on one unreviewed note are the ones to go check.

The output

One artifact out of a dozen fragments:

• A single spec, not a backlog of half-thoughts
• A trust state on every claim, so the loudest voice does not win by default
• Sources preserved, so "why this?" has a real answer
• Your judgment recorded, with your name against the calls you made

Why this beats a founder backlog doc

A founder backlog is a list of everything you have ever noticed, in the order you noticed it. Every line reads the same whether it came from one offhand remark or from four customers in a row. Recording what you reviewed, what you left unreviewed, and what is still an assumption puts that difference on the page where the team can see it.

Try it yourself

1. Collect 5 to 10 recent bits of customer signal from wherever they live
2. Open Pathmode, choose a product, go to the Evidence tab, and paste each one
3. Start an intent for the problem you think they point at
4. Work the Inbox and use the strongest signals as backing for the exact claims they support

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