Join at the $47/mo founding price →

Guide LibraryAI · Complete guide

The Archive Audit: Turn Recorded Calls Into Pricing, Objections, and Proof

You have years of recorded sales and client calls you have never been able to use. This is the method for turning them into your real pricing, your actual objection list, and a case-study bank — without acting on a confident wrong answer.

Every company that sells a considered purchase is sitting on the same unused asset: years of recorded conversations. Discovery calls, quote reviews, kickoffs, check-ins. The recordings exist. Nobody can use them. They live in a vendor’s cloud behind a search box that only answers questions you already know to ask.

This is the method for turning that archive into three things you can act on: the price your own conversations have converged on, the objection your buyers actually raise (which is usually not the one you think), and a case-study bank drawn from work you already did.

It is not “point an AI at your transcripts.” That approach fails in a specific, dangerous way — and understanding that failure is most of the value here.

The Diagnosis

The Problem Isn’t Access. It’s That Wrong Answers Look Right.

You can already open your recording tool and search it. So why has nobody mined this?

Because every failure mode in this work returns a confident, plausible, wrong answer instead of an error. Nothing crashes. Nothing warns you. You get a number, it looks reasonable, and you make a decision on it.

The risk is not that you find nothing. The risk is that you find something convincing and wrong, and reprice on it.

Four ways this happens, all of them silent:

  1. 01
    The search cap that never tells you. Most conversation platforms cap a single query’s results — commonly around twenty — and return them with no cursor and no “there’s more” flag. Ask for a whole year and you get the cap back, whether that year holds twenty conversations or two thousand. The response looks complete because nothing says otherwise.
  2. 02
    The interface is not a counter. Scrolling a list and estimating gives you a number that feels earned. It is wrong. These interfaces lazy-load a few hundred items and stop. Only exhaustive, programmatic pagination is authoritative.
  3. 03
    Your archive contains other people’s prices. Recorded archives mix your own calls with webinars, courses and competitor content your team watched and recorded. Grep for dollar figures and you will find plenty — some of them are your competitors’ prices, presented to you as your own. In one measured archive, contamination was about 3% overall but roughly 14% of the pricing-relevant files, because that is exactly where someone had been studying other people’s offers.
  4. 04
    A summary cannot know what it was not given. Hand a language model a truncated export and it will summarize the truncation, fluently and without hedging. The model is not the weak link. The retrieval is.

The test that separates real from plausible

Ask anyone proposing to do this work one question: how will you know the extraction was complete? If the answer is “the API returned everything,” they have not hit the cap yet and do not know it exists.

The Method

Four Phases, Two Weeks

Phase 1 — Establish the true size

Before extracting anything, find out how much there is. This sounds trivial. It is the phase that catches everything.

The technique is adaptive window-splitting: query a date range; if the result comes back exactly at the cap, split the range in half and query both halves; repeat. A window is only believed when it returns fewer results than the cap — that is the sole available evidence that nothing was truncated.

Then a second-axis sweep. Date-splitting bottoms out at a single day, and a single day holding more than the cap stays truncated no matter how finely you cut dates. Partitioning on something independent — a title substring, a folder, a participant — slips underneath it and surfaces what dates could not reach.

80

what the naive sweep reported

1,038

what adaptive splitting found

13×

the undercount, on a real archive

The deliverable is an inventory report that states the count, the date range, the total runtime — and explicitly names which windows are floors rather than complete counts. An honest floor is worth more than a confident total.

Phase 2 — Extract into something you own

Transcripts move out of the vendor and into plain markdown on your infrastructure, with a documented schema: speaker attribution, summaries, action items, and a link back to the original.

Three properties matter, and they are all about trust rather than convenience:

Deterministic. Re-running produces byte-identical files. Same input, same bytes, any machine. A pull that produces different output on each run cannot be verified against itself.

Resumable. An interrupted run continues where it stopped instead of starting over. On an archive of a thousand conversations that is the difference between a coffee break and an afternoon.

Non-destructive. Nothing is overwritten in place. If a conversation changed upstream, the previous version is preserved before the new one lands.

Phase 3 — Separate your voice from everyone else’s

The contamination pass. Before any mining, split what your team said from what your team watched.

Only then does extraction happen: price points actually discussed, objection language ranked by frequency, the split between decision-friction and price-resistance, recurring named relationships, and commitments made and then dropped.

Every finding carries an evidence grade. A pattern that appears in one place is labelled as such. A pattern that replicates across two independent archives — different years, different tools — is the only kind strong enough to act on directly.

Phase 4 — Leave it working

A searchable portal over the archive, a sync tool that adds new conversations without destroying old notes, and a runbook so it can be re-run without the person who built it.

What It Finds

The Three Findings Worth the Engagement

Your real price. Not the price on your website — the number your own conversations keep circling. When the same figure tops the frequency count in two independently captured archives, from different years and different tools, that is not a hunch. That is your market telling you something you have not written down.

Your real objection. Most teams assume price resistance and optimize packaging. The frequency counts often say otherwise: very few conversations contain “too expensive,” while a great many contain “let me think about it.” Those are opposite problems. One is solved with packaging. The other is solved with a reason to decide now. Optimizing the wrong one is expensive and invisible.

Your case-study bank. The proof you need for sales pages already exists in kickoff and delivery calls — the before-state, in the customer’s own words, that you would otherwise have to invent.

Say this before the report lands, not after

Findings from keyword frequency are leads, not verdicts. “How much” catches “how much time.” Anything acted on gets read in context first. A method that admits its own error bars is the only kind worth trusting with a pricing decision.

Before You Start

Three Things to Settle First

Do you have enough? Under roughly two hundred recorded conversations there is nothing to mine, and the honest answer is to skip this. Volume is the qualifying condition.

Who else is in the recordings? These are real conversations with real customers. Decisions about transcribing backlogged audio turn on where that audio may be sent, not on which service is most accurate. Confidentiality sets the constraint; accuracy picks from what’s left.

Was it lawfully recorded? Recording consent law varies by state and country. Confirm before touching the archive.

Find out what's actually in your archive

The scoping call is free and it is a real filter — if your archive is too small or too incomplete to produce findings, I will tell you on the call. The audit runs two weeks and starts with the inventory, so you learn the true size of what you have before anyone commits to mining it.

Put it into practice

This guide works best inside the architecture.

The free Creator Vault is the pre-wired system every guide on this site plugs into. Already have it? The next step is building yours live, with me.

Next guide

The Claude Tutorial: Cowork, Obsidian, Skills & the Full Ecosystem

A practical tour of the Claude ecosystem — Claude.ai, Claude Code, Cowork, skills, and MCP — and how knowledge workers actually use it daily.