A quote is supposed to do two things: give the client a clear number, and give you a clear yes or no. Most of the tools people use for it manage neither.
The usual workflow goes like this: write the figures in a Word doc, export to PDF, attach to an email, then wait. The client has to print, sign, scan, and email it back — or just reply "looks good" and you guess that means approval. Two weeks later you find out they wanted to change one line, but by then you've started the work. There's no record of what was agreed and no way to lock it down once they say yes.
The fix isn't a fancier PDF. It's giving the quote a real lifecycle.
What a quote needs that an attached PDF doesn't have
A quote is a small contract. To be useful as one, it should have:
- A status that both sides can see. Draft, sent, accepted, declined, expired. Not "I think they replied yes."
- A single canonical version. What the client sees is what you sent — not a copy that could have been edited after the fact.
- A clear acceptance moment. A timestamp, an action, a record. Not a forwarded email chain.
- A clean path to invoicing. Re-typing the same line items into an invoice is the single most error-prone step in the cycle.
A PDF in an inbox has none of these. A quote on a stateful page has all of them.
A quote lifecycle that holds up
The simplest model that works in practice has six states:
`` draft → sent → accepted → converted (invoice created) ↓ declined | expired ``
You move draft to sent when you're ready for the client to see it. The client moves sent to either accepted or declined — usually by clicking a button on a page rather than replying to email. You can mark a sent quote as expired manually, or set a "valid until" date that does it automatically.
Once a quote is accepted, declined, or converted, it's locked. That sounds restrictive but it's the only way the signed version stays trustworthy. If you can edit a quote after the client accepted it, then "accepted" doesn't mean anything.
Numbering quotes separately from invoices
Use a separate number series for quotes — something like QUO-2026-001 rather than reusing invoice numbers. There's a practical reason: most quotes don't become invoices. If your sequence is shared, every declined quote leaves a gap in your invoice numbering. EU tax authorities expect invoice numbers to be contiguous per prefix-year. A 30% acceptance rate on quotes becomes a 30% completeness rate on invoices, which is awkward to explain.
Reset the counter at year boundary. QUO-2026-042 should be followed by QUO-2027-001 in January, not …-043. This makes per-year reporting effortless and matches how most accountants want to see the figures laid out.
Convert, don't re-type
When a quote is accepted, the next step is invoicing the same work. Every minute spent copying line items, tax rates, and notes from one document to another is a minute spent introducing typos.
The convert action should:
- Create a new invoice with the same client, line items, tax rate, currency, and notes.
- Mint a fresh invoice number from your invoice sequence — not the quote sequence.
- Record a reference back to the source quote, so the audit trail is intact.
- Be idempotent. Clicking Convert twice in a row should return the same invoice, never create a duplicate.
That last point matters more than it sounds. Browsers retry. Clients double-click. If your conversion isn't idempotent, you'll eventually issue two invoices for the same accepted quote, and one of them will be paid while the other ages into overdue and triggers reminder emails to a confused customer.
Send the link, not the attachment
Most quote PDFs are opened once and never again. The client glances at them in their phone preview, decides they'll "look at it properly later," and never does.
Replacing the attachment with a private link changes the friction in two directions. The recipient gets a clean page that loads in any browser without downloads. You get a record of when they opened it, how many times, and from where. If they want to ask a question, there's a form on the page — and the message goes straight to your invoicing email rather than getting lost in their reply-to-an-attachment.
The link should be unguessable (192 bits of entropy is plenty) and revocable. If a deal goes cold and you don't want the quote sitting at a public URL, revoke and the link 404s.
Use "valid until" honestly
The "valid until" date on a quote isn't decoration. It's the cleanest way to handle the awkward conversation that starts with "we'd like to go ahead — is the price still good?" three months after you quoted it.
Set the date based on how confident you are in the inputs. A fixed-scope project with current rates: 30 days. A complex engagement priced against your current team availability: 14 days. A pass-through quote that includes a third-party cost (hardware, hosting, a sub-contractor): match the validity of that upstream price.
When the date passes, the quote auto-expires. If the client comes back, you issue a fresh one — possibly the same number with a new validity, possibly a revised one. Either way, no awkward back-pedalling.
What this looks like in Plain Statement
We built quotes the way we wished they worked. Each quote has its own numbered series (QUO-YYYY-NNN), runs through the lifecycle described above, and locks once accepted. The share link goes to a clean, branded page where the recipient can Accept, Decline (with a reason), or send a question. When you hit Convert on an accepted quote, the resulting invoice carries a sourceQuoteId reference so your audit trail is complete.
The whole quote workflow is part of the Basic plan. Try the free quote generator — quote PDFs are free to create and download without an account.