Ask about SubPro, pilot availability, submittal workflows, review flags, and exports.
I ran the jobs where submittals took months.
I'm John Devitt. I spent twenty years as a construction project manager on aviation, infrastructure, federal, and heavy civil work, and SubPro is the tool I wanted on every one of those jobs.
Why I built this
Nobody had fixed it, and the book kept landing on my desk.
Every job I ran had the same stretch in it. A project engineer, sometimes me, sat with the project manual and typed each required submittal into a spreadsheet. Then came the hunt: the data sheet, the SDS, the shop drawing, for every product the book named, one manufacturer website at a time. Then the submittal packages, built one by one. Then the tracking. Then, months later, closeout, when we pulled all of those documents together again for a binder nobody wanted to build.
I have been on projects where the whole process took months. I remember sitting in the truck before the gate opened, reading, and thinking that with all the technology we carry onto a jobsite, somebody should have fixed this already. They hadn't.
So I built it. SubPro is my start at changing how submittals get made and managed. It cannot make the design team make up its mind, and it does not try. What it does is make your side of the process clear, fast, and checkable, from the bid-day product list to the closeout package at the end.
If you have run submittals on real jobs and want to help build this, start at careers. The FAQ covers pilot scope, file handling, and the promises I refuse to make.
How the company runs
- Small on purpose SubPro LLC is founder-led, patent pending, and staffed to run pilots well. Everything on this site is a claim about the current build, and I would rather tell you what it does not do than oversell what it does.
- I read the flagged rows Rows SubPro flags get a construction PM's read before delivery. Right now that PM is me. I make no calls on your behalf; flagged rows come back to your PM with the page behind them.
- One mailbox, one call Pilots start at pilots@sub-pro-ai.com or on a 15-minute fit call. There is no sales team between you and the person who answers, because the person who answers is me.
What I will not do
My word on it, in writing.
- Promise a perfect extraction. Spec books contradict themselves. Every row carries its page, and a person reads the ones that need judgment.
- Ship a row without a source. If SubPro cannot point at the page a requirement came from, the row is not ready to trust, and it says so.
- Keep a copy of your spec book. Working files are deleted once the deliverables land. Nothing you send trains a model. The full commitment is on the data handling page.
- Ask you to rip anything out. The output is PDF and Excel, and it drops into the project system your GC already runs.
- Make a public claim without proof. No logos, no quotes, and no number without its method beside it.
Send us one spec book.
The fastest way to judge me is to judge the work. One fit call, one of your spec books, and a drafted log you can check page by page.