Proposal

Capture the client's requirements before scoping anything. Do not price
yet.

Record:

• Client and the project in one sentence
• The problem they want solved and the outcome they expect
• Deliverables they have asked for, explicitly
• Constraints — timeline, budget signal, must-haves, exclusions
• Open questions where the ask is still unclear

If this comes from a discovery call, pull from those notes. If
requirements are ambiguous, list the questions for the operator rather
than guessing.

Save the requirements as a task note with task_notes_add. The next step
— Scope & Pricing — reads this note.

Read the task notes with task_notes_list — the note from the
Requirements step contains the client's needs, deliverables, and
constraints. Work from it.

Define scope and pricing. What good looks like:

• A scoped list of deliverables, each with what is and is not included
• Timeline or phases
• Pricing for each deliverable or a clear total, with the model
  (fixed, retainer, hourly) stated
• Explicit exclusions, so scope creep has a boundary
• Assumptions the price depends on

Save the scope and pricing as a task note with task_notes_add. Then ask
the operator to approve the scope and the numbers before any drafting.
This is a checkpoint — committing to a price is the judgment moment, so
the AI cannot advance until you approve.

Read the task notes with task_notes_list — the Scope & Pricing note
holds the approved numbers and deliverables, and the Requirements note
holds the client's context. Work from them.

Write the full proposal:

• A short summary that restates the client's problem and your outcome
• Scope and deliverables exactly as approved — no figure changes
• Timeline and pricing as approved
• Terms, assumptions, and exclusions
• A clear next step for the client to accept

Save the full proposal as a task note with task_notes_add. If it exceeds
10,000 characters, split across notes or store where the operator keeps
documents and record the location. The Client Review step reads this note.

Read the task notes with task_notes_list — the Draft note holds the
proposal and the Scope & Pricing note holds what was approved. Work
from them.

Check the proposal before it goes to the client:

• Every figure matches the approved pricing exactly
• Deliverables match the approved scope — nothing added or dropped
• The client's name, project, and details are correct
• No placeholder text, broken formatting, or internal note left in

Ask the operator to approve the proposal for sending to the client. This
is a checkpoint — sending to the client is irreversible, so the AI cannot
advance until you approve. If you reject, the workflow returns to Draft.

The proposal is approved and ready to send to the client. Confirm the
final proposal is saved as a task note, then close out the task.