Where did that quote go? Customer conversation notes that answer back

Six months after a decision, someone asks why we are building a feature. I know I heard the reason from three different customers. I just cannot find a single one of them.

That sentence is on the front page of Crossroad because it is the reason Crossroad exists. But the problem is not a Crossroad problem. It is a notes problem, and most of the fix has nothing to do with software. This post is the system I wish I had used for the first ten years of my career, and how the tool grew out of it.

Why the usual places lose the quote

Every founder and product person I know keeps customer conversations in one of four places. All four fail in the same way: they are easy to write to and nearly impossible to ask.

• A Notion or Google doc per call. Fine on the day. Six months later you have 40 documents titled “Call with Acme” and no memory of which one had the sentence about the API.
• Recordings and AI transcripts. Nobody rewatches a call. A transcript is 9,000 words, of which 40 matter, and the tool that made it does not know which 40.
• CRM notes. Written for the deal, not for the product. Three fragments, no context, and the account manager's paraphrase instead of the customer's words.
• Slack. The best quotes are pasted there in the moment and are gone by Friday.

The common thread: you filed by conversation, but you retrieve by question. “What did prospects say about integrations?” does not map to any document title.

Three rules that fix most of it

I have tried tagging systems, weekly synthesis rituals and a research repository with a five-figure price tag. The things that actually survived contact with a busy week are these three rules.

1. Keep the exact words, not your summary

When you write “customer wants better reporting”, you have already lost the evidence. What they said was “I export to Excel every Monday because your dashboard hides no-shows”. The second version tells you what to build. The first one tells you nothing, and in six months you will not remember which you meant.

So: quotes go in quotation marks, in the language they were said, unedited. Your interpretation is welcome, but it lives in a separate line and it is labelled as yours.

2. One place, and no filing on the way in

Capture has to cost nothing, or it stops happening on the first busy Tuesday. That means no form, no tags, no “which project is this” dropdown. Paste the sentence, or select it in the browser, or forward the email, and move on. Structure is something a system should add afterwards, not something a human should be asked for in the moment.

3. Retrieve by question, with the source attached

The test of a notes system is not whether you can find the document. It is whether you can ask “which accounts mentioned payouts?” and get the accounts, the quotes, and where each quote came from. An answer without the source is an opinion. An answer with the source is evidence you can put in a roadmap review and defend.

What “answers back” looks like

This is where the tool comes in. Crossroad is those three rules turned into a product: you capture text from anywhere (a sentence you select in the browser, a pasted transcript, a forwarded email, a screenshot of a review), it splits the text into individual insights and keeps the exact quote for each one, and then you ask questions in plain language and get answers with numbered citations that click through to the quote and the source.

Here is a real exchange from the demo workspace, which holds 12 sample sources from a fictional booking platform called Slotwise. I asked it whether customers complain about pricing. This is what came back, lightly reformatted:

There are no insights about customers complaining about pricing. No mentions of pricing being too high, unexpected charges, or pricing model dissatisfaction. The closest related topics are payment flow transparency (Studio Verde found the no-show fee setup confusing and wanted to preview charges before enabling them) and payout timing (Bella Hair Studio complained about weekly payouts straining cash flow). Neither is a complaint about Slotwise's own pricing.

Two things matter in that answer. It said no when the honest answer was no, instead of inventing a pricing complaint to be helpful. And every claim carried a citation, so the two “closest related topics” were one click away from the sentence a customer actually said.

Start this week, with or without a tool

If you never install anything, do this:

1. Make one document called “Heard” and never make a second one. Every quote goes there, newest at the top.
2. Each entry is four lines: who (and whether they are a customer, a prospect, or a colleague), the date, the exact quote in quotation marks, and one line of your read, marked as yours.
3. Once a week, read the last seven days out loud. It takes ten minutes and you will notice the second time someone says the same thing.

That gets you rules one and two. Rule three, asking questions across hundreds of entries and getting the source back, is the part a document cannot do. It is the part Crossroad does. Try it on the demo workspace before you decide whether you need it.