Payment terms to mention in a proposal (without writing a legal essay)

Clients rarely hire you because your payment terms were poetic. They hire you because you sound capable, sane, and easy to work with.

Payment terms still matter. They set expectations before emotions run high, before the deadline slips, and before someone says “we will pay when everything is perfect” while asking for round six of revisions.

The goal in a proposal is not to replace a contract. The goal is to state the basics in plain language: when money moves, what has to happen first, and what is not included in the quoted price.

If you price fixed work, pair this article with fixed-price proposal pricing. If you split delivery into chunks, read how to propose milestones next.

What payment terms actually do in a proposal

Payment terms answer four questions the client may not ask out loud:

1. When do I pay?
2. What do I pay for at each step?
3. What happens if I am slow to approve or provide assets?
4. What happens if the scope grows?

You do not need fifteen clauses. You need visible defaults so nobody argues from memory later.

Think of the proposal as a preview of how you run projects. Calm, specific, and normal beats legal-heavy every time.

The minimum set that covers most freelance projects

For many fixed-scope jobs, this set is enough:

• Deposit or start payment (often 30-50% to begin, or 100% of milestone 1)
• Milestone or delivery payments tied to named deliverables
• Final payment before handoff of files, access, or launch
• What pauses work (missing content, no approval within X days, disputed scope)
• How scope changes are priced (change request, separate quote, or hourly overflow)

You can add net terms (Net 7, Net 14) when the client is a company with accounts payable. On marketplaces with escrow, describe the same ideas in platform-friendly language even when the platform handles the mechanics.

Copy-ready block: short payment terms paragraph

Use this as a starting point and edit numbers to match your risk:

Payment terms: 40% to schedule kickoff and reserve the slot, 40% when the staging deliverable is approved, and 20% before final handoff (files, access, and launch support). Work pauses if key inputs (copy, brand assets, logins) are not provided within 3 business days of request, or if feedback is not returned within 5 business days. Anything outside the agreed scope list is quoted separately before work begins.

That is not a legal essay. It is a boundary clients can understand in one skim.

Deposits: how to say it without sounding distrustful

Clients sometimes read “deposit” as “you do not trust me.” Reframe it as scheduling and focus.

Good reasons deposits exist:

• You turn down other work for their window
• You buy licenses, subcontract help, or book dedicated hours
• You start discovery and setup that has real cost

Softer line for smaller jobs:

To start, I take 50% upfront and the remainder on delivery of the final files. That lets me block time on my calendar and begin immediately once I have your brief assets.

Firmer line for larger builds:

Projects like this start with a 40% kickoff payment once scope is confirmed in writing. The schedule below shows the remaining payments tied to deliverables you can review on staging.

If the job post already signals risk (vague scope, rush timeline, many stakeholders), a deposit is not aggressive. It is professional. See why clients ignore proposals for tone mistakes that matter more than deposit percentage.

Milestone payments tied to deliverables, not vibes

Milestone language should name what the client receives, not internal task labels.

Weak: “Payment 2 due week 3.”

Strong: “Payment 2 due when the staging site is ready for your review (all agreed pages, mobile layout, contact form working).”

Example tied to a three-step web build:

Milestone 1 (paid on start): scope document, sitemap, and technical plan you approve.

Milestone 2 (paid on approval): staging site with agreed pages and forms; one consolidated feedback round included.

Milestone 3 (paid before launch): revisions within agreed limits, deployment, and handoff checklist.

This mirrors the structure in milestone proposals but keeps the client’s eye on money moments.

Hourly and retainer payment terms (short version)

Hourly proposals still need payment clarity:

• Billing cadence (weekly, biweekly, monthly)
• Minimum increment (e.g., 15 minutes or 1 hour)
• How overages on fixed mini-tasks are handled
• Whether unused retainer hours roll over

Example:

I bill biweekly for hours logged in [tool], with a weekly cap of [X] hours unless we agree in writing to extend. Invoices are due within 7 days. If a task exceeds the agreed cap, I will flag it before additional hours accrue.

Keep hourly payment terms shorter than fixed-price terms. The scope moves more; the payment rhythm should feel routine.

Net terms for business clients

When your client is a company, they may expect Net 14 or Net 30. That is fine if you price for cash flow risk.

Plain-language version:

Invoices are Net 14 from receipt. Work on new phases begins after the prior milestone invoice is paid. Late payments pause scheduling of new work until the account is current.

If Net 30 is non-negotiable for them, consider slightly higher rates or a larger upfront milestone. You are effectively lending them time.

Late approvals and “we are still deciding”

Many payment disputes are really approval disputes. Separate them in writing.

Feedback is due within 5 business days per review round. If feedback is delayed, the timeline shifts and any rush deadline may need to be re-quoted. Work on the next milestone begins after written approval of the current one.

That protects you without accusing the client. You are describing how calendars work.

Scope changes and out-of-scope work (payment angle)

Payment terms should point to how extra work gets priced, even if the detailed scope list lives elsewhere.

Requests outside the agreed deliverable list are estimated in writing before work starts. Small additions may be handled as a fixed add-on; larger shifts become a new milestone or change order at [rate].

You will expand the creative “out of scope” language in scope creep paragraphs. Here, keep it about money: no silent free work.

Marketplace-specific notes (keep it one sentence)

On Upwork, Fiverr, Freelancer.com, Khamsat, and similar channels, the platform may control escrow. Still state your logical terms so messages and contracts align.

Example:

I am happy to work within the platform milestone flow. Logically, this maps to: 40% at kickoff, 40% at staging approval, 20% at handoff, with the same deliverable names as above.

Clients appreciate when you translate platform mechanics into outcomes. It reduces “I thought the whole fee was for unlimited changes” confusion.

Mistakes that cause payment pain later

Burying terms at the bottom in legalese. Clients skim. Put a short Payment terms heading mid-proposal or right after scope.

One lump sum with no approval gates. You fund the entire risk; they learn late they wanted something different.

No link between payment and deliverables. “50% upfront, 50% on completion” without defining completion invites endless tweaks.

Saying “industry standard” with no numbers. Standards vary by country and niche. Use your numbers.

Apologizing for getting paid. Confidence is not arrogance. “To begin, kickoff is 40%” is normal.

FAQ

Should payment terms go in the first proposal or only after they shortlist me?

If the job is fixed-price or over a few hundred dollars, include a short terms block in the first strong proposal. Waiting until “later” often means negotiating from a weaker position.

What deposit percentage is normal?

30-50% upfront is common for custom work. Milestone-heavy projects sometimes use 100% of milestone 1 as the “deposit” instead of a separate label.

Can I ask for 100% upfront?

Sometimes, for very small, well-defined tasks. For larger builds, full upfront often reduces trust unless the client already knows you. Milestones usually convert better.

Do I need to mention taxes and currency?

If you invoice internationally, one line helps: currency, who pays transfer fees, and whether your quote is ex-VAT or includes tax where required.

Before you send

Run the proposal checklist and confirm:

• Each payment ties to a deliverable or date the client understands
• You stated what pauses work (missing inputs, late feedback)
• Scope changes have a pricing path, not a vague “we can discuss”

Payment terms are not the exciting part of freelancing. They are the part that keeps exciting projects from turning into unpaid therapy. Say them clearly once, then deliver work worth the structure you set.

---

Bottom line: mention deposits, milestone triggers, and scope-change pricing in plain language. Clients respect freelancers who sound organized, not lawyers who sound scared.