No. It is a full homebuilder operating system — a backend with plan and option management, a margin-locked pricing matrix, a takeoff rules engine, a sales and contract engine, community and lot admin, and a native integration layer. The buyer-facing selection screen is one surface on top of all of that.
Native API connections to JobTread, TurnkeyBuild, Takeoff.Guru, GoHighLevel, and any ERP or accounting platform (e.g. Oracle JD Edwards, Sage Intacct). No middleware, no CSV bridges.
When a sale is confirmed, the Configurator generates the contract, fires the lot-level takeoff, creates the JobTread project with budget loaded, requests sub pricing through TurnkeyBuild, issues POs, and makes lot P&L visible — all in the same transaction, with no manual re-entry.
At a Top 50 Homebuilder: ERP adoption went from 38% to 94%, the sales-to-purchase-order cycle dropped from 14 days to 48 hours, manual re-entry steps went from 11 to 0, option-pricing errors from ~8/month to 0, and $94,000 of annual tech waste was eliminated in year one.
Because the integration is pre-built and proven in production, deployments are measured in weeks, not months.
No. The Configurator is the sales-to-PO layer most ERPs are missing. At the Top 50 Homebuilder we kept Oracle JD Edwards and built the layer that finally got it adopted.