Hourly Rate vs Project Fee: Which Should You Charge?

The Decision Test: Can You Define the Deliverable in One Sentence?

The difference between choosing hourly and project pricing is a single question that takes 10 seconds to answer. Ask yourself: can you describe exactly what the client gets in one sentence? If the answer is yes, charge a project fee. If the answer is no, charge hourly.

Here is the test in action. A client says, "I need a 5-page marketing website with a contact form." That is one sentence. That is a defined deliverable. You charge a project fee of $4,500 to $8,000 depending on your experience level. Now consider a different client who says, "We need help improving our web presence and figuring out our digital strategy." That is vague. The scope is undefined. You charge $85 to $150 per hour until the scope becomes clear.

This test works because the underlying risk is what determines the right pricing model. When you know exactly what you are building, you can estimate the hours, pad for contingency, and set a fixed price. You control the profit margin. When the deliverable is fuzzy, charging a flat fee means you absorb all the risk of scope changes, endless revisions, and shifting requirements. A web developer who charges a $6,000 flat fee for a project that was described as "build us something cool" is gambling. A copywriter who charges $100 per hour for an open-ended brand messaging exploration is being smart.

The one-sentence test is not about simplicity. A complex project can still pass the test. "Redesign our 40-page e-commerce site with migration from Shopify to WooCommerce" is complex, but it is defined. You can scope it, estimate it, and price it as a $15,000 to $25,000 project fee. The test is about clarity, not complexity.

When Hourly Wins: 4 Scenarios Where Time-Based Billing Is the Right Call

Hourly rates between $75 and $200 are the correct choice in four specific scenarios that share one trait: unpredictable scope.

The first scenario is ongoing maintenance and support. A graphic designer retained for weekly social media assets at $95 per hour bills only for time spent. Some weeks require 3 hours of work, others require 12. A project fee here would either overprice slow weeks or underprice busy ones. The same applies to a web developer on a $125-per-hour retainer for bug fixes and small updates. The client pays for what they use, and you get paid for every hour you work.

The second scenario is discovery and strategy phases. Before a UI/UX designer can quote a $12,000 app redesign, they need 10 to 15 hours of research, user interviews, and competitive analysis at $135 per hour. Charging a project fee for discovery is risky because you do not yet know what the project is. Billing $1,350 to $2,025 for that discovery phase protects you and gives the client a clear deliverable: a strategy document that defines the actual project.

The third scenario is when the client controls the pace. If a copywriter is embedded in a marketing team, attending their meetings, waiting for their feedback, and adjusting to their timeline, hourly billing at $110 per hour is fair. The client is renting your time, not buying a deliverable. Freelancers in these embedded roles typically bill 15 to 25 hours per week, generating $1,650 to $2,750 in weekly revenue.

The fourth scenario is when the client has a history of scope changes. Some clients change direction constantly. A web developer who has worked with a client before and knows they will request 30 to 40 revisions on every page should charge $100 to $150 per hour rather than a flat fee. The hourly model turns scope creep from a profit-killer into additional revenue. If the client requests 20 extra hours of changes, that is $2,000 to $3,000 in additional billings rather than unpaid overtime.

When Project Fees Win: 4 Scenarios Where Flat Pricing Earns You More

Project fees of $2,000 to $50,000 are the correct choice in four scenarios where you can control scope and leverage your speed.

The first scenario is when you have done the exact same work before. A web developer who has built 30 WordPress marketing sites can deliver a $5,500 project in 25 hours. At an hourly rate of $125, that same project would bill only $3,125. The project fee rewards your expertise and efficiency. A copywriter who has written 100 landing pages can deliver a $2,500 landing page package in 8 hours, effectively earning $312 per hour. Hourly billing punishes speed. Project fees reward it.

The second scenario is when deliverables are concrete and countable. A graphic designer quoting a brand identity package with a logo, 3 logo variations, a color palette, typography guide, and business card design charges $3,500 to $6,000 as a project fee. Each deliverable is specific. Each can be checked off a list. There is no ambiguity about what "done" means. A UI/UX designer quoting 10 wireframes and 10 high-fidelity screens for a mobile app charges $8,000 to $14,000 as a flat fee. The scope is locked.

