← Read the full guide

CLIENT WORK HQ · 7:10 WATCH

Deposit Invoice: How to Ask for a Deposit Without Awkwardness

Published Oct 15, 2026

Read the companion guide

Our #1 pick is Workspace369.

THE TAKEAWAY

Watch it. Put it to work.

Ask for a deposit in writing, with the proposal, before anyone treats the start date as locked. State the project total, the first payment, what it lets you begin, the due date and the milestone for the balance. Example: $3,200 total, $800 first, $2,400 later. Confirm payment first, then the kickoff date.

Open on YouTube ↗Workspace369 proposals and deposits ↗
Read the video transcript +

A two-thousand-dollar project. Six hundred before work. Fourteen hundred later. How do you ask without making it awkward? Make the deposit part of the agreement, then show exactly what happens next.

A deposit request should arrive with the project terms, before anyone assumes the start date is locked. Tell the client the total price, the first payment, and what that payment allows you to begin. In our example, the total stays two thousand. Six hundred comes first. The remaining fourteen hundred comes later.

Those are illustrative numbers. Choose the amount around this project, your upfront commitments, and what the client agrees to. A small consultation and a production job with materials can have very different first-payment needs. Discuss it while you are discussing scope. A surprise payment demand after approval creates an avoidable second negotiation.

Be specific about the next milestone too. The client should know when you will ask for the balance. The useful question is not whether a deposit sounds normal. It is whether both sides understand this payment schedule. Start with the work and costs you commit before the next payment.

List those commitments before picking a percentage. For a design project, that might mean discovery, research, and an initial concept round before the first review. For a larger job, it might include a supplier reservation. Verify those costs instead of guessing at a round number. Our worked example uses a two-thousand-dollar fee, a six-hundred-dollar deposit, and a fourteen-hundred-dollar balance.

Six hundred is thirty percent of two thousand. That arithmetic explains the example; it does not prescribe your policy. If the project is long, consider agreed milestone payments instead of leaving every remaining dollar until the very end. Tie payment to a clear start, an agreed review, and the final delivery. Each moment should be recognizable.

Avoid a vague middle milestone such as halfway done. Name the actual deliverable or approval that triggers that payment. Here is a simple message you can adapt. Keep the price and next step together so nobody has to hunt. The project total is two thousand dollars.

The initial payment is six hundred, due before we begin discovery. The remaining fourteen hundred is due at the agreed delivery milestone. The proposal sets out the scope and payment schedule. Please review the proposal and deposit request. Once the agreed payment is confirmed, I will confirm the kickoff date.

That is enough. You have named the amount, the timing, the purpose, and the action you want them to take. Use a real date where you have one. Before kickoff is clearer when the proposed kickoff also has a date. If the date depends on payment, say so plainly.

Do not promise a fixed slot and quietly attach conditions later. Keep the tone practical. You are explaining the way the project starts, not apologizing for asking to be paid. Before sending, check the right client, the agreed amount, and the due date. Give the payment request a description that identifies the project and says it is the initial payment toward that project.

Avoid a bare line that only says deposit. The client should be able to connect it to the approved work. Check the payment destination and delivery address. A perfect explanation is useless if it goes to the wrong person. Where taxes apply, check the correct treatment for your location and situation before finalizing the document.

Keep cancellation and refund terms in the agreement. Do not invent those terms inside a last-minute payment email. If the client questions a term, resolve that question before starting. An unanswered concern does not disappear when work begins. Save the agreed version.

You want one clear record of the scope, schedule, and payments both sides understood. In Workspace369, deposit settings sit alongside the proposal. You can review the request in the context of the actual project. Open the proposal settings on your phone. The deposit controls belong to this proposal.

Turn on Require deposit on accept to include a deposit in this proposal’s acceptance flow. Review the percentage and calculated amount against the price you agreed with your client. Check the client-facing deposit request before sending. The amount should match the agreement. The screen here is a faithful animated example with fictional data.

Configuring a request does not mean anyone has paid. Keep those two states separate in your own process. A sent proposal, an accepted proposal, and a payment are different events. When a payment arrives, verify its status in your records before marking the corresponding project step as ready. If payment has not arrived, first check whether the client received the request and whether a question is holding it up.

A useful follow-up repeats the project, the amount due, and the next step. It should not introduce new terms. For example: checking that you received the six-hundred-dollar initial payment request for the website project. Let me know if anything needs clarifying. Once payment is confirmed, we can confirm the agreed start.

The sequence is agree the work, verify the initial payment, then confirm the reserved start. If your schedule changes while you wait, communicate the new availability. Do not silently keep a date you cannot deliver. Do not send several competing payment requests for the same deposit. Find the existing record before creating another one.

And do not treat a screenshot of a payment instruction as the same thing as a confirmed payment in your records. At reconciliation, start with the two-thousand-dollar total. Subtract the six hundred already paid. Fourteen hundred remains. That is the most important final check.

The client should be able to see how the first payment affects what remains. Use your system’s supported deposit or payment workflow. Check the records so the same payment is not counted twice. If scope changes, agree the additional work and price separately. Then review the updated total and payment schedule together.

Keep the original scope, the new request, and the separate agreement visible. A deposit does not define unlimited work. Before asking for the balance, compare the agreed price, payments received, and remaining amount. Resolve discrepancies before sending. Your repeatable process is simple: agree the schedule, request clearly, confirm payment, and reconcile the balance.

For your next project, write the first-payment explanation before you send the proposal. You will spot unclear terms much sooner. The example wording and payment checklist are in the description. Make the start clear before the work begins.