Consulting Payment Terms: Deposits, Net-30, Escrow

Consulting payment terms are the commercial rules that decide when money changes hands — deposits, net-30 invoicing, retainers, milestone billing — and they matter far more than most buyers realize, because the terms you agree decide how much risk each side carries before any work exists. The wrong terms either expose your budget to a stranger or push so much risk onto the consultant that the good ones walk away. This guide compares the common arrangements, explains what's actually fair to both sides, and shows how holding funds in escrow changes the underlying risk math rather than just shuffling it around.

Why payment terms are really about risk

It's tempting to treat payment terms as administrative boilerplate — the bit at the bottom of the contract you skim past. They aren't. Every set of terms is a statement about who trusts whom and for how long. Strip away the legal language and each arrangement answers the same question: at any given moment, who is owed something they haven't yet received?

When you pay a deposit, you are owed work you've already partly funded. When a consultant invoices net-30, they are owed money for work they've already delivered. When you both wait for a milestone, neither is exposed beyond that one tranche. The terms aren't neutral plumbing — they decide, milestone by milestone and day by day, which party is carrying the counterparty risk.

That's why "what are the standard terms?" is the wrong question. There's no universal standard, because the right terms depend on the stakes and the trust. A decade-long relationship with a large firm can run on net-60 because the trust is already banked. A first engagement with an independent can't, because it isn't. Match the terms to the situation, not to whatever the last contract happened to say.

Deposit plus balance

The oldest arrangement: pay a share up front, the rest on completion. It's intuitive and it splits the go-first risk between both parties — you advance some money, the consultant advances some work.

The deposit does real work. It confirms you're a serious buyer, and it compensates an independent for reserving capacity they could have sold to someone else. A modest deposit is fair and normal, and refusing any deposit at all can read as not taking the engagement seriously.

The risk lives in the size. A small deposit tied to an early concrete deliverable is fine. A large one — half the fee before any work exists — shifts the project's full risk onto you, because once that money is in the consultant's hands, getting it back if the work disappoints depends entirely on their goodwill. There's no mechanism behind a deposit; it's just trust with extra steps. The practical rule: keep deposits small, tie them to something you'll actually receive early, and treat an insistence on a large up-front share as a signal worth examining.

Net-30, net-60, and pay-on-completion

At the other end sits invoicing after delivery: the consultant does the work, sends an invoice, and you pay within an agreed window — 30 days, 60, or on receipt. This is the standard in established B2B relationships because it fits corporate accounts-payable cycles and assumes trust that's already been earned.

Net terms are comfortable from the buyer's seat — you only pay for work you've already received. But notice what they ask of the consultant: they fund the entire engagement out of pocket, deliver it, and then wait weeks to be paid, hoping the invoice is honored promptly and in full. For an established firm with a balance sheet, fine. For an independent or small boutique on a new engagement, net-30 on the full fee is a serious cash-flow risk — they're extending you a month or more of unsecured credit on top of doing the work.

This is why the suppliers most willing to accept long net terms from a new client are often the ones with the least leverage, not the best track record. Strong independents on a first engagement will usually ask for a structure that doesn't make them your unsecured lender — a deposit, milestone billing, or escrow. That's not them being difficult; it's them managing the same risk you'd manage in their position.

Retainers

A retainer is a different animal: a fixed recurring fee — usually monthly — that buys access or capacity rather than a specific deliverable. You're reserving a consultant's availability and attention over time, common for ongoing advisory relationships, fractional executive work, or any engagement where the value is continuous judgment rather than a discrete output.

Retainers are clean when the work genuinely is ongoing and hard to decompose into milestones. The risk is that "access" is vague, and vague is where money leaks. A retainer with no definition of what it includes can drift into either party feeling short-changed — you feeling you're paying for availability you don't use, or the consultant feeling every request is scope creep. The fix is to write down what the retainer covers (hours, response times, included deliverables) and what falls outside it, so the recurring fee is anchored to something real. If the work actually has discrete deliverables, milestone billing is usually the cleaner fit — reserve retainers for genuinely continuous engagements.

Milestone billing

Milestone billing ties each payment to a specific deliverable being completed and accepted. The budget is broken into tranches, each attached to a unit of work with its own acceptance criteria, and you pay each tranche as its milestone clears.

This is the structure that best matches a defined project, because it aligns payment with progress. The consultant gets paid steadily as they deliver rather than waiting until the end, so the cash-flow burden of pay-on-completion mostly disappears. You only pay for work that's actually accepted, so your exposure at any moment is bounded to the milestone in flight rather than the whole fee. And because money moves piece by piece, any disagreement is contained to a single tranche instead of putting the entire engagement at risk.

