Skip to content

Free buyer tool · runs in your browser

Compare software development quotes side by side.

Put two to four software development quotes next to each other. The tool turns each one into the same figures, flags what a quote leaves out, such as testing, a warranty or IP ownership, and writes the questions to send each vendor. It works only from the numbers you enter, and nothing leaves your browser.

ExampleThree fictional quotes from Vendor A, B and C, so you can see how a comparison reads. Type over them, or start blank.

Your quotes

Two to four quotes. Enter what each quote states and leave the rest empty: the tool works only from your numbers and never fills a gap with an assumed rate. Nothing you type leaves your browser.

Quote 1: Vendor A

Leave empty if the quote gives only a rate.

Only if the quote states one.

What the quote includes
Quote 2: Vendor B

Leave empty if the quote gives only a rate.

Only if the quote states one.

What the quote includes
Quote 3: Vendor C

Leave empty if the quote gives only a rate.

The monthly price, per person or for the whole team.

What the quote includes

3 quotes compared. Vendor A: 0 items to check; Vendor B: 9 items to check; Vendor C: 2 items to check.

Side by side

The quotes side by side: the numbers you entered, the figures worked out from them, and what each quote includes.
FieldVendor AVendor BVendor C
Pricing modelFixed priceFixed priceDedicated team
Total price$48,000$21,000$55,385
How the total was foundas quotedas quotedworked out: monthly rate × timeline
Timeline16 weeks7 weeks20 weeks
Team size423
Estimated hours960––
Rate as quoted––$12,000 per month, whole team
Cost per week$3,000$3,000$2,769
Cost per month$13,000$13,000$12,000
Effective hourly rate (total ÷ hours)$50.00––
Payment milestones42–
Paid upfront20%50%–
Change-request termsIn writingNot statedIn writing
Discovery and requirementsIncludedMissingMissing
UX/UI designIncludedIncludedMissing
QA and testingIncludedMissingIncluded
Project managementIncludedMissingIncluded
DevOps and deploymentIncludedIncludedIncluded
DocumentationIncludedMissingIncluded
Post-launch warrantyIncluded, 8 weeksMissingMissing
Ongoing maintenanceMissingMissingIncluded
Source code and IP assigned to youIncludedMissingIncluded
Hosting and infrastructureMissingMissingMissing
Third-party licencesMissingMissingMissing
Items to check092

What each quote leaves open

Gaps are items most buyers expect a quote to cover. Checks are numbers or terms worth confirming. Notes are items often left to the client, worth knowing either way.

Vendor A

  • NoteOngoing maintenance: not included

    Software needs security patches, dependency updates and small fixes after launch, whoever does them.

    Adding it: Usually a separate monthly retainer or hourly support after the warranty ends. Ask for its terms now, not after launch.

  • NoteHosting and infrastructure: not included

    Servers, databases and cloud services are a running cost. Know whether this quote covers them or leaves them to you.

    Adding it: Usually billed to you by the cloud provider, or passed through by the vendor. Ask for the expected monthly bill.

  • NoteThird-party licences: not included

    Paid libraries, APIs, maps, email or payment services carry their own fees, sometimes per user.

    Adding it: Usually paid by you to each provider. Ask for a list of every paid service the build depends on.

