The embedded engineer connects what your office and field have already standardised on — nobody is asked to migrate. This is the list we intend to support, ranked by what mid-market GCs run most. None of it is in production yet, because there is no client in production yet.
The pairing most engagements would start with: a construction ERP (Vista, Sage 300 CRE, Foundation, CMiC) and a project-management platform (Procore, Autodesk). Cost codes, commitments, change orders and field hours reconciled, with a conflict log a controller can actually read.
The support list is meant to grow the way the work does — a client needs a system connected, so it gets connected, and anything reusable becomes part of the core. Tell us what you run and we will say honestly how involved it would be.
Priority means it is in the first wave of connectors we are building. On request means we will scope it when a client needs it. Nothing here is running in production yet.
Job cost, AP, payroll and commitments.
PriorityJob cost and commitments.
PriorityJob cost and payroll.
PriorityGL and AP for smaller finance stacks.
PriorityJob cost, GL and project accounting.
On requestJob cost and AP.
On requestGL and project accounting.
On requestCost codes, commitments, change orders, daily logs.
PriorityCost management, RFIs and submittals.
PriorityCost and issues.
On requestDaily reports and field notes.
On requestThe spreadsheets holding the gaps together today.
PriorityMarkups and submittal packages.
On requestModel takeoff to bill of materials.
On requestModel coordination and layout.
On requestPayroll export from field hours.
On requestSSO, Teams alerts and SharePoint closeout.
On requestDirect dataset for portfolio reporting.
On requestTell us the system and we will tell you honestly how involved connecting it would be.