A client emails: "What's your day rate for an on-site workshop?" You've never quoted one before. Your instinct is to multiply your hourly rate by eight and hit send — and that instinct is about to cost you money.
A day rate isn't "hourly × 8." It's its own pricing model, sitting between hourly billing and a flat project fee, and it solves a problem neither of those handles well: pricing a single day of your full attention. Create a clean invoice for the engagement → — free PDF generator, no signup, works for a single day-rate line item just as well as a full project.
What a Day Rate Actually Is
A day rate is a fixed price for one day (or half-day) of your time, regardless of exactly how many hours that day runs long or short. It's common for workshops, on-site consulting, audits, strategy sessions, and short engagements where "how many hours will this take" is the wrong question to be asking in the first place.
It's not the same as hourly billing, where every hour is tracked and billed separately. And it's not the same as a flat project fee, where the price covers a whole deliverable no matter how many days it takes. A day rate sits in between: the unit is the day, not the hour or the project.
The Formula (Don't Just Multiply by 8)
Here's where the "hourly × 8" instinct breaks down: a billed day isn't 8 fully billable hours. Travel, setup, prep the night before, follow-up notes, and the simple fact that nobody does 8 focused hours of client work without a single interruption all eat into it.
Day Rate = (Hourly Rate × Realistic Billable Hours per Day) × (1 + Buffer)
Break that into three pieces:
- Hourly rate — your normal, defensible hourly number. If you don't have one yet, work that out first; the day rate formula only holds up if the hourly number underneath it is honest.
- Realistic billable hours per day — we'd suggest budgeting 5 to 6, not 8. An on-site day includes travel, small talk, setup, and context-switching that a pure hourly gig wouldn't bill for, but a client expects you to be "there" for. (This is a working rule of thumb, not a published statistic — adjust it to match your own actual on-site days.)
- Buffer — 15-25% on top, to cover prep the day before and follow-up after (notes, a summary email, next steps). That work isn't part of the billed day itself, but it's real work you did because of it.
Worked example: your hourly rate is $100. You bill 6 realistic hours for an on-site day, and add a 20% buffer for prep and follow-up.
$100 × 6 = $600, then $600 × 1.20 = $720 for the day.
Compare that to the naive version — $100 × 8 = $800 — and notice the naive number is actually higher. That's not a mistake. The naive multiply-by-8 approach overcounts billable hours but skips the buffer entirely, so it can land anywhere relative to a properly built day rate. The point isn't that day rates are always cheaper or more expensive than hourly × 8 — it's that guessing gets you the wrong number in either direction. Do the math instead.
When a Day Rate Wins
A day rate is the right tool in a specific, recognizable set of situations:
- On-site work. You're physically present for a client, and hour-by-hour tracking would be awkward or impossible to enforce anyway.
- Workshops, training, and facilitation. The value isn't "hours worked," it's "did the workshop happen and land well." A day rate matches how the client is actually thinking about it.
- Audits and short diagnostics. A one- or two-day engagement to assess a codebase, a marketing funnel, or a business process. Scoping this by the hour invites the client to negotiate every hour; a day rate ends that conversation before it starts.
- You want to stop justifying hours. Some clients micromanage hourly timesheets — asking why a task took 45 minutes instead of 30. A day rate removes that friction entirely. You showed up, you delivered, the price was agreed before you walked in.
- Agencies and consultants scoping short engagements. When a project is genuinely 1-5 days of work, day-rate math is simpler for both sides than building an hourly estimate and hoping it holds.
When Hourly Still Wins
Day rates aren't a universal upgrade. Stick with hourly when:
- The engagement is ongoing or open-ended — retainer-style support, bug fixes, small recurring tasks. There's no clean "day" to price; hourly (or a monthly retainer) fits better.
- The work is remote and asynchronous. If you're not physically present and the client can't observe a "day" happening, hourly with clear time logs is more transparent for both sides.
- The scope is genuinely unpredictable hour to hour. Some days you'll do 2 hours of real work, other days 9. If that variance is the norm, forcing it into a fixed day rate either underpays you or overcharges the client depending on the day.
- You're new to the client relationship. Hourly with visible time tracking builds trust before you're comfortable quoting a flat day price with confidence.
Day Rate vs Hourly vs Flat Fee, Side by Side
| Hourly | Day Rate | Flat Project Fee | |
|---|---|---|---|
| Unit priced | Each hour | Each day | The whole deliverable |
| Best for | Ongoing, unpredictable, remote work | On-site work, workshops, short diagnostics | Well-scoped deliverables (websites, logos, reports) |
| Client sees | A running total | One number per day, known in advance | One number, known in advance |
| Your risk | Low — every hour is paid | Moderate — a long day costs you | Higher — scope creep eats your margin |
| Efficiency reward | None — faster work earns less | Some — a short day still pays the full rate | Full — finish faster, keep the difference |
If you already default to flat fees for defined deliverables, the flat-fee vs hourly guide covers that decision in more depth. A day rate is really the third leg of that same stool — the specific case where the natural unit is neither an hour nor a whole project, but a day.
How to Quote a Day Rate to a Client
Keep it simple and confident. You don't need to show your math — just state the number and what it includes.
"My day rate for on-site workshops is $720, which covers the session itself plus prep beforehand and a written summary afterward. For a two-day engagement, that's $1,440. I'll send a proposal with dates once we confirm scope."
Two things worth naming up front: what counts as "a day" (a standard 6-8 hour on-site block, not sunrise to sunset). And what happens if the client wants to extend it — bill the overage at an agreed hourly rate, stated in advance, rather than discovering it in the moment.
Common Mistakes with Day-Rate Pricing
- Multiplying hourly × 8 with no buffer. As the worked example above shows, this either overcounts your actual billable hours, undercounts your prep/follow-up time, or both — the naive math doesn't reliably land in your favor.
- Not defining what "a day" means. Without a stated range (say, 8am-4pm), a client can reasonably expect a 10-hour day for the same price.
- Forgetting travel time on multi-day, out-of-town engagements. Either build travel days into the quote explicitly or price them separately — don't let them quietly become unpaid.
- Using a day rate for genuinely unpredictable work. If some days are 2 hours and others are 10, a fixed day rate is the wrong tool; go back to hourly until the work stabilizes.
Quick Decision Checklist
- Is the client physically on-site with you, or is the work a discrete workshop/session? → Day rate.
- Is the engagement short (1-5 days) with a clear start and end? → Day rate.
- Is the work ongoing, remote, and hard to bound to "a day"? → Hourly.
- Is it a full deliverable you can scope end-to-end? → Flat project fee — see the flat-fee vs hourly guide.
- Are you new to this client and still building trust? → Hourly first, day rate once the relationship is established.
Frequently Asked Questions
How many hours should I count as "a day" for pricing purposes?
Budget 5-6 realistic billable hours for an on-site day, even if the client is physically present for 8 — that's the rule of thumb this guide uses in the formula above, not a fixed rule. The gap accounts for setup, breaks, and context-switching that happen on any real workday but aren't pure focused output.
Should I charge for travel days separately from the day rate?
Yes, for anything requiring an overnight stay or significant travel time. Either quote a separate (often reduced) travel-day rate or fold it into the total as a distinct line item — just don't leave it unstated and hope the client assumes it's included.
Is a day rate the same as a "per-diem"?
No. A per-diem typically covers expenses (meals, incidentals) during travel, on top of whatever you're being paid for the work itself. Your day rate is the price for your work; a per-diem, if one applies, is separate and usually set by the client's own travel policy.
Can I offer a discount for multi-day bookings?
You can — a modest reduction (5-10%) for booking 3+ consecutive days is a reasonable option to consider, since it reduces your own scheduling and prep overhead per day. Just don't discount so deeply that a 5-day booking pays less per day than your floor allows.
Put the Math to Work
Take your honest hourly rate, multiply by 5-6 realistic hours, and add a 15-25% buffer for prep and follow-up. That gives you a day rate you can quote with confidence — no guessing, no "hourly × 8" shortcut that quietly shortchanges either side. Once the engagement's confirmed, the free invoice generator turns that day rate into a clean, professional invoice in under a minute — no signup required.
Sources
- Plutio, Freelance Pricing Models Compared: The 2026 Playbook — general overview of cost-plus-buffer and day-based pricing approaches for freelancers (plutio.com).