ERP software as a driver of growth: when is it time to adopt one?

Growth stalls on management, not on lack of work

A construction company rarely stops growing because there is no work. More often the owner can no longer keep up. Information about what happens on site passes through one person, and as long as they can visit every site, that works. Once there are more sites than days in the week, the evenings go into compiling invoices and making phone calls.

To a small construction company, ERP sounds big, expensive and difficult. In practice a construction ERP is a phone app for the site and a browser view for the office. Hours, quotes, extra work, photos and invoices sit in one place instead of five different tools.

This article works out when a system pays for itself, which signs show it is needed, and how to roll it out without stopping the sites.

What the system actually replaces

A small construction company usually already has a system. It is just scattered:

• hours on slips, in a notebook or as WhatsApp messages on Friday
• quotes in Excel templates, each a copy of the last one
• extra work in phone calls and chat threads
• photos on workers' phones
• receipts in an envelope or the glovebox
• invoices in an invoicing program, typed in by hand from all of the above.

Each of these works on its own. The problem is at the joins: the person invoicing asks for the hours, the supervisor asks for the photo, the owner asks whether that extra work was agreed. The benefit of an ERP is not that any of these is done more elegantly. It comes from information being recorded once and flowing from the quote to the project, from the project to the invoice, and from the invoice to the accounts.

What breaks at each size

On your own or with one other. Everything fits in your head, but quotes and invoicing eat evenings. The benefit comes from quoting, recording hours against the project, and having photos and extra work under the site instead of in a camera roll. The office is the owner, so every evening saved is their own.

Three to five people. The first pain point. The owner is no longer on every site, and information starts to travel as stories. Invoicing slips because the details have to be asked for, and the first extra work goes unbilled.

Six to ten. Site management separates out. Now there are people who need information but cannot reach it, because it is in the owner's head. Each supervisor builds their own way of working, and comparing the profitability of sites becomes impossible.

More than ten. Subcontractors, site access control, construction reports and tax numbers come into play. Without a shared system, compiling these every month is a job of its own.

Something different breaks at each stage. So rather than asking "when should we get a system", the better question is what in the company does not scale right now.

Three signs you have hit the limit

Invoicing is late. An invoice needs to know what was done and how much. When the owner is not on site, that has to be asked for, and the asking moves to the evening. Cash flow slows just when growth ties up money, and some work never gets invoiced at all.

You cannot know a project's status without a call. Can you say right now how many hours have gone into the current contract and how much of the budget is left? If not, the information is in people rather than in the company. It disappears with holidays, sick leave and resignations.

The same job is done in different ways. One supervisor writes hours in a notebook, another on a phone, a third remembers. While the sites go well, it does not matter. When you need to find out which site was more profitable and why, there is nothing to compare.

The numbers: when the system pays for itself

Take a six-person construction company with about ten sites a year and turnover of around 700,000 euros.

What the system costs. The FiSAS Builder plan includes four users for 119 euros a month, and two extra users cost 10 euros a month each. That is 139 euros a month, about 1,670 euros a year excluding VAT on annual billing.

Unbilled extra work. If one 400-euro extra job goes unbilled on every second site, that is 2,000 euros a year. This is a cautious estimate. Many owners recognise sites where more than one extra job went unbilled.

Unrecorded hours. If each person leaves half an hour a week unrecorded and the hourly rate is 55 euros, that is around 7,400 euros a year of unbilled or misallocated work for six people. On fixed-price contracts the amount is not direct invoicing, but it shows up in the pricing of the next quote.

The owner's evenings. If compiling invoices, chasing hours and copying quotes takes five hours a week and the system halves that, the saving is about 110 hours a year. That time usually comes out of selling.

Pricing accuracy. When actual hours are known by work phase, the next quote is priced on data rather than on feel. One percentage point better margin on 700,000 euros of turnover is 7,000 euros a year.

A single billed extra job per quarter covers the system's annual cost. The rest is margin, time and more accurate quotes. For a ten-person company, the Master plan costs 199 euros a month for ten users, and the same calculations are proportionally larger.

Where to start

It is not worth switching everything on at once. An order that works for most construction companies:

1. Hours against the project by phone. The biggest cost item and the basis for everything else. Recording takes a worker half a minute, and the owner sees the hours straight away.
2. Extra work. Recorded when it is agreed, with a price and the client's approval.
3. Quotes and invoicing. An accepted quote becomes a project, and approved hours and extra work move to the invoice.
4. Photos, site diary and communication. Useful from day one, but their value often only shows when something goes wrong.

The first step usually works within a week when it starts on one site with time to learn. The next one is added once the previous step is a habit rather than an experiment. In practice a small construction company is fully up and running in a few weeks, not months.

Two mistakes sink a rollout most often. The first is leaving the old way as an option: if hours can be recorded either on the phone or in the notebook, they go in the notebook. The second is starting on the hardest site, where nobody has time to learn anything new.

When a system does not solve the problem

A system does not bring in work. If the problem is sales, faster invoicing will not help.

Nor does a system fix pricing on its own. If contracts are priced too low, faster invoicing at first only means the loss shows sooner. That is still useful, because only actual figures tell you what to change in your pricing.

And if the crew has never recorded hours anywhere, the first job is to agree why they are recorded and what is done with them. When recording is half a minute on a phone and something follows from it, such as faster pay or extra work getting billed, the habit usually changes quickly.

Three questions when choosing a system

Feature lists look the same everywhere. These three questions tell you more.

What does a worker have to do differently? Ask to see time recording on a phone from the worker's point of view, not the office's. If it takes more than a minute, it will not get done.

Does it work on site? Poor signal, cold fingers and bright light. Recording has to work without a connection and sync when the connection returns.

Where does the information end up? Invoices need to reach the accounts without retyping. Otherwise the system adds work in the office instead of removing it.

It is also worth asking yourself what problem you are solving. When there is a one-sentence answer, such as "extra work goes unbilled" or "invoicing is two weeks late", you also know where to start and how to tell whether it worked.

How this works in FiSAS

FiSAS is built for small and medium-sized construction companies, and the plans are tiered along the sizes described above:

• Maker, €69/month, 1 user: quoting, projects, time tracking, tasks and work orders, documentation and subcontractors. For working on your own or with one other.
• Builder, €119/month, 4 users: adds invoicing, measuring from images and quantity take-off, scheduling, communication, reports and accounting integrations. For a growing team.
• Master, €199/month, 10 users: adds expenses and purchase invoices, inventory, TR safety measurement, site access control and construction reports to the Tax Administration. For companies of 10–20 people.

Prices exclude VAT on annual billing, and extra users can be added as needed. Invoices transfer to Netvisor, Procountor or Fennoa, so the accountant gets them in the same place as before. The subscription can be cancelled at any time.

Workers record hours on their phone even without a connection, photos and observations are stored straight on the project, and supervisors see them immediately. An accepted quote becomes a project whose budget is compared with actual hours and costs, and approved hours and extra work move to the invoice.

Test your own situation

Ask yourself: if you were unreachable for two weeks, what would stop in the company? Invoicing, quotes, or knowing what is happening on site? The answer tells you what does not scale, and that is also where to start.

FiSAS can be tried free for 14 days without payment details. One site and one thing, such as recording hours by phone, is enough for the trial. Two weeks later you will know how many hours used to go unrecorded.