BidForge

The Problem
General contractors in the construction industry were drowning in emails. Finding the right subcontractor to bid on a project meant sifting through hundreds of messages, following up manually, comparing bids in spreadsheets, and awarding contracts through even more email chains. There was no single system, just noise. BidForge was built to eliminate that entirely.

What I Built

BidForge is a full-stack SaaS platform that handles the complete bidding lifecycle. Contractors post RFPs with full project documentation, invite subcontractors filtered by trade, location, and certification, and receive structured bids directly on the platform. Bids are compared side-by-side with detailed sortable breakdowns, and contracts are awarded with a single click, with automatic notifications sent to every bidder instantly.
I also built in a real-time in-app messaging system so that all communication between contractors and subcontractors happens within the platform, tied to the relevant project. No more email threads. Every conversation is in context.

The Hardest Part
The in-app chat was the most technically demanding feature of the build. Getting real-time messaging right ensuring messages delivered instantly, stayed in sync across sessions, were tied correctly to their project context, and handled edge cases like reconnections and concurrent users required me to slow down and architect it properly before writing a single line. I had to think through the data model, the event system, and the UI state carefully. Getting it wrong would have broken the core value of the platform. I got it right.

The Outcome
BidForge is live and fully functional. It is a complete, production-ready platform built entirely by me solo, full-stack, from database schema to UI. Every feature from RFP creation to contract award to real-time messaging works end-to-end.