How to estimate project hours before you send a quote

Quick answer: estimate project hours by breaking the brief into deliverables, turning those deliverables into phases, estimating the work by task and role, then adding time for reviews, project management, QA, admin, meetings, and risk. Don't estimate only the "main work." Most bad quotes miss the work around the work.

A simple formula:

total hours = delivery hours + review hours + project management + QA + admin + risk buffer

That gives you the base for an hourly quote, fixed price, or range.

Start by reading the brief slowly

Start with the brief, not the price.

Read the brief once for the obvious work. Then read it again for the hidden work.

The obvious work is usually easy to see:

• Design a landing page
• Create a brand identity
• Build a website
• Make social assets
• Redesign a product flow
• Prepare a pitch deck

The hidden work takes more attention.

Look for phrases like:

• "Simple"
• "Quick"
• "Just a few"
• "Polish"
• "Refresh"
• "Light animation"
• "Help with launch"
• "A couple of revisions"
• "We are still deciding"
• "We need it by Friday"

Those words often hide extra hours. "Light animation" might mean one small hover state, or it might mean a full motion concept. "Brand refresh" might mean a color cleanup, or it might mean a new identity system. "Help with launch" might mean one final check, or it might mean QA, analytics, CMS fixes, stakeholder calls, and last-minute changes.

Before estimating, write down the questions the brief does not answer. If you can't answer these questions, refer to our comprehensive Ultimate Proposal & Pricing Guide for Creative Agencies to structure your scope boundaries, or sell a dedicated discovery phase first.

Turn deliverables into phases

Don't estimate one big block called "website" or "brand project." Break the project into phases.

Phases help you see the order of work. They also make the quote easier to explain later.

For a landing page project, phases might look like this:

1. Brief review and kickoff
2. Content and structure
3. Wireframe
4. Visual design
5. Revisions
6. Development handoff
7. QA and launch support

For a brand and website project, phases might look like this:

1. Discovery
2. Brand direction
3. Identity design
4. Website structure
5. Website design
6. Development support
7. QA and handoff

Once you have phases, you can estimate each part instead of guessing the whole project.

Estimate by task and role

Total hours matter, but role mix matters too. A project may include strategy, design, copy, development, QA, and project management. Those hours may have different costs, rates, and levels of difficulty.

If you are a solo freelancer, roles still help. You may be the same person doing everything, but strategy time is different from production time. Client calls are different from design time. QA is different from concept work.

This is more useful than saying, "Landing page, maybe 25 hours." Specifying hours in a transparent, table-based breakdown helps you ditch static spreadsheets, avoid formula mistakes, and provide clients with undeniable cost breakdowns. You can see what is included. You can also see what might be missing.

Include review rounds

Review time is not free time. Every review round takes hours. You prepare the work, present it, receive feedback, interpret comments, make changes, and sometimes explain why a request affects the rest of the project.

A revision round is a batch of feedback at a specific stage. It is not one comment.

For example, a landing page quote might include:

• One wireframe review
• Two visual design revision rounds
• One final pre-handoff review

If there are many stakeholders, increase the review estimate. If feedback is not consolidated, increase it again or write a rule into the quote:

"This estimate includes two consolidated revision rounds. Extra rounds will be quoted separately or billed hourly."

That one sentence can save a lot of pain.

Add project management and admin

Project management is easy to forget because it doesn't feel like "the work." But it still takes time.

Project management and admin include:

• Scheduling calls
• Writing updates
• Preparing agendas
• Following up on feedback
• Organizing files
• Managing timelines
• Checking approvals
• Answering client questions
• Sending invoices

Even solo freelancers do project management. You may not call it that, but you still do it. For small projects, PM and admin might be 10-15% of delivery time. For complex projects with multiple stakeholders, it can be much higher.

Add QA and handoff

QA is not only for developers. Creative projects need checks before delivery.

For design work, QA might include:

• Checking desktop and mobile layouts
• Checking spacing and alignment
• Reviewing exported files
• Making sure links and assets are correct
• Preparing source files and layers
• Writing transparent handoff notes

