Project indexBusiness development system

MODUS BD Tracker
Carry a public project lead into a real follow-up.
I built the MODUS BD Tracker to connect early public signals with the relationship work that follows. It brings three states’ worth of research into one team workspace.
Explore the workspace- My role
- Business development strategy, data workflow and implementation
- Scope
- Iowa, Wisconsin and Maine · SQL and Cloudflare
Get there before the bid notice
A school board might discuss a facilities plan months before an RFQ appears. A bond vote adds a different kind of evidence. Neither necessarily means the firm should pursue the work, but both are worth remembering when someone calls an architect or owner.
I designed a multi-level collection and AI-assisted research process for Iowa, Wisconsin and Maine. Regional reports feed a SQL-backed workspace on Cloudflare. A lead keeps a route back to its source so the team can inspect what actually happened before deciding what to do.
Separate incoming research from team decisions
In this snapshot the workspace lists 275 active opportunities across three regions. The team can search by project, owner or partner and narrow by deadline, stage, priority or assignee. That gives the person planning outreach a way to make a review list for a particular market or office.
I kept the research and the next step visible together. A board agenda can tell us an issue was discussed. A person needs to decide whether it is relevant, who already knows the client and when it makes sense to follow up.
See which opportunities are being pursued
A long list makes volume visible. It is less useful when a partner asks which teams are forming or which proposals are in development. The pipeline places active pursuits in stages, with the project, deadline and follow-up on the card.
List and pipeline are two views of the same work. The team can review new signals broadly and then move to the shorter set that needs a conversation or a decision. A project can stay in research until someone has a reason to move it.
Keep the trail from one week to the next
Each weekly import is a snapshot of outside information. The team’s decision about a lead has a different life span. I kept dated reports accessible and designed updates so that importing more research preserves the notes and decisions attached to the project.
The report library gives a reviewer a practical audit trail. They can return to a dated source file, check where a lead came from and continue the discussion from the board.

