What is SubPro?
SubPro is submittal automation for construction teams. It turns your project specs into a reviewable submittal log and assembled packages, with every row citing the page it came from, exported as files your team can edit.
Plain answers to what SubPro does, what a pilot looks like, how your files are treated, and what you get at the end. If your question is not here, ask us directly.
SubPro handles the early submittal work: it reads the specs, drafts the log, flags what needs a human decision, and preps a clean handoff for the tools your team already uses. The hours your team gets back are the point.
SubPro is submittal automation for construction teams. It turns your project specs into a reviewable submittal log and assembled packages, with every row citing the page it came from, exported as files your team can edit.
SubPro is built for general contractors, specialty contractors, preconstruction teams, project managers, project engineers, and document control teams working through spec-heavy commercial projects.
It takes the first pass out of the spreadsheet loop: reading specs, building rows, finding source pages again, and preparing a log that the project team can inspect before downstream tracking begins.
PDF submittal packages, a submittal log in Excel, and a submittal schedule in Excel, plus chat that answers questions from the spec book and the log. Every row keeps its source page and review flags.
No. SubPro is focused on preparing the log and package context before tracking, routing, approvals, and closeout workflows take over.
No. SubPro prepares reviewable output and keeps source context visible. The project team still verifies requirements, responsibility, substitutions, compliance, and final package decisions.
Many teams use the terms differently. In SubPro content, both refer to the structured list of required submittals that the team reviews, cleans up, assigns, and exports for handoff.
A pilot fit call checks project type, spec volume, timing, current workflow, expected output, and data-handling needs before any production file work begins.
Yes, that is how every pilot starts. One spec set, so both sides can judge the output, the timing, and the fit before anything scales up.
Bring the project type, approximate spec page count, trade focus if any, target deadline, current tools, and any requirements around NDAs, approved transfer methods, or file retention.
Projects with incomplete project specifications and project manuals, unclear ownership, unusual contractual requirements, or strict data-handling needs may require additional review before SubPro work begins.
The AI does the reading: it works through the specs, drafts the rows, and answers questions about the spec book. People make the calls. Every AI-drafted row cites its source page so your team can check the work instead of trusting it.
No. Specs are processed for the job, then deleted, and are not used for AI training or unrelated purposes.
No. The public website is not a production file-upload portal. Project-file handling expectations are confirmed before real work begins.
No. SubPro prepares review-ready output. Contractors still verify requirements, ownership, substitutions, compliance, package decisions, and professional review obligations.
SubPro handoff can include PDF submittal packages, a submittal schedule XLSX, and a submittal log XLSX. Exact deliverables are confirmed before work begins.
Yes. SubPro hands off editable Excel files and PDFs, so whatever your team uses for tracking and approvals picks up right where SubPro leaves off. Nothing to rip out, nothing new to adopt.
No public pricing model is currently published on the website. Scope, timing, deliverables, data handling, and fees if applicable are confirmed in writing before work begins.
Book a call or contact SubPro with your project type, spec volume, current workflow, deadline, and file-handling expectations.
Bring a real spec question. We can talk through your project type, spec volume, current workflow, and the right next step.