Public buyers purchase a wide range of goods, works and services, from facility management to engineering studies and IT. For many suppliers, though, public procurement still looks like a closed world, full of forms and unwritten rules. In our experience, the companies that win regularly are not always the biggest. They are the ones that treat each bid as a project, with a method and a clear decision process.
Here is the approach we recommend, shaped by what we see on the buyer side.
1. Choose your tenders instead of answering everything
The first mistake is to answer every call that looks vaguely relevant. A good bid takes time: reading the file, asking questions, writing the technical response, building the price. Spreading that effort too thin produces generic bids that score poorly.
Before committing, ask a few simple questions:
- Does the scope match what we already do well, with references we can show?
- Can we meet the selection criteria: financial capacity, insurance, certifications, staff?
- Is the evaluation weighted towards price, quality or both, and where do we stand?
- Do we have the time and the people to produce a strong response before the deadline?
A clear "no bid" decision is a good decision. It frees resources for the tenders you can actually win.
2. Read the file like an evaluator
A tender file usually contains the rules of the consultation, the technical specifications, the administrative clauses and a pricing template. Suppliers often go straight to the specifications and skim the rest. That is where points are lost.
The rules of the consultation tell you exactly how your bid will be assessed: the criteria, their weighting, sometimes the sub-criteria and the expected format of the technical response. Build your answer around that structure. If the buyer asks for a methodology note in a given order, follow that order and use the same headings. An evaluator comparing several bids will thank you for making their job easier.
Note every unclear point and use the question period. Questions and answers are generally shared with all candidates, so they also show you what your competitors are worried about.
3. Get the administrative part right
A bid can be rejected before anyone reads the technical response, simply because a document is missing, unsigned or out of date. Keep an up-to-date set of standard documents: company registration extract, tax and social security certificates, insurance certificates, references and staff CVs. Check the electronic signature requirements well before the deadline, and upload early. Platforms can be slow on the last day, and a late bid is a rejected bid.
4. Write a technical response that answers the need
The technical response is where you make the difference. Avoid copying a generic brochure. Show that you have understood the buyer's context, its constraints and its risks, then explain how you will deliver:
- the organisation and the team, with named roles;
- the method, the steps and the deliverables;
- the way you will manage quality, deadlines and incidents;
- relevant references, described in terms of results and similar context.
Be concrete and verifiable. Commitments that you can demonstrate are worth more than broad promises.
5. Build a price you can defend
Price is rarely the only criterion, but it is always one of them. Fill in the pricing template exactly as requested, check consistency between the unit prices and the total estimate, and make sure your price matches the resources described in the technical response. An abnormally low offer can be questioned by the buyer and may be rejected if it cannot be justified.
6. Learn from every result
Whether you win or lose, ask for the reasons. Public buyers must inform unsuccessful candidates and can share the scores and the strengths of the winning bid. This feedback is valuable: over a few tenders, it shows you where you lose points and what to improve.
How we can help
Our consultants have run tenders on the buyer side and know how bids are read and scored. We can support your team on a single strategic bid or help you organise a recurring tender process: bid or no bid decision, file analysis, writing and review of the technical response, pricing consistency and post-award feedback.