Everything BAU AI does, from first bid to closeout.

Clara scans 1,000+ portals for bid opportunities and ranks each one against your company profile, such as trade, size, region and bonding. Your team can also add any ITB or RFP by upload or email forward. For a bid worth a look, Clara drafts a Go/No-Go memo with every criterion cited to the page, and your team decides.

1. Set up your company profile and region
2. Review ranked matches in one bid inbox
3. Read the cited Go/No-Go memo and decide

What you getA short list of bids that fit, each with a written Go/No-Go memo your team can check page by page.

Clara reads the whole solicitation, from the instructions to bidders and the general and supplementary conditions to specifications, addenda and bid forms, in PDF, DOCX or XLSX. Each finding, such as uncapped liquidated damages, bond requirements or a soils risk, links to its page and clause, so estimators check the pages that matter.

1. Upload or forward the bid package
2. Clara reads every document and flags risks
3. Open each finding at its cited page

What you getA cited list of risks and requirements for the package, ready before anyone starts the estimate.

When your team passes on a bid, Clara writes down the reasons, such as fit, risk, capacity and schedule, and ties each one to the page it came from. The record stays on file with the package. When the same owner or project type comes back, the next conversation starts from documented facts, not memory.

1. Decide No-Go on a reviewed package
2. Clara records the reasons with page citations
3. Find the record when the owner returns

What you getA history of the bids you passed on and exactly why, each reason tied to its source.

Before design is far along, an owner or developer may ask whether a concept is worth pursuing. From the concept information you provide, the platform drafts an indicative cost range, a timeline and a list of risks, each with its source. Your preconstruction team reviews the assumptions and decides what to bring to the conversation.

1. Describe the concept and upload early documents
2. Review the indicative cost range and timeline
3. Check the risk list and its sources

What you getAn early, sourced view of cost, time and risk to discuss with the owner before design starts.

For each bid, the platform gathers zoning, flood risk, elevation, soils and environmental data for the project site and shows where each item came from. An estimator pricing a job in Travis County, TX sees the site conditions that may affect foundations or schedule next to the bid package, then decides what to price or ask about.

1. Open a bid with a known site
2. Review zoning, flood, soils and environmental data
3. Note site risks for pricing or RFIs

What you getSite conditions for each bid in one place, each with its source, before pricing starts.

Clara reads the instructions to bidders and lists every form, signature, notarization and enclosure the bid needs. She fills the bid form, AIA A305 qualification statement, bid bond details and HUB or DBE forms from your company records in the AI Brain, with a source on every field. Missing or expired items are flagged, not guessed.

1. Upload the bid package and instructions to bidders
2. Review filled fields and settle open items
3. Your team signs, notarizes and submits

What you getFilled bid and qualification forms as PDF and editable DOCX, every value sourced and ready for signature.

Clara reads the owner's unit-price bid schedule in XLSX or PDF and suggests a unit price for each item from your past estimates and bid tabs in the AI Brain. Each price shows its labor, material, equipment and markup sources. Items she cannot price stay open, and outliers against your own history are flagged.

1. Upload the owner's unit-price bid schedule
2. Review suggested prices and settle open items
3. Export the priced schedule as XLSX or CSV

What you getA priced bid schedule with the source of every unit price, ready for your estimator's final review.

After your team makes a Go, the Go/No-Go memo and its citations move with the bid package. Dora takes the owner contract, Nova levels the sub bids against the scope Clara extracted, and Theo takes off quantities from the plan set. Nothing is read twice, and your team decides at every step.

1. Make the Go decision on Clara's memo
2. Agents pick up contract, sub bids and plans
3. Review each agent's cited findings

What you getOne project record from bid to buyout, with findings that keep their citations from agent to agent.

Dora reviews the contract you upload against AIA A201, A101 and A401, ConsensusDocs 200 and 750, EJCDC C-700 and owner-drafted forms. Each change that shifts risk, such as uncapped liquidated damages or broad indemnification, is marked with the base clause it departs from, the page and a question for counsel. Your attorney decides.

1. Upload the owner contract and supplementary conditions
2. Review each flagged deviation at its page
3. Send drafted questions to counsel or owner's rep

What you getA cited first read of the contract and a list of questions for counsel, before anyone signs.

When markups or tracked changes come back from the owner, Dora reads them in context rather than as isolated edits. Changes are grouped by risk theme: liquidated damages, indemnity, retention, payment terms, schedule and termination. Each change is cited to its page, so your team and counsel can see what moved and decide.

1. Upload the marked-up or tracked-changes contract
2. Review changes grouped by risk theme
3. Decide what to accept or push back on

What you getRedlines sorted by risk theme, each cited to its page, so negotiation starts with the changes that matter.

Dora reads your subcontract against AIA A401 or ConsensusDocs 750 and against the prime contract. It checks that flow-down terms match, including pay-if-paid, retainage, indemnity and insurance, and flags gaps where you would carry risk the subcontractor does not. Each flag is cited to its clause and page.

1. Upload the prime contract and the subcontract
2. Review mismatched flow-down terms
3. Adjust the subcontract before issuing it

