Guide6 min readUpdated
How to Compare Design Quotes Fairly Before You Hire
Learn how to compare design quotes fairly: why they differ, what a good quote must include, and the real risks of choosing only the cheapest one.
Imagine a coaching centre in Asansol asks three designers to quote for a student app. One quote says a low number. One says double. One says a number in between. The owner picks the lowest and later learns it covered only 8 screens, while the app needs 25. This guide shows how to compare design quotes so that you compare like with like.
A design quotation is a written offer that states what a designer will deliver, by when and for what price. The price is only one line of it. The other lines decide what you actually get.
Why do design quotes differ so much?
Design quotes differ because designers count different things, not only because they charge different rates. The same words, such as "app design", can mean 8 screens or 40.
The usual reasons are:
- Scope. One designer includes sign up, error states and settings. Another includes only the main screens.
- Process. One quote includes research and flow mapping. Another starts straight from the interface.
- Revisions. One quote allows two rounds. Another allows unlimited rounds with a hidden limit.
- Files and hand-off. Some quotes include organised Figma files for developers. Others hand over images.
- Experience. A designer who has built many products may price more, or less, because of speed.
- Location and team size. A solo freelancer and a studio have different costs.
For app work, a quote based on the number of screens is common. The guide on app design cost per screen explains why. For wider context, read UI UX design cost in India. Prices in the market vary, so no single number is the correct one.
What should a good design quote include?
A good quote lists the deliverables, the scope limits, the revisions, the timeline, the payment terms and the files you will own. If one of these is missing, ask for it before you compare.
Use this checklist:
- Deliverables. Exactly what you receive: screens, a logo set, icons, a prototype.
- Scope. Number of screens, pages, user roles or items. Also what is excluded.
- Revision rounds. How many, and what counts as one round.
- Timeline. A start date, stage dates and a delivery date.
- Payment terms. Amounts, due dates and payment methods.
- Files and rights. Formats, such as Figma or vector files, and who owns the final work.
- Extras. What costs more, such as extra screens or extra rounds.
- Assumptions. What the designer expects from you, such as content or feedback within 2 days.
For reference, my own logo package states 3 concepts, 2 revision rounds, vector files and guidelines for ₹1,000 to ₹1,500. App and website design is a custom quote based on screens and user roles, with 2 to 3 revision rounds. Payment is 50% to begin and 50% on completion. I give these figures only as an example of a clear structure.
How do you compare quotes line by line?
You compare quotes by putting them in one table with the same rows. Then you fill in each cell from the quote, and mark any blank as a question.
| Row | Quote A | Quote B | Quote C |
|---|---|---|---|
| Screens or items | |||
| User roles covered | |||
| Error and empty screens | |||
| Revision rounds | |||
| Timeline in days | |||
| Files you receive | |||
| Hand-off to developers | |||
| Payment split | |||
| Total price |
Fill the price row last. Many people look at it first and then stop reading. When you fill the other rows first, the price starts to make sense.
A blank cell is not a bad sign by itself. It is a question. Send the same questions to every designer. Then you compare answers, not guesses.
How do you get quotes you can actually compare?
You get comparable quotes by sending every designer the same written brief. A brief is a short document that states your goal, your users, your screens and your deadline.
Include these items:
- What the product does, in two sentences.
- Who uses it, for example sellers, buyers and an admin.
- A list of the screens you already know you need.
- Your timeline and your budget range, if you have one.
- Examples of products you like, and why.
Our guide to writing a design brief gives a simple format. If you do not know the screens yet, say so. Ask the designer to quote a first stage, such as flow mapping and wireframes, and then quote the rest. Wireframes are simple layouts that show where things go before any colour or style. You can read about the stages in wireframe vs mockup vs prototype.
You can also try the cost calculator for a first estimate, so that you know whether a quote is far from a reasonable range.
What are the risks of choosing the cheapest design quote?
The cheapest quote is risky when its low price comes from a thin scope, not from a fair rate. The risk is not the low number. The risk is the gap between what you expect and what is written.
Common problems:
- Missing screens. The app needs 25 screens and the quote covers 8. Extra screens cost extra.
- Few revisions. One round is included, and changes then cost more.
- No hand-off. The developer receives flat images and has to guess spacing and colours.
- Rushed work. A low price may mean the designer takes many projects at once.
- Hidden extras. Source files, fonts or exports cost more later.
The cheapest quote can also be perfectly fine. A new designer may charge less to build a portfolio, and a small task such as five icons may truly cost little. Ask three questions: What is included? What is not? What happens if I need more? If the answers are clear and written, a low price is a good deal.
The most expensive quote has its own risk. A high price does not prove quality. Ask the same questions of it.
What if two quotes look equal?
When two quotes look equal, choose the designer who understood your problem better. Look at the questions each one asked. A designer who asked about your users, your devices and your deadline was thinking about your product. A designer who only sent a number was not.
Also consider these points:
- Speed and clarity of replies.
- Work in your domain, such as a marketplace or a booking app.
- Willingness to explain a decision.
- Comfort on calls. Meetings over Google Meet, WhatsApp or phone should feel easy.
For a bigger choice between a solo designer and a studio, read freelance designer vs design agency. If your team is wondering about fixed prices or hourly billing, see fixed price vs hourly design projects.
Should you negotiate?
You can ask for a fair adjustment, but a lower price with the same scope is not always honest. A better request is to reduce the scope, for example by starting with the main flow. That keeps the quality and fits your budget.
If you would like a quote that follows the checklist above, you can send me your brief and I will reply within 24 hours.
Frequently asked questions
How many design quotes should I get?
+
Two to four is enough. More than that creates confusion, and each designer needs the same written brief so the quotes can be compared.
Is it fine to ask a designer to match a lower quote?
+
You can ask, but a better approach is to ask what can be removed or phased to fit your budget. Matching a price without changing the scope usually reduces quality.
Why does my quote change after I give more detail?
+
A quote is based on the scope known at that time. When you add screens, user roles or features, the work grows, so the price changes. A good designer shows what changed.
Should a quote include revisions?
+
Yes. A good quote states the number of revision rounds and what counts as a round, so you know what happens when you want changes.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.