Your BD Team Is Duplicating Work Across Every Portal

The Coordination Problem Nobody Talks About

A business development director at a large South African IT services integrator manages a pipeline worth R200 million in active bids. His team of six BD managers each tracks different government departments — SITA, provincial departments, state-owned enterprises like Eskom and Transnet. Every week, someone on the team downloads a massive CSV from the eTender portal, scans it manually, and copies relevant entries into a shared spreadsheet.

The spreadsheet has 47 tabs. Nobody is confident it's complete. Last month, two team members spent three days preparing a response to the same tender without realising it. The month before, they missed a R8 million contract from a provincial department because it fell between two people's coverage areas.

This isn't a South African problem. It's a scaling problem. When tender discovery depends on individual humans checking individual portals and reporting back to a shared spreadsheet, the system breaks exactly when the stakes are highest — when the team grows, when the geography expands, when the pipeline gets large enough that nobody can hold the full picture in their head.

When the Team Outgrows the Spreadsheet

A partner at an international engineering consultancy runs the German public sector environment practice — 40 staff in Hamburg, bidding on EU-funded environmental impact assessments, water management projects, and climate adaptation studies. Her team bids on contracts from German federal agencies via TED, Länder agencies across 16 different state e-procurement platforms, and EU institutions directly.

Junior staff spend two full days per week aggregating opportunities from these platforms into a usable format. That's €800 per week in labour costs — just for the searching, before anyone evaluates a single tender. And the cross-border EU opportunities published on TED under different country codes? Those get missed entirely because nobody has time to check every classification.

The breaking point came when the team lost a €400K contract to a competitor who had spotted it three weeks earlier on a Länder platform the team didn't monitor. The opportunity had been there the whole time. Nobody was looking.

The International Team That Stopped Duplicating

A grants and partnerships manager at an international NGO faces a different version of the same problem. Her team of three — one in London, one in Dhaka, one in Dar es Salaam — tracks competitive tenders from FCDO, the EU's EuropeAid, the World Bank, the African Development Bank, the Asian Development Bank, and a half-dozen UN agencies.

Every Monday, all three team members independently scan the same portals. They share findings in a Slack channel that has become so long nobody reads it. Development sector procurement portals publish tenders with generic titles that don't mention "water" or "sanitation" — the NGO's core focus — so keyword searching on these portals returns either everything or nothing.

What changed: one shared pipeline, filtered by keywords like "WASH," "water supply," "sanitation," and "hygiene promotion," delivered to a Google Sheet that all three team members access. The Dhaka and Dar es Salaam staff stopped spending their mornings duplicating the London team's portal checks. The London manager stopped spending her Mondays aggregating findings from three time zones.

Replacing the €500/Month Legacy Service

A commercial director at a publicly listed Dutch construction company runs a six-person tender team. They've been paying €500+ per month for a legacy tender monitoring service that predates the modern web. It sends them 200 irrelevant tenders per week alongside the 15–20 they actually want. The filtering is primitive — sector-level only, no keyword matching, no location granularity beyond country.

His team spends hours every week sorting signal from noise. The service doesn't integrate with their bid management system, so every relevant tender gets manually re-entered. When he explored alternatives, the comparison was stark: better filtering, direct API integration, AI-assisted response generation for standard PQQ sections, at a fraction of the cost.

The 30-day parallel run was decisive. The new system found everything the legacy service found, plus tenders from municipality procurement pages and cross-border Belgian and German opportunities the old service didn't cover.

What Scales With the Team

"We had six people checking four countries' worth of portals and still missing things. The spreadsheet was a fiction everyone maintained but nobody trusted. When we switched, the first thing we noticed wasn't the time saved — it was the tenders we'd been missing."

Business Development Director, South African IT services integrator

The Real Cost of Manual Coordination

Teams that track tenders manually don't just lose time. They lose in three specific ways that compound as the team grows:

• Duplication. When multiple people check the same portals independently, you're paying for the same work multiple times. In a six-person team, this can represent 15–20 hours of wasted effort per week.
• Coverage gaps. The paradox of manual checking: the more people you assign, the more likely something falls between their coverage areas. Each person assumes someone else is checking that portal, that region, that sector.
• Institutional knowledge loss. When the person who checks a specific portal leaves or goes on holiday, their coverage disappears. Automated systems don't take holidays.

For a team of six with an average salary cost of €60K per year, 20 hours of wasted weekly effort represents roughly €31,000 annually in pure labour cost — before accounting for the revenue impact of missed opportunities.