SubPro lives in the messy middle between the spec book and the final submittal handoff, because that is where the week goes.
SubPro is built by John Devitt, a project manager with 20+ years running complex construction across aviation, infrastructure, federal, and heavy civil work, and a U.S. Army veteran. On every one of those jobs, the same task kept eating a PE's week: turning a spec book into submittals. Not just listing what's required, but hunting down the right product data sheet, SDS, and shop drawing for every spec'd product across hundreds of pages, hoping nothing slipped before it hit the project system. SubPro is the tool he wanted on those projects. If you have run submittals on real jobs and want to help build the fix, start at careers.
They need the spec book turned into something a reviewer can actually check: a log that cites its sources, the supporting files pulled together, and a clean export into the tools they already run.
Every row SubPro drafts traces back to the spec page it came from. If a tool wants a reviewer's trust, it has to show its work first. That one rule shaped everything else here. The FAQs cover the rest: pilot scope, what happens to your files, and the promises SubPro refuses to make.
Rows with source references and review context.
Available supporting files grouped with the log.
Ask questions across the full spec book or generated submittal log.
Flags and source context are there so teams can verify before handoff.