Scope of Work Builder
Turns a walkthrough into a designer-ready scope. No pricing, no gaps.
Your installers should not have to reverse-engineer the sale in the driveway.
Scope of Work Builder takes your walkthrough notes and turns them into a complete, numbered scope your system designer can build from: every room, every system, assumptions and exclusions stated, open questions flagged. No pricing by design. Runs on Claude and Cowork from a plain conversation, no connectors needed.
Download the skillThe problem
Sales closes with loose specs. Operations inherits a vague proposal and a set of assumptions nobody wrote down. Three weeks later the tech is on site asking questions that should have been answered before the contract was signed, and the client is watching the team scramble.
One bad handoff costs 2 to 8 technician hours on a mid-size project, and most shops absorb it silently because nothing catches it. The margin does not disappear on the proposal. It disappears in the gap between what was sold and what the install team knew.
The fix is a scope document that exists before the handoff, written the same way every time.
What you get
How it works
Dump the walkthrough. Paste your voice memo transcript, type your notes, or describe the job room by room from memory. Messy is fine.
Capture the client record. It requires the client's full name, site address, phone, and email before the scope is final. Missing fields get stamped in the header, nothing slips through blank.
Guided fact-find. It fills the gaps one question at a time: room count, systems per room, client priorities, site conditions, existing equipment staying or going. No walls of questions.
Scope assembly. It organizes everything into the numbered scope with assumptions and exclusions spelled out, then reads it back for your corrections.
Handoff package. It closes with the open questions list and the designer brief, so the person receiving the scope knows the client's mind, not just the room list.
Confirmation email. It offers to draft the same-day recap to the client: pleasure meeting you, here is everything we discussed, we're starting the design, reply if anything is missing. Scope locked in writing while the walkthrough is still fresh.
Example output
Scope: Primary Bedroom (Room 2 of 7)
Open questions: shade fabric selection owner or designer, existing switch locations staying, closet touch panel yes or no.
Designer brief: Client is design-sensitive, everything visible must disappear or match finishes. Budget signaled flexible on bedroom, tight on patio. Wife is the decision maker on anything visual.
Confirmation email: "Hi Mr. Smith, pleasure meeting you today. Below is everything we discussed, room by room. We're starting on the design now. If anything is missing, reply here and we'll fold it in before the design locks."
How to trigger it
Works with
Install + download
Click the download link below and save the file.
In Claude: go to Settings, then Skills, and upload the file.
In Cowork: open the Skills panel and upload the file.
Test it: say "run the scope of work builder" and describe the last job you walked.
The core prompt
Use this if your platform has no Skills support. Paste it into custom instructions.
# Scope of Work Builder You turn a messy AV walkthrough into a complete scope of work a system designer can build from. The user is an AV integration owner or salesperson. This skill contains NO pricing by design. Ask for the raw material first: transcript, notes, or a description from memory. Then require the client record: full name, full site address, phone, and email. Missing fields get stamped REQUIRED - MISSING in the scope header, never silently dropped. Then fill the gaps one question at a time, never bundled: room count and names, systems per room, client priorities, site conditions, existing equipment staying or going. Then produce: 1. Scope of Work: numbered by room and system. Nothing implied. 2. Assumptions: everything treated as true but not confirmed on site. 3. Exclusions: what the job does not include, stated plainly. 4. Open Questions: everything unanswered that could change scope or schedule. 5. Designer Brief: one paragraph on the client's priorities, constraints, decision makers, and where to be careful. 6. Offer once to draft the client confirmation email: a short, plain recap in the owner's voice (here is what we discussed, we're starting the design, reply if anything is missing) with a client-friendly scope below it: rooms and systems only, no assumptions, no exclusions, no designer brief. Draft only, never send. Rules: never assume scope the user did not state. Never add pricing, budgets, or product costs. Read the scope back for corrections before finishing. Flag conflicts between client wishes and site conditions.
Need the full priced proposal instead of just the handoff doc? The Proposal Builder runs the same walkthrough all the way through: scope, priced BOM, labor estimate, and client-ready proposal copy.
This is a template, not a finished product. Run it on your last real walkthrough, adjust the room and system categories to how your shop works, and swap the email template's phrasing to your own voice. Save your customized version. The structure is built. You supply the details that make it yours.