What you getSubcontracts whose payment, retainage, indemnity and insurance terms line up with the prime contract.

The clause library holds contract clauses your team has reviewed, along with the positions you took, shared across preconstruction and counsel. Dora reviews new contracts against it as well as against the standard forms, so a clause you pushed back on before shows up with that history. The clause library is included on Studio and Enterprise.

1. Add reviewed clauses and your positions
2. Dora checks new contracts against the library
3. Update entries as negotiations settle

What you getA shared, growing record of your contract positions that every new review starts from.

A change starts as a potential change order when the team spots added scope or receives an owner request. It is priced, its budget and schedule impact are shown, and it moves to an approved change order once the owner signs off. People approve each step along the way.

1. Log the potential change order
2. Review its budget and schedule impact
3. Track it through owner approval

What you getA tracked path from potential to approved change orders, with budget and schedule impact on each.

Nova reads subcontractor and supplier proposals in PDF, scanned PDF, Excel or DOCX and maps every line to one scope by CSI MasterFormat. It shows line by line what each bidder included, excluded or left out, and prices missing scope back in at the median of the bidders who carried it, cited to the proposal page.

1. Upload the sub bids for one trade
2. Review the scope matrix and flagged gaps
3. Check each adjustment at its proposal page

What you getA leveled bid tab that compares totals for the same scope, with every adjusted dollar traced to its source.

Nova compares each line in a sub's bid with the median of the other bidders on the same scope and flags lines far above or below it. Front-loaded mobilization is a common case, since it would be paid on the first pay application, ahead of the work. Each flag cites the line in the sub's proposal.

1. Level the sub bids to one scope
2. Review lines flagged against the median
3. Fix the schedule of values before award

What you getA clear list of unbalanced lines to settle with the sub before the schedule of values is set.

Once the bids are leveled, Nova builds the bid tab and drafts an award memo that ranks bidders on adjusted totals and states its reasons, including scope adjustments, open clarifications and bond details. Every adjustment carries its page cite. Your team reads the memo, confirms open items with the subs and makes the award.

1. Finish leveling and list open clarifications
2. Review the drafted memo and its citations
3. Your team decides and makes the award

What you getA leveled bid tab in XLSX and an award memo in PDF that documents why the award was made.

Each subcontractor has a record with its scope and insurance on file. Through the subcontractor portal, subs see the information the GC chooses to share and can respond in one place, so the project team spends less time chasing documents by email.

1. Create subcontractor records with scope
2. Keep insurance documents on file
3. Share project information through the portal

What you getSubcontractor scope and insurance in one record, with a portal for sharing information both ways.

Theo reads 2D PDF plan sets, vector or scanned, checks the drawing scale and takes off areas, lengths and counts. Every quantity carries its sheet, view and calculation and is tagged to a CSI MasterFormat division. Your estimator approves each line before it moves on, and open points go on an RFI list.

1. Upload the 2D PDF plan set
2. Review quantities marked on each sheet
3. Approve lines and export by CSI division

What you getFirst-pass quantities by CSI division, each with its sheet and calculation, exported to Excel or CSV.

When a new revision of the plan set arrives, load it and Theo shows which quantities changed, on which sheet and by how much. Old and new values sit side by side, so the estimator can accept or dispute each change before it reaches the estimate or a change order discussion.

1. Load the new plan revision
2. Review changed quantities sheet by sheet
3. Accept or dispute each change

What you getA clear record of what changed between revisions and by how much, before it reaches your price.

Theo compares its takeoff with your estimate, the issued bid form or an AIA G703 schedule of values. It lists every item that differs or has no counterpart, with the source. Lines over the threshold you set stay blocked until your estimator reviews them, and open points go on the RFI list.

1. Pick the estimate, bid form or G703
2. Review every difference with its source
3. Resolve blocked lines or add RFIs

What you getA list of quantity differences between the plans and your numbers, so short counts surface before bid day.

A project manager or estimator starts from a takeoff or a plain-language description of the work, such as added scope from an owner request. The platform drafts a quote and lists every assumption it made, so the reviewer can check quantities, exclusions and pricing basis before anything goes to the customer.

1. Start from a takeoff or a description
2. Review the draft and its listed assumptions
3. Edit and approve before sending

What you getA draft quote with its assumptions written down, ready for your review and approval.

Patrick builds the project from what preconstruction already knows: Nova’s awarded subs, Theo’s quantities, Dora’s contract terms and Clara’s bid documents. Your project manager reviews the setup instead of retyping it.

1. Mark the bid as won
2. Patrick drafts budget, schedule and team
3. The project manager confirms the setup

What you getA live project on day one, with nothing re-entered from the bid.

Patrick keeps a live picture of every job: milestones and float, buyout progress, open RFIs and submittals from Colin, punch status and cost from Fina, each with the person accountable.

1. Open the job
2. See what is late, open or at risk
3. Click through to the item and its owner

What you getKnow where every job stands without a status meeting.

Import from Primavera P6 or MS Project with logic and float kept, or build the schedule in the Gantt chart. Milestones, dependencies and calendars stay intact.

