Skip to content

Integrations

WE DON'T PLUG INTO
YOUR STACK. WE SPEAK ITS FILE FORMATS.

There is no Procore app to install, no Autodesk connector to authorise and no Revit plugin. You upload documents to the programs in your browser, and what comes back is a file written in the format the system on the other side actually imports — a Procore budget CSV, a Sage job-cost budget, a Bluebeam quantity summary, an Excel matrix.

That is the whole integration story, and it is the honest one. Everything below is a format one of the five live programs writes today, on every plan, with nothing to configure.

Read this first

FILES IN, FILES OUT. NO API CALLS.

Nothing to authorise

No OAuth screen, no API token, no admin sitting in your Procore or Autodesk tenant granting a third party permission to read the project. There is nothing to grant, because we never connect.

You see every file

Each export lands in your downloads as a file you can open, read and correct before anything reaches your PM platform. Nothing we produce appears in your systems until you import it deliberately.

Works the same on every plan

Formats are not a tier. Field, Pro and Firm write the same exports for the programs each plan opens. There is no connector licence and no per-integration fee.

The trade-off is stated plainly: a file handoff means somebody clicks import. What it buys you is that a tender package under NDA never gets handed to a connector, and that a bad number is caught in a spreadsheet rather than after it has already written itself into your budget.

Inbound

WHAT YOU CAN UPLOAD

Scanned pages and photographed drawings go through OCR, so a set that came back from the printer as a flat image is still readable. Everything below is a format the programs parse today.

Drawing sets

Read

DWG · PDF · DXF

Blueprint Auditor reads DWG drawings, vector and scanned PDFs and DXF exports — sheets, layers, dimensions and title-block data.

Scans & photos

Read

PNG · JPG · TIFF · BMP · WebP · HEIC

Photographed spec pages and scanned addenda are OCR'd before they are read. A phone photo of a marked-up sheet counts as a document.

Specs & manuals

Read

DOCX · DOC · RTF · PDF · TXT · MD

SpecChecker and ScopeGuard read the project manual in whatever the consultant issued it as, including the Word file nobody bothered to PDF.

Sub quotes

Read

PDF · DOCX · XLSX · CSV · EML

Bid Leveler takes quotes as they arrive — a letterhead PDF, somebody's spreadsheet, or the raw email with the price in the body.

Spreadsheets

Read

XLSX · XLSM · XLS · CSV

Existing takeoffs, door and window schedules, and your own rate sheets. AI Estimator will price a quantity list you already have.

DWG

Convert first

Not read directly

DWG is Autodesk's proprietary binary. Blueprint Auditor converts it in-process with read directly, and every format AutoCAD has written since 2003 — 2004, 2007, 2010, 2013, 2018 — reads whole. A drawing saved as R13, R14 or 2000 is refused by name, with the one instruction that fixes it: Save As a 2004-or-later DWG, or export DXF. It says which rather than half-reading it.

Outbound

EXPORTS, BY WHERE THEY LAND

Each row is a real export in the program named, written with the columns the target system's importer expects. Where a format is our own shape rather than a vendor's published one, it says so.

Where it goes From What the file is
Procore AI Estimator
Bid Leveler
ScopeGuard
Budget import CSV — cost code, description and amount split by cost type. Bid tab CSV. Issue/punch import CSV using the column names Procore's importer expects. File import, not a connector.
Sage 300 CRE
Sage 100 Contractor
AI Estimator Job cost budget CSV with labour / material / equipment / subcontract categories and budget hours, ready for the job cost import.
QuickBooks
Desktop & Online
AI Estimator Estimate line CSV at sell price with taxable lines marked, so the client-facing number does not get retyped into accounting.
Bluebeam Revu AI Estimator
ScopeGuard
Quantity summary CSV carrying the takeoff source reference, so each line can be checked back to the sheet it came from. Markup summary CSV with subject / comment / status columns.
Excel, Sheets
or any project log
All five Blueprint Auditor's Excel report. Bid Leveler's levelling matrix, bid comparison and findings register. SpecChecker's conflict matrix. ScopeGuard's buyout register. AI Estimator's CSI division roll-up and buyout list sorted by lead time.
Email, Word
or a PDF reader
All five Drafted RFIs as text, one per finding, ready to paste. Clarification letters. The scope paragraphs to attach to each subcontract. Client proposal and award recommendation as PDF. Audit summary as Markdown for a wiki or a weekly report.
Your own tooling SpecChecker
ScopeGuard
Bid Leveler
Full project data as JSON — every finding with its source references intact — plus a flattened findings payload if you are posting into an internal endpoint of your own. Our shape, documented in the file.

Inside the plan

THE PROGRAMS HAND OFF TO EACH OTHER

The handoffs that matter most are not to a third party at all — they are between the programs your plan already opens. A Pro or Firm plan runs the whole chain without anything being retyped.

01

Blueprint Auditor → AI Estimator

Measured quantities move across in the estimator's own import format, so a takeoff becomes a priced bid without a second measurement.

02

Bid Leveler → AI Estimator

The levelled subcontractor number goes back into the estimate as that trade's cost, carrying the adjustments that produced it.

03

Bid Leveler → ScopeGuard

Open findings from levelling arrive as the scope questions to settle during buyout, instead of being lost between the two meetings.

Blueprint Auditor and AI Estimator are on every plan including Field. SpecChecker, Bid Leveler and ScopeGuard open on Pro and Firm. See what each plan opens →

Straight answers

WHAT WE DO NOT DO

No live two-way sync

Nothing we produce lands in Procore, Autodesk Build or ACC by itself. Somebody imports the file. If a vendor tells you their AI writes back automatically, ask what happens when it is wrong.

No plugins

There is no Revit add-in, no Bluebeam plugin and no Procore marketplace app. Nothing installs into software you already run.

No mailbox, Slack or Teams ingest

We do not read your project mailbox or sit in your channels. You can upload an .eml file to Bid Leveler; that is the extent of it.

No public API

There is no endpoint to call us on and no webhook to subscribe to. The JSON exports exist so you can feed your own tools from a file instead.

Some of this will change. When a connector ships it will appear here as something you can use that day, not as a status badge on a page — and until then this page says no.

Need a format we don't write?

TELL US THE COLUMNS.

If your accounting package or project log imports a shape we do not write yet, send us a sample of the file it expects. Adding an export format is small work and it ships to everyone on the plan, at no extra cost. A genuine live connector into your own systems is different work — that is a custom build, quoted separately.

Send Us a Sample File →

The fastest way to check

RUN A REAL SET THROUGH IT.
OPEN WHAT COMES BACK.

Seven free days, unlimited. Upload a drawing set or a folder of sub quotes, export the file your system needs, and open it in Excel before you decide anything. That answers the integration question better than any matrix.

Account and card required · nothing charged until day 8 · cancel in one click.