ClientCasa
GuidesPackages

Build a Package

Bundle several charges into one named package you drop into a proposal with a single pick — sold at a flat price or summed from its parts.

A package is a reusable set of line items you sell as one thing — think "Wedding — Gold" or "Monthly Retainer". Under the hood it's a catalog item with composition set to bundle: instead of a single price, it owns the component line items that make it up. Drop a package onto a Quote and all its items come along in one pick. You can sell it at a flat price or let it total up its parts, offer tiers the client picks between, and add-ons they toggle on.

Create a Package

  1. Go to Charges in the sidebar (/dashboard/charges) and open the Packages tab (/dashboard/charges?tab=packages).
  2. Click New package (or Manage packages, then New package).
  3. Give the package a name (e.g. "Wedding — Gold").
  4. Under What's included, add the line items — a description, quantity, unit price, billing frequency, and whether each line is taxable. This is the same row editor the invoice and Quote forms use.
  5. Choose how the package is priced (see below), then click Create package.

Price the Package

A package has two pricing modes, set with the Package price radio buttons:

  • Sum of items — the package price is the total of its components. Change a component's price and the package price follows.
  • Set one price — you enter a fixed package price. ClientCasa compares it to the components total and shows the difference as client saves when the fixed price is lower (a discount) or premium when it's higher.

The editor always shows the components total beneath the radios so you can see the bundle's underlying value as you set a flat price.

Offer Tiers and Add-ons

Each line in a package can play a role in how the client picks options. Open a row's presentation menu (the button on the row) to set it:

  • Base — always included. By default a base line is locked so the client can't remove it (it renders as "Included").
  • Tier option — one of a set the client picks between (Good / Better / Best). Group the alternatives together so the client picks exactly one, and give each a tier label. You can mark one as recommended to highlight it.
  • Add-on — an extra the client can toggle on or off. Set it pre-ticked (an opt-out upsell) or unticked (opt-in).

Lines can also be made client-editable quantity within a min and max — useful for "number of hours" or "extra guests". These selection choices are what drive the totals and what converts into billing when the proposal is accepted.

Drop a Package into a Proposal

Packages surface in the Quote block of a smart file (your proposal):

  1. In the composer at Forms and Agreements (/dashboard/smart-files), add or open a Quote block.
  2. Click Add package and search your saved packages, then pick one. Its component lines are appended to the Quote as new rows, ready to adjust for this client.
  3. Adjust any line, set tiers or add-ons, then send the proposal as usual.

Editing a package later never rewrites a proposal you've already sent — the dropped lines are a snapshot taken at drop time.

You can also work the other way: from the composer's actions menu, Save quote lines as a package bottles the current Quote's line items into a new reusable package.

Let Clients Choose (Interactive Configurator)

By default the client sees the package's resolved configuration as a static "here's what I'm proposing" list. To let them configure it themselves, turn on Let the client choose options at the bottom of the Quote block (off by default).

When it's on, the public proposal page renders tier cards, add-on toggles, and quantity steppers with a live total. The client's picks are saved back before they accept — so what they configured is exactly what gets billed. See Accept a Proposal for what happens on acceptance.

Track How Packages Perform

The Packages tab on the Charges page is also a read surface for attach-rate insights. For each package it shows:

  • Price and component count.
  • In proposals — how often the package has been dropped into a proposal, with how many of those were won.
  • Win rate — the share of proposals using a package that were accepted.
  • Add-on take — how often the package's add-ons are selected.
  • Revenue — total from won proposals, and the date the package was last used.

These numbers come from real Quote usage, so they fill in as you send proposals with packages.

Via the API

Packages are catalog items with composition: "bundle". The Catalog Items API returns each item's composition, bundlePriceMode, and bundleFixedPrice. A package's component line items are managed in the dashboard rather than through the API.

On this page