Bid: Found
The problem
My dad consults for utility companies across the US. To win work, he has to find open bids that match what he does, and every municipality posts its bids on its own website, in its own format.
He had no structured way to keep up. He spent a few hours each week clicking through sites looking for anything relevant, and still reached only a fraction of the municipalities he cared about. Any bid he missed was work he never got the chance to pursue.
The old way
- Remember which municipal sites to check
- Visit each one and find its bids page
- Skim every listing for relevant work
- Run out of time well before the list ends
Who uses it
One consultant, my dad, every week.
How Bid: Found works
A scheduled job scrapes 600+ municipal bid sites each week, which takes about 15 minutes, and matches every open bid against his keywords. When he logs in on Monday morning, the matching bids are waiting for him to review.
In a typical week, it scans more than 2,000 open bids across 12 states and narrows them to a few dozen worth his attention.
Runs on a schedule. About 15 minutes, with no one watching.
Keeps only the open bids that fit his work.
He decides which bids to pursue.
Coverage every week
600+ municipalities checked every week, with each dot one site
Where it could go
Any consultant or contractor who chases public-sector bids has this same problem across hundreds of sites.
Built with
About 5 days from start to live, including discovery across the municipal sites. Built with Claude Code.
- Python 3.11
- FastAPI
- SQLAlchemy
- Jinja2
- PostgreSQL
- httpx + BeautifulSoup
- Playwright
- APScheduler weekly job
- Docker on Railway
- Daily GitHub Actions backup
His time spent finding bids, per week