Why you cannot compare quotes on price alone
You asked several studios for proposals and received three documents: for €1,900, €3,200 and €4,800. It is tempting to take the middle one or the cheapest, but a price gap rarely means “more expensive” and “cheaper”. It usually means each price covers something different. One contractor counts design, copy and edits, another only the build. One includes three months of support, another does not mention it at all.
So first you have to bring the quotes to a common denominator, and only then compare. This article covers the second step of the process. The first step, deciding who to ask in the first place, is in how to choose a web development company: a checklist of questions to ask before signing and the red flags. Here we assume you already have the quotes in hand.
The most reliable way to make quotes comparable is to send everyone the same requirements document. For a website that is the brief from our website brief template; for an app, the template in our app requirements document guide. If you had no document, do not worry: below we show how to put even quotes of very different shapes into one table.
Compare development proposals: a 10-row table
Make a table: contractors in columns, questions in rows. For each proposal, find the answer to every question. If the document has no answer, write “not stated” and ask the contractor later. An empty cell is information too.
| Row | What to look for in the proposal |
|---|---|
| 1. Scope of work | The list of pages, screens or features. Does it match your document? |
| 2. What is not included | Is there a “not included” section (copy, photos, translations, integrations)? |
| 3. Design | Custom or template, how many concepts and rounds of edits |
| 4. Timeline | Total time and stages. When the clock starts and what is needed from you |
| 5. Payment | Prepayment, stages, what happens if either side is late |
| 6. Ownership | Whose name the domain, code and accounts are in, who owns the result |
| 7. Third-party costs | Which subscriptions and services you pay for, and how much |
| 8. After launch | Support, bug-fix warranty, price of edits |
| 9. Quality checks | Tests, mobile screens, speed, security, forms and emails |
| 10. Proof of experience | Work in a similar niche that you can open and check |
Once it is filled in, you will almost always see that “three quotes at different prices” have turned into three different products. Now you can level them: ask the cheapest contractor to price the missing items, and ask the most expensive to show what makes up the difference. A good studio will answer calmly and item by item.
How to compare software development proposals: criteria, weights and scores
Once the scope is levelled, weighted scoring helps, a method often used in procurement when choosing suppliers. The idea is simple. You choose 6–10 criteria, give each a weight (how much it matters to you: 1, 2 or 3) and give each contractor a score from 1 to 5. Multiply score by weight and add up. The result reflects your priorities, not somebody’s gut feeling.
Which criteria to use
- Experience in your niche (weight 3): similar projects you can open.
- Clarity of scope (weight 3): it is clear what is included and what is not.
- Ownership of the result (weight 3): domain, code and accounts are in your name.
- Timeline and stage plan (weight 2): realistic and spelled out.
- Support and edits after launch (weight 2).
- Security and data (weight 2): how forms, access and backups are protected.
- Communication (weight 2): how fast and to the point they answer before the contract is signed.
- Verifiable examples and reviews (weight 2).
Change the weights to suit you. If you need a website for a bank check in a day, the weight of timeline can be 3. If the project will run for years, the weight of support is higher. The key is to agree on the weights with yourself before you see the result, otherwise the weights get bent toward a favourite contractor.
Price is deliberately not on this list. It is easier to compare separately: “how many euros you pay for one point”. That is the main figure, instead of “simply the cheapest”.
A worked example and the comparison calculator
Take an imaginary example: these are not real quotes, just an illustration. Three contractors offered €1,900, €3,200 and €4,800. After scoring on the criteria above, they got, say, 3.1, 4.1 and 4.2 out of 5 (a weighted average score, as in the calculator below).
| A | B | C | |
|---|---|---|---|
| Price | €1,900 | €3,200 | €4,800 |
| Score out of 5 | 3.1 | 4.1 | 4.2 |
| Price per point | €613 | €780 | €1,143 |
Here is what it shows. Contractor C has the best score, but the 0.1-point gap over B costs €1,600: the overpayment for each extra point is huge. Contractor A is cheapest, but 3.1 points means the proposal has weak spots you will probably pay to fix later. Often the sensible pick is B, but only if your weights really reflect your priorities.
In the calculator below, enter the prices and scores of three proposals. It shows the weighted score, the rank and the price per point, and warns you if the lowest price coincides with the lowest score. You can edit the contractor names; the criteria and weights come from the list above, so if your priorities differ, take that into account when you score.
Compare three quotes against your criteria
- Experience in your niche
- Clear scope and a “not included” list
- Domain, code and accounts in your name
- Timeline and stage plan
- Support and edits after launch
- Security and data protection
- Speed and specifics of answers before the contract
- Verifiable work examples and reviews
Enter the price of each quote and score from 1 (weak) to 5 (excellent); an empty score is ignored. The score is a weighted average across the criteria from the article, with weights 1–3 set in advance. The result is a tool for thinking, not a verdict: clarify the disputed points with the contractors.
Hidden costs: what to check besides the contract sum
Two estimates for the same sum can cost very different amounts a year later. Check four things.
- Subscriptions and services. Domain, paid email, database, mailing service, an AI model for bots. Do you pay for them directly, or through the contractor with a markup? With us, the domain and third-party subscriptions are paid by the client directly, at actual cost, with no markup, and at the start many services run on free plans.
- Price of edits. An hourly rate, a bundle of hours or unlimited text changes. Ask what counts as an “edit” and what counts as a “new feature”.
- Support. Whether it is mandatory, what it includes (updates, backups, monitoring) and whether you can decline it. With us, website maintenance is optional, in packages from €49 a month.
- Exit. What happens if you want to change contractor: will you get the source code, the access and the documentation?
Ask an accountant about taxes and mandatory payments in your country: they are not in any contractor’s estimate. For websites it also helps to look at the ownership period: compare what pays off over three years, a ready-made platform with a subscription or custom development with a one-off payment. There is a walk-through with a calculator in website builder vs custom website, and market price benchmarks are in how much a website costs.
The lowest price: when it is fine and when it is not
A low price is not suspicious in itself. A contractor may have lower overheads, ready-made building blocks, or may take on a task they have done many times. A low price combined with a vague proposal is what should worry you. Go through the list, especially if you are choosing someone in your city and want to meet in person.
- The document has no “not included” section but plenty of generic words such as “modern responsive design”.
- The timeline is two or three times shorter than the others and nobody explains how.
- The contractor will not put the domain and accounts in your name, or does not say where the project will be hosted.
- They ask for the full sum upfront with no stages.
- Questions get generic answers or no answer on time.
If even one of these five matches, ask clarifying questions in writing to all contractors at the same time and compare the answers. The speed and specifics of the reaction before signing usually predict well how the project will go. When a contractor openly says what is and is not in the price, and the price is still low, that is simply a good proposal.
The reverse is also true: a high price is no guarantee of quality. Ask them to explain what it consists of. If the answer boils down to “that is how we price it”, that is a signal.
How to decide when the scores are almost equal
Sometimes the two leaders differ by only 2–3 points. Three methods remove the uncertainty without paying extra for “the best”.
- A call with the team. Talk for 30 minutes with the people who will do the project, not only the sales manager. Ask them to retell your task in their own words: it quickly shows whether they understood it.
- Check the references. Open two or three of their projects in a similar niche on your phone. Look at speed, forms and legal pages. If you can, ask the project owner how the work went.
- A small paid stage. Instead of signing a big contract right away, order one clearly limited piece of work: a prototype, a product map or the first page. For complex systems this is how we work ourselves: an architecture session for €3,500 gives you a product map and an estimate. The fee counts toward the project, and the map stays with you either way. You can hand it to another studio for comparison.
For more on questions to ask a contractor and contract terms, see how we work and the article on choosing a studio mentioned above. Examples of finished projects are on the case studies page.
What to choose in your situation
- The quotes differ widely in price. Level the scope with the 10-row table and recalculate the price per point. Often the gap almost disappears.
- They are all about the same sum. Focus on ownership of the result, support and experience in your niche. These are things you learn about too late if you do not ask now.
- One quote is clearly cheaper than the rest. Ask it written questions about “what is not included” and about putting access in your name. A good answer makes the proposal strong.
- You have only one quote. Get at least one more so you have something to compare against. Free price benchmarks are in our articles on website and app costs.
- You urgently need a website for a bank check. Then timeline and clarity matter most. Our website in 24 hours costs €599, and the clock starts when we have the brief, the materials and access to the domain.
- The project is complex, a platform or an app. Do not compare estimates blind: fix the requirements first, ideally through an architecture session.
Still choosing a format and budget in your country? Send us the quotes you have through the contact page, and we will tell you honestly which criteria matter most for your project and what size is realistic.
Frequently asked questions
How many quotes should I collect?
Usually three to five is enough. With fewer than three it is hard to understand the market, and with more than five they are hard to compare and you lose time. It matters more that everyone gets the same requirements document.
How do I compare quotes written in different formats?
Put them in one table by rows: scope, what is not included, timeline, payment, ownership, third-party costs, support. Where the document says nothing, write “not stated” and ask the contractor.
Which criteria matter most?
For most projects: experience in your niche, clarity of scope, ownership of the result (domain, code and accounts in your name) and support after launch. But you set the weights yourself, based on your priorities.
Should I take the cheapest quote?
It is fine if the scope is clear and you know what is not included. It is worrying when a low price comes with vague text, a short timeline nobody explains and a refusal to put access in your name.
Can I ask for a discount when comparing quotes?
You can, but it is better to ask to adjust the scope: sometimes part of it can be moved out or done later, and the price drops honestly. A discount paid for with fewer quality checks usually ends up costing more.
What if I am not sure of my scores?
Ask every contractor the same written questions, hold a call with the team and look at their work in a similar niche. For large projects a small paid stage helps, for example an architecture session.
How do I decline a contractor politely?
Write briefly and to the point that you chose another proposal, and on which criterion. Good studios value feedback, and the market is small: courtesy will help on your next project.
Sources
- What is RFP scoring model? · Hyperbots
- RFP scoring: a guide to weighted scoring · Responsive
- How to set up weighted scoring for RFPs · RFP360