Data Extraction
Qpoint wanted to learn from its sales calls, but they existed only as recordings and transcripts that nobody could compare side by side.
Calls now flow from the meeting recorder through Claude into structured records. The first run listed 79 transcripts and turned one demo call into scored themes, pains and requests.
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The tool fetches meetings from the recorder and keeps only calls with outside prospects.
Transcripts come in on their own · came from Mark Parson
- 2
Claude reads a transcript and writes down interest, themes, pains and requests.
One call becomes a record · came from Mark Parson
- Two weeks after closing, calls without a date got one from the recorder's details. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
The tool fetches meetings from the recorder and keeps only calls with outside prospects.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Claude reads a transcript and writes down interest, themes, pains and requests.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Built the first pipe from recordings to findings
Git authorship: the record names nobody, and the repo's first commit (2026-02-25) carrying this work is his.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 0 decisions · 8 key-change entries · 441 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c1 →