Hourly pricing feels safe until youโre booked solid and still wondering where the profit went. Packages feel risky until you realise they can cap scope, lift margins and make buying easier. If you want the fuller strategic backdrop, cross-reference Pricing Strategy for Your Businesses: The Complete Playbook while you read this.
In this article, weโre going to discuss how to:
- Work out whether hourly or packaged work produces the highest margin in your business
- Reduce scope risk without turning into a contract lawyer
- Use packaging to improve perception and close deals faster
The Real Difference Between Time And Outcomes
Hereโs the simplest framing: hourly sells time, packages sell outcomes. That difference changes everything, from how clients behave to how you staff delivery.
Hourly pricing is a meter. Packages are a promise with boundaries. Both can work, but you need to know what youโre optimising for: utilisation, margin, speed to close, or predictable delivery.
Quick sense-checks:
- If the work is unclear, hourly can be a sensible discovery tool.
- If the work is repeatable, packages should usually win because you can standardise delivery and price for value.
- If the buyer wants certainty, packages remove the fear of an open-ended bill.
- If you need leverage, packages force you to build process and delegation.
When Hourly Wins (Yes, Sometimes)
Iโm not anti-hourly. Hourly pricing can be the right tool when youโre genuinely in โunknown unknownsโ territory or when the client needs ongoing, irregular support.
Good Uses For Hourly
Hourly works best when the client is buying access, not a defined result. Think: troubleshooting, incident response, or advisory where the agenda changes every week.
Examples where hourly is often rational:
- Discovery and diagnostics: Youโre paid to find the real problem before you commit to solving it.
- Volatile priorities: Founder support, rapid hiring, investor prep.
- Unbounded environments: Legacy systems, messy data, multi-stakeholder politics.
The Hidden Tax Of Hourly
The downside is behavioural. Hourly tells the client: โUse less of meโ. It also tells your team: โTake longer and we earn moreโ, which is the opposite of what a good operator wants.
Watch for these warning signs:
- Your best people are rewarded for being slow, not effective.
- Youโre constantly explaining invoices instead of explaining results.
- You canโt forecast revenue unless you forecast hours, which is fragile.
How Pricing Packages Beat Hourly On Margin
Pricing packages usually make more money because they let you price the outcome, not the input. You stop capping revenue at โhours availableโ and start charging for the change you create.
At small scale, margin comes from two things: selling certainty and delivering efficiently. Packages do both if you build them properly.
A Quick Margin Comparison (With Real Numbers)
Letโs run a simple example for a service business.
Hourly model: 25 hours at ยฃ120 per hour = ยฃ3,000 revenue.
Delivery cost: a consultant at ยฃ45 per hour, 25 hours = ยฃ1,125. Gross profit = ยฃ1,875. Gross margin = 62.5%.
Package model: Same outcome priced as a ยฃ4,500 fixed package because it saves the client ยฃ15k in waste, reduces risk, or unlocks growth.
Even if delivery takes 22 hours (because youโre more focused), cost is ยฃ990. Gross profit = ยฃ3,510. Gross margin = 78%.
Thatโs the lever: pricing packages create room for delivery efficiency to show up as profit, not as a smaller invoice.
Packages Also Fix The โCeiling Problemโ
Hourly has a hard ceiling: the number of billable hours you can sell. Packages can scale in three directions:
- Up: Higher value outcomes.
- Out: More buyers through standardisation.
- Down: Delegation and tooling that cuts delivery cost.
Scope Risk: The Bit That Quietly Kills Profit
The honest reason many founders stick with hourly is fear of scope creep. That fear is valid, but itโs solvable. Scope creep doesnโt come from clients being evil, it comes from you selling something fuzzy.
Build Packages Around Inputs You Can Control
You canโt control the clientโs organisation, decision speed or politics. You can control what you produce, how many rounds you include and how much access you provide.
Define your package with boundaries that map to delivery effort:
- Deliverables: Exactly what artefacts the client gets.
- Rounds: 1 to 2 revision cycles, not โuntil youโre happyโ.
- Access: One weekly call, Slack access limited to business hours, responses in 24 to 48 hours.
- Dependencies: โClient provides X by date Yโ so the clock doesnโt become your problem.
Use A Change Control Trigger, Not A Fight
Most scope arguments happen because you make it personal. Make it procedural instead. Agree a trigger upfront.
Example trigger language: โIf we add a new deliverable, expand to another department, or add more than one extra review round, weโll quote a variation within 24 hours.โ
That keeps relationships calm and margins protected.
Perception: Buyers Pay More For Clarity
Perception isnโt fluff, itโs a commercial lever. Hourly pricing looks like โlabourโ. Packages look like โa solutionโ. Buyers pay more for solutions because they reduce decision load and remove fear.
If your service is vaguely described, the buyerโs brain does this: โI donโt know what Iโm buying, so Iโll minimise risk by negotiating price.โ Clear packages do the opposite: โI know what I get, so I can decide quickly.โ
Three Buyer Questions Your Package Must Answer
If you can answer these in a few lines, youโll close faster and discount less:
- What do I get? Tangible artefacts and access.
- What does it change? The business outcome.
- What will it cost me? A fixed price with clear exclusions.
Data To Gather In 2 Hours (Before You Touch Pricing)
Donโt start with a price point. Start with evidence. In most businesses, you can pull enough data in a couple of hours to make a confident call on packages vs hourly.
Internal Signals (Start Here)
Pull these from invoices, timesheets, project notes and Slack threads:
- Median delivery time for your top 10 common jobs.
- Variance: fastest vs slowest delivery time for the same job.
- Rework rate: number of revisions, calls, โquick tweaksโ.
- Gross margin by client: revenue minus direct delivery cost.
- Time sinks: onboarding, reporting, chasing inputs, meetings.
Public Signals (Then Check The Market)
Youโre not copying competitors, youโre understanding the buyerโs frame.
- Competitor packaging: whatโs bundled, whatโs excluded, how itโs named.
- Price anchors: ranges shown on websites or marketplaces.
- Review patterns: what clients praise or complain about, especially around responsiveness and clarity.
Once youโve got this, you can build packages around whatโs repeatable and profitable, not what you โfeelโ should work.
A One-Sentence Offer Template You Can Fill Today
Use this to force clarity and avoid scope creep before it starts:
Offer template: โWe help [type of client] achieve [measurable outcome] in [timeframe] using [method], with [3 included deliverables], for ยฃ[fixed fee].โ
If you canโt fill the brackets without waffling, youโre not ready for a package yet. Start with a paid diagnostic, then package the solution.
Validation In 7 To 14 Days: Small Tests, Fast Learning
You donโt need a big rebrand and a new website to switch. Validate your packaging with small, low-risk tests.
Test 1: Quote Two Ways (Same Lead)
For your next 5 sales conversations, present an hourly option and a package option. Donโt make hourly look terrible, just make the package clearer. Track:
- Close rate by option.
- Time to decision in days.
- Discount pressure: did they ask for money off or scope changes?
Test 2: Sell A โPilot Packageโ
Take your most repeatable project and turn it into a 2-week pilot. Price it slightly higher than the hourly equivalent, but cap the scope tightly. Your goal is to see whether buyers value certainty.
Test 3: Productise One Painful Meeting
If youโre doing the same โstrategy callโ every week, package it as a fixed workshop with outputs. Example: โ90-minute pricing teardown, followed by a 2-page action plan within 48 hours, ยฃ750โ. Itโs a clean test of appetite and willingness to pay.
Completion check: If 3 out of 5 prospects pick the package or accept it without heavy negotiation, youโre onto something.
Unit Economics That Hold At Small Scale
Packages only work if the maths works when youโre small and busy. Donโt assume volume will save you. Build packages that survive on 10 to 50 customers, not 10,000.
A Simple Unit Economics Model
For each package, write down four numbers:
- Price: ยฃP
- Delivery hours: H
- Blended cost per hour: ยฃC (include salary, freelancers, and a realistic overhead allocation)
- Non-delivery time: A (sales, onboarding, admin)
Then calculate:
Direct cost = (H + A) ร ยฃC
Gross profit = ยฃP โ direct cost
Gross margin = gross profit รท ยฃP
As a rule of thumb for a service business, if a package canโt hit 60% gross margin at your current delivery speed, youโre buying yourself a stressful job, not a business.
Price For Variance, Not The Average
Your average delivery time is a lie if variance is high. Price using the 75th percentile time, not the median. That gives you room for real-world mess without eating margin.
Operational Guardrails That Protect Margin And Time
Packaging is as much an ops decision as it is a pricing decision. If you sell fixed scope but deliver like a bespoke agency, youโll get crushed.
Guardrails That Work In Live Ops
- Intake form before kickoff: No form, no start date. It stops โmissing inputsโ becoming your unpaid labour.
- Single point of contact: One client owner who can approve, not a committee.
- Delivery calendar: Fixed slots for calls and reviews so your week doesnโt get shredded.
- Standard artefacts: Templates for plans, reports, handover docs.
- Stoplight tracking: Green, amber, red status on every project, reviewed twice a week.
These guardrails arenโt bureaucracy, theyโre how you keep a promise profitably.
Mini Cases: What This Looks Like In The Wild
Here are three small examples with numbers and the trade-offs made visible.
Micro case 1, Leeds B2B lead-gen agency: They billed ยฃ95 per hour and argued about invoices every month. They launched a ยฃ2,400 โPipeline Sprintโ package capped at 3 campaigns and 2 review rounds. Average delivery time fell from 28 hours to 18 hours because they stopped doing โnice-to-haveโ work, margin improved, and they dropped low-fit clients.
Micro case 2, Edinburgh fractional finance: The founder sold day rates and got stuck in reactive work. He created 3 monthly packages: ยฃ1,250, ยฃ2,500, ยฃ4,000 with defined meeting cadence and board pack output. The ยฃ4,000 tier became the default because it looked like โa proper finance functionโ, not โa person for hireโ.
Micro case 3, London UX contractor: She insisted on hourly because scope was uncertain. She kept hourly for discovery only, then moved delivery to fixed packages: prototype, usability test, handover. Clients stopped micromanaging hours, she hired a junior to run testing, and her effective rate rose above ยฃ180 per hour on the packaged work.
Risks And Hedges: Avoid The Naรฏve Mistakes
Packages can make you more money, but only if you price and run them like a grown-up. Here are the common traps and how to hedge them.
Risk 1: Underpricing Because You Think In Hours
If you anchor on hours, youโll recreate hourly pricing in disguise. Hedge it by anchoring on value, then checking unit economics. Ask: whatโs the cost of the problem staying unsolved for 90 days?
Risk 2: Selling A Package Without A Delivery System
If each project is reinvented, fixed price becomes fixed pain. Hedge it by standardising artefacts and running a weekly delivery rhythm before you scale sales.
Risk 3: Discounting Instead Of Re-scoping
Discounts are permanent, scope is negotiable. Hedge it with a rule: if a buyer asks for 15% off, offer 15% less scope or reduced access instead.
Risk 4: Taking On Low-Quality Inputs
Client chaos is expensive. Hedge it with prerequisites: no kickoff until assets, data, or access are provided. If they canโt meet prerequisites, charge for an onboarding clean-up package.
A Practical Do / Donโt Checklist Before You Switch
Use this as your final sanity check before you rebuild proposals and pricing pages.
- Do: Package the most repeatable 1 to 2 services first, not your entire business.
- Do: Price using the 75th percentile delivery time so variance doesnโt wipe you out.
- Do: Put โincludedโ and โnot includedโ in plain English on the proposal.
- Donโt: Offer unlimited revisions, unlimited calls, or instant responses as a default.
- Donโt: Let the clientโs indecision become your unpaid project management.
Download The Offer Packaging Blueprint And Build Your First Profitable Package
If you want a step-by-step way to turn your best repeatable service into a clean offer with proper boundaries, download the Offer Packaging Blueprint: Turn One Service Into a High-Value Product and use it to build your first package this week, then test it with 5 real conversations.
- Packages beat hourly when you define the outcome, cap the scope and build delivery around repeatable artefacts.
- Validate in 7 to 14 days by quoting both ways, selling a pilot, and checking gross margin against real delivery time and variance.
- Operational guardrails like intake prerequisites, revision limits and change control triggers protect your margin and your calendar.
FAQ For Packages Vs Hourly Pricing
Are pricing packages always more profitable than hourly?
No, but they often are when the work is repeatable and the buyer values certainty. Profit comes from pricing the outcome and delivering efficiently, not from the word โpackageโ on the proposal.
How do I set a package price if Iโve only ever billed by the hour?
Start with your 75th percentile delivery time, multiply by your true blended cost, then add a margin target. Then sanity-check the number against the value of the outcome and what the market anchors look like.
What if the client insists on hourly?
Offer hourly for discovery only, then convert to a fixed package once the scope is known. You can position it as โweโll spend up to ยฃX to define the plan, then Iโll quote a fixed fee to deliver itโ.
How do I stop scope creep on a fixed package?
Define deliverables, rounds and access in plain English, then use a change control trigger that automatically creates a variation quote. It keeps the relationship calm and stops you eating extra work.
Should I offer tiers or one package?
Start with one tight package so delivery is consistent, then add a higher tier once you see where buyers ask for more support. Tiers work best when the difference is access and speed, not a random grab bag of features.
Whatโs the biggest sign my package isnโt working?
If youโre consistently over-delivering and your gross margin is dropping below your target, your scope boundaries are too loose or your delivery system isnโt mature yet. Fix the process first, then raise the price or reduce inclusions.
Author: Pricing & Monetisation