1. Import or build the schedule
2. Patrick keeps logic and float
3. Track milestones on one chart

What you getOne live schedule the whole team works from.

Patrick pulls the next three weeks from the master schedule, adds what the field reports and keeps it current every day.

1. Patrick builds the look-ahead
2. Field progress updates it
3. Share it with foremen and subs

What you getA look-ahead that is never a week out of date.

Patrick shows the driving path to every milestone and recalculates it when progress, deliveries or changes move a date.

1. Patrick marks the driving path
2. Dates move, the path updates
3. See what is driving each milestone

What you getAlways know which activities you cannot let slip.

Patrick reads progress from Lex and deliveries from Dario and warns when an activity on the critical path is falling behind, with the reason.

1. Progress and deliveries come in
2. Patrick checks them against the plan
3. Alerts with the reason attached

What you getEscalate risk before it becomes delay.

Patrick lays out options, such as resequencing, splitting an area or adding a shift, with the effect on the milestone and who would need to be told.

1. A date is at risk
2. Patrick drafts recovery options
3. Your scheduler picks one

What you getOptions in front of you, not just a red bar.

Patrick sends each trade the activities they own in the coming weeks and collects their confirmations or conflicts before they become delays.

1. Patrick sends each sub their activities
2. Subs confirm or flag conflicts
3. Conflicts surface early

What you getCoordination without the weekly phone tree.

Patrick lists each scope package, the awarded sub from Nova, the subcontract status from Dora and the buyout value against the budget line, so nothing is left unbought when work starts.

1. Packages come from the estimate
2. Patrick tracks award and subcontract
3. See buyout savings or overruns by line

What you getA buyout that is finished before the trades are needed.

Action items from meetings, RFIs, site walks and reports land on one list. Patrick assigns each to a person, sets a due date from the schedule and reminds the owner before it slips.

1. Items arrive from every agent
2. Patrick assigns owner and due date
3. Reminders until it is closed

What you getOne task list per job that people actually close.

Walk the job and take photos as you normally would. Patrick drafts a punch item for each defect it sees, with room, trade and description. Nothing counts until a person confirms it.

1. Walk and take photos
2. Patrick drafts the items
3. A person confirms, edits or drops each one

What you getA punch list in minutes, not an evening of typing.

Patrick places each confirmed item on the sheet where it was found, so trades see exactly where to go and you see where items cluster.

1. Items are pinned from photo location
2. Filter by trade or status
3. Share the plan view with the trade

What you getPunch items you can find on site.

Confirmed items are assigned to the subcontractor responsible, with due dates and reminders. The trade closes an item by sending a photo of the fix, and your team verifies it.

1. Patrick assigns items to trades
2. Trades get due dates and reminders
3. Close on a photo, verified by your team

What you getA punch list that closes itself, with proof.

Patrick keeps defects and warranty claims on the same record as the punch list, with the responsible trade, photos and history.

1. Log a defect or warranty claim
2. Patrick links trade and history
3. Track to resolution

What you getOne history per defect, from walk to warranty.

Share a live, read-only view of punch progress with the owner or owner’s rep. You decide what they see and when.

1. Choose what to share
2. Send the owner a link
3. They see progress, not your internal notes

What you getFewer status calls at closeout.

Each day Patrick summarizes what changed on the schedule, which activities moved and what drove it, linked to the field records.

1. Patrick reads the day’s changes
2. Recap beside the schedule
3. Open any change to its cause

What you getSchedule changes you never have to dig for.

Dario drafts purchase orders from the estimate or Theo’s takeoff, keeps them on the job and tracks each line from sent to received. Your team approves every order before it goes out.

1. Pick the job and the supplier
2. Check the drafted lines and prices
3. Approve and send the order

What you getEvery open order on the job in one list, with what is still to arrive.

A foreman sends what they need, by message or voice note. Dario checks it against the takeoff and what is already on order, picks the usual supplier and drafts the purchase order for approval.

1. A foreman asks for material
2. Dario checks quantities and open orders
3. The PM approves the order

What you getMaterial on site when it is needed, without phone calls to the office.

Every supplier has one record: contacts, terms, price lists, open orders, deliveries and invoices across all your jobs.

1. Import suppliers or add them as you go
2. Dario links orders and documents
3. Open any supplier to see everything

What you getOne record per supplier instead of folders and inboxes.

For the materials you buy often, Dario compares unit prices and on-time, complete deliveries across suppliers and over time, so you know who to call first.

1. Choose a material or category
2. Compare price and delivery record
3. Decide who gets the order

What you getPrice history and supplier scores from your own orders.

Dario keeps supplier agreements and their end dates on file and reminds you ahead of renewals, so terms do not lapse in the middle of a job.

1. Add or forward the agreement
2. Dario reads terms and dates
3. Get an alert before renewal

What you getNo surprise price changes from a lapsed agreement.

Dario books each delivery into a slot at the right gate and laydown area, checks it against crane and hoist bookings and tells the supplier and the site team when it is coming.

1. Supplier confirms the delivery
2. Dario books gate, time and laydown
3. Site and supplier get the slot

