Secret ingredients to quality software


Do you know when to go for a Tender?

Created on 04 Sep 2020 | Last updated by Ulysses Maclaren on 21 Oct 2020 05:36 AM (6 months ago)

Tenders, RFP (Request for Proposals) RFQ, (Request for Quote) plus other various names, are all a way for an organisation to conduct a buying process with set rules and a supposedly level playing field. For the most part, certain elements of Tenders can be counter-intuitive to building great software. In many cases, it needs the buyer to know exactly what the end product will be. Plus the buying process can require the tendering company to spend large amounts of time with a very low chance of success, unless you follow a few principles.

Government departments are a classic example of an organisation that needs to produce Tenders. There is a fiduciary requirement when spending public money that the purchasing process is transparent and allows all suppliers to compete on a level playing field. These can be very time consuming and expansive documents and they limit contact with key stakeholders and decision-makers.

Why is it a problem for software consultancies?

Most Tenders have a few things in common when it comes to software. They are very rigid and are structurally counter-intuitive to the agile method of building software. Often, Tenders have rigid rules and look for a fixed price with complicated and time-consuming processes to alter the agreed-upon framework.

What is the problem for sales teams?

There are never any guarantees of winning any work regardless of the efforts taken to win business, but Tenders often invite significantly more competitors that you would generally need to compete with. Secondly, Tenders are written documents that are supposed to level the playing field - this is not always the case.

Generally when a supplier and vendor relationship is formed, there are 1000's of data points - reputation, past client success, culture, displayed skills, communication style, internal disciplines, plus many other intangible items. Tenders often don't ask questions where the relevant strengths of a supplier can be demonstrated - you are forced to only answer the questions asked.

Tenders can favour an incumbent supplier - or suppliers with an intimate knowledge of the client.

Be selective with tenders you reply to

Tenders are time-consuming for a sales team and generally need a process like a spec review performed at no cost, in order to complete a response and, as a result, decision to submit a tender needs to follow a few key principles:

  1. Do you have a pre-existing relationship with the key stakeholders, or does the tendering process allow you to build a relationship where you can not only complete a document, but some of the intangibles are taken into account in person-to-person meetings.
  2. Although organisations will generally be guarded about information about the competitors, if there are any more than 4 known competitors and the above no. 1 point about the relationship is not strong enough to make the vendor feel that they will be naturally shortlisted, do not respond. You are probably only there to make up the numbers.
  3. Look carefully at the process to make changes and how detailed the scope is. Also, see if a spec review can be undertaken to fine-tune the estimates and scope. Plus make sure the process of Agile development is something that can be undertaken.

Tenders can be a waste of time, with low skilled assessment by purchasing people who can overly focus on cost and a narrow set of requirements. Only go for them if you have a good chance of winning.

We open source. This page is on GitHub