Estimates and invoices serve different purposes in business. Learn when to send an estimate, when to send an invoice, how they differ legally, and how to use them together in your workflow.
Before you do any meaningful amount of work for a client, there's a document that precedes getting paid: the estimate. After the work is done, there's another document that demands payment: the invoice. Getting these two confused—or using the wrong one at the wrong time—is one of the most common freelancer mistakes.
This guide clarifies exactly what estimates and invoices are, how they differ, when to use each, and how to use them together in a smooth client workflow.
An estimate (also called a quote, proposal, or bid) is a document that tells a prospective client how much you expect to charge for specific goods or services. It's sent before work begins to get client approval and establish expectations.
An estimate communicates:
An estimate is a sales document—its job is to sell the client on working with you and get their approval to proceed.
An invoice is a formal request for payment issued after goods or services have been delivered. It demands payment for value already provided.
An invoice specifies:
An invoice is a billing document—its job is to get you paid.
| | Estimate | Invoice |
|---|---|---|
| When sent | Before work begins | After work is completed |
| Purpose | Sales — get approval to start | Billing — collect payment |
| Payment demand | Not yet | Yes — specifies amount due |
| Obligation | Not a payment obligation | Creates payment obligation |
| Binding? | Not typically; varies by state | Yes, once accepted by client |
| Legal status | Proposal/invitation to negotiate | Debt instrument |
| Reversal | Can be revised before approval | Should not be revised after sent (use credit memo) |
| Followed by | Invoice (once work is done) | Receipt (once payment received) |
| Common numbers | EST-001, QUO-001, PROP-001 | INV-001, BILL-001 |
Send an estimate in these situations:
Any project where you expect to be paid—regardless of size—should begin with an estimate or proposal. This establishes the scope, price, and terms before any work starts.
Exception: For very small, quick jobs (a 1-hour task, a minor deliverable), you might just invoice after completion without a formal estimate. But even a brief "this will cost approximately $[X]" message in writing before starting creates important documentation.
For projects over $2,000 or spanning more than 2 weeks, a detailed estimate or formal SOW (Statement of Work) is essential. This protects you from scope creep and establishes a clear contractual baseline.
If a client asks "How much would this cost?", they're asking for an estimate. Respond with a formal estimate document—not an invoice.
Any time you're offering custom pricing (not a standard rate card), send an estimate so the client can see the breakdown and approve before you begin.
Send an invoice in these situations:
The moment work is completed and accepted (or after the deliverable is provided), send an invoice. Don't wait days or weeks—invoice immediately to maintain cash flow.
For multi-phase or long-term projects, invoice at agreed milestones. This prevents you from doing months of work before getting paid.
For ongoing retainer arrangements, send invoices on the agreed schedule (monthly, quarterly). Retainer invoices are often the same amount each period—automating them saves significant time.
If a client approved an estimate but the project hasn't started yet and requires a deposit, invoice for the deposit upfront.
Here's how estimates and invoices work together in a typical client engagement:
CLIENT INQUIRY
↓
SEND ESTIMATE / PROPOSAL
↓
CLIENT APPROVES (signs estimate, sends deposit, or confirms in writing)
↓
BEGIN WORK
↓
[Milestone 1] → SEND MILESTONE INVOICE #1
↓
[Milestone 2] → SEND MILESTONE INVOICE #2
↓
WORK COMPLETED
↓
SEND FINAL INVOICE
↓
CLIENT PAYS
↓
SEND RECEIPT
Step 1 — Estimate (before work):
> "Hi Client, as discussed, here's my estimate for your new website:
> - Discovery & Strategy: $1,500
> - Homepage Design: $2,000
> - Inner Pages (5): $2,500
> - Mobile Development: $1,500
> - Total: $7,500
> This estimate is valid for 30 days."
Step 2 — Invoice (after each milestone):
> "Invoice #1023 — Milestone 1: Discovery & Strategy — $1,500, due Net-30."
Step 3 — Final Invoice (after completion):
> "Invoice #1027 — Final Payment: Website Project — $3,000, due on receipt."
Yes—but it's riskier.
If you do work without a prior estimate or agreement, you're working on a "time and materials" basis with an implied contract. The client implicitly agreed to pay reasonable rates for work performed. An invoice after the fact is your way of documenting what you did and what it's worth.
However:
Best practice: Always send an estimate before significant work.
In most invoicing tools, you can convert an estimate to an invoice—essentially copying the line items from the estimate into a new invoice document. The invoice gets a new number and a new date, but the pricing typically matches the approved estimate.
This is a good workflow:
Important: Don't send the same estimate as both an estimate AND an invoice. That's confusing. Use estimates for pre-work; invoices for post-work.
A quote and an estimate are essentially the same thing. In practice:
Both are non-binding price proposals. If you're in a trade (construction, manufacturing), quotes may be more legally binding depending on the industry and jurisdiction.
A proposal is a more detailed estimate that typically includes:
Think of a proposal as an estimate dressed for a formal business presentation. For large engagements ($10,000+), proposals are more professional and persuasive than simple estimates.
Never invoice for work that hasn't been approved. Send an estimate first, get approval in writing, then do the work.
If you send an "invoice" before work is done, clients may treat it as optional. Use the correct terminology.
Estimate approved, work done, and you forgot to invoice? This happens constantly. Set a reminder: when you mark a project "complete," send the invoice immediately.
If your invoice amount doesn't match your approved estimate, the client will question it. Either the invoice should match the estimate, or you need to clearly communicate why there's a difference (scope change, additional work, etc.).
Estimates need unique numbers too. EST-001, EST-002, etc. Without numbering, it's impossible to track which estimates were sent to which clients and which were approved.
Estimates and invoices are not interchangeable—they serve different purposes at different stages of the client relationship.
The rule: Estimates before work. Invoices after work. Never confuse the two.
Using them correctly protects you legally (clear scope and approval before work), manages client expectations (they know the price before you start), and ensures you get paid (you have a professional invoice that demands payment after delivery).
Want to create professional estimates and invoices in one place? Try Eonebill Free
View Pricing → | Blog Home → | Home →

Ready to switch? Start for free — no credit card, no contracts, just faster payments.
Start Free →Join the community
Subscribe to our newsletter for the latest news and updates
Ready to streamline your freelance workflow?