What you getA delivery calendar for the site that everyone can see.

Dario reads supplier dispatch notices and tracking links and shows each delivery on the map with its ETA and contents. The site team gets a heads-up before the truck arrives.

1. Supplier dispatches the truck
2. Dario tracks it to the site
3. The gate gets an ETA alert

What you getNo more calling suppliers to ask where the truck is.

Snap or forward the ticket from site. Dario reads the supplier, the items, quantities, unit prices and who signed for it, even from a scan or a crumpled photo, and files it to the right job.

1. Photograph or forward the ticket
2. Dario reads lines and signature
3. Confirm anything it flags

What you getDelivery tickets as structured data, with no retyping.

Dario compares what arrived with what was ordered, line by line, and marks each one matched, short or substituted. Open lines stay open until someone on site confirms.

1. Dario matches ticket to PO
2. Shorts and substitutions are flagged
3. Your team confirms or follows up

What you getA received log tied to both the ticket and the order.

Dario keeps one booking calendar for cranes, hoists, lifts and your own equipment across jobs, warns about clashes and moves bookings when the schedule changes.

1. Request a crane or a machine
2. Dario checks availability and clashes
3. The booking goes to the operator

What you getEquipment where it is needed, and idle time you can see.

Dario lists rented equipment by job with the rate and the rental period, flags machines that have sat idle and drafts the off-rent call so rentals stop on time.

1. Rentals are logged from the order
2. Dario watches use and due dates
3. Off-rent requests go out on time

What you getLower rental bills, without chasing paperwork.

Dario keeps a running count of material at the yard and on each job. Before a new order goes out, he checks whether another job or the yard already has it.

1. Received and used material is logged
2. Dario keeps the stock count
3. Transfers are suggested before orders

What you getLess surplus, fewer duplicate orders.

Dario keeps the logistics plan for each job on the site drawing: gates, laydown, hoists, crane reach and truck routes, and updates it as the job moves through its phases.

1. Mark up the site plan
2. Dario links bookings to each area
3. Share the plan with subs and suppliers

What you getEveryone knows where to unload and where to store.

Lex writes the daily report from photos, voice notes and messages: weather, crew, work completed, deliveries, inspections and safety. Your superintendent checks it and sends it.

1. Crews send photos and notes
2. Lex drafts on your template
3. The superintendent reviews and sends

What you getA finished daily report every evening, with a source on every line.

From the truck or the deck, a voice note is enough. Lex transcribes it, pulls out the work items, hours and issues, and adds them to the right section of the report.

1. Record a voice note on site
2. Lex transcribes and structures it
3. It lands in the daily report

What you getField updates without forms, in the language your crew speaks.

Photos from the thread, the app or the walk are filed automatically with their time and place, so you can find the east wall on level 2 from three weeks ago in seconds.

1. Photos arrive from any channel
2. Lex tags job, date and location
3. Search or filter any time

What you getProgress photos you can actually find.

Lex builds the manpower log from sign-ins, foreman notes and messages: crew counts by trade and company, hours, and equipment on site. It feeds the daily report and Fina’s labor costs.

1. Crews sign in or foremen report
2. Lex counts crews, hours and equipment
3. It lands in the report and job cost

What you getA manpower record you can stand behind in a dispute.

From photos, notes and quantities installed, Lex records percent complete by activity and location. Patrick updates the schedule from it and Fina uses it for the pay application.

1. Foremen report work in place
2. Lex records percent complete
3. Schedule and billing use the same figure

What you getOne progress number for the field, the schedule and the owner.

Lex records the weather at the site address and logs any time lost, with the activity affected and the photos that show it. Patrick sees the delay against the schedule.

1. Weather is pulled for the site
2. The superintendent marks lost time
3. Delay days are logged with proof

What you getDelay records built the day they happen, ready for a time extension request.

Lex keeps your inspection and quality checklists on the phone. Each item is checked with a photo, failed items become punch or action items, and inspector results are logged with the date.

1. Pick the checklist for the inspection
2. Check items with photos on site
3. Failures turn into tracked items

What you getInspections passed the first time, with the record to show it.

Lex logs safety observations and incidents from the field and keeps toolbox talk attendance with the daily report, ready for an OSHA question.

1. Report an observation or talk
2. Lex adds it to the safety log
3. Review open items each week

What you getA safety record that keeps itself current.

Lex drafts the incident report from a voice note or message: what happened, where, who was involved, witnesses and photos. The safety manager reviews it and the corrective actions are tracked to close.

1. Report from site by voice or text
2. Lex drafts the incident record
3. Safety reviews and tracks the fix

What you getFaster incident records and a safety log OSHA-ready reviewers can follow.

Drop in a folder or ZIP, even messy or rotated scans. Lex recognizes and classifies the documents, checks them for each subcontractor, worker and piece of equipment, and shows what is missing or expired.

1. Upload a folder or ZIP
2. Lex classifies and checks each file
3. Review gaps and set alerts

What you getA compliance summary per sub, crew and machine, with alerts before anything expires.