QA is often the first thing people forget when estimating, and the last thing they rush when the deadline is close. Put it in from the start.

Count meetings and client feedback

Meetings can quietly change the estimate. A project with one kickoff call and one review call is not the same as a project with weekly check-ins, stakeholder presentations, and late feedback sessions.

Estimate meetings directly:

Remember that feedback does not only take time during the call. It takes time after the call, when you turn comments into actual revisions.

Add time for unknowns and risk

Every estimate has unknowns: missing copy, multiple decision-makers, messy files, or tight deadlines.

A risk buffer is extra time added because the estimate is uncertain. For a clear project, 10% may be enough. For a project with some unknowns, 15-20% may be better.

estimated work = 60 hours
risk buffer = 15%
buffer hours = 9
total estimate = 69 hours

If you don't add risk, the risk doesn't disappear. It usually becomes unpaid, non-billable client work later.

Fixed price, hourly, or range

Your hour estimate can support different pricing models:

• Fixed pricing: Works best when scope is extremely clear. If the project grows and your price does not change, your effective hourly rate drops. If you are struggling with setting your baseline pricing, read our guide on how much to charge for a design project.
• Hourly pricing: Works best when scope is unclear or ongoing. It protects your margin if work changes or expands.
• Range estimate: Useful when details are still missing. (e.g. "Based on this draft, the project looks like 45-60 hours. We can confirm a fixed quote after we outline page counts.")

When to sell a discovery phase

If the brief is too vague, don't force an estimate. Sell a paid discovery phase. It is a small paid step that helps define the real project before giving a fixed price.

Check capacity and timeline

An estimate is not only about total hours. It is also about when those hours can happen. A 60-hour project over 8 weeks is simple. A 60-hour project due in 10 days requires extreme rush. If your team needs to track concurrent deliverables, consider how these tasks flow—see our analysis of Roadbase vs Asana to understand task vs proposal scheduling.

Sample estimate table: brand and landing page project

Worked example with numbers

Let's say a client asks for a coaching landing page. You estimate 50 hours of work. If your rate is $55/hour:

50 hours x $55/hour = $2,750
$2,750 + $100 expenses = $2,850 total fee

If the client says the number is too high, you can adjust scope (e.g. remove copywriting, reduce revisions) instead of randomly discounting your core rates.

Checklist before sending the quote

• Did I list the deliverables?
• Did I name what is not included?
• Did I break the project into phases?
• Did I estimate by task or role?
• Did I include review rounds and client calls?
• Did I include PM and admin time?
• Did I include QA, handoff, and file cleanup?
• Did I add a risk buffer?
• Did I write clear assumptions?

What to do after the project

Compare your initial estimate against your actual tracked hours. This is how you learn and get faster:

• Did delivery take more time than expected?
• Did reviews overshoot?
• Did PM leak time?

Roadbase helps you draft accurate estimates directly from vague client briefs, review your assumptions, and transition approved work straight into simple, visual team tracking. Once a project is created, you can switch to Kanban view, track the state of phases and tasks, and leave notes (see how this board-based workflow compares in Roadbase vs Trello).

The full time-tracking module is built-in and free for every user (including the free-tier plan). This comparison of estimated vs actual time ensures your next project bid is based on real-world history, rather than a hopeful guess.

FAQs

How do I estimate project hours if I am new?

Start by breaking the project into phases and tasks. Estimate each task separately, then add time for reviews, meetings, PM, admin, QA, and risk. Track actual time so the next estimate is better.

Should I show the client my estimated hours?

It depends. Some clients like seeing hours. Others only need the project price, scope, timeline, and assumptions. Even if you do not show the full hour breakdown, you should create it internally so your quote has a real structure.

What if the client wants a fixed price but the scope is unclear?

Do not force a fixed price too early. You can quote a range, write strong assumptions, or sell a paid discovery phase. A fixed price only works when the scope is clear enough to estimate responsibly.

Should I track time on fixed-price projects?

Yes. Time tracking is useful even if the client is paying a fixed fee. It shows whether your estimate was accurate and which parts of the project took more time than expected. That information helps you price the next project better.