First Review + Monthly QA
- Direct bid package upload
- PDF, DOCX, TXT, CSV, and XLSX support
- Public CSV/XLSX URL connector
- Google Sheets export link
- Email attachment ingestion
Connector and Ingestion Paths
Choose the input path that fits your workflow: direct upload for the first bid review, shared-file connectors for monthly QA, or tokenized API push during enterprise rollout.
Enterprise Automation
- Everything in Monthly QA
- Google Drive shared CSV/XLSX
- Dropbox shared CSV/XLSX
- Direct API push connector
- Tokenized CSV/XLSX and API push from Procore, Autodesk ACC, or ERP exports
- Desktop sync agent for legacy systems
What “API Push” Means
Enterprise source systems can push CSV/XLSX-style payloads or mapped record objects into a token-protected connector endpoint. Native marketplace OAuth integrations are handled as implementation work when a customer needs them; the current production-ready path is export, shared-file sync, or tokenized push ingestion.
Data Storage
Uploaded bid, estimate, and outcome files are stored in the configured private storage path with application file encryption available. Production AWS S3 storage is configured to request server-side encryption (AWS KMS by default, or AES-256 when selected).
Required Fields For Best Results
- Branch, location, region, or office
- Project, bid, estimate, or opportunity ID
- Bid amount, estimated cost, margin, or markup
- Estimator, owner, trade, project type, or customer
- Submitted date, due date, or closed date
- Won/lost status when available
- Actual revenue, actual cost, or final margin when available
- Notes, exclusions, addenda, or RFI context when available
Setup Flow
- Start with one bid package review to validate the report and action queue.
- Use Smart Upload to keep package, estimate, and outcome files organized.
- Add a shared-file connector or tokenized API push once the first run is clean.
- Map branch, project, bid, estimator, and outcome fields before expanding branches.