Milestone billing depends entirely on the quality of the milestones, which is a scoping problem before it's a payment one. The connection runs straight back to your consulting project scope: the deliverables and acceptance criteria you define there are the milestones you bill against. Vague milestones produce contested invoices; crisp ones make each payment a clean, evidenced act. The discipline that makes milestone billing work is decided before you ever discuss terms.

How escrow changes the math

Every arrangement above leaves the go-first risk somewhere. Deposits put it on the buyer. Net terms put it on the consultant. Milestone billing shrinks it to one tranche but doesn't remove it — within each milestone, someone still goes first. Escrow is the only structure that takes the risk off both sides at once.

Escrow funds the budget up front into a neutral account: the money leaves your control, so the consultant can see it's genuinely committed, but it doesn't reach them either — it's held by a third party and released only as each milestone is accepted. The deposit's weakness (money in the consultant's hands you can't easily recover) and net-30's weakness (work delivered with payment not yet secured) both vanish, because the funds are simultaneously committed and gated. Neither party is extending the other unsecured credit.

To be precise about what this does and doesn't do: escrow won't dictate an outcome or return your money regardless of the facts. It's a holding-and-release mechanism, not insurance. What it changes is the risk math — your exposure drops from "the whole fee against the whole project" to "one milestone against one deliverable," and unreleased funds always sit in neutral territory rather than in either party's account. That's a structural improvement the other terms can't match, because they only move the risk around; escrow removes it. For the full mechanics of how funds move at each stage, see what is milestone escrow.

The same project, four sets of terms

It's easier to feel the difference with a number on it. Take a $60,000 engagement broken into four equal milestones, with a new independent consultant you found through a marketplace. Watch where the exposure sits at week six, halfway through.

• 50% deposit, balance on completion. You've paid $30,000 against one accepted milestone and a half-finished second one. If the consultant stalls now, recovering the overpayment is a goodwill negotiation, not a mechanism. Your exposure: roughly $15,000 of paid-but-undelivered work.
• Net-30, full fee on completion. You've paid nothing; the consultant has delivered roughly $30,000 of work and is carrying all of it on faith that you'll pay the final invoice. Their exposure: the entire amount delivered so far. A strong consultant won't accept this from a stranger.
• Milestone billing, no escrow. You've paid for the two accepted milestones ($30,000) and owe nothing more until the third clears. Cleaner — but within each milestone, someone still goes first, and the consultant is funding the in-progress third milestone unpaid.
• Milestone billing in escrow. The full $60,000 was funded up front into a neutral account; $30,000 has released against two accepted milestones, $30,000 still sits in escrow. Neither side is exposed beyond the milestone in flight, and the unreleased money never reached either party's account.

Same fee, same work, wildly different risk profiles at the midpoint. The terms aren't a formality — they decide who's holding the bag if week six goes wrong.

Red flags in proposed terms

A supplier's payment terms tell you something about how they run their business. A few patterns are worth pausing on.

A large up-front share with no milestone structure — "60% to start" against a single deliverable due in three months — concentrates risk on you and often signals cash-flow pressure. Resistance to defining milestones at all ("we'll just bill monthly for the team") usually means the work isn't scoped tightly enough to be safe for either side. Refusal to use escrow when offered, paired with insistence on a big deposit, is worth a direct conversation: a confident supplier with a track record rarely needs the money in hand before delivering. None of these is automatically disqualifying — there are legitimate reasons for each — but each deserves a question rather than a reflexive yes.

Choosing terms that are fair to both sides

Fairness here isn't a compromise that leaves both parties slightly unhappy — it's an arrangement where neither carries risk they shouldn't have to. A few principles get you there.

Match the terms to the trust. A long, proven relationship can run on net terms because the trust is already banked. A first engagement can't, and pretending otherwise just means someone's quietly exposed. New supplier, real money — reach for escrow or milestone billing, not a handshake and net-60.

Don't ask the consultant to be your bank. Pay-on-completion on the full fee, or long net terms with no deposit, asks an independent to fund your project for free and then wait. The strong ones decline; the desperate ones accept. Neither is the supplier you want.

Don't hand over money against nothing. Large up-front deposits and prepaid retainers with vague scope expose your budget with no mechanism behind it. Keep advances small and tied to concrete early deliverables.

Prefer structures that bound the risk. Milestone billing caps exposure to one tranche; escrow removes the go-first problem on top of that. Whenever the scope is clear enough to define milestones, these are fairer to both sides than the all-or-nothing alternatives — which is most of the time.

The throughline is that fair terms and safe terms are the same terms. For the practical step-by-step on applying this when you actually pay — what to release and when — see how to pay a consultant safely. Get the terms right at the start, while it costs nothing, and the rest of the engagement runs on rails instead of arguments.