How to Research a New Commercial Lead Before You Send a Service Proposal With AI

Commercial leads are easy to under-research. A busy owner sees a company name, skims the inquiry, and sends a generic proposal because there is no time to build a real brief.

That is where Claude for Small Business can help. The point is not to make Claude flatter the prospect. The point is to collect the business context you already have, separate confirmed facts from guesses, and identify what should shape the proposal.

Who this is for

This workflow is for B2B service providers, consultants, agencies, facility service vendors, trade businesses, and owner-led companies that send proposals to commercial prospects.

It is best when the lead has context spread across more than one place: HubSpot, email, meeting notes, shared documents, old quotes, Slack messages, calendar events, or customer files.

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 contain lead context, such as HubSpot, Google Workspace, Microsoft 365, Slack, QuickBooks, PayPal, Canva, or DocuSign.
• Permission to access the relevant records.
• The lead's company name, contact name, website, or customer relationship management record.

For the fallback workflow, you need:

• A general AI tool.
• The lead's inquiry, website copy, meeting notes, and any relevant internal notes pasted into the chat.

How to capture or gather the source material

Do not start with a blank prompt. Build a source packet.

For Claude for Small Business, ask Claude Cowork to look only at specific places:

• The HubSpot company or contact record.
• The latest inquiry email or form submission.
• Recent email threads with that contact.
• Calendar events tied to the prospect.
• Internal documents with prior proposal examples.
• Slack threads about the account, if your team uses Slack for sales or operations.
• DocuSign status, if a prior agreement or template matters.

If you need public website context, copy the relevant website text into the prompt or provide the material in a document. Do not let the proposal depend on unverified assumptions.

Step-by-step workflow

1. Ask for a lead brief, not a proposal

The first output should be internal. It should help you understand the prospect before you write.

{
  "task": "Create an internal commercial lead brief before proposal drafting",
  "business_context": {
    "our_business": "Replace with your business type",
    "service_being_considered": "Replace with the service or project type",
    "approval_rule": "Do not send messages, update records, or stage outreach without my review"
  },
  "lead_context": {
    "lead_name": "Replace with company or contact name",
    "connected_sources_to_check": ["HubSpot", "Google Workspace", "Microsoft 365", "Slack", "Calendar", "DocuSign"],
    "manual_sources": "Paste website text, notes, or other source material here if needed"
  },
  "instructions": [
    "Use only the connected and pasted sources I provide.",
    "Summarize what the lead appears to do.",
    "List confirmed facts separately from reasonable inferences.",
    "Identify likely operational priorities that matter for our service.",
    "List proposal hooks that are specific but not exaggerated.",
    "List missing details we should clarify before sending a proposal.",
    "Do not draft the proposal yet."
  ],
  "output_format": {
    "lead_snapshot": "short paragraph",
    "confirmed_facts": "bullet list",
    "reasonable_inferences": "bullet list",
    "proposal_hooks": "bullet list",
    "missing_information": "bullet list",
    "risk_notes": "bullet list"
  }
}

2. Remove weak or unsupported claims

Lead research gets dangerous when it sounds specific but is not traceable.

Review the brief and delete anything that is not supported by a source. Keep a line only if you can point to where it came from: the website, the inquiry, the email thread, the customer relationship management record, the meeting notes, or another real source.

3. Ask for the proposal angle

Once the brief is clean, ask Claude to turn it into a proposal angle, not a full proposal.

{
  "task": "Turn the lead brief into a proposal angle",
  "instructions": [
    "Use the approved lead brief.",
    "Suggest 2 to 3 proposal angles that connect the prospect's situation to our service.",
    "For each angle, explain what source fact supports it.",
    "Avoid hype, flattery, and claims that are not source-backed.",
    "Recommend the safest angle to use in the proposal introduction."
  ],
  "output_format": {
    "proposal_angles": [
      {
        "angle": "short label",
        "why_it_fits": "source-backed rationale",
        "source_facts_used": "bullet list",
        "risk": "what could be overstated"
      }
    ],
    "recommended_angle": "short recommendation"
  }
}

4. Draft a short opening section

The opening should show that you understand the prospect without pretending you know more than you do.

{
  "task": "Draft the proposal opening from the approved lead brief",
  "instructions": [
    "Write a short opening section for a commercial service proposal.",
    "Use only confirmed facts and cautious, clearly framed inferences.",
    "Do not overstate the prospect's problems.",
    "Do not mention private internal notes directly.",
    "Keep the opening under 175 words."
  ],
  "output_format": {
    "proposal_opening": "short section",
    "claims_to_verify_before_sending": "bullet list"
  }
}

5. Save the lead brief with the proposal file

For future use, save the final lead brief with the proposal or customer relationship management record. This is useful if the prospect replies months later and you need to remember why the proposal was framed that way.

Fallback workflow with a generic AI tool

Use this path when you do not have Claude for Small Business or do not want connected tools involved.

Create a simple source packet:

1. Paste the lead's inquiry.
2. Paste website text or a short company description.
3. Paste call notes.
4. Paste any relevant prior quote or proposal notes.
5. Paste your service description.

Then use this prompt:

{
  "task": "Create a commercial lead brief for proposal drafting",
  "input": {
    "lead_inquiry": "Paste the inquiry here",
    "company_source_material": "Paste website copy or public description here",
    "internal_notes": "Paste call notes, prior emails, or customer relationship management notes here",
    "our_service": "Paste your service description here"
  },
  "instructions": [
    "Summarize what the company appears to do.",
    "Separate confirmed facts from reasonable inferences.",
    "List likely operational priorities relevant to our service.",
    "List 3 to 5 source-backed facts or clues we can reference in a tailored proposal.",
    "Then draft a short proposal opening paragraph in plain English.",
    "Do not invent facts. Use placeholders for anything missing."
  ],
  "output_format": {
    "lead_snapshot": "short paragraph",
    "confirmed_facts": "bullet list",
    "reasonable_inferences": "bullet list",
    "proposal_hooks": "bullet list",
    "proposal_opening": "short paragraph"
  }
}

Quality checks

Before using the lead brief, check:

• Every factual claim traces back to a real source.
• Old information is not treated as current.
• Internal team comments are not repeated in customer-facing language.
• The brief does not exaggerate the lead's problems.
• The proposal angle fits the service being sold.
• Claude did not confuse similarly named companies or contacts.
• Nothing sensitive from connected tools appears in the final proposal.

Common failure modes and fixes

The brief turns into a sales pitch

Stop and ask for an internal research brief only. Do not draft customer-facing language until the facts are clean.

Claude overstates the lead's pain points

Require separate sections for confirmed facts and reasonable inferences. Use only confirmed facts in the proposal opening unless you phrase an inference cautiously.

Connected context is stale

Ask Claude to label dates on source material. A three-year-old email should not drive today's proposal unless it is still relevant.

The workflow ignores the owner’s service strategy

Add your ideal customer, minimum project size, service area, turnaround capacity, and disqualifiers before asking for proposal angles.

More Claude for Small Business workflows

This article is part of the Claude for Small Business workflow cluster on PromptedWork. Start with the Claude for Small Business tool page for the explainer, then use the Anthropic workflows series to compare the related workflows and decide which one fits the job.

• How to Build a Weekly Owner Brief With Claude for Small Business
• How to Turn a Slow Sales Month Into a Promo Campaign With Claude for Small Business
• How to Turn a Customer Inquiry Into a Clear Service Quote With AI
• How to Turn a Customer Inquiry Into a Short Proposal for Commercial Work With AI