Good, Better, Best: Estimate Packages That Help Customers Choose

A customer gets one estimate with one number and one decision: yes or no. That is tidy, but so was the fax machine. Estimate Packages let a Local Business Pro operator present distinct, selectable scopes with their own included work, totals, discounts, tax treatment, deposits, and eligible membership choices. Good-better-best is a useful way to organize those options, not a rule that every proposal needs exactly three. The customer chooses an active package before approval, and the selected scope can move into configured agreement, payment, job, and invoice steps. Those steps still depend on the estimate’s settings.

A package is real scope—not a prettier subtotal

An Estimate Package is a named option built from selected estimate line items. Each option can have a customer summary, included work, display order, recommendation or default state, and calculated terms.

That distinction matters. If “Good,” “Better,” and “Best” all contain the same services under three decorative headings, the customer does not have three choices. They have one choice wearing different hats.

Start with reusable lines from Pricebook Services, products, equipment, fees, or other valid estimate items. Decide which lines belong in each option; the package keeps them together and calculates that scope’s total.

Use one active package when the job has one clear path, or several when the customer has a real decision. Multiple active choices require a valid selected or default package before approval. Archived or unavailable options do not wander back into the deal like a salesperson who missed the meeting.

Build choices customers can actually compare

Good-better-best works when each package answers a different version of the customer’s problem.

Good: solve the immediate problem

The “good” option covers the defined need with a complete, workable scope. It is not code for “bad,” and it should not omit work the job genuinely requires.

For an HVAC replacement, that might be the code-compliant equipment replacement and the work required to install it. For an electrical panel project, it might be the panel replacement without the additional protection or broader service upgrade included in other options.

Better: add a useful layer

The “better” option can add durability, efficiency, comfort, coverage, or another clearly described outcome. The reason belongs in the customer summary, not buried in an internal note.

An arborist proposal could pair tree removal with stump grinding. A plumbing proposal could move from repair to replacement. The option is different because the work is different—not because somebody made the heading blue.

Best: complete the broader outcome

The “best” option can address the larger project: HVAC equipment plus indoor-air or control improvements, a panel replacement plus surge protection and a broader service upgrade, or tree removal with grinding and cleanup.

“Recommended” is a presentation choice, not proof that one package is objectively safest or right for every customer. Operators still need to explain why an option fits the property, the requested outcome, and the actual conditions.

Price, tax, discount, deposit, and membership rules stay attached

Each package can carry the terms needed to understand that option:

• a calculated total based on its included estimate lines;
• fixed or percentage discount treatment;
• taxable and non-taxable scope;
• a fixed or percentage deposit requirement, including supported inherited settings;
• a customer summary and recommendation or default state; and
• an eligible membership plan when that path is configured.

The important word is configured. A package does not automatically need a deposit, agreement, membership, or payment step. If a package includes an eligible recurring plan, the linked service agreement, provider, and payment setup still govern enrollment. Selecting an option is not the same as activating a membership.

The customer proposal displays active choices and included scope. One active package avoids an unnecessary choice; multiple active packages require a valid choice or default so approval uses the correct terms.

What happens when the customer chooses

The selected package becomes the estimate’s approved scope: its included lines, total, deposit terms, and applicable requirements are the terms that move forward.

From there, the estimate-to-job revenue workflow follows the business’s configuration. A required signature, linked agreement, deposit, or full payment can pause approval until that condition is satisfied. Configured approval behavior may create a job, a draft invoice, or a deposit invoice using the selected scope. It is not accurate to say every approved estimate always creates both a job and an invoice.

Once approved, package changes are locked while the chosen option remains readable. That protects the accepted scope from casual edits after the customer has signed or paid. If somebody needs to alter the work later, the answer is not to quietly rewrite yesterday’s option.

For the full approval sequence, see what happens after the customer chooses.

Four realistic package workflows

HVAC replacement

Create a code-compliant replacement, an option with efficiency or comfort improvements, and a broader indoor-air or controls package. Each card needs different services and its own total. No structure guarantees the customer’s selection.

Electrical panel upgrade

Present panel replacement, panel plus surge protection, and a broader service upgrade. Configure any signature or deposit requirement explicitly and preview it in the customer flow.

Arborist tree-care proposal

Use separate scopes for removal, removal plus stump grinding, and removal with grinding and cleanup. Do not present optional lines as legal or safety requirements unless the job and qualified professional support that conclusion.

Plumbing water-heater decision

Offer repair, standard replacement, and a higher-spec replacement using shared service lines where appropriate. If one includes a membership, confirm plan eligibility and agreement and payment setup.

Where packages stop and change orders begin

Packages organize choices before approval. They help the customer select the scope they want from the active options on the estimate.

When conditions change after the job exists—hidden plumbing damage, an electrical discovery, an added tree hazard, or revised ductwork—use the change-order workflow for changed scope. A change order documents the later addition or adjustment without pretending it was part of the package the customer originally approved.

That clean dividing line keeps the proposal honest: packages answer “Which planned scope do you want?” Change orders answer “What changed after the work was approved?”

Safeguards for the operator

Estimate Packages include a few boundaries worth respecting:

• Staff need the relevant estimate access to manage package choices.
• A default must be active, and the last usable selected or default option cannot be removed casually.
• Public customer actions use the valid shared estimate link and reject stale or unavailable choices.
• Agreement and payment requirements follow the selected package and current configuration.
• Package scope locks after approval while the approved choice remains available for review.

These keep “customer chose Option B” from turning into an afternoon of interpretive accounting.

Frequently asked questions

What is a good-better-best estimate?

It is a proposal pattern that presents meaningfully different scopes as customer options. In Local Business Pro, each package can include its own estimate lines, total, summary, and commercial terms.

Does Local Business Pro require exactly three packages?

No. A proposal can use one or more active packages. Good-better-best is practical editorial guidance, not a fixed product rule.

Can each package include different services?

Yes. Each package can select a different subset of valid estimate lines, which gives every option its own scope and calculated total.

Can a package require a deposit or agreement?

Yes, when those requirements are configured. They are not mandatory for every package, and membership enrollment still depends on eligible plan, agreement, provider, and payment setup.

What happens after the customer selects a package?

The chosen lines and terms become the approved estimate scope. Signature, agreement, payment, job, and invoice behavior then follow the estimate’s configured workflow.

Build the first set around a decision customers already face

Choose one common estimate where customers genuinely weigh different scopes. Build the options from valid line items, make the differences obvious, set the active/default choices, confirm any deposit or agreement requirements, and preview the public proposal before sending it.

The practical guide to create and send an estimate is a good next stop. One well-built option set will teach the team more than twenty theoretical packages collecting dust.