Count the places a tender can surface in Senegal. The national public procurement portal. World Bank and African Development Bank notices on their own platforms. Announcements from the AFD, the European Union, USAID, the UNDP. Sector channels run by ECOWAS and WAEMU. The country offices of agencies that publish locally rather than from headquarters.
Now be honest about how many of these you actually check each morning. Three? Four? That gap is precisely where the difference lies between the firms that win consistently in Dakar and those that discover the right contracts three days after they close.
In Senegal, the problem is almost never knowing how to respond. It is seeing the call in time.
Why the Senegalese market is so fragmented
Senegal has one of the densest concentrations of international cooperation activity in West Africa. Dakar hosts regional offices of UN agencies, development banks and international NGOs that cover the entire Sahel corridor from the capital. The direct consequence: contracts are plentiful, but they do not pass through a single window.
Three families of sources coexist, and they do not talk to one another:
- National public procurement, published on the country’s regulatory portal. This is where state-funded and loan-financed contracts appear, often with a share carried out by local providers.
- Multilateral and bilateral donor contracts, each published on its own platform: the World Bank, the African Development Bank, the AFD, the European Union, USAID, the UNDP. A single intervention in Senegal can generate notices on two or three of these channels at once.
- Regional and sector channels: ECOWAS and WAEMU run their own procurement, and some announcements move through country offices rather than headquarters.
A Dakar-based firm trying to cover its sector does not have one site to open in the morning. It has ten. And none of them tells you what the other nine have published.
The hidden cost nobody measures
Here is the calculation I rarely see written down plainly. Monitoring ten portals by hand, checking for new entries, opening each notice to decide whether it concerns you, costs an hour every morning. Sometimes more, when several calls land in the same week.
That hour is stolen from something. From the proposal in progress. From following up on a submitted file. From the time your strongest writer should spend on the technical section instead of sorting through alerts. The cost of manual monitoring is not a line in a budget. It is core work chipped away every single day.
And the worst part is not even the lost time. It is that the lost time is not enough. By watching a handful of portals, you do not just have an illusion of coverage: you have the illusion and the blind spot together. You have seen one room of the house and you believe you have walked the whole place.
Keyword calibration, the silent trap
There is a second layer to this, and a subtler one. Even on the portals you do watch, you filter. You have set alerts on “health,” “water,” “training.” Reasonable. Except a tender squarely in your field can be published under a label you never anticipated: “capacity building,” “technical assistance,” “feasibility study” in a sector your keyword does not catch.
So the call exists, it is public, it is open, and you never see it. Not through negligence, but because your reading grid was too narrow. A keyword that is too precise shields you from noise and cuts you off from real opportunities. A keyword that is too broad drowns you. Calibrating that balance by hand, across ten portals with different logics, is a full-time job nobody has.
What changes when detection is covered
The right answer is not to work harder on monitoring. It is to take it out of your hands. Serious coverage of the Senegalese market aggregates national, multilateral and regional sources continuously, then delivers a digest filtered by theme and country instead of leaving you to open each portal one by one.
That is the principle ICOpedia is built on: a watch that continuously scrapes more than a hundred public sources across francophone Africa, including the portals and donors active in Senegal, and alerts you by sector. You do not configure ten separate alert systems. You describe your field once, and the relevant calls surface, including those whose wording would never have triggered your own filter.
For detection in Senegal, the logic is the same as for World Bank tenders: one aggregated, alerted source beats ten portals watched one at a time.
And once the call is detected
Seeing the call in time is half the battle. The other half is deciding quickly whether it is worth your time. A development sector ToR often runs to 50-200 pages: eligibility criteria, technical weighting, eliminatory administrative documents. Reading it in full only to discover on page 40 that you were never eligible to begin with costs you half a day.
This is where Coco, the AI assistant in ICOpedia, comes in. It reads a ToR in three minutes, extracts the eliminatory criteria, the weighting grid and the mandatory sections, and computes a match score against your profile. The decision stays yours, and so does the writing: Coco does not draft your bid for you. It keeps you from investing two weeks in a contract that was lost from the start, and it tells you where to concentrate your hours when the contract is worth it.
What to take away
In Senegal, you do not lose tenders because you respond badly. You lose them because the market is scattered across national portals, multilateral donors and regional channels, and no team can monitor all of that by hand without burning an hour a day and still missing half of it.
The first decision is not to write better. It is to genuinely cover your sources, then to triage quickly what deserves your energy. The rest follows.
Want to see the tenders in your sector in Senegal without watching every portal by hand? Try ICOpedia free, seven days, no credit card.