The third scenario is when the client needs budget certainty. Many clients, especially those at agencies or corporations, need to get budget approval before work begins. Telling a marketing director the project costs $7,500 is easier for them to approve than saying it costs $125 per hour for an estimated 50 to 70 hours. The flat fee removes their financial anxiety and makes the sale faster. Freelancers who switch from hourly to project-based pricing for these clients report closing deals 30 to 40 percent faster.

The fourth scenario is when you want to scale your income without working more hours. A copywriter charging $100 per hour caps their annual income at roughly $150,000 to $180,000 assuming 30 billable hours per week. The same copywriter charging $3,000 per website copy package and completing two packages per week earns $312,000 annually while working fewer total hours. Project fees decouple your income from your time, which is the single most important shift in building a sustainable freelance business.

The Hybrid Model: Project Fee Plus Hourly for Out-of-Scope Work

The hybrid model combines a $3,000 to $15,000 project fee for defined deliverables with an hourly rate of $100 to $175 for anything outside the original scope. This is the most common pricing structure used by experienced freelancers, and it solves the biggest weakness of pure project pricing: scope creep.

Here is how it works in practice. A web developer quotes a 7-page website for $6,500. The proposal specifies exactly what is included: 7 pages, 2 rounds of revisions per page, responsive design, contact form integration, and basic SEO setup. The proposal also states that any work outside this scope, such as additional pages, extra revision rounds, or new feature requests, is billed at $130 per hour. When the client inevitably asks for an eighth page and a blog section, the developer sends a quick note: "Happy to add those. The additional page is roughly 4 hours and the blog setup is roughly 6 hours, so that is approximately $1,300 at my hourly rate. Want me to proceed?" The client either approves the additional cost or decides those additions are not essential.

A copywriter uses the same structure. The base package is $2,800 for a homepage, about page, services page, and 3 blog posts. The contract specifies 2 rounds of revisions per piece. Additional revisions beyond that are billed at $110 per hour, with a minimum of 1 hour per revision round. This protects the copywriter from the client who wants 7 rounds of edits while keeping the initial price competitive.

The hybrid model works because it aligns incentives. The client gets budget predictability for the core project. You get protection against scope expansion. The key is specificity in your proposal. Every deliverable, every revision round, every included feature must be listed. The dividing line between project scope and hourly scope must be unmistakable. Freelancers who use the hybrid model report earning 15 to 25 percent more per project compared to pure flat-fee pricing because they actually get paid for the extra work that inevitably arises.

How to Convert an Hourly Rate to a Project Fee

The conversion formula is straightforward: estimated hours multiplied by your hourly rate multiplied by 1.2 equals your project fee. The 1.2 multiplier is a 20 percent buffer that accounts for project management overhead, client communication, revisions, and the unexpected complications that arise in every project.

Here is a real example. A UI/UX designer charges $125 per hour and estimates a mobile app design project at 60 hours. The calculation is 60 hours times $125 times 1.2, which equals $9,000. That $9,000 project fee includes a built-in buffer of $1,500 for the inevitable extras. If the designer finishes in 55 hours, they effectively earned $163 per hour. If the project runs to 65 hours, they still earned $138 per hour, which is above their baseline rate.

For a web developer charging $100 per hour who estimates a website rebuild at 45 hours: 45 times $100 times 1.2 equals $5,400. A copywriter at $90 per hour estimating 20 hours for a full website copy project: 20 times $90 times 1.2 equals $2,160.

The 1.2 multiplier is a starting point. Adjust it based on three factors. First, client communication style. If the client is responsive and decisive, 1.15 is sufficient. If the client has a large team with multiple stakeholders, use 1.3 or even 1.4. Second, your familiarity with the work. If you have done this exact type of project 20 times, use 1.1 because your estimate is accurate. If this is a new type of project for you, use 1.35 because your estimate is likely optimistic. Third, revision expectations. If the contract includes 2 rounds of revisions, 1.2 is fine. If the client expects unlimited revisions, use 1.5 or switch to hourly entirely.

