“We’d need a contact at GIZ.” You hear it in almost every firm that starts looking at German development contracts. The assumption underneath: without a prior meeting, without someone dropping your name at the right moment, you stand no chance.
Let me be blunt. That is wrong. An upstream meeting is neither necessary nor sufficient to win a GIZ tender. It does no harm, but it never replaces the one thing that actually decides the outcome: reading what GIZ publishes, and reading it better than your competitors.
What GIZ buys, and how
GIZ (Deutsche Gesellschaft für Internationale Zusammenarbeit) is Germany’s technical cooperation agency. It runs programmes across much of West Africa and the Sahel, mandated chiefly by the German development ministry. To deliver, it buys services on a large scale: technical expertise, studies, training, implementation partners. Consultancy work makes up a significant share of its contracts, from a single expert report to a full project.
Two facts about how it procures, and both are verifiable. First, GIZ publishes its contracts for services, construction and supplies in accordance with German and European public procurement law, on digital platforms (GIZ : Procurement of Services/Construction). Second, it separates contracts awarded from Germany from those awarded in the field: for local tenders, the relevant country office runs the process. GIZ also keeps a central database of external experts where you can register (GIZ : Contractor).
The practical consequence: a firm based in Accra or Bamako does not have a single window to watch. It has several. And that is where the game is won or lost.
The real bottleneck is detection, not writing
People assume the hard part of a GIZ tender is writing it well. The hard part comes earlier: seeing the tender in time.
A call you discover three days before the deadline is already lost, no matter how good your technical proposal is. And GIZ contracts are scattered across the procurement platform, country-office announcements and sector channels. Tracking all of that by hand means an hour every morning sorting through mismatched alerts. Time stolen from writing and from fieldwork.
That is also what feeds the inside-contact myth. When you keep missing tenders because you never saw them, you conclude you need to “be in the loop.” In reality, the loop is public. It is just poorly covered.
Why the upstream meeting is neither necessary nor sufficient
Meeting a GIZ team before a call can clarify context. But the evaluation happens on paper, against a published and binding grid. A committee scoring your offer judges what is written, not the quality of your last coffee together.
Two signals are worth ten meetings, and both are open to everyone:
- The country strategy and active programmes. GIZ states its thematic priorities by country. Reading that frame lets you anticipate where the next contracts in your sector will come from.
- The award history. Public contract awards are often disclosed: who won, for what kind of work. That is perfectly legal competitive intelligence, and it tells you whether your segment is reachable or already locked up by organisations five times your size.
The bid/no-bid call is made there, before you write a line. Not in a meeting room.
Reading a GIZ tender: the grid before the pen
When the call lands, the winning reflex is not to start writing. It is to take apart the terms of reference and pull out three things, in this order:
- The eliminatory criteria. One unmet requirement (a missing administrative document, an eligibility condition you do not satisfy) and the file is dropped before the technical review. It is the most common reason for elimination, and the most avoidable.
- The technical weighting. Which section carries how many points. That dictates where to invest your writing hours. A bid that elaborates a low-weight section and rushes the decisive one loses on score, not on substance.
- The required submission format. Page limits, language, mandatory structure, how to submit. GIZ works in German, English and French depending on the contract, so confirm the required language before you start.
A development sector ToR often runs to 50-200 pages. Analysing it properly by hand takes half a day that few teams have when three calls land in the same week.
Where the tool saves time
This upstream work is exactly what Coco, the AI assistant in ICOpedia, speeds up. It reads a 47-to-200-page ToR in three minutes, extracts the eliminatory criteria, the weighting grid and the mandatory sections, and computes a match score against your profile. You keep control of the decision and the writing: Coco does not write your bid for you, it stops you spending two weeks on a contract you were never eligible for from page one.
And for detection, it is the same principle as for World Bank tenders: a watch that aggregates the sources and alerts you by sector and country, instead of leaving you to monitor ten portals one by one.
What to take away
The inside contact is a comfort, not a success factor. On GIZ tenders in Africa, the firms that win consistently are not the best connected: they are the ones who see the calls first, read the grid before they write, and say no quickly to contracts that are not for them.
Start by making yourself visible: register your organisation in the GIZ expert database, and set up a watch that genuinely covers your sources. The rest is a question of method, not relationships.
Want to see the GIZ tenders in your sector without watching every portal by hand? Try ICOpedia free, seven days, no credit card.
