Should you charge by the hour or by the project?

The short answer

Charge by the hour when the work is hard to define upfront, the client may change direction, or you need to tie billing to time actually spent. Charge by the project when the scope is clear, the deliverable is specific, and you can estimate the work without turning every small change into a new invoice.

The better choice is the one that matches how the job actually behaves. If you price the wrong way, you either eat unpaid time or create fights about what was “included.”

Start with the shape of the work

The question is not which method is more professional. It is which method fits the job.

Hourly works best when the scope moves

Use hourly pricing when any of these are true:

1. The client has not settled on the final scope.
2. The work depends on feedback that may change the direction.
3. You cannot predict how many revisions, site visits, or troubleshooting steps will be needed.
4. The job may expand after you start.
5. You need a clean way to bill for time spent on research, calls, planning, or back-and-forth.

Hourly pricing is easier to defend when the client keeps adding tasks. It also works better when the work is diagnostic or open-ended, because the price follows the time the job actually takes.

Project pricing works best when the result is clear

Use project pricing when:

1. The deliverable is known.
2. The main tasks are repeatable.
3. You can describe what is included and what is not.
4. The client wants a single number before they approve the work.
5. You want the invoice to reflect the value of the result, not just the clock.

Project pricing is often better for fixed deliverables because the client can compare options easily. It also gives you room to price for judgment, experience, and speed, not just raw time.

Ask what would make the price unfair

A pricing method is a problem when it makes either side feel trapped.

If you charge by the hour, the client may worry the job will drag on. That fear is stronger when they do not understand the work or cannot see progress. If you charge by the project, you may worry that a smooth job will pay the same as a messy one with many extra steps.

A good test is simple: which method would feel unfair if the job changed in the middle?

• If the client changes the scope often, hourly protects you.
• If the scope stays steady, project pricing can reward your efficiency.
• If both sides need predictability, a project price with a clear change process is usually easier to manage.

Use the client’s need for certainty as a clue

Some clients want to know the final cost before they start. Others care more about flexibility and want you to adjust as the work unfolds.

When the client wants certainty

Project pricing usually fits better when the client needs to budget, get approval, or compare the job against other spending. It helps when the client is asking for one clear number and does not want to watch time sheet entries.

That does not mean you should guess. It means you should define the scope tightly enough that the price has a real boundary.

When the client wants flexibility

Hourly pricing may be safer when the client says they are still figuring things out. It also works when the job will likely change after the first round of work or when the exact path is not clear yet.

That can be especially useful for consulting, troubleshooting, or ongoing help where the problem is the work itself.

Decide whether the job has a natural endpoint

Project pricing fits work that ends cleanly:

• A website page package
• A repair job with a defined fix
• A set of documents or deliverables
• A one-time design or build task

Hourly pricing fits work that can continue without a clean finish line:

• Advisory calls
• Repairs that may lead to more repairs
• Ongoing admin help
• Client requests that keep evolving

If you cannot say what “done” means, charging by the project gets harder to hold together.

Protect yourself with scope boundaries

If you choose project pricing, the real protection is not the number. It is the scope.

Put these things in writing before the work starts:

1. What the final deliverable is.
2. What is included.
3. What is excluded.
4. How revisions work.
5. What happens if the client asks for extra work.

That is where many project prices fall apart. The number looked fine, but the scope was too vague.

A practical way to handle this is to write the boundary in plain language:

This price includes the agreed deliverable and one round of revisions. Any work beyond that scope will be quoted separately before it begins.

If you want to give the client a formal price before they approve the work, use a quote maker. If the total is still a working number because the job may shift, send an estimate maker version instead.

Use hourly pricing when you expect the unknowns to stay unknown

Hourly pricing is not a fallback for “I do not know how to price this.” It is a good choice when time is the thing you can measure honestly.

It helps when the work includes:

• Research that may expand
• Troubleshooting that can go in several directions
• Client meetings that affect the work itself
• Waiting time that is part of the job
• Rework caused by changing instructions

If you are tempted to offer a project price on an uncertain job, ask whether you are really pricing the deliverable or just hoping the job turns out as expected. If it is the second one, hourly may be safer.

