How Freelancers Can Use Claude Cowork to Turn a Sales Call Into a Personalized Proposal While Traveling

If Claude Cowork is new to you

Start with the Claude Cowork explainer page in the site's Tools menu before you run this workflow. Cowork runs in Claude Desktop and can work on the local files you choose to share. For related examples, see the Claude Cowork tool hub and the Anthropic Workflows series.

For phone-to-desktop assignment, the phone is the request surface and the desktop is the work surface. Update both apps, keep Claude Desktop open, keep your computer awake, and check the current phone assignment plan requirements before relying on the workflow while traveling.

Problem and who this is for

A good sales or discovery call happens while you are traveling. You want the proposal drafted before the context fades, but the real proposal assets live on your desktop: templates, boilerplate, pricing notes, and past examples.

This workflow is for freelancers and consultants who want proposal momentum without waiting until they are back at their desk.

Why Cowork fits this workflow

Cowork fits this workflow because the proposal assets usually live on your desktop: local templates, scope rules, pricing notes, approved examples, and proposal boundaries. Your phone can capture the call details while you are traveling, but Cowork can use the prepared desktop project to shape the draft.

Use Cowork when the proposal needs to follow local templates and reusable rules instead of becoming a generic draft from memory. Cowork can inspect the project folder, use proposal-rules.txt, apply the approved structure, and save the draft where you can review it later.

Why not normal Claude chat?

Normal Claude chat can draft a proposal from pasted call notes. That is fine for a quick one-off draft when you do not need local files.

Cowork is better when the proposal must use local templates, reusable pricing and scope rules, saved project context, and prior examples. It keeps the proposal workflow grounded in your desktop materials while the phone captures only the fresh call recap.

Prerequisites

• Claude Desktop with Cowork available on a paid Claude plan.
• A clearly scoped proposal project or folder on the desktop.
• Local templates, proposal rules, and approved example proposals.
• A call recap in voice or text.
• If assigning from phone: the current Claude mobile app, Claude Desktop open, your computer awake, internet on both devices, and current plan support for phone assignment.

Set up the proposal project before you travel

Set up the desktop project before the sales call. The travel workflow only works well if Cowork already has a scoped place to find templates, rules, and draft outputs.

Use this project structure:

templates/
proposal-rules.txt
example-proposals/
call-recaps/
draft-proposals/
archive/

Use templates for approved proposal structures. Use proposal-rules.txt for pricing rules, scope boundaries, assumptions, exclusions, confirmation language, and anything that must stay tentative. Use example-proposals for one or two approved examples that show style or structure. Use call-recaps for voice memo summaries or typed call notes. Use draft-proposals for new drafts. Move old drafts and outdated examples into archive.

Add project instructions so Cowork can reuse the same proposal rules:

{
  "project_name": "Proposal Drafting From Sales Calls",
  "project_purpose": "Use Claude Cowork to turn a sales or discovery call recap into a personalized proposal draft using approved local templates and proposal rules.",
  "project_instructions": [
    "Use the newest call recap unless I specify another file.",
    "Use templates as structure only, not as factual source material for the current client.",
    "Use proposal-rules.txt for pricing, assumptions, exclusions, confirmation language, and scope boundaries.",
    "Do not invent case studies, guarantees, delivery dates, client results, pricing, or commitments.",
    "Mark unclear scope, pricing, timeline, or dependencies as [TO CONFIRM].",
    "Create a proposal outline before drafting the full proposal.",
    "Save drafts only in draft-proposals and do not send anything."
  ],
  "file_naming": "proposal-draft-client-name-yyyy-mm-dd"
}

The project setup keeps the rules close to the files. Your call recap supplies the client-specific facts.

How to gather the source material

1. Immediately after the call, capture the client's goals, deliverables, timing, budget signals, and open questions in a short voice memo or typed recap.
2. Save the recap in call-recaps if you are at your desktop, or paste/dictate it into the phone assignment if you are traveling.
3. Keep your approved proposal templates in templates.
4. Put reusable pricing notes or scope rules into proposal-rules.txt.
5. If there are relevant past proposal examples, keep no more than one or two approved examples in example-proposals.
6. Exclude unrelated client material from the working project.

