Skip to content
Sanfeliu Software

Guides

Custom software quote: what it should include and how to compare two

A custom software quote should say what the software will do, feature by feature, what each feature costs, what is left out, when it will be delivered, how it is paid, what it will cost each month after handover and who will own the code. If you have two quotes that look nothing alike, don’t compare the totals: compare what each one includes. The cheaper one is almost always the one that leaves more out, or the one that counts hours which can stretch later.

Updated

Thirty minutes, free and with no obligation, with the engineer who would lead the project.

Before you ask: what to have clear

  • The problem, in one sentence. What is costing you hours or money today, and what you would like to happen instead.
  • How it is done now. Who is involved, with which programs and which spreadsheets.
  • What must not change. The ERP, the invoicing program or the way the warehouse works.
  • Who will use it. Three people in the office, the whole sales team, or your customers too.
  • The data you already have. Where it is, how many years of it, and whether anyone trusts it.
  • Whether a date is driving it. A campaign, a change in regulation or an old program that will stop working.

You don’t need a requirements document. With this, in a half-hour conversation a supplier can already tell you whether it is clear to them or whether they need to look at it more carefully first.

What a quote should include

  • The scope, by feature. What the software will do, piece by piece, written so that the people who will use it can understand it.
  • The price of each piece and the total. And if it is by the hour, how many hours there are and what happens when they run out.
  • What is left out. This is the part that saves the most arguments: if it isn’t there, everyone imagines something different.
  • The timeline and the deliveries. When you will see the first thing working and how often there will be a new one.
  • What you have to provide. Access, data, content and one person who tests each delivery.
  • How it is paid. How much up front, how much at each delivery, and how long the quote is valid.
  • The day after. Hosting, maintenance and changes: what they cost each month and whether there is a minimum term.
  • Who owns it. The code, the domain and the accounts, and where the data will be kept.

If the accepted quote is going to act as the contract, read it as a contract. We are not lawyers: if you have a legal question, have it reviewed.

How to compare two quotes that look nothing alike

  1. Put them side by side by feature, not by total. Make a list of everything that appears in either one and mark who includes it.
  2. Look at what each one leaves out. Bringing over the old data, the connections to other programs and the training are what is missing most often.
  3. Look at who carries the risk. With a fixed price, if the work runs long that is the supplier’s problem; with estimated hours, it is yours.
  4. Add what is paid every month. Compare what you will have paid after a few years, not just on delivery day.
  5. Ask what happens if you walk away one day. If the code is yours, you can carry on with another supplier; if not, you start again.

If after all this one of the two is still much cheaper, ask why. Sometimes there is a good reason; other times, the work simply hasn’t been understood.

When a quote can’t be given straight away

Some work can’t be quoted properly after a single conversation: when more than one system is involved, when nobody knows for certain how the process is done today, or when what is being asked for is to put things in order rather than one specific tool.

In those cases, a serious supplier will suggest a step first: a prototype to check that they have understood the problem, or a study that ends in a phased roadmap, with a price for each phase. A fixed price given blind ends badly for someone: either the supplier gets burned and cuts corners, or they set it high enough to cover themselves.

Warning signs in a quote

  • A single line with a total, without saying what it covers.
  • Estimated hours with no cap.
  • Not a word about what is paid after handover.
  • It doesn’t say who owns the code.
  • It arrives the same day, without anyone having asked how you work.

How we quote at SANFELIU

At SANFELIU, a custom software consultancy in Barcelona, nothing is quoted in the first conversation: it is a thirty-minute call, free of charge, to understand the problem. For a specific tool, we then build a prototype with your data in one to three days, and the price comes once you have seen it working. If the project involves the whole business or more than one system, it starts with the audit, which ends in a phased roadmap with a fixed price per phase.

The proposal is a single document of eight or nine pages: the problem in your own words, screenshots of your demo, each feature with what it includes and its price, the timeline, what is left out, the continuity plan and who owns the code. The price is fixed per feature, never by the hour, and the proposal is valid for thirty days. There is a sample proposal on the how we work page, and reference prices are public on the pricing page.

Thirty minutes, free and with no obligation, with the engineer who would lead the project.

Frequently asked questions

What should a custom software quote include?

What the software will do, feature by feature, and the price of each one; what is left out; the timeline and the deliveries; what you have to provide; how it is paid; what hosting and maintenance will cost each month, and who will own the code, the domain and the accounts.

Why are two quotes for the same project so different?

Because they are almost never quoting the same thing. One includes bringing over the old data and the other doesn’t; one counts maintenance and the other leaves it for later; one gives a fixed price and the other estimated hours. Before comparing totals, make both answer the same list of features.

Do you have to pay to get a quote?

It depends on the work it takes. For a specific tool, the quote comes out of a conversation and a look at your data. When the project touches the whole business, a study has to come first, which is fieldwork and is paid for: make sure the roadmap that comes out of it is yours and that you can carry it out with whoever you like.

What should you prepare before asking for a quote?

The problem in one sentence, how it is done now and with which programs, what must not change, who will use it, what data you have and whether a date is driving it. You don’t need a requirements document.

What about a quote for a custom website?

You look at it the same way: by feature. The pages and the languages, and whatever the website has to do besides showing things, such as bookings, a catalogue or forms that feed another program. At SANFELIU, the multilingual website has a fixed price, published on the pricing page, and each extra feature has its own fixed price in the proposal.

Tell us about your case in thirty minutes.

Book a meeting with the engineer who would lead the project: thirty minutes, free and with no obligation. If we’re a fit, we tell you how we’d start; if not, who to turn to.

Or email me@joansanfeliu.com

Prefer to write?

Tell us about your case in a few lines and we’ll reply by email.