Good-Better-Best Package Builder
Turns your price book into three tiers you can quote in one line.
Design the package once. Quote it forever.
Package Builder takes your price book and turns it into predetermined Good, Better, and Best tiers for the systems you sell every week: media rooms, whole-home audio, shades, networks, surveillance. Once the tiers exist, a proposal stops being a design project and becomes a selection. Runs on Claude and Cowork from a plain conversation, no connectors needed.
Download the skillThe problem
Every proposal in your shop is a custom design, even when the last ten media rooms were 80 percent identical. That costs you twice. First in hours, because someone rebuilds the same system from scratch every time. Second in margin, because pricing drifts: the same room gets quoted three different ways by three different people, and the client who shops your quote finds the inconsistency.
Predetermined tiers fix both. The thinking happens once, calmly, with your real numbers. After that, quoting a media room is one sentence: "use my Better package." Clients decide faster too, because three clear options beat one open-ended number every time.
What you get
How it works
Load your price book. First question every run: paste or attach your equipment list with models, prices, and labor rates. With it, tiers come back priced in your numbers. Without it, you get the full tier structure with placeholders and a clear list of what to fill in.
Pick the system. Media room, whole-home audio, shades, network, surveillance, outdoor. One system per run keeps the tiers sharp.
Set the anchors. It asks what your typical low, middle, and high builds look like for that system, one question at a time, using jobs you have sold.
Build the tiers. It assembles Good, Better, and Best with line items, labor, and the upgrade logic between each step.
Client-facing table. It closes with the comparison table in plain language, outcomes instead of SKUs, ready for your proposal.
Example output
Media Room Packages
Upgrade logic: Good to Better is "you'll hear the difference the first movie night." Better to Best is "this is the room your friends talk about."
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 "build my media room packages" and paste your price book.
The core prompt
Use this if your platform has no Skills support. Paste it into custom instructions.
# Good-Better-Best Package Builder You turn an AV integrator's price book into predetermined Good, Better, and Best packages for one system type at a time (media room, whole-home audio, shades, network, surveillance, outdoor). Ask for their price book first: equipment list with models, prices, and labor rates. With it, price every tier from their data. Without it, build the full tier structure with [PLACEHOLDER: confirm model/price] on every line and tell them what one-page doc to build. Then ask, one question at a time: which system type, what their typical entry-level build looks like, their typical mid build, and their typical high-end build, based on jobs they have sold. Produce: 1. Three tiers with line items: equipment categories, quantities, models and prices from their book, and labor hours per tier. 2. Upgrade logic: one plain-spoken line per step up, written the way an owner would say it to a client in the living room. 3. A client-facing comparison table: outcomes, not SKUs. Rules: never invent prices or models. Tiers must be internally consistent (Best includes everything implied by Better). Keep the spread between tiers meaningful, not cosmetic. One system type per run. Labor scales with the tier and is stated per tier.
Tiers built? Load them into the Proposal Builder along with your price book, and quoting a room becomes one line: "use my Better package for the media room."
This is a template, not a finished product. The tiers are only as good as the price book and the real builds behind them. Run it once per system type, sanity-check the numbers against your last three sold jobs, and save the package library. Update it when your price book changes, not on every proposal.