Construction company software: sites, crews, measurements, costs
Author:
Paweł Matusiak
·
The site manager on WhatsApp, the estimate in Excel, hours on paper. Construction software shows who is on which site, what left the store and whether the job is still in budget — before profit “evaporates” on stage three.
Small and mid-size construction does not die on the wall — it dies on information. The crew does not know today’s scope. The office does not know how many hours went into the job. The client asks for a variation and progress photos live on the foreman’s private phone. Construction software puts jobs, crews, materials and costs in one panel. WhatsApp stays for “bring an angle”, not as the only truth about the budget.
Typical margin leaks
Profit “evaporates” not when the slab is poured, but on hours written from memory on Friday, on material with no job code, on a scope change by word of mouth. At three sites at once one truth in the owner’s head is not enough. A client who cannot see progress holds the instalment — and suddenly there is no cash for the crew.
- Hours and overtime written down “at the end of the week”.
- Material off the shelf with no job code — then you lack it and buy twice.
- Scope changes by word of mouth, no variation, no reprice.
- Several sites at once, and one truth in the owner’s head.
- The client cannot see progress, so they hold the instalment.
- A subcontractor bills a measurement that is not the one your site manager has.
Who this system is for (and what it is not)
A main contractor, a finishing crew, an installer, a small firm with 2–10 jobs in parallel. We do not replace BIM, Autodesk or a full payroll ERP. We join the operation: who, where, at what cost, at which stage. CAD stays where it is. Accounts can get an export. If you want a 3D model and clash detection — that is another product and another budget.
A job file and one board
A job has a client, an address, a stage, a budget, a team, subcontractors and a document list. Stage status does not live in the site manager’s head. The board shows which topics are in budget, which are drifting, which wait on material or a client decision. A second scheme uses the same engine — as in a developer CRM, except here the cost matters, not the flat brochure.
- A job file: client, address, stage, budget, team.
- Crew rotas and time recording (a phone app for the foreman).
- Materials: issues to site, deliveries, leftovers.
- Measurements and reports with photos, a date, optional GPS.
- Cost vs budget: an alert when the job starts to drift.
- A client panel: progress, documents, invoices — fewer “any news” calls.
Time on site — offline, not Excel on Friday
The foreman ticks the crew and hours on a phone. Not every worker needs an account. Basements and plots with no signal need the same approach as the field service app: store locally, sync when the network returns. An hour typed that day is different from “about 9 hours, I forget overtime” on Sunday. Overtime and weekend work should be visible before they blow the budget.
Materials, leftovers and buying the same thing twice
An issue with no job code ends with stock sitting on one site and a Friday-after-4 pm purchase on another. The system will not replace a storeman, but it will show what went to which job, what came back, what is missing for tomorrow’s scope. Leftovers after handover have value — if you know where they sit.
Measurements, photos, variations
A protocol with a photo and a date ends the “that was not there” fight. Measure at the stage, not from memory at the end of the job. A spoken scope change is the dearest feature the system does not have — the variation and the reprice should sit on the job card before the crew moves. We do not promise an import from every estimating format; we import when we can read the file you use.
The client, instalments and KSeF
The client panel shows progress and documents, not your margin and not the fight with the subcontractor. An instalment moves more easily when the stage and the protocol are visible. Invoices between VAT payers from 2026 — KSeF per ksef.podatki.gov.pl: 1 February 2026 when 2024 sales exceed PLN 200 million (including VAT), 1 April 2026 for the rest. B2C invoices optional. Often the invoice stays in the accounts tool and the site system passes lines and a stage number. When the panel issues — KSeF in an app. We do not interpret SAF-T or tills here — that is the accountant.
Subcontractors without a view of your margin
A separate login, only their scope and their reports. They do not see your budget or other crews. Same role idea as in a workshop: the mechanic need not see the parts margin.
Construction SaaS or a custom panel
Site packages exist. They are often heavy, priced for a large scheme or in English. Custom when you have your own measurement flow, several small jobs and do not want to pay for a seat the crew will not open. Criteria: off-the-shelf or custom.
- One pilot job and the foreman’s time recording.
- Materials and measurements once the hours no longer lie.
- A client panel and variations when the inside is true.
- A second job and subcontractors — when the first did not go back to WhatsApp.
If this month “kind of added up” in Excel again — describe parallel site count and whether hours, materials or the client hurt more. The MVP is usually one pilot job and time recording. The rest after the first month of numbers that are true.
A week board, not a 400-row Gantt
A small builder does not need PMP. They need an answer: who is on which site this week and whether Wednesday’s scope has material. A week board with a crew drag is enough to start. Gantt and dependencies (“plaster after first fix”) come when someone actually uses them. Most firms that bought a heavy schedule go back to a sheet on the cabin wall — because updating 400 rows takes longer than the plaster.
Weather, a delivery and illness break the plan. The system should let you move a day and leave a trace, not pretend Monday’s plan survived until Friday. The client panel shows the stage, not every hour of slip — otherwise you get 15 calls about rain.
Site data security and private phones
Progress photos on the foreman’s private phone leave with them. A protocol in the app sits on the company server, with a role and a backup. That is not “crew surveillance”. It is the only way a scope dispute does not depend on someone who no longer picks up. GPS on a photo is an option when the plot is large and you need to know which building — not tracking the trip to the shop.
A budget you see mid-month, not after the cost invoice
Labour cost from hours and material cost from issues give a picture before accounts collect supplier invoices. That does not replace bookkeeping. It gives an alert: topic X has passed 80% of budget and the stage is half done. Then you talk about a variation or a cut, not after handover. An alert without clean hours and issues is a guess — that is why those two pieces are in the MVP and a pretty chart comes later.
A lump-sum subcontractor and an hourly crew on the same topic must meet in the report. Otherwise “it kind of added up” means nobody knows which contract is eating profit. The system will not decide for you. It will show which contract the hole sits on.
Stage handovers, defects and warranty after completion
A stage handover with photos and a defect list is cheaper than a final handover from memory. A defect has a location, a fix date and an owner. After the job that list should not die in a PDF on a drive — it stays for warranty. The client ticks or raises in the panel; the crew gets a fix job as in field service. We do not build a full helpdesk on day one. We build a defect card that does not vanish between WhatsApp and the notary handover.
Warranty on labour and on material have different dates. Mixing them ends in a free fix you should not do, or a refusal you cannot defend. The job card holds both.
Plant, hire and travel — when they start eating the budget
A lift hired for three days and brought twice because nobody knew it sat on the other site is a classic leak. A thin plant register (what, where, until when) is enough before you buy a full fleet module. Crew travel and lodgings on an out-of-town job should also sit in the topic cost, not in the site manager’s private receipts. At the start an “extra cost” field with a category; full fleet records — when van and machine count justify it.
A generation change and the owner who is the only database
In many builders, margin and variation truth sit in the owner’s head. Illness, leave or succession ends with nobody knowing what the client was promised. The system is a fallback: the job card, variations, measurements and hours stay when the owner does not pick up. That argument is stronger than “digital transformation”. We still start with one job, not a lecture about the cloud.
Hours the same day and offline on a plot with no signal
An hour typed from memory on Friday is a different number than an hour ticked on site. The foreman marks the crew on a phone; not every worker needs an account. Basements and plots need the same offline-first as the field service app: store locally, sync when the network returns. Overtime and weekend work should be visible before they blow the budget. An export to payroll stays — we do not build full pay on day one.
If after a month of pilot the hours still arrive from memory, we do not switch on the client panel. First the phone entry must be faster than paper. The system will not replace the site manager. It takes counting out of their head. A week board (who is on which site, whether Wednesday has material) is enough; a 400-row Gantt goes back to the cabin wall because updating it takes longer than the plaster.
Material with a job code, leftovers and buying the same thing twice
An issue with no job code ends with stock on one scheme and a Friday-after-4 pm purchase on another. The system will not replace a storeman. It will show what went out, what came back, what is missing for tomorrow’s scope. Leftovers after handover have value if you know where they sit. A lift brought twice because it sat on the other site is the same leak in plant form — a thin register (what, where, until when) before you buy a fleet module.
- A variation and a reprice on the card before the crew moves — a spoken change is the dearest feature the system does not have.
- Measure at the stage, with a photo and a date, not from memory at the end of the job.
- A subcontractor sees their scope and reports, not your margin.
- A defect after handover: location, date, owner — the list does not die in a PDF on a drive.
The instalment, the client panel and KSeF on stage invoices
The client panel shows the stage, the protocol and defects, not the fight with the insulation supplier. An instalment moves more easily when progress is visible. Invoices between VAT payers from 2026 — KSeF per ksef.podatki.gov.pl: 1 February 2026 when 2024 sales exceed PLN 200 million (including VAT), 1 April 2026 for the rest. B2C optional. Often the invoice stays in accounts and the site system passes lines and a stage number. We do not interpret SAF-T or tills. Path: KSeF in an app.
Frequently asked questions
- Will the crew have to type on site?
- The foreman: day list, hours, a photo. Not every worker needs an account.
- Offline?
- Yes, for basements and plots with no signal — sync when the network returns. Same idea as the field service app.
- Will this replace estimating software?
- It does not have to. It can hold items and variations. Import from an estimate — if we can read the format you use.
- For subcontractors?
- A separate login, only their scope and their reports. They do not see your margin.
- Is this BIM?
- No. We do not replace a 3D model or trade coordination. We watch people, material and cost.
- Payroll?
- An hours export to the tool you already use. We do not build full payroll on day one.
- How many sites to start?
- One pilot. The engine is the same; the second job comes when the first does not lie.
- KSeF on stage invoices?
- If you issue invoices as VAT payers — the Ministry timetable (1 February / 1 April 2026). The accountant names the document; we wire the panel or a bridge to accounts.
Related service:
Custom software for companies
Describe your project