Claude CoWork for Tradespeople

Want the complete Claude setup for contracting work in 15 minutes instead of building it yourself?

The Contractor Claude Vault is the done-for-you version of everything in this guide: a full Claude Project setup file with your trade, service area, and voice — plus 40 contractor-specific prompts organized by job phase, three worked-example templates (estimate, change order, progress update), and a 7-section workflow guide built for the way contractors actually work.

One-time $29, instant download, no subscription. Get the vault →

What is Claude CoWork?

Claude CoWork is the practice of using Claude as a persistent, knowledgeable co-worker embedded in your daily trades workflow. This is not about asking a chatbot a one-off question and hoping for the best. It is about configuring Claude with your business context, service offerings, and communication style so that every interaction produces output you can actually use.

Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (<context>, <instructions>, <format>, <avoid>) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity. They work in ChatGPT too, but are optimized for Claude.

Think of Claude as the best office help you have ever had, one who never forgets your pricing, knows how to write a professional estimate, and can draft a scope of work or customer email in seconds while you focus on the actual job. The difference between tradespeople who dabble with AI and those who gain a real edge comes down to setup and consistency.

This guide walks you through setting up Claude specifically for trades work, the five workflows that will save you the most time, and the prompting techniques that separate generic output from production-ready content.

Install the Tradesperson Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them. Pick whichever you use:

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Tradesperson plugin packages the workflows below as native skills and slash commands.

Open the Cowork plugin directory in your desktop app.
Filter by Cowork, search for "Tradesperson", and click Install.
The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste https://github.com/alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/tradesperson

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans). Higher friction; only worth it if you want the auto-activating skills, not the slash commands.

What the plugin gives you (any surface)

Slash command	What it does
`/estimate`	Generate customer estimates with itemized line items, labor, materials, and payment terms
`/inspection-report`	Draft structured inspection reports from jobsite notes with findings and recommendations
`/scope-of-work`	Create detailed scope-of-work proposals with specifications, timelines, and materials
`/customer-email`	Draft follow-ups, warranty info, maintenance reminders, and scheduling confirmations

Auto-activating skills (no command needed — Claude applies them when relevant):

Trade Documentation — Building codes awareness, permit references, industry-standard terminology, and inspection reporting
Customer Relations — Professional trade communication, estimate presentation, warranty explanation, and client follow-up

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task — that combination is the full Claude CoWork setup.

Setting Up Claude for Trades Work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism (set context once when starting a Cowork task). Claude Code users get the plugin's ambient skills automatically — no Project setup needed. The workflows themselves are surface-agnostic — paste the prompts wherever you're working. The key to getting consistently useful output from Claude is using Claude Projects. A Project lets you set custom instructions that persist across every conversation, so you are not re-explaining your business every time.

Step 1: Create a Trades Project. In Claude, click "Projects" and create one called something like "My Trades Business."

Step 2: Set your custom instructions. In the Project settings, add instructions like:

You are my trades business assistant. Here is my context:

<business-profile>
- Name: [Your Name], [Your Company]
- Trade: [Plumbing / Electrical / HVAC / Roofing / General Contracting / Painting / Landscaping]
- License number: [Your License Number and State]
- Service area: [City/Region]
- Typical jobs: [Residential service calls / Commercial installations / New construction / Remodels]
- Pricing model: [Flat rate / Time and materials / Per-unit pricing]
- Brand voice: [Straightforward and professional / Friendly and approachable]
</business-profile>

<rules>
- When writing estimates, always include a clear scope of work, material list, and payment terms.
- When writing customer communications, keep language simple and jargon-free.
- Always note that estimates are valid for 30 days and subject to on-site verification.
</rules>

Step 3: Upload reference documents. Add your estimate templates, standard scope of work language, warranty information, or past proposals to the Project knowledge base. Claude will reference these when generating content.

Step 4: Start every session inside this Project. This ensures Claude always has your context loaded.

Your Top 5 Workflows with Claude

1. Customer Estimates That Win Jobs

Give Claude your job notes and let it build a polished estimate that builds trust.

<task>Write a detailed estimate for a residential bathroom remodel.</task>

<context>
- Customer: Mark and Lisa Thompson, 412 Cedar Lane, Austin, TX
- Scope: full gut remodel of master bath (8x10), tub to walk-in shower (36x60), 60" double vanity, new toilet, tile floor/shower walls, 3 light fixtures, exhaust fan
- Mid-range materials, customer choosing tile/fixtures, 8-10 days labor, $85/hr 2-man crew
</context>

<instructions>
- Sections: demo, plumbing, electrical, tile/flooring, fixtures, cleanup
- Material and labor estimates per section, add permits line
- Payment terms: 50% deposit, 25% rough-in, 25% completion, valid 30 days
</instructions>

<avoid>Guaranteeing exact dates, including undiscussed work, or quoting customer-selected fixtures</avoid>

Before Claude: 1-2 hours writing up the estimate after a site visit. After Claude: 10 minutes to input notes, 10 minutes to verify and finalize.

2. Scope of Work Documents That Prevent Disputes

<task>Write a scope of work for an HVAC system replacement.</task>

<context>
- Customer: David Chen, 2,200 sq ft home (1998)
- Current: 3-ton Carrier AC (R-22), 80% AFUE furnace. Ductwork acceptable, no replacement
- Proposed: 3-ton 16 SEER2 Trane AC, 96% AFUE variable-speed furnace, new thermostat
- Additional: new line set, disconnect, plenum ductwork modification. Permit required
</context>

