Executive summary
Packaging and tiering means turning a custom services offer into a small number of defined packages, or services pricing tiers. Each package has a stated scope, a price, a delivery model, and clear boundaries (fences) that say what moves a customer from one package to the next. Add-ons cover anything outside the box. The result is a price list a salesperson can quote in one conversation and a delivery team can staff against.
The case for doing it is margin visibility and control. When every engagement is quoted from scratch, you cannot tell which kinds of work earn money, discounts are negotiated as a lump, and a scope overrun looks like a delivery problem instead of a pricing problem. When engagements fit into packages, you can compute margin per package, margin per delivery hour, and mix. You can then decide, with numbers, which package to lead with and where to raise or drop price.
This page covers the choice of value metric, how to build three tiers, how to check each tier against cost and capacity, how to handle scope change, and how to measure whether the packaging works. It sits beside Price Waterfall Analysis, which shows where list price leaks, and Discount Approval Matrix and Governance, which protects the prices you set here.
When to use this
Use packaging and tiering when:
- Most proposals are priced by estimating hours and applying a blended rate, and no two look alike.
- Margin varies widely between engagements of the same type, and nobody can say why.
- Reps and partners discount fees to win work and the discount is not tied to scope.
- Delivery teams absorb scope creep without billing for it.
It is less useful for genuinely one-off, bespoke work, though a rate card and standard add-ons still help.
Diagnostic questions
Answer from your project accounting system, proposals, and time records.
- How many distinct engagement types did you sell in the last 12 months, and what share of revenue does each represent?
- For each type, what are the actual delivered hours, the loaded cost per hour, and the realized price per hour?
- What is the spread in gross margin across engagements of the same type, and what explains the best and the worst?
- How often does actual effort exceed the estimate, by how much, and who absorbs it?
- What is billed as change orders versus absorbed as unbilled work?
- What do customers say they are buying: hours, outcomes, risk reduction, speed, or access to people?
- Which customers would pay more for faster delivery, higher service levels, or senior staff, and which want the minimum?
- How is the proposal priced today: time and materials, fixed fee, retainer, or a mix, and does the choice follow any rule?
- How much capacity (delivery hours by skill level) do you have, and how is it utilized?
- How are discounts applied to services fees, and do they reduce scope or just reduce price?
- Which contract terms (acceptance, warranties, termination, change order language) apply to a standard engagement, and has counsel reviewed the standard package terms?
Question 4 and question 5 together measure how much margin you are leaking to unscoped work. That is often the first thing the packaging can fix.
Framework: metric, tiers, fences, add-ons
1. Value metric: what the price scales with
A value metric is the unit the price scales with. Choose one that grows when the customer gets more value and when your cost to serve grows. Common choices in services:
| Metric |
Fits when |
Risk |
| Hours or days |
Work is truly effort-driven and unpredictable |
Rewards slowness, punishes efficiency |
| Deliverables or outcomes |
Scope can be defined, outcome is visible |
Scope disputes if deliverables are vague |
| Sites, entities, users, or locations |
Effort scales with these |
Edge cases need rules |
| Service level (response time, coverage) |
Customers value availability |
Capacity must match promises |
The best metric tracks your cost drivers and is easy for the customer to forecast. If effort mostly scales with the number of entities, price by entity and keep hours as an internal cost measure.
2. Tiers: three packages, not seven
Three tiers is the usual starting point. The middle tier is the one you want most customers to choose, the lower tier is the entry point and a reference for value, and the top tier anchors the range and serves customers who need more. Each tier should be defined by what the customer receives, not just a price:
| Element |
Essential |
Standard |
Premium |
| Scope |
Core deliverables only |
Core plus configuration, training, and reporting |
Standard plus integration, advisory, and executive reviews |
| Delivery model |
Standard playbook, junior-led |
Standard playbook, senior oversight |
Tailored plan, senior-led |
| Service level |
Business hours |
Priority response |
Named lead, defined response commitments |
| Change handling |
Add-ons at rate card |
Limited change allowance |
Larger change allowance |
The tiers must differ on dimensions that matter to different customers, otherwise the tiers are just three prices. Every tier should have a margin target and a capacity plan, set before launch.
3. Fences: why customers move up
A fence is a rule that makes a lower tier unattractive for customers who would get more value from a higher one. Good fences are about scope and service, not artificial limits:
- Scope fences: number of entities, sites, workflows, or deliverables.
- Service fences: response times, named contact, frequency of reviews.
- Term fences: annual commitments unlock the middle tier price; month to month is priced higher.
- Resource fences: seniority of the delivery team.
4. Add-ons and change orders
Everything outside the tier goes on a rate card of add-ons at a stated price, and a change-order process handles work that appears during delivery. An add-on is priced from cost and value. A change order is priced from the rate card and the effort it needs. Both need contract language that allows them, which is a matter for counsel and your own standard terms.
How to price each tier
Pricing a package uses three inputs: cost to deliver, value to the customer, and market position. Cost sets the floor, value sets the ceiling, and market position (what alternatives cost and how your offer compares) sets where in the range you sit.
Cost floor.
Package cost = Planned delivery hours × Loaded cost per hour + direct expenses + a contingency for estimate risk
Package margin % = (Price − Package cost) ÷ Price
Use loaded cost per hour: salary, benefits, and overhead allocation per billable hour at the utilization you actually achieve, not the utilization you hope for. Use the estimate from the last several comparable engagements, using actual hours, not the hours you sold.
Value ceiling. Ask what the customer saves or gains from the outcome. Where the result is quantifiable (hours saved, errors avoided, cash released), the price should be a fraction of the value. Where it is not, use the next-best alternative: what the customer would pay to do it in-house or with another provider.
Fixed fee versus time and materials. A fixed fee transfers estimate risk to you and rewards efficiency. Time and materials transfers it to the customer. A package is a fixed fee, so base the estimate on actuals, add a contingency, and write scope assumptions into the package. Where scope is genuinely uncertain, use a paid discovery phase before committing to a price.
Step-by-step process
Weeks 1 to 2: Baseline
- List engagement types and compute actual economics for the last 12 months: revenue, hours, loaded cost, gross margin, and realized price per hour. Owner: FP&A with Delivery lead. Output: engagement economics table.
- Measure scope leakage. Estimated versus actual hours and the amount billed as change orders. Owner: Delivery lead. Output: leakage summary.
- Interview customers and lost prospects on what they buy and compare you to. Owner: Head of Sales. Output: value-driver notes.
- Document capacity by skill level and utilization. Owner: COO or Delivery lead. Output: capacity table.
Weeks 3 to 4: Design
- Choose the value metric. Owner: CEO or Head of Sales with the CFO. Output: written metric and the reason.
- Define three tiers: scope, delivery model, service level, and fences. Owner: Delivery lead and Head of Sales. Output: package definitions.
- Cost each tier from actual hours and loaded cost. Owner: FP&A. Output: cost and margin per tier.
- Set prices between the cost floor and the value ceiling, and test price ratios between tiers. Owner: CFO and Head of Sales. Output: price list and margin per tier.
- Write the add-on rate card and change-order process. Owner: Delivery lead with Legal. Output: rate card and a change-order template.
Weeks 5 to 8: Pilot
- Pilot with new proposals in one segment or region. Track win rate, discount, and chosen tier. Owner: Head of Sales. Output: weekly pilot log.
- Track delivery against package hours for the first engagements. Owner: Delivery lead. Output: actual hours versus package hours.
- Adjust fences and prices based on early evidence. Owner: CFO and Head of Sales. Output: revised package sheet.
Weeks 9 to 12: Roll out
- Train sales and delivery on the packages, the fences, and the change-order process. Owner: Head of Sales and Delivery lead. Output: training done and a one-page guide.
- Update proposal templates and the quoting tool, so proposals start from a package. Owner: Sales Ops. Output: templates. See CPQ and Quote Discipline.
- Set the review cadence. Monthly: tier mix, margin by tier, scope leakage, discount by tier. Owner: CFO. Output: first review minuted.
Templates
Package definition sheet (copy into a spreadsheet)
| Element |
Essential |
Standard |
Premium |
| Customer profile |
|
|
|
| Value metric and quantity |
|
|
|
| Deliverables |
|
|
|
| Delivery model and seniority mix |
|
|
|
| Service level |
|
|
|
| Planned hours |
|
|
|
| Loaded cost per hour |
|
|
|
| Package cost |
|
|
|
| Price |
|
|
|
| Margin % |
|
|
|
| Fences |
|
|
|
| Change allowance |
|
|
|
| Standard terms reviewed by counsel (Y/N) |
|
|
|
Add-on rate card
| Add-on |
Unit |
Price |
Planned hours |
Margin % |
Available to tier |
Scope assumptions (for every package)
What the customer provides, what is excluded, how many review rounds are included, what triggers a change order, and the acceptance criteria.
Metrics and KPIs
| Metric |
Formula |
Data source |
| Gross margin by tier |
(Revenue − delivery cost) ÷ revenue |
Project accounting |
| Gross profit per delivery hour |
(Revenue − delivery cost) ÷ hours |
Project accounting and time |
| Realized price per hour |
Revenue ÷ delivery hours |
Project accounting |
| Tier mix |
Engagements or revenue by tier ÷ total |
CRM |
| Estimate accuracy |
Actual hours ÷ package hours |
Time records |
| Scope leakage |
Unbilled hours beyond package ÷ package hours |
Time records and billing |
| Discount by tier |
Discount $ ÷ list $ in each tier |
CRM and invoices |
Targets by method. Set the margin target for each tier from your own best trailing engagements of that type, and treat the loaded cost per hour as the floor below which you do not sell. Set estimate accuracy targets from your own last twelve months of actual versus estimate. Do not copy a margin or utilization target from a survey.
Common mistakes
- Pricing from hours at a blended rate. It hides the difference between junior and senior work and between predictable and unpredictable engagements.
- Too many tiers. More than three or four creates choice paralysis and a quoting problem.
- Tiers that differ only in price, or no fences. Customers who need Standard will buy Essential, and you have created a discount.
- Estimating from what was sold, not what was delivered. If the last five Standard engagements took more hours than the package assumed, the package is underpriced.
- Absorbing scope creep. Unbilled changes turn a 50% margin package into a 40% one without anyone seeing a decision. See the worked example.
- Ignoring capacity. A mix shifted to the top tier may need more senior hours than you have.
- Standard terms that no one has reviewed. Acceptance, warranty, change order, and termination language is a legal matter. Follow your own agreements and have counsel review the package terms.
- Never revisiting prices. Review tiers when loaded cost per hour changes, using the approach in Price Increase Playbook.
Worked example
Illustrative. All numbers are made up to demonstrate the method. They are not benchmarks.
A services firm has a loaded delivery cost of $85 per hour and defines three packages.
| Tier |
Price |
Planned hours |
Delivery cost |
Gross profit |
Margin |
Price per hour |
Gross profit per hour |
| Essential |
$60,000 |
400 |
$34,000 |
$26,000 |
43.3% |
$150.0 |
$65.0 |
| Standard |
$110,000 |
640 |
$54,400 |
$55,600 |
50.5% |
$171.9 |
$86.9 |
| Premium |
$185,000 |
960 |
$81,600 |
$103,400 |
55.9% |
$192.7 |
$107.7 |
Price steps. Standard costs 1.83 times Essential ($110,000 ÷ $60,000) for 1.6 times the hours (640 ÷ 400). Premium costs 1.68 times Standard for 1.5 times the hours. Price rises faster than effort, which is what makes the upper tiers worth selling and gives customers a reason to move up for the added service level.
Current mix. A year of 30 engagements: 10 Essential, 14 Standard, 6 Premium.
- Revenue: 10 × $60,000 + 14 × $110,000 + 6 × $185,000 = $600,000 + $1,540,000 + $1,110,000 = $3,250,000.
- Hours: 4,000 + 8,960 + 5,760 = 18,720.
- Delivery cost: 18,720 × $85 = $1,591,200.
- Gross profit: $1,658,800, a margin of 51.0%, or $88.6 per hour.
Target mix. After a year of fences and positioning, the plan is 6 Essential, 14 Standard, 10 Premium.
- Revenue: $360,000 + $1,540,000 + $1,850,000 = $3,750,000.
- Hours: 2,400 + 8,960 + 9,600 = 20,960.
- Delivery cost: 20,960 × $85 = $1,781,600. Gross profit $1,968,400, margin 52.5%, $93.9 per hour.
The shift adds $500,000 of revenue and $309,600 of gross profit, but needs 2,240 more delivery hours, and the added hours are the senior-led Premium work. If the senior team has no spare capacity, the target mix is not available, and the right move is to raise the Premium price or add senior capacity first.
Scope creep. Suppose a Standard engagement runs 20% over: 768 hours instead of 640. Cost becomes 768 × $85 = $65,280, and the margin falls from 50.5% to ($110,000 − $65,280) ÷ $110,000 = 40.7%. If the 128 extra hours are out of scope and billed through a change order at a rate card price of $165 per hour, revenue becomes $110,000 + $21,120 = $131,120, and the margin is ($131,120 − $65,280) ÷ $131,120 = 50.2%. A change order process nearly restores the margin. Absorbing the overrun costs nearly ten points.
What the example says: the tiers have different margins and different capacity needs, so mix matters as much as price. And the biggest controllable leak is scope that is delivered but not billed.
AI prompt assistance
Provide your own data and verify the output against project accounting before using it in a price list.
1. Compute engagement economics.
I will paste a CSV of 12 months of completed engagements with revenue, hours by role, loaded cost per hour by role, and engagement type. Compute gross profit, gross margin, realized price per hour, and gross profit per hour by engagement type. Flag engagements where actual hours exceeded estimated hours by more than 15%.
Check: tie total revenue and hours to project accounting and recompute one engagement by hand.
2. Group customer interview notes by value driver.
Here are notes from 15 customer interviews and 5 lost-deal calls. For each, tag what the customer said they were buying (outcome, speed, risk reduction, access to senior people, price), what they compared us to, and what would make them move to a higher or lower package. Quote the sentence supporting each tag.
Check: confirm quotes against the source notes and do not treat a count of tags as a statistic.
3. Test package prices against cost.
For the three packages below, with planned hours by role, loaded cost per hour by role, and prices, compute package cost, gross profit, margin, and gross profit per hour. Then show margin if actual hours run 10%, 20%, and 30% over plan, with and without change-order billing at $165 per hour for the overrun.
Check: verify two scenarios manually, and confirm the loaded cost per hour comes from finance, not from the model.
Implementation guide
| Phase |
Weeks |
Owner |
Exit criteria |
| Baseline |
1-2 |
FP&A and Delivery lead |
Engagement economics, scope leakage, customer interview notes, capacity table |
| Design |
3-4 |
CFO, Head of Sales, Delivery lead |
Value metric, three packages, prices, add-on rate card, change-order template |
| Pilot |
5-8 |
Head of Sales |
One segment quoting from packages; actual hours tracked; prices and fences adjusted |
| Roll out |
9-12 |
Head of Sales and Sales Ops |
Teams trained; proposal templates updated; monthly review running |
Governance: the CFO owns price and margin targets, the Head of Sales owns the packages in market, the Delivery lead owns estimates and scope control, and Legal owns standard terms. Report tier mix, margin by tier, gross profit per hour, and scope leakage monthly.
What to expect: the margin effect appears over two to three quarters as engagements complete and actual hours are compared to plan. Do not change the tiers on a single engagement's result.
Downloadable assets
The package definition sheet, add-on rate card, scope assumptions list, and review agenda above are designed to be copied into a spreadsheet. The EBITDA improvement calculator can translate a change in gross margin into EBITDA. The price waterfall builder computes list-to-pocket leakage from your own figures.
Related resources
Frequently asked questions
What is packaging and tiering in services pricing?
Packaging and tiering means defining a small number of services packages, each with a stated scope, delivery model, service level, and price, plus fences between them and add-ons for extras. It replaces pricing every engagement from scratch. The aim is margin visibility, faster quoting, and a clear way to say yes to extra work at a price.
How many tiers should a services firm offer?
Three is the usual starting point: an entry tier, a middle tier that most customers should choose, and a top tier that anchors the range. More than four tiers usually produces confusion in selling and complexity in delivery. Add tiers only when a distinct customer need cannot be served by the existing three.
Should I use fixed fee or time and materials?
Use a fixed fee for packaged work where the scope can be defined and your estimates are based on actual hours, and time and materials where effort is genuinely uncertain. A paid discovery phase can size uncertain work before a fixed price is set. A fixed fee shifts estimate risk to you, so write scope assumptions and a change-order process.
How do I stop scope creep from eating margin?
Write scope assumptions and exclusions into every package, price add-ons on a rate card, and use a change-order process for work that appears during delivery. Track unbilled hours beyond package hours by engagement. In the illustrative example, absorbing a 20% overrun cut margin by about ten points, and billed change orders restored most of it.
How do I set the price for each tier?
Set the floor from cost: planned hours times loaded cost per hour, plus direct expenses and a contingency. Set the ceiling from the value to the customer or the next-best alternative. Then position the price within that range and check margin per hour and capacity for each tier. Revisit prices when loaded cost per hour changes.
How this works in a System of Performance
Packaging only pays if you can see what each package earns after delivery. In most services firms that picture is split across the CRM, the time system, project accounting, and billing. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want to see which of your engagements earn what you think they earn, bring it to us as a launch partner.