Separate Engineering Hours from Payment Percentages in Freelance Web Quotes

Most freelance web quotes hide a quiet accounting bug:

“Milestone 1 is 25% of the hours, so charge 25% upfront.”

That feels fair. It is often bad cash flow.

Discovery, information architecture, and component setup can be a smaller share of total hours than the final integration and QA — yet that early work is what unlocks the rest of the project. If your deposit only matches early hours, you fund the risky front of the job with your own time.

The fix is simple to say and easy to forget in a spreadsheet:

Track two numbers that are allowed to disagree.

1. Estimated engineering hours — the effort you expect to spend.
2. Cash-flow share % — the share of the fee due at each gate (deposit, staging, launch).

They should reconcile to 100% on the money side. They do not need to match hour-for-hour.

A concrete example (illustrative only — not a rate recommendation)

Suppose a brochure + CMS site:

Phase	Est. hours	Hour share	Cash-flow share (chosen)
Discovery & IA	12	20%	40% deposit
Build & CMS	30	50%	30%
QA, launch, handover	18	30%	30%
Total	60	100%	100%

At an example rate of $75/hour → $4,500 project fee.

Deposit at 40% = $1,800, even though early hours are only 20% of effort.

You are not “overcharging” for discovery. You are front-loading commitment so the client has skin in the game before you open the repo — and so you are not financing their project.

Label example math as example math. Your real rate and splits are yours.

Why clients still accept it

Non-technical buyers rarely argue with hour tables. They argue with surprises.

When the proposal shows:

• what is in scope / out of scope,
• when each payment is due,
• what deliverable unlocks the next invoice,

…the deposit percentage reads as structure, not greed — especially if you also state a 0% late-fee / work-pause policy instead of interest-like penalties.

A practical workflow (spreadsheet or tool)

1. List deliverables and estimate hours per phase.
2. Set cash-flow shares that protect kickoff (many freelancers start near ~40% — your choice).
3. Confirm money shares sum to 100%.
4. Write acceptance triggers in plain language (“staging URL with form working,” not “when it feels done”).
5. Export a clean PDF the client can forward internally.

If you want the arithmetic without rebuilding formulas each time, we publish a free browser calculator (no signup):

👉 Website project price & deposit calculator

For the full milestone proposal + bilingual PDF path, the live workspace is here:

👉 DevQuoteFlow free starter workspace

Related reading on our site (canonical source for the calculator article): the same calculator page above. For a broader proposal outline, see the freelance web developer proposal template guide.

Mistakes to avoid

1. Forcing payment % to equal hour % “for fairness.”
2. A deposit too small to fund discovery.
3. Open-ended revisions with no change-order path.
4. Promising SEO rankings or revenue you do not control.
5. Invented “industry average” close rates in your marketing.

Pricing note (if you try the product)

DevQuoteFlow’s published live pricing is a free starter tier and Pro Freelancer at $15/month or $144/year, billed via Paddle. This article is not a discount or affiliate pitch — just the numbers on the public pricing section.

---

Prepared with AI assistance; reviewed and approved by the DevQuoteFlow founder.