How to Turn a Discovery Call Recording Into a Fixed-Price Quote With NotebookLM

The problem and who this is for

This workflow is for freelancers and consultants who run a discovery call, leave feeling clear, and then lose that clarity when it is time to price the job. The usual failure pattern is simple. The call felt productive, but the quote gets built from memory, scattered notes, and vague optimism. That is how fixed-price work turns into underpriced work.

A better path is to treat the discovery call as source material. Pull the transcript into NotebookLM, keep the quote grounded in what the client actually said, and force yourself to separate confirmed scope from assumptions and open questions.

Prerequisites

You need a recorded call or a transcript, a NotebookLM account, and a simple quote template in Google Docs, Word, or plain text. You also need a pricing floor or at least a target range before you ask AI to help write the quote.

NotebookLM is the best fit here because the output depends on a real source conversation, not just your memory. It can work from uploaded source material and produce source-grounded summaries, reports, FAQs, and briefing-style outputs from that material. NotebookLM desktop also supports briefing documents and related report outputs, while the mobile app still has feature limits for many of those artifacts. See the Sources Checked section at the end of this article for the official help pages I checked.

How to capture and gather the source material

1. Record the discovery call in the meeting tool you already use, or use your phone's recorder if the call is happening by phone and the other party has agreed.
2. Export the transcript if your meeting tool provides one. This is the cleanest path.
3. If you only have audio, create a transcript first. Use the recorder's built-in transcription, your meeting platform's transcript export, or any normal transcription tool you already trust.
4. Clean the transcript before upload. Fix speaker names, remove obvious transcription errors, and spell out prices, deadlines, and numbers correctly.
5. Save the transcript as plain text, Google Doc, Word file, or PDF. Keep your own notes as a second source if they contain pricing context or delivery constraints that were not spoken clearly on the call.
6. If you have a standard quote template, upload that too. It gives NotebookLM a structure to follow.

The workflow

1. Create a new notebook for this prospect.
2. Upload the call transcript and your quote template. Add your own call notes if they contain useful constraints.
3. Ask NotebookLM to extract the client's goal, requested deliverables, likely decision criteria, deadlines, dependencies, and unknowns.
4. Save the best response as a note.
5. Ask for a briefing-style output that turns the call into a fixed-price quote outline with clear exclusions and assumptions.
6. Move the draft into your quote document and add your real number. Do not let AI choose your price unless you already supplied the pricing floor or range.
7. Read the quote once only as the client. If a reasonable person could mistake an assumption for an included deliverable, rewrite it.

Primary tool instructions: NotebookLM

Use NotebookLM on desktop for the strongest version of this workflow.

1. Open NotebookLM and create a new notebook for the prospect.
2. Upload the transcript and any related notes or template files.
3. In chat, ask for a source-grounded summary first. Do not jump straight to the final quote.
4. After the summary looks right, ask for a briefing document or report-style draft that separates confirmed scope, exclusions, assumptions, and open questions.
5. Export or copy the result into your working quote document.

This is usually better than a blank-chat workflow because it keeps the quote tied to the source call instead of drifting into generic sales copy.

Alternative tool instructions

ChatGPT

Use ChatGPT if you want file upload plus fast drafting in one chat. Upload the transcript or paste it in, then ask for a quote outline with explicit exclusions and open questions. If file upload is not available on your current plan, paste the cleaned transcript in sections.

Gemini

Gemini is a good fallback if you already keep the transcript in Google Docs, Drive, or another Google workflow. Upload or attach the file, then use the same structure as the fallback prompt below.

Claude

Claude works well when the transcript is long and you want careful language cleanup before the quote is finalized. Upload the transcript and ask for a concise, source-grounded quote skeleton. Review every assumption before sending.

Copy and paste prompt blocks

NotebookLM prompt

{
  "role": "quote-builder",
  "goal": "Turn the uploaded discovery-call materials into a fixed-price quote draft.",
  "inputs": {
    "ideal_client": "Describe the client type in one line.",
    "service_type": "Describe the service you plan to deliver.",
    "call_transcript": "Use the uploaded transcript or pasted notes.",
    "pricing_context": "Include your target fee range or pricing floor if you have one.",
    "known_constraints": "List timing, approvals, or dependencies already mentioned."
  },
  "instructions": [
    "Extract the client goal, requested deliverables, success criteria, deadlines, stakeholders, dependencies, and any unknowns.",
    "Separate what was explicitly requested from what was implied but not confirmed.",
    "Draft a quote with these sections: Project Summary, Deliverables, What Is Not Included, Assumptions, Client Responsibilities, Timeline, Price, and Next Step.",
    "Use plain business language.",
    "Flag any item that should stay open instead of pretending it is settled."
  ],
  "output_format": {
    "style": "brief, client-ready, specific",
    "sections": [
      "Project Summary",
      "Deliverables",
      "What Is Not Included",
      "Assumptions",
      "Client Responsibilities",
      "Timeline",
      "Price",
      "Next Step"
    ]
  }
}

Fallback prompt for ChatGPT, Gemini, or Claude

{
  "role": "scope-analyst",
  "goal": "Summarize a discovery call into a fixed-price quote outline without inventing scope.",
  "inputs": {
    "transcript_or_notes": "Paste the call transcript or cleaned notes.",
    "service_description": "What service are you offering?",
    "price_or_range": "Optional",
    "known_exclusions": "Optional"
  },
  "instructions": [
    "Use only the supplied material.",
    "List concrete deliverables and separate them from optional add-ons.",
    "Write a section called Open Questions for anything that still needs confirmation.",
    "Do not add features, pages, meetings, or revisions unless they were mentioned."
  ],
  "output_format": {
    "sections": [
      "Client Goal",
      "Recommended Scope",
      "Exclusions",
      "Assumptions",
      "Open Questions",
      "Suggested Price Positioning"
    ]
  }
}

Quality checks

• Every deliverable should connect back to something the client actually asked for.
• Every important assumption should be visible, not hidden.
• Exclusions should be concrete. Say what is not included.
• Deadlines should reflect dependencies. Do not promise a timeline that starts before assets or approvals arrive.
• Price should be your decision. Use AI for structure and clarity, not as an authority on your business economics.

Common failure modes and fixes

The quote sounds polished but still feels vague

Ask the tool to replace abstract phrases with deliverable language. For example, swap "support implementation" for "one kickoff call, one draft review, and one final delivery file."

The quote keeps growing

Add a rule in your prompt that anything not explicitly requested should move into Exclusions or Open Questions.

The transcript is messy

Clean names, dates, and numbers before upload. Small transcription errors often create big pricing errors.

The client mixed several project ideas into one call

Ask the tool to split the work into core scope, optional add-ons, and future-phase ideas before it drafts the quote.

Sources Checked

• https://support.google.com/notebooklm/answer/16206563 (accessed 2026-03-24)
• https://support.google.com/notebooklm/answer/16215270 (accessed 2026-03-24)
• https://support.google.com/notebooklm/answer/16296687 (accessed 2026-03-24)
• https://help.openai.com/en/articles/8555545-uploading-files-with-advanced-data-analysis-in-chatgpt (accessed 2026-03-24)
• https://support.google.com/gemini/answer/14903178 (accessed 2026-03-24)
• https://support.anthropic.com/en/articles/8241126-what-kinds-of-documents-can-i-upload-to-claude-ai (accessed 2026-03-24)

Quarterly Refresh Flag

Review by 2026-06-22. Recheck NotebookLM desktop versus mobile feature support, supported source types, and file-upload behavior in ChatGPT, Gemini, and Claude before updating this article.