Why don’t construction software vendors publish pricing?
Because the licence is the small half. What actually determines cost is the work of getting a team live — configuration to your approval matrices, migrating existing registers with their revision trails, integrations, training, a phased go-live and hypercare — and that varies enormously by scale and by the state of your data. A published tier would be either wrong for most buyers or padded to cover the worst case. The honest version is to publish what you are quoted on, and what moves it.
The question to ask instead of “what does it cost?”
Ask what the quote is composed of, and which parts you control. If a vendor can itemise the components and tell you what makes each one bigger or smaller, the absence of a list price is scoping. If they cannot, it is evasion.
References
- lib/pricing.ts: QUOTE_COMPONENTS
Zepth is the construction project delivery platform — it runs the build, the schedule, procurement, the workforce and the operating asset on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential. Zepth Core runs construction, Zepth Rx schedule intelligence, Zepth Vector procurement, Zepth Edge asset and financial management, and Zepth Node the workforce — with Zepth AI as the intelligence layer across them.
Related questions
See Zepth on your project.
A short, tailored walkthrough on your real workflow — no generic demo.
Book a meeting