Upload one spec book. By tomorrow you have a working submittal log, a section register, and a short list of the rows that deserve a second look, in the same format our pilot customers get. Every row cites the spec page it came from, and the whole thing comes back titled and numbered like your own paperwork.
Both builds return the same three files in editable Excel: the log, the register, and the flags report. The difference is how much of the checking is done before it reaches you.
The fast first pass. SubPro reads every section, drafts every row, and hands you a flags report that says exactly where to look before you lean on it. You spend an hour making calls instead of a week typing. It is a draft, and we say so out loud.
The finished article. After the draft, a construction PM with twenty years of field time works every flagged row against your book before it ships. What lands in your inbox is ready for your workflow, not your red pen.
Orders placed after 5pm Eastern usually land the next morning. The 12 to 24 hour clock starts when your upload finishes, not when you pay.
Stripe checkout, card or the usual alternatives. Your email is your order: no account, no password, no sales call.
The upload page takes one PDF spec book up to 1,000 pages and 150 MB. Add your project name and number there and the finished log comes back titled and numbered like your own paperwork.
SubPro reads every section overnight and drafts the rows, each one keeping its source page. On the Reviewed Build, the PM then works the flags before anything ships.
A delivery email links to your order page: submittal log, register, and flagged-rows report, all in Excel. Links stay live for 30 days.
Not a template with your name on it. A populated log in the format SubPro delivers on pilot projects: one row per requirement, spec section and title, type, manufacturers and products where the book names them, and a status column ready for your workflow.
Every required submittal as a row, numbered under your project number, with the source page cited. Status colors and columns for dates, responsible party, and revisions.
The section-by-section view: which CSI sections demand submittals and how many, for planning the fight before it starts.
The honest sheet. The rows the build was least sure about, plus unusual items, each with the reason it needs your eyes. On the Reviewed Build these come back worked, not just listed.
Rendered from a sample build so you can see the actual sheets: your project name in the title, your numbering on every row, and the flags report that tells you where to look.
Title band, sequential numbering under the project number, manufacturers and products where the spec names them, and a status column ready for your workflow.
Each line the pipeline was unsure about, with the reason spelled out. This is the sheet the Draft Build asks you to review.
The self-serve build handles one project book up to 1,000 pages and 150 MB. If your book blows past that, or you are staring at a shelf of them every month, the economics change and so does the tooling. That is what a pilot fit call is for. Pilot pricing is scoped to the work and confirmed in writing before anything starts.
Your spec book is deleted after delivery, on either build. We extract the log; we do not keep a library of your documents, and nothing you upload trains anything.
A first pass, and the name says so. Every row is drafted with its source page, and the flags report lists the lines that deserve your judgment before you rely on them. The Reviewed Build has those rows worked by hand before delivery.
Our processing system, and on the Reviewed Build, the reviewer working your rows. Deleted after delivery, never kept, never reused. Your download links last 30 days.
You hear it from us before you have to ask, you get a full refund, and your log still gets built and delivered. Missing our own deadline is our bill, not yours.
Before delivery: yes, no questions. After delivery: talk to us and we will be reasonable. Write to pilots@sub-pro-ai.com from your order email.
What a log is, what the output looks like, and how the full product works.
Column by column, what a finished log tracks.
Exactly what ships, file by file.
The engine behind the build, end to end.