Overseas Engineering BD Reference

Problem Solved

Overseas engineering BD often gets stuck after identifying websites: teams still need a repeatable way to turn tender notices, registries, industry directories, and business contacts into qualified outreach lists. This skill targets engineering, solar, steel-structure, and power-infrastructure markets such as Tanzania and Uganda. It organizes fragmented data sources into a reference structure, reducing repeated work on links, search strategies, and field requirements.

How It Works

The skill is a knowledge base, not an executor. It delegates runtime work to Universal Task OS. It supplies three main inputs:

• Task catalog and dependency topology: organized as OE1 data collection, OE2 intelligent processing, OE3 data management, OE4 outreach preparation, and OE5 outreach execution.
• Component requirements: covering tender scraping, PDF OCR, information extraction, contact enrichment, number pre-check, email design, and script generation.
• Exemplar index: pointing to high-quality intel, lists, and outreach samples.

The workflow checks whether the dependency is available, loads references/oe-catalog.md to confirm task type, then reads oe-requirements.md and exemplars.md. The catalog, samples, and dependencies are passed to the execution layer for orchestration. If the dependency is missing, it falls back to read-only reference mode and refuses data collection, extraction, or outreach execution.

Boundaries

It fits overseas BD for engineering consulting, power contracting, solar microgrids, and steel-structure plants, especially when public sources must become structured lists. Its quality depends on upstream data reliability, target-market compliance, and whether the execution layer can perform scraping and outreach. It does not provide concrete customer records or send messages directly.