Numbered workflow steps

1) Send the proposal task while the call is still fresh

{
  "task": "Draft a personalized proposal from my call recap using my desktop templates",
  "input": {
    "call_recap": "DICTATE OR PASTE THE CLIENT GOALS, DELIVERABLES, TIMELINE, AND OPEN QUESTIONS",
    "proposal_project": "Proposal Drafting From Sales Calls",
    "template_folder": "templates",
    "proposal_rules_file": "proposal-rules.txt",
    "output_folder": "draft-proposals"
  },
  "rules": [
    "Use the Proposal Drafting From Sales Calls project instructions.",
    "Use the local template structure.",
    "Create a proposal outline before the full draft.",
    "Personalize the opening and scope to this client only.",
    "Keep unclear pricing, scope, timeline, or dependency items marked [TO CONFIRM].",
    "Do not invent case studies, guarantees, delivery dates, client results, pricing, or commitments.",
    "Save a draft only. Do not send anything."
  ],
  "output_format": {
    "type": "proposal_draft"
  }
}

If you are using phone assignment, send this from the mobile app only after the desktop app is open and the computer is awake. If you are already at your desk, run the same request directly in Claude Desktop.

2) Let Cowork build the outline and draft on the desktop side

Cowork can use your local templates and create the draft without requiring you to upload each file manually from your phone. The desktop project supplies the template, rules, and output folder.

3) Review and tighten when you reach your desk

Check the scope, assumptions, exclusions, pricing language, case studies, timeline, guarantees, dependencies, and next step. Then decide whether you want to shorten it, turn it into a statement of work, or rewrite sections before sending it yourself.

Future proposal runs

After the project is set up, the next call can use a shorter phone or desktop request:

Draft a personalized proposal from this sales call recap using my proposal project.

For a stricter reusable prompt, use this:

{
  "task": "Draft a personalized proposal from this sales call recap using my proposal project.",
  "rules": [
    "Use the Proposal Drafting From Sales Calls project instructions.",
    "Use local templates and proposal-rules.txt.",
    "Mark uncertain scope, price, timeline, and dependency details as [TO CONFIRM].",
    "Do not invent case studies, guarantees, or dates.",
    "Save a draft only."
  ]
}

Update proposal-rules.txt whenever your pricing, assumptions, exclusions, or approval language changes. Keep old drafts in archive so they do not accidentally shape a new client's proposal.

Tool-specific instructions

Claude Cowork with dispatch

• Read the Claude Cowork explainer page in the site's Tools menu if needed.
• General Cowork work depends on Claude Desktop and a paid plan with Cowork available.
• Phone assignment is separate. It depends on the current mobile app, current desktop app, desktop app open, computer awake, internet on both devices, and current plan support.
• Cowork can work against the local files you have already set up on the desktop, which is the main win for this workflow.
• Cowork should draft only. It should not send the proposal, promise terms, or finalize pricing without your review.

Quality checks

1. The draft clearly reflects this client's goals rather than generic boilerplate.
2. All uncertain scope, pricing, or timeline items stay marked for confirmation.
3. The output is saved in the expected local folder and the template files remain unchanged.
4. The proposal does not promise deliverables you never discussed.
5. Case studies, client results, guarantees, timelines, and pricing come from approved material or are marked [TO CONFIRM].
6. Nothing is sent automatically.

Common failure modes and fixes

The draft is too generic

Fix: make your call recap more specific and include the client's stated outcome, urgency, and constraints.

Cowork pulls in the wrong example file

Fix: reduce the template folder to only the files relevant to this proposal type.

The pricing language becomes overconfident

Fix: keep your proposal-rules.txt explicit about estimates, assumptions, and confirmation points.

The proposal promises too much

Fix: add stronger rules for exclusions, dependencies, guarantees, and timeline confirmation. Review the proposal manually before sending it to the client.