The estimate remains separate from costs
Approved items and supplier invoices are compared manually, often using categories created at different times.
ZENCANTIERI · CONSTRUCTION PROJECT COST CONTROL
ZenCantieri: Approved estimate, recorded costs, visible variances.
For construction and engineering businesses managing multiple projects that need a clearer view of project cost control.
ZenCantieri connects the approved budget baseline with supplier invoices to show where actual costs differ from approved amounts, by construction project and category.
Alpha · assisted demo using synthetic data. Scope, data and integrations are defined before launch.
- Approved, versioned baseline
- Costs by construction project and category
- Dashboard and budget status
WHEN COST CONTROL REQUIRES RECONSTRUCTION
The cost data is there. The connection to what was approved is missing.
When estimates, revisions and invoices follow different paths, finding the source of a variance requires manual comparisons across categories that are not always consistent.
Revisions obscure the reference point
Without an authoritative baseline, it becomes difficult to distinguish the approved budget from subsequent variations.
Variances emerge too late
Identifying which construction project or category needs attention requires reconstructing figures from different tools.
ONE WORKFLOW, FIVE STEPS
From the baseline to portfolio priorities.
ZenCantieri creates a clear line between the approved budget and recorded costs. The pilot project starts with the process and the data actually available.
-
Structure the operational context
Organise clients, suppliers, categories, units of measure and the construction project’s financial details.
-
Approve the baseline
Prepare an itemised estimate and approve an immutable revision as the current financial reference.
-
Allocate recorded costs
Allocate supplier invoice amounts excluding VAT across categories and, where useful, baseline items.
-
Review the variance
Compare budget, actual costs, remaining budget and utilisation by construction project and category as at the selected date.
-
Prioritise the portfolio
Dashboards and financial statuses highlight construction projects that are over budget, need attention or include unbudgeted costs.
Alpha · pilot project
Assess a pilot project
Let’s review the workflow against your process.
A guided demo helps compare what is already available with the data, integrations and responsibilities in your context.
INSIDE ZENCANTIERI
The estimate and costs remain in the same context.
Real screens from the isolated Alpha environment: all names, amounts and content shown are synthetic data.
Search, filters and statuses make projects requiring further review easy to identify.
An approved revision becomes immutable, while subsequent variations retain the previous reference.
The recorded amount excluding VAT is allocated by category and can be linked to baseline items.
WHAT CHANGES IN DAY-TO-DAY COST CONTROL
From an individual cost to a clear priority.
The demo tests how the baseline, invoices and variances can create a shared financial overview for your process.
An authoritative budget
The approved baseline remains separate from subsequent revisions and available for reference.
Costs in context
Allocations connect the recorded amount excluding VAT to the construction project, category and financial item.
Clear priorities
Statuses and thresholds help identify the construction projects and categories requiring further review.
From detail to portfolio
The same financial logic can be reviewed for an individual construction project or across the project portfolio.
CLEAR SCOPE
We show the Alpha core and define the pilot before adding integrations.
ZenCantieri is not presented as a complete construction ERP. Data, roles, security, external connections and service arrangements are assessed before launch.
ALREADY AVAILABLE IN THE DEMO
- Clients, suppliers, construction projects, categories and units of measure
- Estimates, revisions and an immutable approved baseline
- Supplier invoices and their status: paid or outstanding
- Allocation of amounts excluding VAT by category and item
- Budget, actual costs, remaining budget, variances and a configurable dashboard
TO ASSESS TOGETHER
- Pilot project scope and success criteria
- Import, quality and ownership of initial data
- Delivery note workflow and document archive to be included
- Live integration with Mexal or other management systems
- Hosting, authentication, roles, backups, retention and support
QUESTIONS ABOUT ZENCANTIERI
Clear answers before the pilot project.
These answers distinguish features that can already be demonstrated from decisions that depend on your process, data and business environment.
Have another question?Is ZenCantieri already available?
It is available as an Alpha and an assisted pilot project. Before launch, we define the construction projects, users, data, features to validate and success criteria.
How are actual costs calculated?
Actual costs are the sum of the net-of-VAT invoice allocations recorded by the selected date. Draft and cancelled invoices are excluded; whether an invoice is paid or outstanding does not change its cost.
How does it manage estimate revisions?
Each construction project has a current approved baseline. Approval makes the revision immutable; a subsequent variation is created as a new revision, while the previous one remains in the history.
Does it calculate the construction project’s actual margin?
No. It shows the approved budget, recorded actual costs, remaining budget and variance. It does not manage revenue, work progress statements or a complete profit and loss account, so it does not calculate the project’s actual margin.
Does it replace our management system or already connect to Mexal?
No. The validated core covers construction project cost control. The demo environment only uses a local simulation; a live connection to Mexal or other systems must be assessed and implemented within the pilot project.
How is the demo managed?
The demo uses an isolated environment and entirely synthetic data. Hosting, authentication, roles, backups, retention and integrations must be defined and verified before any operational data is processed.