Project Manager, Preconstruction OS

Clayco is a full-service, turnkey real estate development, master planning, architecture, engineering, and construction firm that safely delivers clients across North America the highest quality solutions on time, on budget, and above and beyond expectations. With $8.1 billion in revenue for 2025, Clayco specializes in the "art and science of building," providing fast track, efficient solutions for mission critical, industrial, life sciences, power & energy, aviation, commercial, institutional, residential and sports & entertainment related building projects.

Precon OS is Clayco’s in-house preconstruction platform (Estimation, GC/GR, Data Manager, Program Management) and the future estimate source for E2B Hub. The foundation is sound, but an estimator cannot yet complete and issue an estimate end-to-end in the platform. Clayco is bringing in an external vendor to close that gap. This role owns the outcome: it directs vendor delivery, protects scope, resolves open decisions, and gets Precon OS to a production-ready MVP that Clayco can run without the vendor.

This is a delivery-governance role, not a coordination role. The work includes a mandatory validation phase, eleven work packages of uneven size and risk, a long list of unresolved Clayco decisions, and two technology stacks.

• Run the vendor engagement - Own the plan, cadence, RAID log and status reporting across all work packages. Hold the vendor to the Definition of Done: delivery is traceable requirements, passing tests and approved evidence, not hours consumed or sprints completed.
• Govern the validation phase (WP-0) - Drive the vendor’s codebase and functional validation, then lead the re-baseline of scope, price and schedule against what is actually found. Hold the line against optimistic assumptions about how complete the Estimation module is.
• Manage scope and sequencing - Enforce the in-scope / out-of-scope boundary and the real dependencies: RBAC unblocks UAT, GC/GR authorization precedes the rate‑engine cutover, lineage work follows the parity proof, and the E2B Hub re-platform follows the API contract.
• Close open decisions - Maintain the decision register (Program Management/Estimation coupling, authorization model, deploy access, stable role identity, E2B Hub override continuity and cutover approach, scale targets, audit retention). Put each in front of the right Clayco owner with a recommendation and a deadline.
• Own acceptance and quality gates - Run the traceability matrix and merge/acceptance gates: GC/GR byte‑identical parity, arithmetic that reconciles to the cent, permission matrix with API‑level redaction checks, concurrency, migrations, manual browser verification, and E2B Hub no‑regression and read‑only enforcement.
• Orchestrate UAT, beta and cutover - Schedule estimator, cost administrator and project director time; triage defects against agreed severity thresholds; plan training and cutover. Lead the final BO-1 acceptance run on a live project with the chief estimator.
• Clear Clayco‑side dependencies - Get staging and production environments stood up, vendor repository, Okta and Azure access provisioned, and deploy‑path questions settled, so the vendor is never blocked on Clayco.
• Coordinate across teams and stakeholders - Keep preconstruction leadership, Platform/Security, Data/BI, the E2B Hub team and any other module vendors aligned. Report clearly and early to executive sponsors on risk, scope change and budget.
• Manage budget and commercials - Track spend against the separately priced packages (WP‑0, WP‑10), process change requests, and approve invoices against accepted deliverables only.
• Secure the handover - Make sure architecture, API, runbook and…