Record eligible calls, create transcripts, use AI to extract specific moments, score each moment for buyer value and public safety, then let the founder restore context before anyone drafts or publishes. Treat calls as evidence, not finished copy.
The important word is extract. A call summary tells you what the meeting covered. A useful extraction finds the objection you answered, the tradeoff you explained, the customer phrase that exposed a problem, or the decision that shows how you think.
Leon Abboud calls this content mining. In his demonstration, AI reviews call transcripts for authority moments, founder stories, and human details. Each result keeps the source moment, why it matters, a public safe angle, and a suggested format.[1]
Why calls beat a blank content calendar
A technical founder may struggle to invent a post topic at 8:00 AM and still explain a difficult product decision perfectly at 2:00 PM. The expertise is present. The writing prompt is artificial.
Calls contain pressure and context. A prospect asks why your implementation takes longer than a competitor's. A customer explains the point where its old workflow broke. An engineer challenges a roadmap choice. The founder has to answer with enough precision for another person to act.
That moment is stronger raw material than "five trends in AI" because it came from a real decision. It also comes with boundaries. Some calls contain confidential roadmaps, personal data, pricing, names, or customer results you cannot publish. The workflow must identify useful moments and reject unsafe ones.
The seven step call to content workflow
1. Set the recording and use rules first
Write down which calls may be recorded, why you record them, who may access them, how long you retain them, which AI tools may process them, and what can reach public content. Check the law and your contracts in every place where you operate.
Consent is not the only possible legal basis in every jurisdiction, so do not copy a generic recording notice and assume the job is done. If your organization relies on consent under UK GDPR, the Information Commissioner's Office says the request must be specific and informed, use clear affirmative action, and leave an audit trail of who consented, when, how, and what they were told.[4]
- Remove personal names unless the person approved attribution.
- Remove company names unless the relationship is public and approved.
- Remove exact deal values, security details, health information, legal issues, credentials, and roadmap dates.
- Do not turn a private customer statement into a testimonial without permission.
- Keep rejected material out of the drafting system.
2. Capture transcripts in one controlled place
Your first version does not need custom software. Pick one eligible call, export its transcript, and store it beside the meeting date, call type, owner, and CRM record.
For teams using HubSpot, the current documentation says HubSpot can capture conversations with its notetaker or sync recordings and transcripts from connected conferencing tools. Supported transcripts can be attached to the associated CRM record.[2] The principle matters more than the tool. Preserve the link between the transcript and the business context.
Start with sales, customer, team, and investor or advisor calls. Do not process every meeting. Exclude calls with unclear recording rights, sensitive personal information, active disputes, protected product details, or no useful connection to a buyer problem.
3. Ask AI to extract moments, not summarize meetings
A summary compresses the call into topics and next steps. That is useful for the CRM. It is usually weak input for content.
Ask for moments instead. Leon's prompt separates three kinds.[1]
- Authority moments show expertise through a decision, diagnosis, explanation, or objection response.
- Story moments capture a mistake, lesson, changed belief, or founder experience.
- Human moments reveal a routine, interest, or preference that gives the founder a recognizable voice.
For buyer education, authority and story moments should carry most of the weight. Human details can help people recognize the founder, but they should not crowd out the problem the buyer came to solve.
Every extracted moment needs a direct source passage or timestamp. If the model cannot point to the source, the idea does not move forward.
4. Run the Call to Content Filter
AI will return more ideas than you should publish. Score each candidate from zero to two on five tests.
| Test | Zero | One | Two |
|---|---|---|---|
| Recurrence | One isolated comment | Similar issue appeared before | Repeated buyer question or objection |
| Decision weight | No effect on a decision | Helpful context | Can change a buying or operating decision |
| Proof | Opinion only | Experience or example | Verifiable method, artifact, or result |
| Public safety | Contains unsafe detail | Can be safely generalized | Clear for public use |
| Buyer utility | Interesting to peers | Useful to part of the market | Helps the target buyer act |
A score of eight to ten earns a content brief. Five to seven stays in the source bank until stronger evidence appears. Anything below five remains an internal note.
The safety test is a veto, not an average. A moment with private customer data does not become publishable because it scored well elsewhere.
5. Restore the context only the founder knows
The extracted line is a bookmark. It is not the full story.
In Leon's video, the report reminds him of a sales conversation. He then explains who the buyer was, what the buyer planned to do, why he disagreed, and what he would teach publicly. The useful content appears when he restores that context.[1]
- What was happening before this moment?
- What did the other person believe or ask?
- What did you decide or explain?
- Which evidence can we show?
- What must remain private?
Record the answers in a short evidence card. Keep the call ID and timestamp attached so an editor can return to the source.
6. Choose one primary asset
One call moment can support a post, article, video, sales email, or FAQ. Leon shows this range in his content mining report.[1] Do not produce every format at once.
| Source moment | Best first asset |
|---|---|
| Repeated question with a clear answer | Search focused article or FAQ |
| Misunderstood category or tradeoff | Founder video or detailed post |
| Objection that slows active deals | Sales enablement article or email |
| Product workflow that needs proof | Demonstration video |
| Strong founder lesson with a clear buyer link | Story led post or newsletter |
Write the detailed version first when the idea needs explanation or evidence. Short posts and clips can point back to that stable source.
Google's people first guidance asks creators to make it clear who produced content, how it was produced, and why it exists. Google also recommends accurate authorship information where readers expect it.[5] A call derived article should name the author, explain the method when it matters, and exist to solve the buyer's problem rather than fill a publishing quota.
7. Review accuracy before style
- Is this what I meant?
- Did we keep the important technical detail?
- Can every claim and example be shown or sourced?
- Did anything private survive the safety pass?
Only then should the editor improve the hook, structure, wording, and distribution format. Do not ask the founder to rewrite the draft. Ask for corrections to judgment, evidence, and boundaries. The production team should handle prose.
A reusable extraction prompt
Use this after you have permission to process the transcript and have removed material your AI provider should not receive.
You are reviewing one call transcript to find source material for founder content. Do not summarize the meeting. Extract only moments that can help a defined buyer understand a problem, make a decision, or see how the founder thinks. Classify each candidate as: 1. Authority: a diagnosis, decision, tradeoff, explanation, demonstration, or objection response. 2. Story: a mistake, lesson, changed belief, or founder experience with a useful consequence. 3. Human: a safe personal detail that helps readers recognize the founder. For each candidate, return: - exact source passage and timestamp - call type - buyer problem - why the moment matters - evidence available in the transcript - private details to remove or verify - public safe angle - best first format - two follow-up questions for the founder Do not invent facts, quotations, results, customer language, names, or context. Reject any candidate that depends on confidential information or cannot be traced to the transcript.
The prompt is deliberately strict. A shorter output with traceable moments is more useful than a long list of plausible topics.
Keep customer data out of casual AI workflows
A transcript may contain personal information, contracts, credentials, financial data, source code, or confidential product plans. Tool choice is part of the editorial process.
Review each provider's current data controls, retention, access, and contract terms before sending transcripts. OpenAI's API documentation says API data is not used to train its models unless the customer opts in. It also says default abuse monitoring logs may contain prompts and responses and can be retained for up to 30 days, with additional controls available to eligible customers.[3] That is one provider's documented policy, not blanket permission to upload any call.
Use the least data needed. Redact before processing. Restrict access. Set retention rules. Keep a record of which transcript, model, prompt, and output produced each idea.
For sensitive industries or regulated data, get legal and security review before building this workflow. A good content idea is not worth breaking a customer promise.
What should come from each call type?
Sales calls
Look for repeated objections, category confusion, decision criteria, comparisons, and the question the founder answered better than the website. Do not publish deal specific negotiation, the prospect's budget, private competitor comments, or the identity of an unannounced buyer.
Customer calls
Look for the words customers use to describe their old process, implementation friction, moments of understanding, and practical advice the founder gives repeatedly. A customer story needs permission and verification. An anonymous pattern may still be useful, but do not disguise one customer's result as a market trend.
Team calls
Look for technical tradeoffs, product principles, rejected options, quality standards, and a decision that changed after new evidence appeared. Remove employee performance discussions, access details, unreleased plans, and anything that would help an attacker.
Investor and advisor calls
Look for category explanations, market misconceptions, and concise answers to hard questions. Remove fundraising details, investor identities, private forecasts, and claims you cannot support publicly.
Four failures that produce generic content
Publishing the summary
"We discussed customer acquisition and product strategy" contains no decision, tension, or evidence. Go back to the transcript and find the exact moment where someone asked, challenged, chose, or changed their mind.
Letting the model complete the story
A plausible sentence can still be false. Keep source passages attached to the draft. Mark every added fact for verification. If the founder cannot confirm it and no source supports it, delete it.
Starting with the format
"We need five LinkedIn posts" encourages the system to stretch weak material. Start with one strong moment, decide what the buyer needs, then choose the format.
Removing all the technical detail
Technical founders earn trust through constraints and tradeoffs. If editing reduces a real model evaluation, protocol choice, migration, or pricing decision to "we focused on quality," the useful part is gone.
A seven day setup for a small founder led team
- Write the boundary. List eligible calls, excluded information, approved tools, access rules, retention, and the public use approver.
- Connect one source. Choose one recording system and one controlled transcript location. Keep a meeting or CRM identifier.
- Process one call. Run the extraction prompt on one eligible transcript. Keep source timestamps. Do not automate publishing.
- Score the moments. Apply the Call to Content Filter. Reject unsafe material. Choose one idea that scores at least eight.
- Interview the founder. Use the five context questions. Collect proof that can be shown publicly.
- Produce one asset. Create the format that best solves the buyer problem. Cite external claims and link to a relevant next step.
- Review the system. Measure founder time, ideas accepted, safety rejections, time to first draft, and whether sales can use the asset.
The result should sound more like the founder
The point of call mining is to preserve judgment that already exists inside the company. AI finds and organizes the moments. The founder restores the meaning. Editors turn that meaning into buyer education. Nobody gets permission to invent the missing pieces.
Start with one call and one useful asset. For the wider operating model, read the Founder Funnel guide to founder led marketing. To connect the finished asset to commercial outcomes, use the Content to Close measurement guide.
Sources
- Leon Abboud, "Find UNLIMITED Content Ideas From Calls You’ve Already Had With AI (33m Views)", published 23 July 2026.
- HubSpot Knowledge Base, "Sync conversation transcripts into HubSpot", updated 4 September 2026.
- OpenAI Developers, "Data controls in the OpenAI platform".
- Information Commissioner's Office, "How should we obtain, record and manage consent?".
- Google Search Central, "Creating helpful, reliable, people-first content".