<instructions>
- Clear inclusions and exclusions, equipment models and warranty terms
- Note old equipment removal, permit/inspection responsibilities
- Plain language, under 350 words
</instructions>

<avoid>Promising energy savings percentages, including undiscussed services, or excessive jargon</avoid>

Before Claude: 45-60 minutes writing scope language from scratch. After Claude: 5 minutes to input details, 10 minutes to review against site conditions.

3. Inspection Reports That Document Everything

<task>Write an inspection report for a residential roof assessment.</task>

<context>
- Property: 1847 Birchwood Drive, Denver, CO, ~28 squares architectural asphalt (installed 2011)
- Shingles: granule loss south slope (60-70% life left), 3 cracked near west ridge
- Flashing: chimney step flashing lifting north side, counter flashing 1/4" gap
- Gutters: pulling from fascia at 2 locations, NW downspout disconnected
- Ventilation: ridge vent OK, 2/4 soffit vents blocked. Decking: no issues
</context>

<instructions>
- Organize by component, rate each (good/fair/needs attention/immediate repair)
- Include recommended repairs with priority, note what is in good shape
- Professional factual tone, under 400 words
</instructions>

<avoid>Estimating roof life in exact years, recommending unnecessary replacement, or including pricing</avoid>

Before Claude: 45-60 minutes writing up inspection findings. After Claude: 5 minutes to input notes, 10 minutes to review for accuracy.

4. Customer Emails That Build Repeat Business

<task>Draft an email updating a customer on their kitchen remodel progress.</task>

<context>
- Customer: Jennifer Walsh, kitchen remodel (cabinets, countertops, backsplash, electrical)
- Good news: demo complete, rough plumbing/electrical passed inspection, cabinets arriving Thursday
- Issue: countertop fabrication 3 days behind, now Monday instead of Friday
- Overall still on track for April 11 completion
</context>

<instructions>
- Lead with good news, address delay honestly, reassure on completion date
- Explain this week's work, friendly professional tone, under 150 words
</instructions>

<avoid>Naming the fabricator, using technical jargon, or over-apologizing for a minor delay</avoid>

Before Claude: 15-20 minutes composing the email between jobs. After Claude: 2 minutes to input the update, 2 minutes to review and send.

5. Invoice Descriptions That Look Professional

<task>Write professional invoice line items for a completed electrical job.</task>

<context>
- Customer: Oakwood Dental Office, operatory build-out
- Work: 3x 20-amp circuits (dental chairs), 2x 30-amp circuits (compressor/vacuum), 6 LED recessed lights with dimmers, 4 duplex + 2 USB receptacles, LV conduit for data, 100A sub-panel
- All work permitted, passed final inspection
</context>

<instructions>
- Clear line items grouped by category (circuits, lighting, receptacles, panel, permits)
- Include quantities, concise but specific enough for customer understanding
</instructions>

<avoid>Hourly rate breakdowns (flat-rate job), NEC references, or vague combined line items</avoid>

Before Claude: 20-30 minutes writing up invoice descriptions. After Claude: 5 minutes to list the work, 5 minutes to review.

Prompt Engineering Tips for Tradespeople

1. Always specify the trade and job type. "Write for a residential plumbing service call" produces very different output than "write for a commercial HVAC installation." Tell Claude your trade and the context.

2. Include material specifics. Brand names, model numbers, and material grades make estimates and scope documents more credible and accurate.

3. Keep language customer-friendly. Add "Write so a homeowner with no trade knowledge can understand" to any customer-facing prompt. Claude will translate technical details into plain English.

4. Upload your best past estimates. Paste a previous estimate you are proud of and say "Match this format and tone." Claude adapts to your style quickly.

5. Mention your licensing and service area. This helps Claude include appropriate permit references and avoid suggesting work outside your scope of practice.

6. Use Claude to draft, then verify on-site. The best workflow is to generate the draft from your notes, then review it against what you actually saw at the job site before sending to the customer.

Privacy & Compliance

Verify local licensing and permit requirements. Claude does not have access to your local jurisdiction's permit requirements, licensing regulations, or code amendments. Always verify that any permit references, code citations, or licensing language in generated documents matches your local requirements.

Do not guarantee timelines. Construction and trades work involves variables outside your control, including weather, inspections, material availability, and subcontractor schedules. Review all Claude-generated estimates and scope documents to ensure they do not make firm completion date guarantees. Use language like "estimated completion" rather than "guaranteed by."

Confirm material specifications. When Claude includes material descriptions, model numbers, or specification references, verify them against current manufacturer data and your supplier availability. Product lines change, and Claude may reference discontinued or unavailable items.

Customer data. Avoid pasting customers' full financial information or sensitive personal details into Claude. First names and general property descriptions are sufficient for generating most documents.

Ready to skip the setup work?

If you'd rather not build this from scratch, the Contractor Claude Vault is the complete Claude setup for working contractors: the full Project configuration, 40 contractor-specific prompts organized by job phase, three worked-example templates, and a 7-section workflow guide — all for $29 one-time.

Get the vault →

Going Further

Ready to build on this foundation? Check out these resources:

Browse our full collection of trades prompt packs and templates for ready-to-use resources
Run an AI readiness audit for your trades business to identify your biggest opportunities
Explore AI-powered tools built specifically for tradespeople to automate even more of your workflow