Building the Catalog Entry for a Brand-New Service Line

Why this matters

Adding a new service to the price book feels simple: name it, price it, tell the office staff. Skip the structure behind those three steps and you get exactly the mess a catalog audit later has to clean up: a service with no clear scope that different techs deliver differently, a price nobody can defend because the cost basis was never worked out, and confusion at the front desk about when to even offer it. Building the entry properly the first time is far cheaper than fixing it after a year of inconsistent delivery.

Step 1: Confirm there is real, repeated demand

Before building anything, verify the service earns a permanent catalog slot rather than staying a one-off custom quote. Look for:

• Repeated requests, tracked from the referral-out or one-off quote log rather than gut feeling.
• A capability match. Do you already have the equipment, licensing, and trained staff, or does adding this service require new investment first?
• A clear customer, not a hypothetical one. "We could probably sell this to someone" is not demand. "Three separate customers asked for this in the last quarter" is.

If demand is thin or unconfirmed, keep quoting it as a custom one-off a while longer rather than building a permanent catalog entry too early.

Step 2: Write the scope of work before naming or pricing anything

The scope is the actual promise to the customer, and it is the piece most often skipped. Write down:

• Exactly what is included, step by step, in enough detail that any qualified tech could deliver the same thing from the description alone.
• What is explicitly excluded. This is what prevents scope creep on the very first job: if a related task is not written as included, it is a separate line item or a change order, not a freebie absorbed into this one.
• Expected duration, so scheduling and dispatch can slot it correctly from day one instead of guessing on the first several jobs.
• Any prerequisite condition (equipment access, another service that must happen first, a site condition that disqualifies the standard scope and requires a custom quote instead).

Step 3: Build the real cost basis

Price before cost is a guess dressed up as a decision. Work out:

• Labor cost, using the actual expected duration from Step 2 against fully loaded labor cost, not just wage rate.
• Material and part cost, including anything consumed even if it is not the headline item (fasteners, consumables, disposal fees).
• Overhead allocation, using whatever method the rest of your catalog already uses so this entry is priced on the same basis as everything else, not a special case.

Step 4: Set the price and the tier placement

• Apply your standard target margin to the cost basis from Step 3, adjusted for anything genuinely unusual about this service (higher liability, specialty equipment amortization, a skill premium for the few techs qualified to run it).
• Decide if it belongs in an existing tier or bundle, or stands alone. See related: Structuring Tiered Service Levels (Good/Better/Best) at Scale.
• Decide the naming approach: generic and instantly recognizable, or a private-label name if the service is differentiated enough to earn one. See related: Private-Label vs Generic Service Naming.
• Set a price range instead of a single fixed price if job-to-job variation is expected to be real, and document what drives the range so a quote does not become an arbitrary number a tech makes up on site. See related: One Price vs a Price Range in the Catalog Decision Tree.

Step 5: Decide visibility and channel

A new entry does not have to go everywhere at once.

• Should it be bookable through self-serve online booking, or does it require a phone conversation because scope varies too much to standardize into a booking form? See related: Catalog Photos and Descriptions for Self-Serve Booking.
• Which locations, if you run more than one, are actually equipped to deliver it today? Don't list it everywhere if only one branch can currently perform the work. See related: Catalog Consistency Across Multiple Locations.

Step 6: Train before you publish

Publish the entry to the catalog only after every tech who might deliver it has seen the written scope and, ideally, shadowed or run one job under it. A service that exists in the price book before anyone has been trained on the exact scope becomes the classic "different tech, different service" problem an audit later has to catch and fix.

Step 7: Set a first-review checkpoint

New entries are the most likely to be mispriced, since the cost basis in Step 3 is a projection, not measured history. Set a checkpoint at a fixed number of completed jobs, or a fixed time window, to compare actual delivered cost and margin against the projection, and correct the price if it is off. Don't wait for the next full catalog audit to catch a new entry that is bleeding margin from day one.

References

• See related: Auditing the Catalog for Dead or Unprofitable Entries
• See related: The Not-in-Our-Catalog Referral-Out Decision Tree
• Trade-standard practice for new service-line rollout
• U.S. Small Business Administration guidance on cost-based pricing