EXECUTIVE CASE STUDY • CONSTRUCTION • SITE COORDINATION
How a concrete contractor measures real production time per site instead of estimating it
On a construction site, the difference between the planned duration and the real one is where the margin goes. PavMar Beton coordinates its sites through a Gantt task module in a self-hosted CRM, with photographic evidence and reports attached to the project record itself.
- Site coordination on a Gantt plan
- Real production times measured, not estimated
- Evidence and reports attached to the project
The contractor’s challenge
Plans on paper, progress in conversation, evidence in phones
Work was planned on a schedule, but progress was reported verbally and photographs of completed stages stayed on the foreman’s phone. Nothing connected the plan, the actual timing and the proof that work was done.
When a client queries a stage weeks later, or when a job turns out to have taken half again as long as quoted, the answer has to be reconstructed from memory and camera rolls.
Planned, then guessed
Durations were estimated from experience, and evidence of completed work lived outside any system.
Planned, then measured
Tasks carry real start and finish times, and photographs or reports attach to the project record as the work happens.
Client testimony
“Site coordination runs in detail through the Gantt task module. We monitor real production times precisely and attach evidence or reports directly to the project record.”
Gantt tasks with evidence on the project record
Each site is a project with tasks on a Gantt plan, with dependencies and owners, so coordination happens against a shared plan rather than a daily phone call.
Because actual times are recorded against the plan, the company can compare quoted duration with real production time per site. Evidence — photographs, reports, documents — attaches directly to the project record.
Modules in use
- Gantt task module — site plans with dependencies, durations and owners.
- Time tracking — real production time recorded against the plan.
- Evidence attachment — photographs and reports stored on the project record.
- Project records — one record per site, with its full history.
The modules are licensed separately, so an installation carries only what it uses.
See the pricingWhat changed on site
Quoting improved because the company now knows what the last ten similar jobs actually took. Client queries are answered from the record, with evidence attached, instead of from memory.
One-time licence
The platform and the active modules are paid once, not every month, for as long as the company uses them.
Unlimited users
People are added without a per-seat cost, so the licence never decides the size of the team.
Own infrastructure
The installation and the database sit on the company’s own server, so the data stays where the company put it.
Related case studies
Other companies running on Zarina CRM
Sixteen deployments across eleven industries, each with the company named and the workflow described, so you can find one close to your own.
STRATEGIC PARTNERSHIP • ENTERPRISE
Move your operation onto a platform you own
The editions, the modules and the one-time licence are the same ones used in this deployment. The installation sits on your server, the users are unlimited, and the licence is paid once.
- Installed on your own server
- Unlimited users
- One-time payment