There is no universal answer to whether you should bill by the hour or by the project. There is, however, a wrong answer for any specific job — and most freelancers learn that the hard way after a flat-fee project balloons into 80 unpaid hours, or after a steady hourly client finally asks the question every hourly client eventually asks: why does this take you so long?
This guide walks through how each model actually behaves in practice, when to reach for which, how to estimate a flat fee without losing your shirt, and how to use a hybrid structure that captures most of the upside of each. If you already have a project priced and ready to bill, the free invoice generator at BuildWithRiz handles either model — line items by the hour or a single fixed line — without forcing you to choose.
Why the pricing model matters more than the rate
Most pricing arguments online focus on the number — "raise your rate to $150/hr" — but the model you bill in is doing more of the work than the number itself. A model determines who carries which risk:
- Hourly billing puts scope risk on the client and efficiency risk on you. Every hour you work gets paid, but your income is capped at your available time, and you are economically penalized for getting faster.
- Flat-fee billing puts efficiency upside on you and scope risk on you too. Finish in half the time and you double your effective rate. Get pulled into another two rounds of revisions and you watch that rate collapse.
Once you see it that way, the question is not "which model is better" but "who should carry the risk on this specific project." That answer changes from project to project, and from client to client.
Hourly pricing: when it works and when it backfires
Hourly is the default for most beginners because it feels safe — you get paid for what you do. That safety is real, with three large caveats.
It rewards slowness. A freelancer who takes four hours to write a landing page earns more than one who takes two, even if the two-hour version is better. Over time, you have to either fight your own incentives or watch your effective rate fall as you get more skilled.
It positions you as a unit of labor, not a service. Clients who buy your time tend to manage your time. They ask for hour estimates before tasks, push back on entries, and start treating the relationship like a part-time job rather than a vendor engagement.
It caps your income at your available hours. If you can comfortably bill 25 client hours per week at $100/hr, you have a $130k ceiling, full stop. Productized offers, retainers, and flat fees are how most six-figure freelancers break out of that ceiling.
That said, hourly genuinely is the right answer when:
- The scope is vague or research-driven — discovery work, audits, exploratory consulting, "we are not sure exactly what we need yet."
- The work is maintenance or ongoing support — bug fixes, edits, small content tweaks, where each task is too small to scope individually.
- The client is demanding and volatile — frequent direction changes, multiple stakeholders, or a track record of expanding scope.
- You are early in your career and do not yet have enough comparable projects to estimate a flat fee accurately.
For those scenarios, hourly is genuinely the safer ground. The trick is to recognize them and not just default to hourly because it feels familiar.
Flat-fee pricing: when it wins and when it costs you
Flat-fee (sometimes called fixed-price or project-based) pricing flips every incentive. The client knows their total cost on day one. You know what you are getting paid. The conversation moves from "how many hours" to "what is this outcome worth," which is almost always a better conversation to be having.
The economic upside for you is that getting better and faster makes you richer, instead of poorer. A logo project priced at $1,800 pays the same whether it takes you 12 hours or 36. As you get more efficient, your effective hourly climbs without you needing to renegotiate anything.
Flat fees also tend to reduce scope arguments, because the conversation shifts from individual line items to "is this in or out of the agreed scope." A well-written contract makes the line clear, and anything new becomes a change order with its own price tag.
Where flat fees backfire:
- The scope is not actually fixed. If revisions are unbounded or stakeholders are unstable, every "small tweak" eats into your margin.
- You underestimated the work. New freelancers routinely underprice flat fees by 30–50%. Without a buffer, the gap comes out of your pocket.
- The client thinks "fixed fee" means "unlimited revisions." If your contract does not name a number, this assumption is the default in their head.
The fix to the last two is the same: build a buffer into your estimate, and write the revision count into the contract.
A hybrid model that protects both sides
The model most experienced freelancers eventually settle on is some version of this:
- Flat fee for the defined scope, broken into 2–3 milestone payments.
- Named revision budget — typically 2–3 rounds — included in that fee.
- Hourly rate for anything outside scope, billed in 30-minute or 1-hour increments, with prior written approval before work begins.
That structure gives the client price certainty on the part they care about most (the deliverable) while protecting you from the open-ended part (revisions and side requests). The hourly out-of-scope rate should be 20–30% higher than your normal hourly, because it is partially a deterrent. If a client wants a fourth round of revisions, they should feel that decision in the budget.
In a quote or invoice template, this looks like:
- Line 1: Project deliverables (per attached scope) — flat fee, e.g. $4,500.
- Line 2: Included revisions — 2 rounds, no charge.
- Line 3 (only when triggered): Out-of-scope work — billed at $145/hr in 30-min increments.
That third line is the one that matters. Without it, "out of scope" is a verbal claim. With it, it is a contract clause.
How to estimate a flat fee without underpricing
The single most common mistake on flat fees is forgetting that "estimated hours × rate" is an estimate, not a price. Your estimate is going to be wrong — and the asymmetry is brutal, because the times you go under save the client money but the times you go over come out of your margin. So the price has to absorb that asymmetry.
A simple formula that works for most freelancers:
Quote = (best-case hours × hourly rate) × (1 + buffer)
Where the buffer depends on how confident you are in the estimate:
- 20% buffer for work you have done several times for similar clients.
- 30% buffer for work that is familiar but with a new client or new platform.
- 40–50% buffer for projects with new technology, new domain, or unstable stakeholders.
Industry guidance from sources like Workquote, Briskly, and Xolo's freelance rate report puts the typical scope-creep buffer somewhere between 20% and 35%, with 25% as the most-cited middle ground. Treat anything below 20% as a finished, polished offer you have run dozens of times.
Worked example: you estimate a website redesign at 40 hours, your hourly rate is $120, and it is a familiar but new client. The quote should be roughly 40 × $120 × 1.30 = $6,240, not $4,800. The extra $1,440 is the price the client pays for the certainty of a fixed fee — and the price you get for absorbing the scope risk.
Common pricing scenarios: which model fits each
A short cheat sheet for the situations freelancers run into most often:
- Logo design, brand identity, single landing page — flat fee. Scope is clear, deliverables are countable.
- Website build with CMS — flat fee with milestones (kickoff / design approval / launch), plus an hourly rate for post-launch tweaks.
- Discovery, audit, or strategy engagement — hourly or a fixed "audit package" with a defined deliverable (e.g., 20-page report) and a capped scope.
- Ongoing content writing, blog production — per-piece flat fee or monthly retainer for a fixed number of pieces. Avoid hourly here; it punishes good writers.
- Bug fixes, small tweaks, support work — hourly with a small minimum (15–30 minutes) per task.
- Custom development or app build — flat fee per phase, with each phase capped, and a separate change-order process for new features.
- Consulting calls — productized flat fee per call (e.g., $300 for a 60-minute strategy session) rather than billing in 6-minute increments.
The general pattern: defined deliverables → flat fee. Open-ended work → hourly. Recurring work → retainer.
How to switch an hourly client to flat fee (without losing them)
Many freelancers want to move to flat fees but worry about scaring off existing hourly clients. The transition is easier than it looks if you frame it as something you are doing for them.
Start with the next clearly-scoped project, not the current one. Send a proposal that says: "For this next project, I would like to quote a flat fee of $X instead of billing hourly. That gives you cost certainty up front and lets me commit to a delivery date." Most clients prefer that. Cost certainty is genuinely valuable to them — many will pay slightly more for it.
Keep an hourly rate available for out-of-scope work and small support tasks during the transition. Over a few projects, more and more of the work shifts to flat fees, and the hourly rate becomes the exception rather than the default.
If a client refuses to move off hourly even for clearly-scoped work, that is a signal in itself. They are buying your time, not your output, and your incentives are misaligned in ways that are hard to fix.
Quick decision checklist
When a new project comes in, run it through these questions in order:
- Is the scope clearly defined and stable? If yes, lean flat fee. If no, hourly until it is.
- Have I done a similar project before? If yes, you can quote a flat fee with a 20–25% buffer. If no, either go hourly or use a 35%+ buffer.
- Is the client's stakeholder list small and decisive? If yes, flat fee is safer. If a committee will weigh in, hourly is safer.
- Is the work primarily one deliverable or ongoing support? Deliverable → flat fee. Ongoing → retainer or hourly.
- Does my financial situation allow me to absorb a 20% overage? If no, charge hourly until it does.
Get those five right and the pricing model picks itself most of the time.
Sources
- Xolo, How to Calculate Freelance Rates — freelance rate statistics and buffer guidance (blog.xolo.io).
- BILL, Flat Rate vs. Hourly: What's the Difference? (bill.com/learning/flat-rate-vs-hourly).
- Wave, Should you charge by the hour or per project? (waveapps.com).
- Indy, Project fee or hourly rate — what should a freelancer choose? (weareindy.com).
- U.S. Small Business Administration, pricing guidance for service businesses (sba.gov).
This is general information, not tax, legal, or financial advice. For your specific situation, consult a qualified professional.