SubForge.
A planned vertical for subcontractor sourcing, vetting, and scheduling in the construction and finished-trades market. Designed against the same operator pattern as the rest of the portfolio.
What it is
Most general contractors and project managers spend a meaningful share of their week trying to find, vet, schedule, and pay subcontractors — and then, when something goes wrong on a job, trying to find out why. The work is patient, repetitive, and exactly the kind of thing I have gotten good at across the rest of the portfolio.
From Jess's perspective
SubForge is the planned product around that pattern: a platform-side business that sits between contractors and the subs they hire. The subs themselves are external labor — contractors hire them through the platform, just as they would today, with the qualification, licensing checks, and relationship work owned by the contractor. SubForge does not employ subs and does not employ a vetting team. What it does is run the operational tail end-to-end on the platform side: sourcing surfaces, paperwork, scheduling, pay-cycle, audit trail. We do not start a vertical we cannot run well. SubForge enters the build queue when the active portfolio is stable enough to take its hands off the wheel, or when a partner with the right operating context wants to run point on the build with us.
Status
Designed and queued. Build has not started; no committed date.