Every freelancer hits this decision eventually: a client asks for a quote, and you have to decide whether to price the work by the day or by the whole project. Get it wrong and you either underprice your time or lose the bid to someone who structured their number better. Here's how to actually decide, and how to invoice cleanly once you have.
What each rate actually means
A day rate is a fixed amount for a full day of your work, regardless of exactly what gets done in it. You multiply the day rate by the number of days the project takes, and that's your invoice.
A project rate is a single fixed fee for the entire scope of work, agreed before you start, regardless of how many hours or days it actually takes you to finish.
The core difference isn't really about hours. It's about who carries the risk if the work takes longer than expected. Under a day rate, the client carries more of that risk, since more days means a bigger invoice. Under a project rate, you carry it, since the fee is fixed no matter how the timeline shifts.
When a day rate makes sense
Day rates work well for engagements where the scope is fuzzy going in, or where you're embedded with a client's team for a stretch of time rather than delivering a single defined output. Think strategy consulting, on-site design sprints, or ongoing development work where requirements evolve as you go. You don't have to estimate total hours upfront, which protects you from underquoting something you can't fully scope yet.
The tradeoff: clients sometimes see a day rate as open-ended, and a day rate alone doesn't reward you for working efficiently. If you finish in half the time a less experienced freelancer would need, you still bill the same number of days.
When a project rate makes sense
Project rates fit well-defined deliverables: a logo, a website build, a set of marketing materials, an app feature with a clear spec. The client knows the total cost before work starts, which makes it an easier yes, especially for a new client who doesn't have a track record with you yet. And if you're fast or experienced, a project rate rewards that. You get paid the same fee whether it takes you three days or five.
The tradeoff runs the other way here: if the scope grows, and it usually does, you're the one absorbing the extra time unless you've built change orders into your agreement from the start.
Converting between the two
If a client asks for a day rate but you'd rather quote a project fee, or the reverse, the conversion starts with a realistic estimate of total days, then some padding. Take your best estimate of total working days, add 15 to 20% as a buffer for revisions and scope drift, and multiply by your day rate to land on a project fee. Going the other direction, take a project fee, divide by your best estimate of total days, and check that number against your actual day rate to make sure you're not accidentally discounting yourself.
How to invoice cleanly under each model
For a day rate: list each billing period's total days as a single line item, or break out individual days if the client wants that level of detail for their own records. Either way, state the day rate explicitly on the invoice so there's no ambiguity if the engagement continues.
For a project rate: a single line item for the full scope is usually enough. If you're invoicing for a large project in stages, tie each invoice to a specific milestone rather than a percentage of "time elapsed," so both you and the client know exactly what triggered that payment. Our guide on invoicing for a retainer covers a related structure if the engagement is closer to ongoing than one-off.
A hybrid approach worth considering
Plenty of freelancers land somewhere in between: a project rate with a defined scope, plus a day rate for anything beyond that scope. This gives the client price certainty for what they asked for, while protecting you if they add requests mid-project. Put this in writing before you start, not after the first scope-creep request lands in your inbox.
Whichever you choose, know your number first
Neither structure works if you don't already know your baseline rate. If you haven't nailed that down yet, our guide to figuring out how much to charge as a freelancer walks through a formula that accounts for your expenses, target income, and billable capacity. Get that number right first, then decide whether a day rate or project rate is the better way to present it. The Freelancers Union resources on rate setting are also a solid outside check if you want to compare notes against other independent professionals.
Getting paid however you price it
Whichever rate structure you land on, Nvoyce turns it into a clean proposal and invoice without the manual math. Line items for day rates, milestone-based invoices for staged project rates, and automatic follow-up either way so you're not the one chasing payment. Start a 7-day free trial, no credit card required, at nvoyce.ai.
Related Reading
- How Much Should You Charge as a Freelancer? A Simple Rate Formula
- Freelance Payment Terms Explained: Which to Use and How to Actually Get Paid
- How to Invoice a New Client for the First Time
Frequently Asked Questions
What's the difference between a day rate and an hourly rate?
A day rate is a fixed fee for a full day regardless of hours actually worked, while an hourly rate bills for exact time logged. Day rates simplify invoicing and remove the need for granular time tracking, but expect a full day's work in exchange for a full day's pay.
How do I convert my day rate into a project rate?
Estimate your total working days for the project, add 15 to 20% as a buffer for revisions, and multiply by your day rate. That gives you a defensible project fee that still protects your time.
Which rate structure is better for a first-time client?
A project rate is usually the easier sell for a new client relationship, since they know the total cost before committing. Day rates work better once you've built trust and the scope is genuinely hard to pin down in advance.
What happens if a project runs longer than expected under a project rate?
You absorb the extra time unless you've built scope change terms into your agreement upfront. This is why clearly defining what's included, and what counts as an add-on, matters before you send the proposal.
Can I mix day rate and project rate work on the same invoice?
Yes. A common structure is a fixed project rate for the agreed scope, plus a day rate for anything the client adds beyond it. List these as separate line items so the distinction is clear.
Does my rate structure affect how I handle taxes?
Not directly, since both are self-employment income reported the same way. What matters is knowing your target take-home number before you set either rate. The IRS self-employed tax center is a good starting point if you're unsure how much of your rate needs to cover taxes versus actual take-home pay.