billable.devDay Rate vs Hourly Rate for Developers: Which to Quote
By Mark Fulton · · 12 min read
Last verified:
A day rate is a fixed price for a defined block of your time, and for most development work it beats an hourly rate once an engagement runs a week or more. Convert it from your hourly floor by multiplying by the hours you will actually deliver (usually 7, not 8), then add a premium of 10 to 20 percent for the context switching and lost flexibility a booked day costs you. Use hourly for small, unpredictable tasks and short advisory work. Use a day rate when a client is buying your focus for whole days: sprints, embedded contracts, audits, migrations. Put the day's length, the half day rate, and the overrun rule in writing before the first day starts, and the rest is arithmetic.
When does a day rate beat hourly for development work?
A day rate wins when the client is really buying your attention, not a count of keystrokes. That describes more development work than people expect.
Sprint-shaped work. A client wants you for three days a week for a month. Tracking 5.5 hours here and 7.25 hours there across those days produces an invoice nobody enjoys reading and a timesheet nobody trusts. Three days at a day rate is one line.
Embedded contracts. You join standups, review pull requests, answer messages, and ship in between. Plenty of that time never lands in a time tracker, and hourly billing quietly penalises you for being available.
Workshops, audits, and migration days. The deliverable is a day of your judgment. Whether the audit finished at 3:40 or 5:15 does not change what the client received.
Clients who dislike open meters. Some buyers get nervous watching hours accumulate. A day is a unit they can budget: five days is a number they can put in a spreadsheet. The same reasoning is behind the hourly versus fixed price trade-off covered in hourly vs fixed price billing for developers.
Hourly still wins in three places. Quick fixes under about two hours, where a day rate would be absurd. Support work with wildly uneven demand, ten hours one week and two the next. And any engagement where the scope is genuinely unknown and you want every hour of discovery paid at your full rate.
If the scope is clear and the client cares about total cost more than your time, a project price may beat both. A day rate sits in the middle: it fixes your price per unit of time without pretending to know the total.
How do you convert an hourly rate into a day rate?
Start from your floor rate, the number your year requires. If you have not worked that out, freelance developer hourly rates walks through the math from a target income, and this post continues from there. That worked example lands on a floor of about $170 an hour, so I will use $170 below. These are illustrative placeholders, not market data. Replace them with your own.
The conversion has three inputs:
- Your hourly rate. The floor, or the rate you actually quote.
- The length of the billable day. Hours of real delivery, usually 6 to 8.
- A premium. What you charge for committing a whole day to one client.
The formula is: day rate = hourly rate x hours in the day x (1 + premium).
Here is that table at $170 an hour. Every cell is just the formula run forward:
| Hours in the day | No premium | 10% premium | 20% premium |
|---|---|---|---|
| 6 hours | $1,020 | $1,122 | $1,224 |
| 7 hours | $1,190 | $1,309 | $1,428 |
| 8 hours | $1,360 | $1,496 | $1,632 |
Pick one cell, then round it to a number a client can say out loud. A 7 hour day with a 10 percent premium comes out at $1,309, so quote $1,300. A client who hears "thirteen hundred a day" does not need to do arithmetic.
The half day rate comes off the same table. Take 60 to 65 percent of the full day rate, not 50, for reasons covered below. At $1,300 that is $780 to $845.
The conversion, written as a quote
| Item | Calculation | Result |
|---|---|---|
| Hourly floor | from your own numbers | $170 |
| Billable day | 7 delivery hours | 7 hours |
| Base day | $170 x 7 | $1,190 |
| Premium | 10 percent | $119 |
| Day rate (rounded) | $1,309 rounded down | $1,300 |
| Half day (60 percent) | $1,300 x 0.60 | $780 |
Check the result against the year, not the day. At $1,300, a developer who books 150 days earns $195,000 in revenue. Whether that clears your floor depends on how many days you can really fill, which is the same occupancy question the hourly math hides in "realization". The day rate does not change the math. It makes the assumption visible: how many days a year are paid?
Is a day rate just the hourly rate times eight?
No, and quoting it that way is the most common mistake. Eight times your hourly rate assumes every hour of the day is billable delivery, with nothing spent on the cost that comes with a block of dedicated time.
Two things pull the number apart from a straight multiplication:
The day is shorter than the shift. A client who books you 9 to 5 does not get eight hours of keyboard time. There is a standup, a break, messages, and the time it takes to get back into the problem after each interruption. That is why many developers price a day on 7 delivery hours even when the calendar block is longer.
The premium has a real reason behind it. A booked day takes a whole slot out of your week. You cannot fit a second client around it, and you cannot rearrange it when something urgent comes in. The client gets certainty, and you give up flexibility. That trade has a price. For a short engagement it is also the case that the day will include setup and ramp-up that an hourly meter would have charged separately.
Should a day rate include a premium?
Usually yes, but a modest one, and you should be able to say what it buys. Ten percent is easy to defend: it covers the lost flexibility. Twenty percent suits short, intense engagements where you clear your calendar on short notice.
Some developers apply a discount instead. A client who books 40 days in advance gets a lower day rate in exchange for the guaranteed income. That is also fair, and I covered the same logic for retainers in how to invoice retainer clients. The rule is the same either way. Decide the direction of the adjustment before the conversation, not during it. If you need to adjust numbers later, how to raise your rates covers the notice and wording.
How long is a billable day?
Define it in the contract, because "a day" means different things to different people, and the dispute always arrives on the day you work the odd one.
A workable definition has four parts:
- A length. "A day is up to 7 hours of work, between 9:00 and 18:00 in the client's time zone, including a standard break."
- What counts. Coding, review, meetings with the client, debugging, and deploys count. Your own admin, invoicing, and unrelated clients do not.
- Who sets the window. If you work from another time zone, name it.
- What happens past the edge. That is the overrun rule, covered next.
Pick a length you can actually deliver. A developer who promises eight hours and works seven is giving a quiet discount every day. A developer who promises seven and delivers seven has a defensible invoice.
A note on classification: if a client controls when, where, and how you work to the point of an employee relationship, that affects how the work is treated for tax purposes. The IRS explains in its independent contractor guidance that an independent contractor is someone whose client controls only the result of the work, not what is done and how. Day-rate work is fine under that test, but a contract that dictates your hours, tools, and methods in detail starts to look like something else. This is general information, not tax or legal advice; talk to an accountant about your situation.
How do you bill half days and overruns?
Half days. Charge 60 to 65 percent of the full day, not 50. Preparing for a session, getting set up, switching in and out of context, and coordinating with the client cost about the same whether you work four hours or seven. Splitting a day in half means giving away more than half the value. Define a half day as up to 3.5 hours, and say what happens if it runs past that.
Overruns. Decide before the day starts what happens when it runs long. There are three honest options:
| Option | How it works | Best when |
|---|---|---|
| Overage at the hourly rate | Hours past the day's length are billed at your hourly rate | Most engagements |
| Overage at a premium | Extra hours billed at 1.5x hourly | Out of hours, urgent work |
| Absorb it, up to a cap | The day rate covers up to 30 minutes over, then overage applies | Long-term clients |
Here is the eleven hour day, with illustrative numbers: a 7 hour day at $1,300, hourly rate $170, and four hours past the end of the day. With overage at the hourly rate, the invoice is $1,300 plus 4 x $170 = $680, for $1,980. At 1.5x, it is $1,300 plus 4 x $255 = $1,020, for $2,320. Either is fine as long as the client agreed to it up front. What is not fine is working the extra four hours without telling them and trying to add it afterwards.
Equally, tell the client when a day ends early. If the work is done at lunch, the day was still booked. That is the point of a day rate: the client pays for availability and focus, not for the minutes. Say it once in the contract and you will rarely need to say it again.
A day rate clause you can paste
Day rate. Contractor's rate is $1,300 per day. A day is up to 7 hours of work between 9:00 and 18:00 (client time zone). A half day is up to 3.5 hours and is billed at $780. Time beyond the day or half day is billed at $170 per hour in 30 minute increments, with the client's approval where practical. Days booked and not cancelled with 48 hours' notice are billable. Invoices are issued weekly and due net 14.
Adjust every number to your own. The structure is what matters: rate, definition, half day, overage, and cancellation. The 48 hour cancellation line deserves its own thought. If a client can cancel a booked day the morning of, your day rate is not a commitment at all, and you have no way to recover the slot. Pair it with payment terms that fit, as in getting paid on time with net terms, deposits and late fees.
How does a day rate look on the invoice?
Simple. The quantity is the number of days, and the price is the day rate. No timesheet, no decimals.
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Development, day rate (7 hr day), week of 14 Oct | 3 | $1,300.00 | $3,900.00 |
| Development, half day (3.5 hr) | 1 | $780.00 | $780.00 |
| Overage, hours past day length | 2 | $170.00 | $340.00 |
| Total | $5,020.00 |
Two tips. First, put the dates in the description. "Day rate, 14, 15 and 17 October" is easier to approve than "3 days". Second, break overage onto its own line, so the client sees the agreed day rate unchanged and the extra hours listed separately. That keeps the conversation about the extra hours and not about your rate.
If you are used to hourly invoices, this is the same layout with a different unit. The hourly invoice template shows the line structure, and in the generator you simply enter days as the quantity and your day rate as the price. For what else belongs on the page, see what belongs on a software development invoice.
Do clients prefer day rates or hourly?
It depends on who is paying. Clients buying a finished result often want a project price. Clients buying your time tend to like day rates because they can predict spend: five days is a number, and "somewhere between 30 and 42 hours" is a range.
Outside the US, day rates are a standard unit. Wise, in its UK guide to pricing web development work, reports a median daily rate for a web developer of £431 in the UK and £575 in London, and notes that web developers often price projects at £1,000 to £20,000 or more. Treat those as one data point for one market, not a target. Your number still comes from your own floor.
If a client pushes back on a day rate, the usual objection is "what if you finish early?" The answer is the one above: the client bought a reserved day and your focus, and you will still deliver the outcome. If they will not accept that, offer hourly with a minimum of four hours per booking. It gets you most of the protection.
Day rate FAQ
Is a day rate just the hourly rate times eight?
No. A day rate is your hourly rate times the delivery hours in the day (often 7), plus a premium for the lost flexibility. Multiplying by eight assumes every hour of the shift is billable delivery, which it never is.
Should a day rate include a premium?
Usually a small one. Ten percent is easy to defend, and up to 20 percent suits short, intense bookings. If the client commits to many days in advance, a discount is just as fair. Choose the direction before you quote.
How do I bill a day that ran to eleven hours?
Follow the overrun rule in your contract. With a 7 hour day at $1,300 and a $170 hourly rate, four extra hours at the hourly rate adds $680, for $1,980. Show the overage on its own invoice line, and ideally get the client's agreement before you work the extra hours.
Do clients prefer day rates or hourly?
Clients buying your time often prefer day rates for predictable spend, while clients buying a finished result usually prefer a project price. Hourly suits small, uncertain tasks. Offer the structure that matches the shape of the work.
Turn it into an invoice
When the rate is set, billing a day rate takes a minute. Open the free generator at billable.dev, enter the number of days as the quantity and your day rate as the price, add the dates to the description, and generate the invoice. No account, and the data stays in your browser.