How to Turn Project Overruns Into Better Pricing Rules for Your Next Client With NotebookLM

The problem and who this is for

This workflow is for freelancers and consultants who finish a project, know it went over, and then move on without extracting the lesson. That is how the same pricing mistake repeats. The overrun itself is not the only cost. The hidden cost is failing to turn that experience into a better quoting rule for the next client.

NotebookLM is a strong fit here because a useful postmortem usually depends on several real sources: the original scope, time logs, revision notes, and the email trail around delays or add-on requests.

Prerequisites

You need the original proposal or scope summary, your time logs or rough effort notes, and at least one source that shows where the project expanded. That could be a revision log, email thread, meeting recap, or internal note.

You do not need perfect data. Even a rough but honest source set is enough to improve your next quote.

How to gather the source material

1. Export the original proposal or scope as PDF.
2. Export your time log or effort summary as CSV, spreadsheet, or plain text.
3. Pull the emails or notes that show where the project grew, stalled, or got revised.
4. If the material is scattered, create one short note that summarizes the project outcome in plain language.
5. Keep the files organized. Name them by function, not by date alone.

The workflow

1. Create a new notebook in NotebookLM for the completed project.
2. Upload the original scope, time log, and revision or email evidence.
3. Ask for a first summary of where the project expanded beyond the quote.
4. Ask for a postmortem memo that separates root causes from symptoms.
5. Ask for reusable pricing rules and better scope language for future proposals.
6. Save the best rules into your proposal template, pricing checklist, or internal quote guide before you forget.

Primary tool instructions: NotebookLM

1. Use a fresh notebook for each postmortem.
2. Upload the original scope first so the comparison has a baseline.
3. Add the time log and the evidence of overrun after that.
4. Ask for a briefing document or report-style memo rather than a loose summary.
5. Export or copy the final rules into the documents you actually use for quoting.

Alternative tool instructions

ChatGPT

ChatGPT is a good fallback if you prefer a faster one-chat review. Upload the files or paste the key excerpts, then use the fallback prompt.

Gemini

Gemini works well when the time log and notes already live in Google Drive. Attach the files and use the same structure.

Claude

Claude is useful when the project notes are long and you want a well-written narrative postmortem before distilling it into rules.

Copy and paste prompt blocks

Primary prompt for NotebookLM

{
  "role": "pricing-postmortem-analyst",
  "goal": "Turn project records into pricing and scope rules for future proposals.",
  "inputs": {
    "time_logs": "Use uploaded spreadsheet or notes.",
    "revision_history": "Use uploaded notes or email summaries.",
    "project_scope": "Use the original scope or proposal.",
    "project_outcome_notes": "Optional"
  },
  "instructions": [
    "Identify where time overran the original expectation.",
    "Link overruns to specific causes such as weak scope, extra revisions, approval delays, or missing client responsibilities.",
    "Draft a postmortem memo with lessons for pricing, exclusions, revision limits, and project setup.",
    "End with practical rules I can reuse in future proposals."
  ],
  "output_format": {
    "sections": [
      "Where The Project Expanded",
      "Why It Expanded",
      "What The Original Quote Missed",
      "Rules To Add Next Time",
      "Suggested Scope Language"
    ]
  }
}

Fallback prompt for ChatGPT, Gemini, or Claude

{
  "role": "project-overrun-reviewer",
  "goal": "Review one finished project and extract better pricing rules for future work.",
  "inputs": {
    "project_summary": "Paste the original scope and what actually happened.",
    "time_or_revision_notes": "Paste the biggest overruns.",
    "goal": "Create reusable pricing and scope rules."
  },
  "instructions": [
    "Focus on reusable lessons, not blame.",
    "Write concrete rules I can paste into future proposals."
  ],
  "output_format": {
    "sections": [
      "Overrun Causes",
      "Reusable Rules",
      "Proposal Language To Tighten"
    ]
  }
}

Quality checks

• The postmortem should tie overruns to evidence, not vague feelings.
• The output should end with reusable rules, not just commentary.
• At least one pricing rule and one scope-language improvement should come out of the review.
• The rules should be specific enough to reuse in the next quote.

Common failure modes and fixes

The memo turns into blame

Ask the tool to focus on system causes and reusable rules, not on personality.

The project records are incomplete

Use the sources you have and label uncertain conclusions as tentative.

The output is too abstract

Tell the tool to write proposal-ready rules you can paste into future quotes.

You never apply the lessons

Add the final rules to your quote template the same day. A postmortem that stays in a notebook changes nothing.

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/16262519 (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 source support, note behavior, and file-upload support in the fallback tools before updating this workflow.