Vendor B

  • GapDiscovery and requirements: not included

    Without a written scope the price has nothing firm to stand on, and every later disagreement turns into a change request.

    Adding it: If it is not in the quote, it is usually sold as a separate paid phase before the build, or folded into the first sprint at the vendor’s rate.

  • GapQA and testing: not included

    Without dedicated testing, defects are found by your users after launch, when they are the most expensive to fix.

    Adding it: Often added as tester hours or a share of the development effort. Ask for it as its own line so you can see it.

  • GapProject management: not included

    Someone has to run the schedule, the scope and the communication. If the vendor does not, you will.

    Adding it: Usually a project manager’s hours or a set share of the fee. Ask who your day-to-day contact is.

  • GapPost-launch warranty: not included

    A warranty means defects found after launch are fixed at the vendor’s cost. Without one, every fix is billable.

    Adding it: Some vendors include a set bug-fix window, others bill fixes as support hours. Get the period and what it covers in writing.

  • GapSource code and IP assigned to you: not included

    If the contract does not assign the code to you, the vendor may keep the rights to it. In the US, commissioned software is not one of the nine kinds of work that can be “made for hire”, so a written assignment is what transfers it.

    Adding it: A contract clause rather than a price item. Ask for full assignment on payment and access to the code repository from the start.

  • CheckFixed price with no change-request terms

    A fixed price covers the agreed scope only. Without written terms for changes, every new request is priced on the spot.

  • CheckTimeline much shorter than the others

    7 weeks against a median of 18 weeks for the other quotes. Check that the scope is the same.

  • CheckPrice much lower than the others

    Under half the median of the other quotes in USD ($51,692). Check what is left out before comparing on price.

  • CheckHalf or more paid before any delivery

    50% upfront. Paying against delivered milestones keeps the risk shared.

  • NoteDocumentation: not included

    Without technical and handover documents, the next team has to relearn the system before it can change anything.

    Adding it: Usually a few extra hours at the end of the build. Ask which documents you receive at handover.

  • NoteOngoing maintenance: not included

    Software needs security patches, dependency updates and small fixes after launch, whoever does them.

    Adding it: Usually a separate monthly retainer or hourly support after the warranty ends. Ask for its terms now, not after launch.

  • NoteHosting and infrastructure: not included

    Servers, databases and cloud services are a running cost. Know whether this quote covers them or leaves them to you.

    Adding it: Usually billed to you by the cloud provider, or passed through by the vendor. Ask for the expected monthly bill.

  • NoteThird-party licences: not included

    Paid libraries, APIs, maps, email or payment services carry their own fees, sometimes per user.

    Adding it: Usually paid by you to each provider. Ask for a list of every paid service the build depends on.

Vendor C

  • GapDiscovery and requirements: not included

    Without a written scope the price has nothing firm to stand on, and every later disagreement turns into a change request.

    Adding it: If it is not in the quote, it is usually sold as a separate paid phase before the build, or folded into the first sprint at the vendor’s rate.

  • GapPost-launch warranty: not included

    A warranty means defects found after launch are fixed at the vendor’s cost. Without one, every fix is billable.

    Adding it: Some vendors include a set bug-fix window, others bill fixes as support hours. Get the period and what it covers in writing.

  • NoteUX/UI design: not included

    Without design, developers decide layouts while they code, and screens tend to be reworked once users see them.

    Adding it: Usually quoted as separate design hours or a design phase. Ask whether you get a clickable prototype or only image files.

  • NoteHosting and infrastructure: not included

    Servers, databases and cloud services are a running cost. Know whether this quote covers them or leaves them to you.

    Adding it: Usually billed to you by the cloud provider, or passed through by the vendor. Ask for the expected monthly bill.

  • NoteThird-party licences: not included

    Paid libraries, APIs, maps, email or payment services carry their own fees, sometimes per user.

    Adding it: Usually paid by you to each provider. Ask for a list of every paid service the build depends on.

Questions to ask each vendor

To Vendor A

  1. What does ongoing maintenance cost after launch, and on what terms?
  2. Are hosting and infrastructure costs included, and whose name are the cloud accounts in?
  3. Which paid third-party services or licences does the build depend on, and who pays for them?

To Vendor B

  1. Is a discovery or requirements phase included, and what written document does it produce?
  2. Who tests the software, how (manual, automated or both), and is that effort in this price?
  3. Who manages the project day to day, and is their time included in this price?
  4. Is there a post-launch warranty, how long is it, and what does it cover?
  5. Does the contract assign all source code and IP to us on payment, and do we have repository access from the start?
  6. How are change requests estimated, approved and billed against the fixed price?
  7. Your timeline is shorter than the other quotes: what is in scope, and how many people work on it?
  8. Your price is well below the other quotes: what does it exclude that they might include?
  9. Can the payment schedule follow delivered milestones rather than an upfront share?
  10. Which documents do we receive at handover: technical, API, deployment and user guides?
  11. What does ongoing maintenance cost after launch, and on what terms?
  12. Are hosting and infrastructure costs included, and whose name are the cloud accounts in?
  13. Which paid third-party services or licences does the build depend on, and who pays for them?