Plans and sheets stay readable and markable on a phone or tablet with no signal. Markups, photos and notes reconcile when the device reconnects.

1. Open the current set on site
2. Mark up and photograph offline
3. Everything syncs on reconnect

What you getThe right drawings on site, signal or not.

Lex summarizes the day per job: work done, deliveries, inspections, safety and open issues, with links to the source records.

1. Lex reads the day’s records
2. A recap per job each evening
3. Open any line to its source

What you getKnow what happened on every job without calling the site.

Fina turns the estimate into a working budget by cost code and keeps committed, actual and forecast cost next to it as the job runs.

1. Import the estimate or budget
2. Fina maps it to cost codes
3. Track committed, actual and forecast

What you getA live budget instead of a monthly spreadsheet.

Every invoice, delivery and timesheet rolls up to the job, so margin against the estimate is current every day, with variances and their causes highlighted.

1. Costs flow in from every source
2. Fina compares to the estimate
3. See variances and their causes

What you getMargin per job you can trust mid-project.

Fina takes hours from daily reports and timesheets and equipment use from the field, applies your rates and posts the cost to the job and cost code.

1. Hours and equipment come from the field
2. Fina applies your rates
3. Cost lands on the job

What you getLabor and equipment cost without manual entry.

Fina tracks each change from potential change order to approved, imports subcontractor change orders, and updates the budget, the contract value and the schedule of values when it is approved.

1. Create or import the change
2. Price it and send for approval
3. Approved changes update budget and contract

What you getEvery change tracked from first notice to the billing line.

Fina drafts each pay application against the schedule of values from field progress and received materials, applies retainage and checks it against the contract before your project manager approves it.

1. Fina drafts from progress
2. Checks retainage and stored materials
3. Your PM approves and sends

What you getPay apps in hours, not days, with backup for every line.

Fina checks each subcontractor’s billing against their schedule of values and progress, tracks retainage and holds payment until the right lien waiver is in.

1. Sub submits a pay app
2. Fina checks progress and retainage
3. Pay once the waiver is in

What you getNo payment without the paperwork.

When a delivery is matched, its value posts to the right job and cost code. Fina sees it before the supplier invoice is approved.

1. Delivery is matched
2. Value posts to job and cost code
3. Fina checks the invoice against it

What you getMaterial cost on the job the day it arrives.

Fina compares every invoice line with the purchase order and the delivery ticket. Where the three disagree, the line is held with the reason and the document that proves it.

1. Invoice arrives by email or upload
2. Fina matches PO, ticket and bill
3. Approve the rest, hold the gap

What you getPay what arrived, hold what did not, with the proof attached.

Supplier and subcontractor invoices arrive by email or upload, are read and matched to the job, and wait for approval. Owner invoices and pay apps are tracked to payment.

1. Invoices arrive by email or upload
2. Fina reads and matches them
3. Approve, schedule and track payment

What you getPayables and receivables in one place, by job.

Connect your accounts or import statements. Fina matches each movement to its invoice or payment and leaves only the exceptions for a person to confirm.

1. Connect accounts or import a statement
2. Fina auto-matches movements
3. Confirm the few exceptions

What you getMonth-end reconciliation in minutes.

Fina combines expected owner payments, supplier and sub bills, payroll and open orders into one forecast, by job and for the company, and shows the lowest point ahead.

1. Fina reads receivables and payables
2. Adds open orders and recurring costs
3. See the forecast by job and company

What you getKnow which jobs drain cash before the bank does.

Fina keeps every due date in view and reminds you before a payment is due or when a receivable is overdue, with the documents ready for follow-up.

1. Fina watches due dates
2. Get alerts before and after
3. Follow up with the backup attached

What you getFewer late payments in both directions.

Fina groups purchasing across jobs so you can see the categories and suppliers with the most impact, and how prices move over time.

1. Fina groups spend by category
2. Review top suppliers and trends
3. Pick where to renegotiate

What you getA clear view of spend before the next buyout.

Describe the work or import a bill of quantities. Fina prices it from your price book and past jobs, applies your margin rules, and turns the approved quote into the contract and the first invoice without retyping.

1. Describe the job or import quantities
2. Fina prices it from your price book
3. Approve and convert to contract

What you getQuotes in minutes, with your margins built in.

Fina applies your rules to every quote, order and pay app, such as a minimum margin, a second approver above a dollar amount or an alert when progress and billing drift apart.

1. Set your rules
2. Fina checks every document against them
3. Exceptions go to the right person

What you getCompany policy applied every time, without a checklist.

Map projects to customers and subcontractors to vendors once, then invoices, bills and commitments sync without retyping. Your accounting system stays the book of record.

1. Connect your accounting system
2. Map jobs, vendors and cost codes
3. Invoices and bills sync automatically

What you getNo double entry between the job and the books.

Fina watches budget movement, pending changes and subcontractor billing and warns you when a job is heading over, with the lines driving it.

1. Fina watches every job daily
2. Alerts when a trend turns
3. Open the lines behind it

What you getProblems while there is still time to act.