Use project pricing when speed is part of your value

A project price can reward you for being efficient. If you know how to do the job well and quickly, charging by the hour may undercut your value.

That does not mean you should rush. It means the client is paying for the result, not for your calendar time. A skilled person can complete some work faster without making it worth less.

Project pricing often makes sense when:

1. You have done the same kind of work before.
2. You know the common problems that come up.
3. Your process is reliable.
4. The client cares about the finished result more than the time spent.

Watch for the common trap on each side

The hourly trap

The biggest problem with hourly pricing is that it can punish efficiency. If you get faster through skill and experience, your revenue may not rise as much as the value you create.

It can also create tension if the client sees time as the only thing they are buying. That tends to turn every minute into a question.

The project trap

The biggest problem with project pricing is scope creep. Once the client feels the price is fixed, they may start treating extra work as part of the original deal.

That is why a project price should always come with a change rule. If the request is outside the original agreement, pause and quote the extra work before you do it.

What to say when you choose one method

The explanation should be simple. Do not make the client guess which option you picked or why.

If you choose hourly

This job is billed by the hour because the scope may change as we work through it. I’ll keep you updated as the work moves forward, and I’ll let you know if the request starts to expand beyond the original plan.

If you choose project pricing

This job is priced as a project because the deliverable and scope are clear. The price covers the agreed work listed here, and any additional requests will be quoted separately before I start them.

That wording keeps the boundary visible without sounding defensive.

Use the pricing method that matches the paperwork

Your pricing method should match the document you send.

If the price is still an estimate because the scope may move, use an estimate maker. If the price is fixed enough that you are committing to a defined deliverable, use a quote maker.

That matters because the client needs to know whether the number is a working projection or a firm offer. The wrong document can make a clear price feel fuzzy.

Build in a change process before you start

If you do project pricing, do not wait until the work is already underway to decide what happens when the client changes their mind.

A simple change process can be this:

1. The client asks for something new.
2. You confirm whether it is inside the original scope.
3. If it is outside the scope, you quote the extra work.
4. You wait for approval before continuing.

That one habit prevents a lot of unpaid time.

You can say:

That request is outside the original scope, so I’ll send a separate price for it before I continue.

Pick the method that fits your cash flow too

A pricing method can be right for the work and still be wrong for your cash flow.

Hourly billing can spread payment over time, which may help on long jobs, but it can also delay full payment if the work drags out. Project pricing often makes it easier to invoice by stage or milestone, which can help you collect sooner.

If you need money earlier, the issue may not be hourly versus project. It may be whether you invoice in one final bill or break the work into parts.

A quick way to decide before you quote

Use this check before you send the price:

1. Can I describe exactly what is included?
2. Can I tell whether the work is likely to change?
3. Can I estimate the time with enough confidence?
4. Does the client want a single number or open-ended support?
5. Would extra work be hard to separate later?

If most of your answers point to clarity and stability, project pricing is usually the better fit. If most of your answers point to uncertainty and change, hourly pricing is safer.

The awkward cases

The client wants a fixed number but the scope is fuzzy

Do not force a project price just because the client asked for one. Narrow the scope first. If you cannot do that yet, give a limited estimate or start hourly until the work becomes clearer.

The job is small but complicated

Small jobs are not automatically project jobs. If the client is likely to keep changing direction, hourly may still be cleaner even if the total number ends up modest.

The work is repeatable but the client is difficult

A difficult client can make either model painful. If they are likely to add requests, dispute scope, or question every decision, choose the method that gives you the clearest boundary and put it in writing.

The project price feels too high to the client

That may mean the scope is too broad, or it may mean the client is used to thinking in hourly terms. Break the work into smaller deliverables and price each part clearly.

What to do after you decide

1. Write the scope in plain language.
2. Choose hourly or project pricing based on how the work behaves.
3. Put the boundary in writing before work starts.
4. Say what counts as extra work.
5. Send the price in a document that matches the way the number works.

Then keep the same logic on the invoice when the job is done. The method you choose at the start should still make sense when it is time to get paid.