DEV Community

Altasks Studio
Altasks Studio

Posted on

Why Your $300 Freelance Project Might Pay Less Than $20 an Hour

A freelance project can look profitable and still underpay you.

Suppose a client offers $300 for “a quick dashboard.” You estimate eight hours, so the job appears to pay $37.50 per hour. That sounds reasonable - until the real work begins.

There is a kickoff call, a messy data export, two revision rounds, payment processing, project administration, and one unexpected request that feels too small to reject. The job takes thirteen hours. After a payment fee and a tax reserve, the cash you can actually use may fall below $20 per hour.

The problem is not only scope creep. It is incomplete pricing.

Here is a simple way to build a better quote.

1. Estimate the entire job, not only production time

Freelancers often estimate the hours spent creating the deliverable and forget the work around it.

Include:

  • Discovery and requirements
  • Client communication
  • Setup and file organization
  • Production
  • Quality review
  • Revisions
  • Delivery and handoff
  • Invoicing and administration

If the project requires five hours of production but two more hours of communication and review, price seven hours - not five.

2. Separate complexity from time

Two projects can require the same number of hours while carrying very different levels of difficulty.

A clear, familiar task may justify your standard rate. A task with poorly documented data, multiple stakeholders, sensitive access, or unfamiliar technology carries more cognitive load and more risk.

A small complexity multiplier makes this visible. For example:

  • Low complexity: 1.00x
  • Medium complexity: 1.10x
  • High complexity: 1.25x
  • Very high complexity: 1.40x

This is not a penalty for the client. It is a way to stop difficult work from being priced as routine work.

3. Give revisions a real cost

“Revisions included” is not a scope definition.

State how many rounds are included and what a revision means. A revision adjusts the agreed deliverable. A new direction, new feature, or new data source is additional work.

You can reserve a percentage of labor for included revisions. Even a 5% buffer is better than assuming revisions cost nothing.

4. Add direct costs before calculating profit

Direct costs include anything required specifically for the project:

  • Paid assets or licenses
  • Subcontractors
  • Travel
  • Data purchases
  • Software used only for this client
  • Variable infrastructure costs

Also include the cost that scales with your time. If each project hour consumes paid API usage, specialized software, or contractor support, model it as a variable cost per hour.

5. Price urgency and risk explicitly

A rush deadline has a cost because it displaces other work and reduces your flexibility. Unclear requirements, a new client, or dependency on third parties also creates risk.

Do not hide these factors in your head. Use a rush surcharge and a separate risk buffer. If neither applies, set them to zero.

Visible assumptions are easier to explain and easier to improve after the project.

6. Gross revenue is not take-home cash

Your quote is not your income.

Subtract payment processing and set aside a tax reserve before judging whether the project meets your target. The correct reserve depends on your location and circumstances, but ignoring it does not make it disappear.

The metric that matters is:

Net cash / estimated hours = effective hourly cash

Compare that result with your minimum acceptable return.

7. Protect the quote with a deposit and an extra-work rate

A deposit protects cash flow and confirms commitment. The remaining payments should be connected to dates or deliverables.

Your proposal should also state what happens when the client requests work outside the written scope. A pre-calculated extra-work rate makes that conversation much easier.

You do not need to argue. You can say:

That request is outside the current deliverable. I can add it for an estimated two hours at the project add-on rate, subject to your approval.

A quote should be a floor, not a ceiling

The calculation above tells you the lowest defensible price based on time, costs, and risk. If the work creates materially more value for the client, you may quote above that floor.

But you should know where the floor is before negotiating.

I turned this workflow into a bilingual Excel + Google Sheets system with a Quote Builder, Profit Dashboard, Client Profit Log, scope-creep rate, and quick-start guide.

Start with the free bilingual checklist and pricing notes:

Get the free Freelancer Pricing Checklist on GitHub

If you want the complete spreadsheet system:

See the Freelancer Quote & Profit Calculator

The best pricing system is not the one with the most complicated formula. It is the one you actually use before every proposal - and review after every project.

Top comments (0)