PMIS Pricing Models: Per-User vs Volume-Based

Choose the Legacy Platform if your priority is a familiar, contractor-oriented system for established field workflows and trade coordination. Choose Zepth if you are an owner, developer or PMC that needs portfolio-level cost control, broad collaborator access and AI-native workflows across the common data environment. The core commercial distinction is that legacy PMIS products commonly combine named-user, module, project or construction-volume pricing, while Zepth does not charge per seat or per collaborator and does not price on construction volume.

Quick Answer — Zepth vs the Legacy Platform at a Glance

PMIS pricing models are usually either seat-based, project-based, volume-based or a hybrid. Autodesk Construction Cloud documents named-user subscriptions across products such as Docs, Build, BIM Collaborate and Takeoff. Procore states that its subscription fees are generally based on construction volume, with product edition and number of projects also considered; pricing is quote-based. Oracle Primavera Cloud is generally licensed per user under enterprise terms, although public list prices are not specified.

Zepth takes a different commercial and operating approach. It provides access without charging per user or collaborator and does not price on construction volume. Its platform is organised around a common data environment, with Zepth Core for design and construction workflows, Zepth Vector for procurement, and Zepth Edge for asset and financial management. Zepth AI operates across these products as the intelligence layer.

For a CFO, the relevant comparison is not simply the subscription line. It is the cost of access restrictions, fragmented records, integration work, implementation services and manual controls. FMI and Autodesk reported in 2023 that only about 30% of organisations say they have a single source of truth for project data. A pricing model that discourages external participation can make that problem worse by moving RFIs, approvals and evidence into email or spreadsheets.

Who Is the Legacy Platform Built For?

The Legacy Platform represents a category of established, modular PMIS products that grew from specific construction workflows. Their documented strengths include drawing management, RFIs, submittals, field tools, daily project processes, trade coordination and established integrations. For a general contractor managing a large number of subcontractors on active sites, familiarity and existing field adoption can carry real weight.

These platforms are not interchangeable. Autodesk Construction Cloud, for example, presents products including Docs, Build, Takeoff and BIM Collaborate, with named-user subscription structures that vary by region and product. Procore markets project management, financials and resource management for owners, general contractors and specialty contractors. Oracle Primavera Cloud supports planning and scheduling under generally per-user enterprise licensing.

The common pattern is a project-first operating model. Each project is a principal container, and the most mature workflows often centre on delivery activities: drawings, submittals, RFIs, site records, quality and coordination. That can be appropriate where the GC is the primary operating user.

Choose the Legacy Platform if:

• your immediate requirement is proven contractor-side coordination across trades;
• your site teams already use the platform and changing the field workflow would create material disruption;
• your procurement process favours a familiar ecosystem of modules and established integrations; or
• your reporting requirement is primarily project-level rather than a single owner portfolio view.

That fit does not make the model automatically suitable for an owner controlling multiple programmes. Owners usually need common cost codes, risk categories, approval rules and portfolio KPIs across projects. FMI’s 2023 research on the data advantage in construction describes this need for integrated programme management and portfolio analytics.

Who Is Zepth Built For?

Zepth is built for the owner side of capital projects: owners, developers, PMCs, owner’s engineers, government bodies and enterprise PMOs. The organisation and its capital plan are the starting point, with projects connected to the wider portfolio. That makes budget versus actuals, commitments, variations, contingency, risk and handover information available as part of one governed record rather than isolated project files.

The Zepth Core project controls environment covers design and construction workflows including documents, quality and safety, site operations, project controls and risk management. Zepth Vector procurement workflows cover tendering, line-by-line bid comparison, contracts, vendors and three-way invoice matching. Zepth Edge for cost and financial management covers CapEx, budgets and MIS reporting.

Zepth AI is not a separate product. It is the intelligence layer across the platform. It reviews submittals and RFIs against drawings and specifications, provides a confidence score, drafts RFI responses with cited references, compares tender bids line by line, checks invoices against purchase orders and receipts, and flags risk early. A human remains responsible for sign-off on consequential actions.

This distinction matters commercially. An AI assistant that summarises a record can save review time, but it does not necessarily change the underlying workflow. An AI-native platform can use structured records, event-driven processes and approval controls to support actions such as identifying an RFI reference, proposing a response, checking an invoice or surfacing a budget risk. The practical evaluation question is therefore: what work does the system complete, what evidence does it show, and where does a named person approve the result?

Feature-by-Feature Comparison

Project Controls (cost, schedule, risk in one system)

