I didn't set out to build software. I set out to stop losing weeks to packages that came back over one missing certificate.
I've worn the hats this tool serves. I've also taught those positions how to use project management software. The information is there and the tools are there — but the flow and the integration were never built for actual field operations. Not for the questions that get asked in the field and need an answer right now. Not for the stop-and-go reporting you get when the day keeps interrupting you.
This got built owning those roles and working in the trenches with QC managers, superintendents and project managers — on federal, commercial and residential work. The design was led by the rigor the U.S. Army Corps of Engineers demands — how work gets reported, filed and logged. What the field needs is consistency, and it needs the answers right now.
I know what a reviewer looks for, what a rejection costs, and how much of a super's week disappears into paperwork that a machine should have handled. So I built the tool I wanted on my own jobs, and I test every piece of it on real work before anyone else sees it.
SPECUP isn't an AI wearing a hard hat. It's the record — what your contract says, and what got decided against it. It knows what a submittal is, what a spec paragraph means, and why a complete package matters. If it doesn't know something, it tells you — that rule doesn't bend.
FounderSpecUp, LLC · Arizona
Everybody makes mistakes. On a job, they cost money and schedule. Russ checks everything against the record, so less slips past a tired human at 9 PM — before it ships, not after it costs you.
Not a chatbot bolted onto a filing cabinet. Russ carries the project the way an experienced hand does — through precon, procurement, the field, and closeout, from the daily walk to the call a PM has to make on the phone.
What is ready, what is blocked, what got installed before its submittal was approved. Talk it in from the deck and it lands in the record.
Submittals, RFIs, deficiencies, the daily report. Drafted from the contract documents, cited to the paragraph, waiting for you to approve.
Precon through closeout, one record. What the superintendent saw this morning is what the PM sees this afternoon — and what the reviewer sees at the end.
It stays in your project. No cross-company training without your consent. With SharePoint write-back, it never leaves your own tenant.
Russ answers from your approved contract documents and cites the paragraph. If it isn't in the record, he says so instead of guessing.
Every correction you make is the record — and it teaches him your project. Correct a register line or the way he reads your question, and he uses it next time.
Already a Microsoft shop? Good. Russ does the construction work; Copilot can find it.
On a drawing, the datum is the reference point every measurement is taken from. Get it wrong and everything built off it is wrong too. On a SpecUp job, the spec is the datum. Every submittal, delivery, daily, inspection and punch item is measured back to it.