Connect Google Workspace or Microsoft 365. Colin links each message and attachment to its project and item, so the conversation sits with the RFI or change it is about.

1. Connect your mailbox
2. Colin links mail to projects and items
3. Find any conversation from the item

What you getOne place for every conversation on the job.

Add Colin to the site thread on WhatsApp or text. Photos, tickets and messages are read and filed to the job and the daily report, with no new app for the crew.

1. Add Colin to the site thread
2. Crews message as usual
3. Colin files everything to the job

What you getField records without asking anyone to change how they work.

Email, text and WhatsApp messages with each company are kept in one thread per job, linked to the RFIs, submittals, changes and invoices they are about, so anyone can pick up the history.

1. Messages come in from any channel
2. Colin files them by company and job
3. Open a company to see the whole history

What you getThe full story of every relationship on the job, in one place.

Colin drafts the RFI from a note or photo, links it to the sheet and detail, and follows up with the architect or engineer until it is answered.

1. Flag a question from site
2. Colin drafts and links the RFI
3. Automatic follow-ups until answered

What you getNo RFI falls through the cracks.

Colin keeps the submittal log, routes each package to its reviewers, tracks due dates and resubmissions, and reminds anyone holding one up.

1. Add or import submittals
2. Route to reviewers with due dates
3. Track approvals and resubmittals

What you getSubmittals that move without chasing.

Record the meeting or upload your notes. Colin writes the minutes in your format, lists decisions and open items with owners and due dates, and sends Patrick the action items.

1. Record or upload the meeting
2. Colin drafts minutes and actions
3. Review and send to attendees

What you getMinutes out the same day, with every action owned.

When a revised set or bulletin arrives, Colin compares it to the last issue, notes which sheets changed and sends each trade the sheets that affect them, with read receipts on the transmittal.

1. A new revision arrives
2. Colin finds the changed sheets
3. Trades get their sheets and confirm receipt

What you getNo one builds from a superseded drawing.

Colin packages the week’s progress, photos, open issues and the budget summary from Fina into an owner-ready report. Your project manager edits and sends it.

1. Pick the week and the owner
2. Colin drafts the report
3. Edit and send

What you getOwner updates that take minutes, not an afternoon.

Crews write or speak in Spanish, the office reads English, and the other way around. Colin translates each message and keeps the original beside it for the record.

1. Crew sends a message in Spanish
2. Colin translates and files it
3. Replies go back in Spanish

What you getClear instructions on site, whatever language the crew speaks.

Colin sends each person a morning digest for their jobs: RFIs waiting on them, submittals due, messages to answer and decisions pending, with a link to each.

1. Colin reads every open item
2. Each person gets their own digest
3. Click through and act

What you getFewer missed replies and fewer interruptions.

Pixer tracks each opportunity from lead to qualified, bidding, submitted, won or lost, with the estimated value, due date, owner and probability, so you see what is coming and what you can staff.

1. Leads arrive from Clara, email and your team
2. Pixer files them by stage
3. Move them on as the bid progresses

What you getA pipeline you can forecast backlog from.

Pixer reads the dates out of each solicitation and puts them on a shared bid calendar, with reminders to the estimator and precon lead before every cutoff.

1. Pixer reads dates from the bid
2. They land on the team calendar
3. Reminders before each cutoff

What you getNo missed pre-bid meeting or late question.

Pixer files every Go/No-Go with its reasons, Clara’s cited findings and the person who decided, so you can see later which bids you passed on and why.

1. Clara drafts the memo
2. Your precon lead decides
3. Pixer keeps the decision and reasons

What you getA bid history you can learn from.

For each pursuit, Pixer drafts the proposal on your template: relevant past projects, team resumes, safety statistics, approach and schedule, pulled from the AI Brain and tailored to the owner’s criteria.

1. Pick the pursuit and template
2. Pixer drafts from your records
3. Your team edits and approves

What you getA strong first draft of every proposal in an hour, not a week.

Pixer keeps your standard inclusions, exclusions and clarifications by trade and proposes the right set for each bid, flagging any that conflict with the solicitation.

1. Pixer proposes the qualifications
2. Conflicts with the bid are flagged
3. Your estimator finalizes the list

What you getConsistent qualifications that protect your scope.

Each client has one record: contacts, past bids and results, projects, preferences and the last conversation, so anyone on the team can pick up the relationship.

1. Clients are created from bids and projects
2. Pixer links contacts and history
3. Open a client before you call

What you getRelationships that do not live in one person’s inbox.

Pixer keeps track of where you are prequalified, the limits and expiry dates, and reminds you before they lapse. Clara fills the questionnaires; Pixer keeps them current.

1. Add each prequalification
2. Pixer tracks limits and expiry
3. Renew before it lapses

What you getNever miss a bid because a registration expired.

After a bid goes in, Pixer reminds the owner of the pursuit to follow up. When results come out, it logs the award, the low bid from the public bid tab where available, and your loss reason.

1. Submit the bid
2. Pixer schedules follow-ups
3. Log the result and the reason

What you getWin and loss data from your own bids, not guesses.