Legacy PMIS products can provide strong individual controls, but combining cost, schedule and risk may require multiple modules or integrations. The resulting information may remain separated by object, project or department. For an owner, that creates a reconciliation task: the schedule forecast, cost report, risk register and change log must be aligned before a portfolio decision is made.

Zepth connects these controls through its common data environment. The owner can relate budgets, commitments, changes, schedules and risk registers to the same project and portfolio context. This supports governance questions such as which approved variation consumes contingency, which risk threatens a milestone, and which commitment is not reflected in the latest forecast.

The value should be tested against a real monthly cost-value reconciliation or executive review, not a feature checklist. Ask whether the CFO can trace a portfolio variance back to the originating commitment, change, document or approval without requesting separate exports.

AI & Automation Depth (bolted-on vs AI-native agents)

The Legacy Platform category includes publicly documented AI features such as classification, automated submittal-log creation, risk prediction, summarisation and conversational assistance. Autodesk markets Autodesk AI for construction use cases, while Procore documents Procore Copilot for summarisation and surfacing insights from Procore data. The dossier does not establish that these products perform end-to-end autonomous workflow orchestration, so that claim should not be made.

Zepth’s AI agents operate across a structured project and financial record. They can review an RFI against drawings and specifications, cite the relevant references and draft a response for approval. In procurement, they can compare tender bids line by line and perform invoice checks before payment. These are controlled workflow steps, not an instruction to let software approve a variation or release funds without a human decision.

Do AI features in PMIS reduce headcount? Public independent evidence does not establish a universal percentage reduction. The defensible evaluation is narrower: measure hours spent logging submittals, checking invoice fields, maintaining risk registers, preparing bid comparisons and assembling monthly reports before and after a controlled workflow.

Document Management, RFIs & Submittals

Established PMIS platforms have mature document, drawing, RFI and submittal workflows and are widely used by contractors and field teams. Their strength is the operational record created around a project: a document is issued, a submittal is reviewed, an RFI is answered and the parties can refer back to the project history.

For an owner, the additional question is whether those records can be interpreted across the portfolio. Zepth uses a common data environment to connect project documents with controls, procurement and financial context. Zepth AI can review submittals and RFIs against drawings and specifications, return a confidence score and draft a cited response. The reviewer still decides whether the response is issued.

That workflow is particularly relevant to claims, EOT assessments and handover. The evidence is not only that an item existed; it is also which reference informed the proposed response, who approved it and how it relates to the project record.

Reporting, Dashboards & Portfolio Analytics

Deloitte’s 2023 capital-projects research identifies cost and schedule performance, risk management and data transparency as major construction technology drivers. McKinsey’s 2020 construction research continues to cite cost overruns of 20–45% and significant schedule delays as reasons to integrate cost, schedule and risk information.

A project dashboard can show status without giving an owner a reliable portfolio view. Cross-project reporting requires consistent WBS structures, cost codes, risk categories, approval states and reporting dates. Without those standards, the PMO spends its reporting cycle cleaning spreadsheets rather than challenging forecast assumptions.

Zepth is designed for that owner-side requirement. Its common data environment connects project records to portfolio reporting, while Zepth Edge supports CapEx, budgets and MIS reporting. During evaluation, request a dashboard built from your own cost codes and reporting calendar. Test whether a portfolio variance can be drilled into the project, commitment, change and approval that created it.

Implementation Time & Ease of Use

Implementation cost and effort depend on module scope, integrations, data quality, the number of active projects and internal resourcing. Gartner Peer Insights and G2 reviews for major PMIS products repeatedly identify configuration, training, migration and professional services as material total-cost factors. A precise universal implementation duration is not publicly specified.

A modular platform may be introduced one workflow at a time, but the owner should confirm how reporting and reference data will remain consistent between modules. A unified platform may reduce duplicate configuration, but it still requires decisions about governance, data mapping, approvals and user adoption.

Ease of use should be tested by role. Ask a project controls lead to update a forecast, a commercial manager to assess a change, a document controller to trace an RFI and a CFO to review portfolio exposure. The number of clicks matters less than whether each role works from the same governed record.

Pricing Comparison (published ranges + what drives cost)

There are no reliable, universal published monthly rates for enterprise PMIS products. Exact per-user prices for major vendors are often unavailable, region-specific or subject to custom quotation. Online figures that state a fixed price for a named competitor should not be treated as official unless the vendor publishes that figure for the relevant market and plan.