To Vendor C

  1. Is a discovery or requirements phase included, and what written document does it produce?
  2. Is there a post-launch warranty, how long is it, and what does it cover?
  3. Is UX/UI design included, and do we receive the design files and a clickable prototype?
  4. Are hosting and infrastructure costs included, and whose name are the cloud accounts in?
  5. Which paid third-party services or licences does the build depend on, and who pays for them?

How this tool decides

  • Every figure is one you entered, or arithmetic on what you entered. The tool holds no rates, salaries or market prices.
  • Prices are compared only between quotes in the same currency. The tool does not convert currencies.
  • Cost per week is the total divided by the timeline in weeks. Cost per month is that figure × 52 ÷ 12.
  • Effective hourly rate is the total divided by the estimated hours, shown only where you entered hours.
  • With no total entered, the total is worked out from hours × hourly rate, or from the monthly rate × the timeline (× team size for a per-person rate), and marked as worked out.
  • A timeline is flagged when it is under 70% of the median of the other quotes.
  • A price is flagged when it is under 50% of the median of the other quotes in the same currency.
  • The numbers are flagged when a worked-out total differs from the quoted total by more than 10%.
  • An upfront payment of 50% or more of the price is flagged.

These are this tool’s own rules of thumb, not an industry standard. Source for the IP line: US Copyright Office, Circular 30: Works Made for Hire (the nine kinds of commissioned work that can be made for hire; software is not one of them) (opens in a new tab), checked 2026-10-18.

What this tool does


Same figures, same checklist, one table.

  • 01

    Normalise the numbers

    A fixed price, an hourly estimate and a monthly team become the same figures: total, cost per week, cost per month and, where hours are given, an effective hourly rate.

  • 02

    Find what is missing

    Eleven items a quote should state, from QA and project management to a warranty and IP ownership. Each gap says why it matters and what adding it usually involves.

  • 03

    Ask each vendor the right questions

    Every gap and every odd number becomes a question for that vendor. Copy them, download the table as CSV, print it, or share the whole comparison as a link.

FAQs · Quote comparison


Comparing software quotes · frequently asked questions

What a quote should include, how to compare pricing models, and what the tool does with your numbers.

At least the scope it prices, the pricing model, a total or an hour estimate, a timeline, the payment milestones and the terms for changes. Then what it covers: discovery, design, QA and testing, project management, deployment, documentation, a post-launch warranty with its period, and who owns the code. The tool checks each quote against that list.
Put both on the same basis. The tool divides each total by its timeline to give a cost per week and per month, and by the estimated hours, where the quote gives them, to give an effective hourly rate. A time and materials quote with no hour estimate has no total to compare, and the tool says so rather than guessing one.
Not when it leaves things out. A low price next to missing QA, no warranty or no change-request terms often means the cost arrives later, as extra hours or a second vendor. The tool flags a price under half the median of the other quotes in the same currency so you check its scope before choosing on price.
Get it in writing either way. In the US, the Copyright Office lists nine kinds of commissioned work that can be "made for hire", and software is not one of them, so without a written assignment the rights can stay with the vendor that wrote it. Ask for full assignment of the code and IP on payment, and repository access from the start.
No. It holds no rates, salaries or market prices of any kind. Every figure it shows is a number you entered, or arithmetic on those numbers, and its rules of thumb are printed beside the result.
No. The comparison runs in your browser. The share link keeps your inputs after the # in the address, which browsers do not send to a server, so a link only reaches the people you give it to.

Next step


Want a quote you can compare line by line?

QalbIT quotes a fixed scope, a monthly dedicated team or hourly time and materials. Ask for a written quote and hold it against the others with this tool.

More free tools


More free tools

Each one opens on a worked example and shows its answer without a signup.

All free tools