How Freelancers Can Use Claude Cowork to Turn a Sales Call Into a Personalized Proposal While Traveling
Capture a sales call recap while traveling, then use Claude Cowork with approved proposal templates and scope rules to draft a personalized proposal for review.
Workflow summary
Quote this workflow accurately
- Best for
- You finish a sales or discovery call while traveling. The client's goals and constraints are clear for the moment, but you still need to turn the recap into a proposal. Your usual templates, scope boundaries, and pric...
- Input
- Cowork access on Claude Pro, Max, Ultra, Team (mobile beta), or Enterprise (mobile subject to owner enablement). The current Claude mobile app, or claude.ai on web as a fallback. A concise recap captured with phone no...
- Primary tool
- Claude Cowork
- Output
- Capture a sales call recap while traveling, then use Claude Cowork with approved proposal templates and scope rules to draft a personalized proposal for review.
- Main risk
- Fix: A mobile started task cannot access a desktop only directory. Add the approved rules to the accessible cloud project/session, or start a separate desktop task with the folder connected. Confirm which source Claud...
- Verification step
- The draft refers to the correct prospect, with no unrelated client's information. The proposal's facts come from the corrected call recap; example proposals supplied structure only. The actual template and proposal ru...
Continue from this article
Scope and privacy warning: Use only this prospect's approved information and the minimum necessary proposal assets. Never expose another client's confidential files or rely on an old proposal as evidence for a new client's facts. Review pricing, case studies, guarantees, timelines, deliverables, and legal or commercial commitments before sending. Claude drafts; you approve and send.
Cowork requirements at a glance: Claude Cowork is available on Pro, Max, Ultra, Team, and Enterprise, not Free. Mobile is supported on Pro, Max, and Ultra, is in beta for Team, and depends on admin enablement for Enterprise. For a proposal drafted while traveling, put approved templates and rules in a cloud-accessible Claude project or session before the call. A mobile-started task cannot access a local-only desktop proposal folder.
If Claude Cowork is new to you
For background, see the Claude Cowork tool hub and Anthropic Workflows series. Cowork works across Claude mobile, web, and desktop. In the unified Claude experience, you simply describe the job in a conversation. If your app still offers a Chat/Cowork selector, choose Cowork for this multistep task.
As of October 6, 2026, new tasks on Pro, Max, and Ultra run in the cloud by default, and the former "Only on your computer" choice is gone. A cloud task continues if your laptop closes. This does not give a mobile-started task direct access to your computer's files. Dispatch is a limited legacy beta unavailable to new users and is not part of this workflow.
Problem and who this is for
You finish a sales or discovery call while traveling. The client's goals and constraints are clear for the moment, but you still need to turn the recap into a proposal. Your usual templates, scope boundaries, and pricing rules may be sitting in files on your desk.
This workflow is for freelancers and consultants who want a useful first proposal draft while the conversation is fresh, without inventing commitments or waiting to type up every detail later.
Why Cowork fits this workflow
A proposal has multiple moving parts: client goals, scope, deliverables, exclusions, pricing assumptions, approval language, and a consistent document structure. Cowork can inspect accessible reference materials, prepare an outline, and produce a proposal draft in a cloud session that you can review later on desktop.
The practical improvement is preparing those rules in advance and forcing an outline review. Without accessible templates or a verified call recap, an agentic run only produces polished guesswork.
Why not normal Claude chat?
A normal Claude response can draft a one-off proposal from pasted notes. Cowork adds value when you want an outline-and-approval workflow, reusable project instructions, accessible templates, and a finished reviewable document. In the unified Claude interface, these capabilities are available without a separate mode switch.
Prerequisites
- Cowork access on Claude Pro, Max, Ultra, Team (mobile beta), or Enterprise (mobile subject to owner enablement).
- The current Claude mobile app, or claude.ai on web as a fallback.
- A concise recap captured with phone notes or dictation after a sales call.
- An approved template,
proposal-rules.txt, and up to two relevant approved example proposals, accessible to the cloud task through the account project or attachments. - A human owner who confirms pricing, scope, exclusions, guarantees, and sending.
You do not need Claude Desktop open for the phone-first cloud route. You do need Desktop open if you choose the separate desktop-started route that accesses connected local files.
Set up the proposal project before you travel
Retain this simple organization on your computer or in your own document storage:
templates/
proposal-rules.txt
example-proposals/
call-recaps/
draft-proposals/
archive/
templates/ is for approved headings and layout. proposal-rules.txt describes pricing approval limits, scope boundaries, assumptions, exclusions, confirmation language, and anything that must remain tentative. example-proposals/ holds one or two examples selected for style, not factual claims. call-recaps/ holds the date-stamped notes. draft-proposals/ contains drafts you have saved; archive/ keeps old materials out of the current set.
Before traveling, choose one of two real execution paths:
- Path A, phone-first cloud (recommended): Create or open an account-based Claude project. Add the current approved proposal structure, pricing/scope rules, and permitted examples to project instructions/knowledge, or provide those documents directly to the cloud session. Verify from your phone that Claude can identify these exact materials before the call. The directory layout above is a filing convention, not a remotely mounted folder. Completed cloud files are available in the task for preview/download; save them to
draft-proposals/yourself. - Path B, local-folder workflow: Keep the materials only on your computer, connect the narrowly scoped folder through Claude Desktop, and start the Cowork task from desktop. That session can then be steered on mobile while traveling. For access to connected local files, the desktop app must remain open; the computer must remain online for the bridge. The cloud session can keep doing cloud work when Desktop is unavailable, but cannot fetch local files then. You cannot create a fresh task from mobile and have it access the folder by merely naming it.
Before you depend on Path A, confirm in the actual Claude mobile app that your account-based project's approved template and proposal-rules.txt are visible to the task. Files attached to a local-folder project do not become cloud project files automatically.
Add these JSON instructions to the Claude project's instruction field, or paste them into the working session. This is a reusable prompt, not a special settings file:
{
"project_name": "Proposal Drafting From Sales Calls",
"project_purpose": "Turn a phone-captured sales call recap into a personalized proposal draft using approved reference materials.",
"project_instructions": [
"Use the call recap explicitly provided for this task as the primary source. In a desktop-started local folder task, use the specified newest file in call-recaps.",
"Use approved templates for structure only, not as facts about the current prospect.",
"Read proposal-rules.txt only if it is accessible; ask me to provide the rules if it is not.",
"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 and pause for my approval before drafting the full proposal.",
"Save or provide drafts only; do not send, publish, or approve commercial terms."
],
"file_naming": "proposal-draft-client-name-yyyy-mm-dd"
}
How to gather the source material
- Immediately after the call, dictate or type the client's stated goal, requested deliverables, timing, budget signals, constraints, decision-maker, and open questions. Do not secretly record a call. Follow consent requirements for recording if you choose to record it.
- Edit obvious transcription mistakes, especially names, amounts, and timing. Separate what the prospect actually said from your assumptions.
- For Path A, paste the corrected recap directly into the Claude mobile task. Do not require
call-recaps/to be mounted on your phone. If you want a permanent source record, also save the recap to your owncall-recaps/folder later. - For Path B, put the recap into the local
call-recaps/folder and use a task that originated on desktop with connected folder access. - Before you rely on any price, make sure your approved rules state what is fixed, what is only an estimate, and who can approve changes.
Numbered workflow steps
1) Start the proposal outline from your phone
Open the account-based Claude project with your approved reference context. In the unified interface, simply request the job; if the older selector is present, choose Cowork. Then paste this JSON prompt and your corrected call recap. Do not ask it to produce final sales terms on the first pass.
{
"task": "Prepare a personalized proposal outline from my sales call recap while I am traveling",
"input": {
"call_recap": "PASTE CLIENT GOALS, DELIVERABLES, BUDGET SIGNALS, TIMING, CONSTRAINTS, AND OPEN QUESTIONS",
"proposal_project": "Proposal Drafting From Sales Calls",
"approved_template": "Relevant template that is accessible in this cloud task",
"proposal_rules_file": "proposal-rules.txt, only if it is accessible",
"example_proposals": "At most two approved examples, for structure and tone only"
},
"rules": [
"List which reference materials you actually read; stop and ask if proposal-rules.txt or the template is missing.",
"Use the recap as the only source for this client's stated needs.",
"Use examples only for structure or tone, never to transplant clients, results, pricing, or case studies.",
"Propose the scope, deliverables, exclusions, assumptions, and open questions.",
"Do not invent case studies, guarantees, delivery dates, client results, pricing, or commitments.",
"Mark uncertain scope, pricing, timeline, and dependencies [TO CONFIRM].",
"Stop after the outline for my review. Do not create or send the final proposal yet."
],
"output_format": {
"client_goal": "Client-stated problem and desired outcome",
"proposed_scope": "Work explicitly supported by the call recap",
"deliverables": "Draft list with supporting call evidence",
"exclusions_and_assumptions": "Clear boundaries and dependencies",
"pricing_and_timeline_status": "Approved terms or [TO CONFIRM]",
"open_questions": "Items requiring confirmation before a proposal is sent"
}
}
2) Review scope, ownership, pricing, and claims
Confirm that the outline uses the correct prospect and template, and that every promised result or milestone is actually supported. Remove another client's information. If budget was only a signal, do not convert it into a fixed quote. Reject invented examples, delivery dates, and guarantees. Approve the outline explicitly when it is accurate enough to draft from.
3) Generate the proposal draft after approval
In the same session, use this second JSON prompt:
{
"task": "Create a review-only personalized proposal draft from the approved outline",
"input": {
"approved_outline": "USE THE OUTLINE I JUST APPROVED",
"file_name": "proposal-draft-client-name-yyyy-mm-dd"
},
"rules": [
"Use the approved template only for layout and structure.",
"Use this client's confirmed call recap and the approved outline for substance.",
"Follow accessible proposal-rules.txt for pricing and exclusions.",
"Keep all unapproved price, scope, timeline, dependency, and guarantee language marked [TO CONFIRM].",
"Do not invent case studies, guarantees, delivery dates, client results, pricing, or commitments.",
"Deliver a reviewable proposal draft, not a final offer or an email send.",
"Do not send anything, publish, or modify customer records."
],
"output_format": {
"type": "proposal_draft",
"sections": ["client goal", "proposed approach", "scope and deliverables", "assumptions and exclusions", "pricing status", "timeline status", "dependencies", "next step", "items to confirm"]
}
}
4) Review the full proposal before sending
From your phone, review the draft if practical, then open the same task on desktop when you can. Check the scope, assumptions, exclusions, price, case studies, timetable, guarantees, dependencies, and requested decision. Use [TO CONFIRM] markers to finish unresolved commercial details. You may shorten the proposal or turn the approved scope into a statement of work, but do not send or sign it automatically.
5) Save the final reviewed draft deliberately
For the phone-first cloud path, download the draft from the session and place it in draft-proposals/ in your own file storage. A named folder in your prompt is not an automatic destination for a mobile-started task. For the desktop-started local-folder path, specify the connected draft-proposals/ destination and verify the file was actually created there without overwriting the templates. Archive outdated material separately after review.
Expected output
You should have a prospect-specific proposal draft that uses your approved structure, states the client's goals accurately, keeps scope and pricing boundaries visible, and flags every unresolved commercial commitment [TO CONFIRM]. It is an internal draft until you approve its terms and send it personally.
Future proposal runs
Reuse the project instructions and approved template/rules. Paste the next call recap into a new cloud task, verify the correct context is accessible, and repeat outline, approve, draft, review. Revise proposal-rules.txt when pricing or scope policies change, and update the account-based project reference material separately; do not assume edits to your local file propagate to a cloud project.
{
"task": "Prepare the next proposal outline from the call recap in this message",
"rules": [
"Use only this prospect's confirmed facts.",
"Name the accessible template and proposal-rules.txt; request missing files.",
"Keep uncertain details marked [TO CONFIRM].",
"Stop for outline approval before creating the proposal draft.",
"Do not send or approve terms."
]
}
Tool-specific instructions and tips
- Claude mobile: Use a cloud Cowork session with accessible account-based project context. You can start and revisit the task while traveling, without Dispatch. The cloud task does not need your laptop awake.
- Account-based project: Keep approved template content and proposal rules available to the task. Confirm which files Claude can actually read. Do not treat project memory as a reliable pricing source of record.
- Claude Desktop: Use it to start the task if your proposal materials remain local-only, then continue monitoring from mobile. Desktop must remain open for local-file access; a mobile-started session cannot directly reach those folders.
- Permissions: Use Manually approve when real file or connector changes are possible. Automatically approve performs safety checks and can pause; Skip all approvals does not perform those checks. File deletions still require approval.
Quality checks
- The draft refers to the correct prospect, with no unrelated client's information.
- The proposal's facts come from the corrected call recap; example proposals supplied structure only.
- The actual template and proposal-rules.txt were available and identified, or missing sources were explicitly supplied.
- Scope, exclusions, deadlines, pricing, and guarantees are approved or visibly marked
[TO CONFIRM]. - All case studies, outcomes, and client results have verifiable, approved sources.
- The draft appears in the correct cloud task or in a verified local
draft-proposals/destination; source templates were not overwritten. - A human reviews and sends the final proposal. Claude makes no promises or external sends.
Common failure modes and fixes
The phone task cannot find proposal-rules.txt
Fix: A mobile-started task cannot access a desktop-only directory. Add the approved rules to the accessible cloud project/session, or start a separate desktop task with the folder connected. Confirm which source Claude actually used before drafting.
The proposal sounds generic
Fix: Add the prospect's stated problem, desired outcome, constraints, and important open questions to the call recap. Keep the approved template, but rewrite the introduction for this prospect alone.
Pricing becomes a fixed commitment
Fix: In proposal-rules.txt, distinguish actual approved prices from provisional estimates. Mark anything unapproved [TO CONFIRM] and require your explicit pricing review.
An old example becomes a fabricated case study
Fix: Allow approved examples to guide structure only. Remove their specific numbers, clients, claims, and outcomes from the new proposal unless you separately verify and authorize them.
Claude creates a file, but the local draft folder is empty
Fix: In a mobile-first cloud session, download and file the output yourself. Use a desktop-started connected-folder session only when direct local saving is needed, and confirm the resulting path.
The proposal commits to work not discussed
Fix: Return to the outline. Explicitly enumerate exclusions, dependencies, and tentative items before approving a final draft. Don't solve missing information by making commitments up.
Sources Checked
- Anthropic Claude Help Center, Get started with Claude Cowork. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork (accessed 2026-11-01).
- Anthropic Claude Help Center, Use Claude Cowork on web, desktop, and mobile. https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile (accessed 2026-11-01).
- Anthropic, Claude Cowork product guide: Getting started. https://claude.com/resources/guides/claude-cowork-product-guide/getting-started (accessed 2026-11-01; some desktop-only setup language predates the cloud/mobile rollout, so use the current Help Center articles for surface behavior).
- Anthropic, Claude Cowork changelog. https://claude.com/docs/cowork/changelog (accessed 2026-11-01).
- Anthropic Claude Help Center, Organize your tasks with projects in Claude Cowork. https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork (accessed 2026-11-01; reverified for project instructions, account context, and local-folder distinction).
Quarterly Refresh Flag
Review on 2027-02-01. Recheck cloud and mobile Cowork availability, project file access, local-folder session restrictions, proposal output export and permissions, and changes to the unified interface.
Related Workflows
How Freelancers Can Use Claude Skills to Turn a Discovery Call Into a Statement of Work
Turn a recorded discovery call into a usable statement of work with milestones, assumptions, and approval terms using Claude Skills.
How Freelancers Can Use Claude Skills to Turn Repeated Prospect Questions Into a Proposal FAQ
Turn repeated prospect questions and objections into a reusable proposal FAQ with Claude Skills.
How Freelancers Can Use Claude Cowork to Review a Deliverable Folder Against a Client Checklist
Use Claude Cowork to compare a deliverable folder against the client brief and catch missing files before delivery.
Help keep PromptedWork sharp
Share a broken step, outdated prompt, or general feedback. This is only for improving this specific workflow.