The recap that gets a reply
- What we heard, in their words
- Where the problem actually sits
- What we would need to confirm
- One next step, not three
Your sales call, written up and ready to send.
A free Claude skill. It reads the transcript, writes the recap or the full scope, and marks every claim it cannot trace back to something that was actually said.
- Free, nothing to sign up for
- Runs inside your own Claude account
- Your transcripts stay yours
Northfield Supply - Discovery Summary - 14 Mar 2026.html
Discovery summary
Northfield Supply
Forty five inbound leads a month, two closed. The handoff between the form and the first call is unowned.
01What we heard
We just send them a calendar link and hope. Honestly nobody owns it after the form.J. Reyes, 06:40
02Scope of work
| Workstream | Where it came from | Weeks | Owner |
|---|---|---|---|
| Pre call qualification | They asked | 1 to 2 | Us |
| First response inside an hour | We propose | 2 to 3 | Shared |
| Pipeline reporting | We are guessing | 4 | Us |
Open with you
- Who signs this off, and were they on the call?
- What is configured in HubSpot today?
- Is there a date behind the Q3 target?
Two choices. Four documents.
Who is going to read it, and how far it goes. The skill asks you both, every time. A client facing document and an internal one are not the same document with sections hidden, so it writes them separately.
Executive summary
Summary plus scope
Client facing
Written to be read by the person who was on the call, and by whoever they forward it to.
The recap, plus the work
- How you would approach it, and why this shape
- Workstreams, with what comes out of each
- Timeline, and which parts wait on them
- What is not included, and why
Internal
For the people who have to quote it, staff it and deliver it. Candid, and marked so it
cannot be sent by mistake.
The debrief
- The read, in three lines at the top
- Qualification, each part marked stated, implied or unknown
- Objections, verbatim, and whether they landed
- What nobody asked, as the agenda for call two
The debrief, plus the draft
- Draft scope, every item tagged by how sure you are
- Who it needs, and where the bench is thin
- What they signalled about budget, in their words
- The scope edges to hold when they push
What it will not do.
Most tools in this category fill the gaps. They read a call where nobody mentioned a budget and produce a document with a budget in it, because a document with a hole in it looks unfinished. This one leaves the hole and labels it.
Invent anything
No number, date, name, job title or quote that is not in the source. Every claim traces back to a line in the transcript, and the internal version prints the ledger.
Quietly widen the scope
Every item is tagged. They asked for it, you are proposing it, or you are guessing. A guess is never written as committed work in something a client reads.
Decide what to charge
It reports what they said about budget and what the work implies about effort. The number is yours. If nobody said one, the section says so.
Anything it does not know comes out as an open question. A call summary with no open questions is either a transcript or a fiction.
It asks about you once, then stops asking.
Ten questions on the first run. Your company name, your website, your defaults, who documents go out from, and the one most people skip: what you do not sell. That last answer is what keeps a scope from drifting into work you would have to refuse.
- 01
It reads your site
Services, the words you use for them, how you deliver, how long your engagements run, and what you can prove. Your vocabulary ends up in the document instead of ours.
- 02
It shows you what it concluded, and waits
Every line comes with where it came from. You correct it before anything is saved. Nothing the site does not support goes in.
- 03
You can hand it your own look
Upload a brand guide, a page whose style you want matched, or just hex codes and font names. Documents come out in your colours and type instead of the packaged ones.
- 04
And your own writing rules
If you have an editorial or content style guide, it writes to yours rather than its own.
How it runs.
- 01
Give it the call
A transcript, an export from whatever records your calls, your own notes, or a filled questionnaire. It does not need a recording.
- 02
It reads twice
Once for what was said. Once for what was missing. The second read is where the open questions come from.
- 03
Pick who reads it and how far it goes
Client facing or internal. Summary, or summary plus scope. Ask for both and you get two files.
- 04
It checks itself before handing it over
Claims traced, arithmetic re-run, every gap either closed or visible, and a check that no internal material ended up in the client version.
- 05
One file
An HTML document that opens anywhere, prints clean, and loads nothing from the internet. Email it, print it, or save it as a PDF.
- 06
Present it from the same file
There is a Present button in the corner of every document. It turns the thing you are reading into a slideshow, built from its own sections, so there is no deck to keep in step with the document. Change one and the other changes.
- 07
Call two, and three
Give it the next transcript and the earlier document. It marks what got confirmed, what changed, and what is still open, rather than starting again.
Install it in about a minute.
A Claude skill is a folder. The download is that folder, zipped.
Most people
Claude.ai or the desktop app
- Download the zip. Do not unzip it.
- Open Settings, then Skills, in the Customize section.
- Upload the zip there.
- Paste a transcript and ask for a discovery summary.
Needs a Pro, Max, Team or Enterprise plan with code execution turned on. On a Mac, Safari expands downloads by default. If you end up with a folder instead of a zip, turn that setting off and download again.
If you work in a terminal
Claude Code
- Unzip it into
~/.claude/skills/ - Or into
.claude/skills/inside one project. - Start Claude Code and ask for a discovery summary.
Python 3 is used for the build step. Nothing else is installed.
Questions.
What exactly do I feed it?
A call transcript is the best input. An export from whatever tool records your
calls works, so do your own notes from the call, a filled intake questionnaire, or a chat
thread where the brief was discussed. The more exact the source, the more it can quote.
Where does my transcript go?
Into your Claude account, the same as anything else you paste there. The skill
is a set of instructions and a stylesheet. It has no server, sends nothing anywhere, and
the document it produces loads nothing from the internet.
Can I make it look like my agency, not yours?
Yes, and you should. Hand it your brand guide or your colours and fonts on the
first run and every document after that comes out in them. There is no branding of mine
anywhere in the skill or in what it produces.
Can I present it, or do I need to rebuild it as a deck?
There is a Present button in the bottom right of every document it produces.
It builds the slides out of the document's own sections when you press it, so there is no
export step and no second file drifting out of date. Arrow keys move through it, Escape
leaves, and printing always gives you the document rather than the slides.
Will it write the proposal for me?
It writes the scope, the workstreams, the timeline and what is excluded. It
will not price them. Pricing is a judgement about the client, your capacity and your
appetite for the work, and it does not have any of those.
Why is it free?
I built it for my own calls and used it for about a year. It is more useful to
me in a hundred agencies than sitting in my own folder. If it saves you the afternoon it
saved me, that is the whole trade.