# How to Turn a Customer Inquiry Into a Short Proposal for Commercial Work With AI Canonical URL: https://promptedwork.com/articles/turn-customer-inquiry-into-short-proposal-for-commercial-work-with-ai Markdown URL: https://promptedwork.com/articles-md/turn-customer-inquiry-into-short-proposal-for-commercial-work-with-ai.md Description: Turn a commercial inquiry into a short proposal using Claude for Small Business, connected business context, and an owner review step before anything is sent. Published: 2026-03-09 Updated: 2026-05-14 Category: Local Business Owners Tags: local-business-owners, commercial-proposals, service-quotes, b2b, ai-workflows, claude-small-business, claude-cowork, anthropic-workflows ## Workflow Summary - Best for: This workflow is for B2B service providers, consultants, agencies, facilities vendors, contractors, and owner led teams that occasionally need a more formal commercial proposal without building a full custom document... - Input: Access to Claude for Small Business. Claude Cowork in the Claude desktop app. The Claude for Small Business plugin installed and enabled. - Primary tool: Claude for Small Business - Output: Turn a commercial inquiry into a short proposal using Claude for Small Business, connected business context, and an owner review step before anything is sent. - Main risk: Cut background, mission statements, and generic praise. Keep only what helps the buyer approve, clarify, or reject the work. - Verification step: The project summary matches the real inquiry. The scope is specific enough to prevent misunderstanding. Exclusions are visible. ## Article Some commercial opportunities need more than a price. They need a short proposal that shows the buyer what you understood, what you will do, what is excluded, when it can happen, what it costs, and how approval works. A generic AI tool can draft that if you paste the inquiry and your notes. Claude for Small Business can be stronger when the proposal depends on connected business context: customer relationship management records, email history, prior proposals, standard templates, payment tools, and signature tools. ## Who this is for This workflow is for B2B service providers, consultants, agencies, facilities vendors, contractors, and owner-led teams that occasionally need a more formal commercial proposal without building a full custom document from scratch. It is a good fit when the customer is serious enough to deserve a proposal, but not large enough to justify a full sales deck. ## Prerequisites For the Claude for Small Business workflow, you need: - Access to Claude for Small Business. - Claude Cowork in the Claude desktop app. - The Claude for Small Business plugin installed and enabled. - Connected tools that hold proposal context, such as HubSpot, Google Workspace, Microsoft 365, QuickBooks, PayPal, DocuSign, Slack, or Canva. - The original customer inquiry. - Your baseline scope, pricing logic, and service constraints. - A standard proposal template or prior example, if you have one. For the fallback workflow, you need: - A general AI tool. - The customer inquiry, quote notes, lead research, pricing rules, and proposal template pasted into the chat. ## How to capture or gather the source material Do not start from a blank proposal request. Gather the material that should control the proposal. Useful sources include: - Original customer inquiry or form submission. - HubSpot deal, company, and contact record. - Relevant email thread. - Call notes or meeting notes. - Prior proposal template from Google Drive or Microsoft 365. - Standard scope language. - Pricing sheet or minimum charge rules. - DocuSign agreement template, if the proposal will require signature. - QuickBooks or PayPal context, if deposit, payment timing, or past payment behavior matters. The proposal should be grounded in these sources. It should not become a generic sales brochure. ## Step-by-step workflow ### 1. Ask Claude for an internal proposal outline first Open Claude Cowork and ask for a private outline. Do not start with the customer-facing proposal. ```json { "task": "Create an internal outline for a short commercial proposal", "business_context": { "our_business": "Replace with your business type", "service_or_project": "Replace with the service being proposed", "proposal_length": "Short proposal, not a full sales deck", "approval_rule": "Do not send, stage, sign, invoice, or update records without my review" }, "source_context": { "customer_or_company": "Replace with company or contact name", "connected_sources_to_check": ["HubSpot", "Google Workspace", "Microsoft 365", "Slack", "DocuSign", "QuickBooks", "PayPal"], "manual_context": "Paste inquiry, pricing notes, or scope rules if they are not in connected tools" }, "instructions": [ "Use only the connected and pasted sources I provide.", "Create an internal proposal outline with project summary, scope, assumptions, exclusions, timeline, pricing, approval steps, and open questions.", "Separate confirmed facts from assumptions.", "Flag any language that could create legal, warranty, scheduling, or payment promises.", "Do not write the customer-facing version yet." ], "output_format": { "confirmed_facts": "bullet list", "assumptions": "bullet list", "proposal_outline": "sectioned outline", "open_questions": "bullet list", "risk_language_to_avoid": "bullet list" } } ``` ### 2. Tighten the scope before drafting This is where most proposal mistakes happen. Claude may write clean language around a weak scope. Fix the scope before you fix the wording. Check the internal outline for: - A real project summary. - Specific included work. - Specific exclusions. - Timeline that matches capacity. - Pricing that follows your rules. - Approval step that matches your process. - No promises that should belong in a contract. ### 3. Ask for the short proposal After the outline is correct, ask Claude to write the proposal. Keep it short enough for a busy buyer to scan. ```json { "task": "Write the short commercial proposal", "instructions": [ "Use the approved internal outline.", "Write a concise customer-facing proposal in plain English.", "Use these sections: project summary, recommended scope, assumptions, exclusions, timeline, pricing, approval steps.", "Keep the proposal practical and specific.", "Do not add mission statements, generic company background, unsupported claims, legal terms, or guarantees.", "Do not send or stage anything until I approve." ], "output_format": { "proposal_title": "short title", "proposal_body": "sectioned proposal", "email_cover_note": "short email that can accompany the proposal", "owner_review_checklist": "bullet list" } } ``` ### 4. Optional: stage the next action If your connected tools support the next step, Claude for Small Business may help prepare an approval workflow, agreement, invoice, or signature packet. Use this only after the proposal is final: ```json { "task": "Prepare but do not send the proposal handoff", "instructions": [ "Use the approved proposal text.", "Prepare the next action only as a draft.", "If DocuSign is connected, prepare the signature handoff but do not send it.", "If QuickBooks or PayPal is connected, prepare deposit or invoice notes but do not create or send payment requests.", "If HubSpot is connected, suggest the customer relationship management update but do not apply it without review.", "Show me every proposed action before anything runs." ], "output_format": { "prepared_actions": "bullet list", "items_requiring_owner_approval": "bullet list", "draft_handoff_message": "message" } } ``` ### 5. Save the approved proposal and source brief Once approved, save the final proposal and internal source brief together. This helps later if the buyer asks why an item was excluded, why a price changed, or what was assumed. ## Fallback workflow with a generic AI tool Use this prompt when you do not have Claude for Small Business or when you prefer manual source control. ```json { "task": "Turn an inquiry into a short commercial proposal", "input": { "customer_inquiry": "Paste the original inquiry here", "lead_research": "Paste the approved lead brief here", "scope_notes": "Paste the work you plan to include", "pricing_rules": "Paste pricing, deposit, or minimum charge rules here", "constraints": "Paste timing, service area, access, exclusions, or capacity limits here" }, "instructions": [ "Create a short proposal with these sections: project summary, scope, assumptions, exclusions, timeline, pricing, next steps.", "Keep it concise and practical.", "Separate confirmed facts from assumptions before writing the proposal.", "Do not invent legal terms, guarantees, or implementation details that are not provided.", "Write in plain English.", "Add an owner review checklist at the end." ], "output_format": { "confirmed_facts": "bullet list", "assumptions": "bullet list", "proposal": "sectioned proposal", "email_cover_note": "short email", "owner_review_checklist": "bullet list" } } ``` ## Quality checks A short commercial proposal should be useful, not inflated. Before sending, verify: - The project summary matches the real inquiry. - The scope is specific enough to prevent misunderstanding. - Exclusions are visible. - Timeline and price match what you can actually deliver. - Approval steps are clear. - Payment or signature steps are only staged after owner review. - No connected system was updated without approval. - The proposal can be read in two minutes by a busy manager. ## Common failure modes and fixes ### The proposal becomes a sales deck Cut background, mission statements, and generic praise. Keep only what helps the buyer approve, clarify, or reject the work. ### Claude adds legal or warranty language Remove it unless it comes from your approved contract language or attorney-reviewed template. ### The proposal hides assumptions Add an assumptions section. This protects both sides and reduces follow-up confusion. ### Connected tools create false confidence A record in HubSpot or an old email does not mean the information is current. Ask Claude to label source dates and use the newest relevant source unless you approve otherwise. ## More Claude for Small Business workflows This article is part of the Claude for Small Business workflow cluster on PromptedWork. Use the [Anthropic workflows series](https://promptedwork.com/series/anthropic-workflows) to compare the related workflows and decide which one fits the job. - [How to Build a Weekly Owner Brief With Claude for Small Business](https://promptedwork.com/articles/build-weekly-owner-brief-with-claude-for-small-business) - [How to Turn a Slow Sales Month Into a Promo Campaign With Claude for Small Business](https://promptedwork.com/articles/turn-slow-sales-month-into-promo-campaign-with-claude-for-small-business) - [How to Turn a Customer Inquiry Into a Clear Service Quote With AI](https://promptedwork.com/articles/turn-customer-inquiry-into-service-quote-with-ai) - [How to Research a New Commercial Lead Before You Send a Service Proposal With AI](https://promptedwork.com/articles/research-new-commercial-lead-before-service-proposal-with-ai) ## Sources Checked - Anthropic, "Claude for small business." Accessed 2026-05-14. https://claude.com/solutions/small-business - Anthropic, "Introducing Claude for Small Business." Accessed 2026-05-14. https://www.anthropic.com/news/claude-for-small-business - OpenAI Help Center, "How does the new file uploads capability work?" Accessed 2026-05-14. https://help.openai.com/en/articles/8982896-how-does-the-new-file-uploads-capability-work - Google Gemini Apps Help, "Upload files & folders to Gemini Apps." Accessed 2026-05-14. https://support.google.com/gemini/answer/14903178 ## Quarterly Refresh Flag Review this article by 2026-08-12 to confirm Claude for Small Business availability, connector behavior, Claude Cowork setup steps, supported tools, and approval behavior.