Track your actual hours on every project fee engagement. After 10 projects, you will know your true multiplier. Most freelancers discover they need 1.25 to 1.35 rather than 1.2, and they adjust accordingly. A graphic designer who tracked 15 brand identity projects found her average overrun was 28 percent, so she switched to a 1.3 multiplier and her effective hourly rate jumped from $95 to $122.

Common Mistakes That Cost Freelancers $5,000 to $20,000 Per Year

The first mistake is quoting a project fee without a written scope document. A web developer who verbally agrees to "build a website" for $5,000 and then discovers the client expects e-commerce functionality, a membership portal, and 25 pages of content has no recourse. The fix costs nothing: write a one-page scope document listing every deliverable, every exclusion, and every assumption. Freelancers who skip this step lose an average of $3,000 to $7,000 per year on underpriced projects.

The second mistake is using hourly billing when you are fast. A graphic designer who creates social media templates in 45 minutes but charges $85 per hour earns $63.75 per template. The same designer charging a $150 flat fee per template earns more than double the effective rate. Every time you get faster at something, hourly billing costs you money. Review your services every 6 months and convert any task you can complete in under 2 hours to a flat-fee mini-package.

The third mistake is failing to specify revision limits on project fees. A copywriter who charges $3,500 for website copy with "revisions included" and then endures 6 rounds of committee-driven feedback effectively works 50 hours on a project estimated at 25. That drops the effective hourly rate from $140 to $70. Always specify the number of revision rounds. Two rounds is standard. Each additional round is billed at your hourly rate.

The fourth mistake is underestimating by anchoring to best-case scenarios. When a UI/UX designer estimates a project at 40 hours, that is typically the best-case scenario where everything goes smoothly. The realistic estimate is 48 to 52 hours. The worst case is 60 hours. Use the realistic estimate in your formula, not the optimistic one. A freelancer who consistently uses best-case estimates and the 1.2 multiplier ends up working at their base hourly rate or below on 70 percent of projects.

The fifth mistake is never raising project fees as you gain experience. A web developer who charged $4,000 per website three years ago and still charges $4,000 today is effectively taking a pay cut after accounting for inflation and their increased skill level. Raise your project fees by 10 to 15 percent annually or after every 10 completed projects, whichever comes first.

Key Takeaways: Your Pricing Model Decision Checklist

Freelancers who choose the right pricing model for each engagement earn 20 to 35 percent more annually than those who default to one model for everything. Here is your decision checklist.

Use hourly rates of $75 to $200 per hour when the scope is undefined, when the client controls the pace, when you are in a discovery or strategy phase, or when the client has a pattern of frequent scope changes. Bill weekly or biweekly. Track time meticulously. Send detailed time logs with every invoice.

Use project fees of $2,000 to $50,000 when you can define the deliverable in one sentence, when you have done the same type of work before, when the client needs budget certainty, or when you want to earn more by working faster. Require 30 to 50 percent upfront before starting work. Define scope in writing. Specify revision limits.

Use the hybrid model for any project over $5,000. Set a flat fee for the defined scope and an hourly rate for out-of-scope requests. This is the standard for experienced freelancers and protects both sides.

Convert hourly to project using the formula: estimated hours times your hourly rate times 1.2. Adjust the multiplier based on client communication style, your familiarity with the work, and revision expectations. Track actual hours to refine your multiplier over time.

Avoid the five costly mistakes: quoting without a scope document, billing hourly when you are fast, omitting revision limits, estimating based on best-case scenarios, and failing to raise your rates annually. Each mistake independently costs $2,000 to $7,000 per year. Combined, they can represent $10,000 to $20,000 in lost income.

The single most important principle is this: your pricing model is not a personality trait. It is a tool you select based on the specific engagement. The best freelancers use hourly billing for some clients, project fees for others, and hybrids for the rest. Match the model to the situation, and your income follows.