Pixer reports your win rate and margin by segment and forecasts backlog from the weighted pipeline, so you can choose where to chase work. Figures come only from your own records.

1. Pixer reads your bid history
2. See win rate by segment
3. Forecast backlog from the pipeline

What you getPursue the work you actually win.

On award, Pixer hands the client, contacts, proposal commitments and bid documents to Patrick, who opens the project with them in place.

1. Mark the pursuit as won
2. Pixer passes it to Patrick
3. The project starts with the full history

What you getNo commitments lost between the sales team and the project team.

The AI Brain connects your past bids, estimates, contracts, spec books, sub proposals and project email into one company knowledge layer. Ask a question, such as which past projects are good references for a bid, and get an answer cited to the document and page. Clara, Dora, Nova and Theo all draw on it.

1. Connect project folders, email and bid files
2. Ask questions in plain language
3. Check each answer against its cited source

What you getA company memory that answers with sources and gives every agent your own history and context.

Project managers and executives can ask plain questions, such as how margin on a job compares to the estimate, which invoices are overdue or where the schedule is slipping. The assistant answers from the project record and shows the sources behind each answer, so the reader can check the figures.

1. Ask a question about a project
2. Read the answer and its sources
3. Open a source to check the figures

What you getSourced answers on margin, invoices and schedule without building a report first.

Invoices, delivery notes, reports, photos and contracts are stored in one archive across projects. Anyone with access can search it instead of digging through project folders and email, which helps at closeout or when a dispute needs the original document.

1. Store project documents in the archive
2. Search across documents and projects
3. Open the original document you need

What you getOne searchable archive of project documents, from delivery notes and invoices to contracts.

Bid packages, contracts, proposals and plan sets come in as PDF, including scanned documents read with OCR, plus DOCX and XLSX. Teams upload files directly or forward them by email, and the agents read them as they are. DWG and DXF are on the roadmap; today, export drawings to PDF and upload them.

1. Upload or forward the documents
2. Scanned pages are read with OCR
3. Agents read and cite the documents

What you getYour existing PDFs, scans, Word files and spreadsheets ready for the agents without reformatting.

Every finding, price and quantity links to the page, clause or sheet it came from. An estimator checking a liquidated damages flag opens the cited page and reads the clause itself, rather than trusting a summary. Citations are checked against the source before a finding is shown.

1. Open a finding, price or quantity
2. Follow the citation to its source
3. Confirm, edit or dismiss the finding

What you getFindings your team can verify against the source document before acting on them.

Bid packages, findings and decisions are shared across the preconstruction team, so estimators, the project executive and counsel work from the same record. When someone reviews a finding or records a decision, the rest of the team sees it, and nobody reads the same package twice. Team collaboration starts on the Duo plan.

1. Invite your preconstruction team
2. Share packages and findings
3. Record decisions on the shared record

What you getOne shared record of packages, findings and decisions across the whole preconstruction team.

Every team reviews bids and contracts a little differently. Custom workflows let you shape review steps and hand-offs around how your team already works, such as who checks a Go/No-Go memo or when a contract goes to counsel. Custom workflows are included on Studio and Enterprise.

1. Map your current review steps
2. Set reviewers and hand-offs
3. Run each package through your workflow

What you getReview steps and hand-offs that match how your team already works.

Each user gets a role: owner, project manager, site manager, crew, office or subcontractor. Roles follow least privilege, so a subcontractor sees only what is shared with them and crew members see what they need on site. Privileged access is reviewed quarterly.

1. Assign each user a role
2. Limit access to what each role needs
3. Review privileged access on a schedule

What you getAccess that matches each person's job, from owner to subcontractor.

BAU AI connects to the tools your team already uses: QuickBooks, Sage, Procore, Autodesk Construction Cloud, MS Project, Primavera, Outlook, Google Workspace and Microsoft Teams. Documents, schedules and costs move between them instead of being retyped, and the project record stays in one place.

1. Choose the tools to connect
2. Authorize each connection for your team
3. Work from one project record

What you getLess retyping between BAU AI and the tools your team already runs every day.

Every action is logged with the user, time, document and citation, including overrides of agent findings. When an owner, auditor or counsel asks how a decision was reached, the team can show who reviewed what and when. The audit trail exports as PDF, JSON or CSV.

1. Work as usual while actions are logged
2. Review who did what, and when
3. Export the trail as PDF, JSON or CSV

What you getA complete record of who did what, on which document, with which citation.

Users sign in through your identity provider using SAML 2.0 or OIDC, so access follows your company sign-in rules. SCIM provisioning with Okta, Microsoft Entra or Google Workspace creates and removes accounts as people join or leave. SSO is included on Studio and Enterprise, and SCIM on Enterprise.

1. Connect your identity provider via SAML or OIDC
2. Turn on SCIM provisioning
3. Manage users from your identity provider

What you getSign-in and accounts managed centrally, so people who leave lose access when IT removes them.

The API gives your own systems structured project and bid data from BAU AI, so internal reporting, dashboards or a data warehouse can use it without manual exports. Your IT team decides what to pull and where it goes. API access is available on the Enterprise plan.

