# AI Client Proposals from Discovery Notes: Keep Scope and Assumptions Clear

Authored ToolFlowKit practice material. These records are teaching examples, not customer data, current vendor offers, or measured software results.

## What should the proposal retain from the meeting transcript?

The source is meeting-transcript-practice.md, whose T-prefixed IDs differ from project-notes-example.md and its N-prefixed IDs. Do not mix the Friday condition into the N-note project, which has no agreed draft due date. The sample is a proposal outline rather than a legal contract; pricing and binding terms must come from your own authorized business process.

| Proposal section | Practice wording | Transcript evidence |
| --- | --- | --- |
| Initial deliverable | One-page onboarding checklist covering account setup and support contact. | T01, T07 |
| Draft timing | Maya can draft by Friday if access returns Wednesday; confirm calendar dates. | T02 |
| Client decision | Please identify the person who approves the final version. | T08 |
| Optional work | A welcome video can be discussed separately; it is outside the initial scope. | T05 |

Guide: https://toolflowkit.com/guides/client-proposal-scope

License: CC0 1.0.