PECOS.Builder
From signed contract to coordinated delivery. One project record, clear responsibilities, visible document status and verified decisions.
Every party. Every dollar. Every date.
Prime contract
Upload the executed contract. AI extracts terms with page citations; a PM confirms value, retention, dates and duties before project setup.
Private original · Reviewed terms · Assigned stakeholders
Project setup
Establish the approved schedule, budget, cost codes, current drawings and project-specific access. Keep the baseline separate from progress and revisions.
Schedule baseline · Budget · Drawings · Access roles
Commitments
Invite trades to price active-project scope, compare proposals, award and execute subcontracts, and review insurance and licenses.
Subcontracts · Purchase orders · Buyout vs. budget
Coordinate delivery
Connect RFIs, submittals, daily logs, photos, meetings, inspections and punch to the current source documents and the next responsible person.
RFIs · Submittals · Field evidence · Meeting actions
A controlled change chain
Capture the request, route design and trade pricing separately, assemble scope and time impact, obtain authorized signatures, then execute and distribute.
Change events · Pricing · Owner decisions · Execution history
Reviewed pay applications
Map sub invoices to the approved schedule of values for human review. Maintain cumulative billing checks, AIA G702/G703 pay applications and separate certification.
Sub SOV · Invoices · Prime pay apps · Retention
Evidence-led controls
Track contractual notices, Texas lien-waiver requirements, insurance expiry and payment blockers. Completion requires the correct reviewed evidence.
Waivers · Insurance · Dated obligations · Exception checks
A searchable handoff
Collect as-builts, warranties, manuals, training and final waivers. Verify turnover requirements and authorized retention release before archiving.
Closeout checklist · Final waivers · Owner archive
Operating model and product direction—not a claim that every automation is activated. Explore the delivery roadmap for readiness and validation requirements.
Project Hub
One record per project: contract, budget and SOV, schedule, drawings, directory, and every CO, RFI, submittal, invoice, pay app and PO with status and full audit trail.
Stakeholder workspaces
GC review desks, owner closed-book visibility, discipline-scoped design records and subcontractor billing/compliance form the reported foundation. Complete dashboards and supplier access are proposed extensions.
Receive, act, confirm
Proposed shared workflow: select a project record and exact version, choose named recipients, assign an action and deadline, send a secure notice, and preserve each acknowledgment and response.
Operations email
Planned item-specific notices carry the record number, version, required action and due date. Inbound matching, retained replies, digests and operational delivery require activation and testing. Ambiguous replies go to review.
Commitments & schedule
Keep dated promises separate from subcontracts, POs and invoices, then link them. Planned alerts begin seven days ahead; due-today and overdue states retain text labels, named actors and escalation. Nightly automation needs validation.
Human-reviewed AI
Contract extraction with page citations, cited project answers, draft changes, invoice mapping and briefs. Preserve sources and review outcomes; AI never approves money, legally certifies a waiver or silently accepts contract terms.
Billing & payment controls
No billing before execution or approved early release. Reviewed waiver/insurance evidence, cumulative payment-line checks, retention and role-based limits gate the next step. Owner approval, architect certification, execution and settlement remain separate. ACH/Plaid and early pay are proposed extensions, not live payments on this site.
Compliance & private originals
Company insurance, W-9, applicable licenses and waiver records linked to the authorized project. Private original files, version history and searchable records support evidence-led review; portable cross-GC reuse requires validation.
Post-contract buyout
Project-specific invitations, trade proposals, scope questions and change pricing after the prime contract is executed. Sales, CRM and the prime pre-bid pipeline are outside this operating scope.