When to Send a Quote Instead of an Invoice

You finished a scoping call. The client wants to move ahead. Now you have to decide: do you send a quote and wait for them to accept, or do you skip that and issue an invoice for the deposit? Get this wrong and you either waste a week on paperwork nobody needed, or you invoice for work the client never actually agreed to, then spend three emails walking it back.

The decision comes down to one question: is the price and scope already agreed, or is it still a proposal? If it's a proposal, send a quote. If it's agreed, invoice.

Send a quote when the number is still a proposal

A quote is your offer. It says "here is what I will do and what it costs, and this offer holds until a date." The client has to say yes before anything is owed. That yes matters more than most people treat it.

Reach for a quote in these situations:

• The client asked "how much would this cost?" and you're answering. Nothing is agreed yet.
• The scope has options. Three tiers, an add-on, a maybe-later phase. The client needs to pick.
• The amount is large enough that someone above your contact has to sign off. A quote with a signature gives them a document to route internally.
• You want a paper trail before starting. A signed quote is your evidence that the client agreed to the price, so a dispute over the invoice later has a shorter argument.

With JupiterInvoice, a quote carries a valid until date and an accept step where the recipient types their name to sign. That name-typed acceptance is the moment scope stops being a conversation and becomes a commitment. You can see exactly how the quote acceptance step works and what the recipient sees when they open it.

Go straight to an invoice when the price is already settled

If you've already agreed the fee, in a signed contract, an email thread, or a previous quote, a second quote is friction for no reason. Invoice.

These cases call for an invoice, not a quote:

• You have a signed statement of work or contract that names the price. The agreement already exists.
• You're billing a recurring client on known terms. Your monthly retainer doesn't need re-approval every cycle.
• The work is done and the number matches what you discussed. Sending a quote after delivery is backwards.
• It's a small, standard job at your published rate. A quote adds a step the client will find odd.

When you're ready, you can create an invoice with your bank details, line items, and terms, then share the private link. The recipient opens it without an account, adds their purchase order number if they need one, and can approve it for payment.

The gray zone: agreed in principle, not in writing

Most real work sits between the two. The client said "yes, go ahead" on a call, you both know the rough number, but nothing is signed. What then?

If the amount is small and the relationship is solid, invoice and move on. If the amount is material, or the client's procurement process will demand a matching document, send the quote first. The extra day it takes to get a signed acceptance saves you from an invoice that accounts payable bounces because there's no approved figure behind it.

Watch for the AP tell. If your contact says "I'll need to raise a PO for that," they are telling you the spend has to be pre-approved internally. A quote gives them the number to build the PO against. Skip the quote and you'll often get the invoice back with a request for a PO you can't produce, because the spend was never formally approved.

How a quote flows into the invoice

The reason to quote first is that acceptance sets up everything after it. Once the client signs, you have the agreed price, the agreed scope, and a timestamp. You turn that into an invoice with the same figures, and there's nothing left to argue about.

The full path from a signed quote to a paid invoice, and how the numbers carry across, is laid out in the guide on the accepted quote to approved invoice workflow. If you're at the earlier stage and want the quote to actually get a yes, the notes on what belongs on a quote cover the fields that make a client comfortable signing.

A quick reference:

A five-second test before you send

Ask yourself: could the client reasonably say "I never agreed to this amount"? If yes, send a quote and get the name typed on the accept step. If no, invoice. That single question resolves most of the cases you'll hit.

If you're not sure your quote will land well for your kind of work, the templates and workflows on the consultant invoicing page show how the accept step fits a project sold in phases. Draft your first one and see how the acceptance reads before you send it to a real client.