A quote is often the deciding document that convinces a potential client to hire you over other options. It is not just a price list; it is the formal presentation of how you will solve their problem and under what terms you will work together.
This guide covers the full process: what to ask before quoting, how to structure the document, how to price it, and how to send it to maximize your chances of closing.
What is a professional quote and why it matters
A quote (sometimes referred to as a proposal or estimate, depending on the level of detail) is the document where you outline the scope of the services you offer, the delivery timeline, and the total cost.
Sending a WhatsApp message saying “I’ll charge you $500 for the website” is not a quote. It lacks context, sets no boundaries, and leaves the door open to endless revisions and confusion regarding payment methods.
A well-crafted quote:
- Conveys professionalism and justifies your pricing.
- Establishes a clear boundary for the scope of work (preventing the dreaded scope creep).
- Sets the rules of the game before starting.
It helps to distinguish it from its neighboring documents, because clients tend to mix them up:
| Document | What it is | When it’s used |
|---|---|---|
| Estimate | Cost approximation, non-binding | Early exploration |
| Quote | Firm price and scope, with a validity period | Before hiring |
| Proposal | Quote + value argument and context | Competitive projects |
| Invoice | Billing document for agreed work | After hiring |
Before quoting: never quote blind
The most expensive mistake does not happen while writing the document, but before: quoting without understanding the project. If the client asks for “a website” and you reply with a price, one of you is going to lose.
Schedule a short call or send a few questions first. At a minimum you need to know:
- The business goal. What is the website, logo, or campaign for? Selling, capturing leads, presenting the company. The goal changes the scope.
- The available inputs. Do they have copy, photos, brand guidelines, access credentials? Everything missing is work for you or a third party, and it must show up in the price.
- The expected timeline. An unrealistic deadline caught early saves you from quoting a project you cannot deliver.
- The budget range. Asking about budget makes many freelancers uncomfortable, but it saves weeks. If the client has a third of what the project costs, better to know before investing hours in the document. And if they have more room than you imagined, you can propose a more complete scope instead of undercutting yourself.
Steps to create the quote
1. Clearly define the scope
Write out in detail what you will do. Instead of writing “Website design,” specify: “Design of a 5-page website (Home, About Us, Services, Blog, Contact), optimized for mobile devices.”
Equally important is clarifying what is not included. For example, if you design the website but do not write the copy or provide hosting, state it explicitly. Exclusions are not stinginess: they are the difference between a profitable project and one that eats your weekends.
2. Estimate delivery times
Break the project down into milestones or phases. Clients appreciate knowing when they will receive progress updates, and for many of them the timeline weighs as much as the price in the decision.
For example:
- Phase 1: Wireframes (5 business days after the upfront payment).
- Phase 2: Visual design and development (15 business days).
Notice the detail: deadlines run “after the upfront payment,” not from the moment the client says yes. That small phrase prevents a project approved in January and paid in March from wrecking your calendar.
3. Set the price and payment terms
Avoid leaving the price as an isolated number at the end of the document. Break it down if the project is complex, or provide a fixed price if the service is packaged.
On pricing models, the three usual options:
- Fixed project price. The clearest for the client. Works when the scope is well defined.
- Hourly rate. Useful for maintenance or fuzzy scopes, but it transfers the uncertainty to the client and tends to create more friction at approval time.
- Packages or tiers. Offering two or three options (for example, “basic website” and “website + blog + initial SEO”) turns the conversation from “yes or no?” into “which of the two?”. It also protects your price: if the budget is short, the client picks the smaller package instead of haggling down the bigger one.
If you charge applicable taxes in your country, you must clarify: does the price include taxes, or are they added at the end? A tax surprise on the invoice is one of the fastest ways to damage trust.
Also, define how you expect to receive the money. It is standard practice in freelance work to ask for an upfront payment. For instance, “50% upfront and 50% upon final delivery.”
4. Give it an expiration date
Every quote needs a validity period (“prices valid for 15 days”). It serves two purposes: it protects you from a client showing up eight months later demanding a price that no longer works for you, and it creates a legitimate reason to follow up without sounding pushy.
If you need help structuring the specific sections of this document, we recommend reviewing our checklist on what to include in a quote.
Clear quote example
Below is a fictional, simplified model of what the body of a quote looks like:
Quote #042 - Visual Identity
Client: ABC Company Date: August 23, 2026 Validity: 15 days
Project Scope:
- Logo Design (3 initial concepts).
- Basic brand guidelines (typography, color palette).
- Not included: packaging design or printing.
Investment:
- Logo: $800 USD
- Brand guidelines: $300 USD
- Total: $1,100 USD (Taxes not included)
Payment Terms: 50% deposit to schedule the project. Remaining 50% before the delivery of editable files.
Revisions: Includes up to 2 rounds of revisions on the chosen concept.
Mistakes that kill quotes
Before sending, make sure you are not committing one of these classics:
- Burying what matters. The client will scan the document, not read it word by word. Total price, timeline, and what’s included must be findable in seconds.
- Talking only about yourself. Two pages of career history and certifications before mentioning the client’s problem. Reverse the order: their need first, your solution second, your credentials last.
- Over-quoting “just in case.” Padding the scope with things the client never asked for raises the price and lowers clarity. What they did not ask for goes in an optional section, with its own price.
- Making the price negotiable by design. Phrases like “price open to discussion” invite haggling. A firm price with scope options negotiates better than a soft number.
- Sending and disappearing. A quote without a follow-up plan is a coin toss.
How to send it and follow up
The way you present the quote matters just as much as the content itself.
Avoid sending loose text in an email body. Send it as a PDF or via a link to a specialized platform, accompanied by a brief and polite message.
- The delivery: “Hi [Name], I’ve attached the quote for the project we discussed. Let me know if you have any feedback.”
- The follow-up: If you do not receive a response in 3 or 4 days, send a friendly message asking if they had a chance to review the document or if they have any technical questions about the scope.
The role of professional tools
Keeping track of sent, approved, and rejected quotes in spreadsheets can quickly become chaotic when managing multiple prospects simultaneously.
With tools like Pagatu, you can centralize your clients, generate organized documents, and know exactly what stage every commercial negotiation is at, making it easier to subsequently request the upfront payment without switching platforms. And if a service repeats, templates and variables save you from building every quote from scratch.
What to do when the client accepts
Congratulations! If the client gives you the green light, the next step is to formalize the agreement via a simple contract, if your service requires it, and request the corresponding deposit payment.
Remember that the quote is the map that will guide the project. Keep it safe and use it as a reference if the client requests new features during development that were not budgeted for: the conversation changes completely when you can reply “sure, that’s outside the approved scope, I’ll prepare an add-on” with the document in hand.