1. Request API access on Enterprise
2. Connect your internal systems
3. Pull structured project and bid data

What you getProject and bid data available to your own systems in a structured form.

Email alerts tell the right people when something needs attention: a new bid that matches your profile, an approaching deadline or a status change on a package or project. Estimators and project managers can act without logging in to check, and each alert points to the item.

1. Choose which alerts you want
2. Receive emails for matches, deadlines and changes
3. Open the linked item to act

What you getTimely emails on new matches, deadlines and status changes, so due dates are not found late.

Many teams retype the same data between estimating, accounting, scheduling and document tools. The calculator asks how often your team re-enters data between your current software and how long each re-entry takes, then estimates what that costs each year. The result is your own estimate, based only on the numbers you enter.

1. List the tools your team uses today
2. Enter how often data is re-entered
3. Review the estimated yearly cost

What you getA yearly cost estimate for duplicate data entry, built entirely from your own inputs.

See project health across the portfolio at a glance, with open issues, milestones and accountable owners, and open any job for the detail.

1. Open the portfolio view
2. Spot jobs that need attention
3. Drill into the job

What you getOperating clarity across every job, without status chasing.

Keep people, companies, trades, contacts and documents in one directory shared by every agent, with each company’s insurance and compliance status.

1. Import or invite companies
2. Assign roles and trades
3. Every agent uses the same records

What you getOne source of truth for who is on the job.

Your bids, contracts and sub proposals are stored and processed on US infrastructure, with primary region us-east-1 and failover inside the United States. Storage and AI inference both stay in the US, and bid data does not move across regions. This applies on every plan.

1. Upload documents to your tenant
2. Storage and inference run in the US
3. Request the security packet for procurement

What you getDocuments and AI processing kept in the United States, documented for your security review.

Your bids, contracts, estimates and the outputs built from them never train BAU AI models or any third-party model. Foundation models run under enterprise terms that prohibit retention beyond the request, and this is a contract term. Support access to documents is opt-in, time-bound and logged.

1. Upload bids, contracts and estimates
2. Agents process them for your tenant only
3. Confirm the contract term in your agreement

What you getYour prices and contract positions stay yours, backed by a contract term rather than a setting.

Each customer's documents are processed and stored in a logically isolated environment. Cross-tenant access is blocked at the data, application and audit-log layers, and outputs are scoped to the calling tenant. Enterprise customers can choose a dedicated single-tenant deployment instead.

1. Your team works in its own tenant
2. Access across tenants is blocked
3. Choose single-tenant on Enterprise if required

What you getCompany data visible only to your team, kept separate from every other customer.

All storage is encrypted with tenant-specific keys, using AES-256 at rest on storage and databases and TLS 1.3 on every connection. Backups are encrypted too. On Enterprise, you can manage the keys yourself, which some owner-driven and federal-adjacent work requires.

1. Data moves over TLS 1.3 connections
2. Stored data is encrypted with AES-256
3. Use customer-managed keys on Enterprise

What you getDocuments encrypted in transit and at rest, with key control available on Enterprise.

You set how long documents are kept, from 30 days to indefinite, and encrypted backups age out per your policy. You can hard delete on demand. If you leave, you export your data, findings and audit trail in machine-readable formats, and deletion is confirmed in writing within 30 days.

1. Set your retention period
2. Hard delete documents on demand
3. Export everything if you leave

What you getControl over how long your data is kept, and a clean, documented exit if you leave.

Uploaded documents are treated as untrusted input. Agents do not follow instructions hidden in a bid package or contract, and tool use is gated by allow-lists. Citations are checked against the source before a finding is shown, and low-confidence reads surface as questions to your team, not silent guesses.

1. Upload documents from any source
2. Agents read them as data, not orders
3. Answer questions where a read is uncertain

What you getFindings that a hidden instruction in a document cannot steer, with uncertain reads raised as questions.

Agents do the first pass and people make the calls. Every finding can be edited, dismissed or overridden, and overrides are logged in the audit trail. There is no automatic bid submission, contract signing or award, so your team reviews, signs and submits everything that leaves the company.

1. Review each agent finding
2. Edit, dismiss or override where needed
3. Your team signs, submits and awards

What you getDecisions that stay with your people, with every override on record.

On Enterprise, BAU AI runs as a dedicated single-tenant deployment with its own resources and database, in your cloud account or on your own servers. Customer-managed keys and inference keep data, keys and the model boundary inside your infrastructure. A data processing agreement is part of every Enterprise agreement.

1. Choose single-tenant cloud or on-premise
2. Deploy in your cloud account or data center
3. Manage network, access and keys yourself

What you getBAU AI inside your own infrastructure, for work with stricter infosec requirements.

On the Enterprise plan, BAU AI can run custom AI models for your company, including your own models when it runs in a dedicated instance or in your own data center. The same rules hold in every option: your data belongs to you, every finding is cited to the page and your company permissions apply.

1. Discuss model needs on an Enterprise call
2. Agree on the deployment and model setup
3. Run the agents with the agreed models

What you getAI models set up for your company, with the same citation and permission rules as every plan.