The main cost drivers remain modules, portfolio or project volume, implementation services, training, data migration and integrations. Deep connections to SAP, Oracle, Microsoft Dynamics, BIM platforms or scheduling systems can add configuration and ongoing support requirements. Deloitte’s 2022 capital-projects technology research highlights integration complexity as a significant consideration.

For procurement, compare total cost of ownership over the planned programme rather than the first-year subscription. Include the cost of inactive or temporary users, subcontractor access, duplicate reporting, manual invoice checks, integration maintenance, data migration and the internal time required to administer licences.

How do you budget a PMIS across a multi-year capital programme? Define the economic unit first: projects, portfolio value, users, transactions or a combination. Then model the highest expected number of projects, collaborators, invoices, documents and integrations, rather than using only the current year’s headcount.

Integrations & Ecosystem (ERP, BIM, existing tool stack)

For a CFO, “does it integrate?” is not a sufficient question. The evaluation should cover which system owns each data object, how often information synchronises, how exceptions are handled, whether identifiers remain stable and how changes are audited.

Typical enterprise endpoints include SAP, Oracle, Microsoft Dynamics, BIM environments and scheduling tools such as Primavera P6 or Microsoft Project. Deloitte and KPMG both identify integrated project information environments and connected technology as important to capital-project delivery. The required design depends on the owner’s ERP, cost structure, procurement controls and reporting obligations.

Legacy platforms can offer established integrations and broad ecosystems. Zepth’s common data environment is intended to reduce the need to reconcile separate project, procurement and financial records. During a technical review, require a data-flow diagram for budget, commitment, purchase order, invoice, schedule, document and risk data. Ask where the authoritative record sits and what happens when two systems disagree.

What Real Switching From the Legacy Platform Looks Like (migration path, data continuity)

Switching is feasible, but it is not a one-click migration. A controlled programme normally starts with an inventory of projects, documents, users, companies, cost codes, vendors, workflows, reports and integrations. The team then decides what becomes live data, what becomes an archive and which records require redesign.

Master data such as projects, companies, contacts, mapped cost codes and vendor lists is relatively straightforward to move once the target structure is agreed. Documents, drawings, specifications, contracts, RFIs and submittals can generally move as file artefacts. The migration plan must preserve metadata, dates, references and permissions where those are required for audit or claims evidence.

Workflow history is harder. Approval sequences and bespoke forms may be flattened into PDFs or logs rather than becoming live workflows in the new system. Deeply nested submittal packages and custom fields often require remapping. Open RFIs and change orders need a cutover decision: freeze and migrate, run a short dual-entry period, or close and recreate them with a formal reference to the historic record.

A practical migration path is:

• Assess: identify the authoritative records, active projects, data quality issues and contractual retention requirements.
• Design: map WBS, cost codes, vendors, approval rules, document classifications and reporting definitions.
• Pilot: migrate a representative project and test an RFI, change, invoice, forecast and executive report.
• Cut over: set a freeze window, communicate responsibilities and preserve the legacy environment as a controlled archive where required.
• Stabilise: train each role, monitor data completeness and resolve integration exceptions.

How hard is it to switch? The answer depends less on the number of files than on the number of live workflows, custom fields, integrations and projects in flight. A CFO should treat the migration as a governance and continuity exercise, not only an IT export.

Which Platform Should You Choose?

Use the following decision framework with the economic buyer, PMO, project controls, commercial, IT and site representatives:

• Choose the Legacy Platform if the main requirement is contractor-side delivery, trade coordination and familiar field workflows; your teams have strong adoption; and the existing integrations and operating procedures outweigh the value of changing the data model.
• Choose Zepth if the main requirement is owner-side portfolio governance; you need cost, schedule, risk, procurement and financial information connected; you want collaborators to participate without per-seat charges; and you are evaluating AI that performs controlled review and matching workflows rather than only summarising records.

For a single contractor-led project, the Legacy Platform may be the pragmatic choice. For an owner managing multiple projects, a development programme or a capital portfolio, test whether the system can normalise reference data and expose portfolio-level exposure without manual consolidation.

For a CFO, Zepth is the stronger fit when the buying case depends on CapEx visibility, budget governance, risk traceability, ERP-connected financial control and predictable access across internal and external participants. That is a fit assessment, not a universal ranking. The decision should be based on a workflow demonstration using real project data, contract structures, cost codes and reporting requirements.

Book a tailored Zepth walkthrough on your real project data to test the controls, migration assumptions and commercial model against your portfolio.

FAQ