10T Studios
← All solutions

Solutions

Systems for construction and trades companies

Short answer

A construction or trades company rarely has a problem with contacts. The problem is that the budget, the job, the materials on order, the photos from site and the invoice live in different files and in people's heads, so until a job is finished nobody knows exactly whether it makes money. We build a system in which the budget flows into the job, the job holds materials, subcontractors and stages, and an invoice for a stage is produced from what was actually delivered. You can start with one part, usually the budget or the invoicing.

01From budget to job

In construction the budget is the document everything later derives from, so nothing has to be retyped from it. Items, unit prices and margin are assembled in the system from your price list and from earlier budgets. Every change for the client is a new version, and it is always clear what went out and what changed afterwards.

Once approved, the budget becomes a job. Its items carry over as a plan — how much material, how many hours, what goes through a subcontractor — and actuals are recorded against it as work goes on. That shows the gap between plan and actual during the build, not after the last invoice.

If you already use specialised budgeting software, we do not have to replace it. We can connect to the export it offers, and the job picks up from the approved budget. How smoothly depends on the form in which your program can output data, and we check that in the audit.

  • 01A budget from the price list with items, unit prices and margin, with versions for the client.
  • 02A job with a plan for materials, hours and subcontracts, and actuals recorded against it as the work goes.
  • 03Materials ordered, delivered and used on a specific job, not just in one shared stock.
  • 04Subcontractors with an agreed scope, price and work status.

02Site diary, photos and crew planning

A site diary in the system is an entry the foreman makes from a phone on site: who was there, what was done, what was delivered, what was found. Photos attach directly to the job and the day, so a month later nobody has to work out whether the photo of the cellar was from Tuesday or Thursday. Problems discovered during the work (a wall in a different state than expected) are recorded with a photo before anyone argues about them.

This is not the official construction diary if regulations require one for the building in question. That one is kept as the regulations say, and ours can be the source it is copied from. What exactly is needed for your build is something the designer or the site supervisor will tell you, not software.

Crew planning is a calendar of people and jobs that changes almost every week: a delivery was late, the weather, someone is ill. The system shows who is where and who is free, and flags clashes. It does not decide for you, but it will not let you discover it on site in the morning.

03Invoicing by stage and warranty work

A job can be split into stages, each a sum or a percentage of the whole. When the foreman marks a stage as handed over, the system prepares the basis for an invoice from what was really delivered in that stage, including any extra work. You then issue the invoice in your accounting program, or the connected system issues it. Advances, retentions and similar terms can be recorded on the job; how they are posted and treated for tax is for your accountant.

After handover come warranty repairs. Each job remembers the handover date, the end of the warranty and what was used, so when a customer calls you know within a minute whether it is a warranty case and which crew to send. A warranty repair is kept as a small job linked to the original, so it is visible what it costs you.

04When you do not need this

If you do a few jobs a year, mostly yourself or with one crew, a spreadsheet, photos on your phone and an accounting program are enough. A system starts to make sense once several jobs run at once, several people work on each, and you lose track of what is running where and what should already be invoiced.

Even then you can try ready-made software for builders first: some of it is adequate if your process is not unusual. Custom is worth it when your budgets, stages or way of invoicing cannot be fitted into a ready-made program without workarounds, or when everything has to reconcile with your accounting and stock.

05Price and how to start

A first usable version for a small or mid-sized company usually falls in the €2,000 to €10,000 range. What drives it is the number of parts you want at once (budgets, jobs, diary, invoicing), the connection to accounting and an existing budgeting program, and whether staff have to work without a signal.

We start with a fixed-price audit: a few days watching how a job moves through your company from quote to warranty, ending in a document on what to build and in what order. The first part people actually use is usually ready within a few weeks, and the rest is added piece by piece. The code and the data stay with you.

Frequently asked

Do we have to stop using our budgeting program?
No. If it can output data in a usable form, we connect jobs to it. If not, budgets can be made in the new system or loaded by hand. We check this in the audit before anything is decided.
Will it work on site with no signal?
Diary entries, materials and photos can be recorded offline and are sent once the signal returns. It is a requirement to state at the start, because it affects how the system is built.
Can the system issue the invoice itself?
It can prepare the basis from a handed-over stage and, as you choose, send the data to your accounting program or issue the invoice itself. How an advance, a retention or a reverse charge is posted is decided by your accountant; the system only records it on the job.
What if we also do service calls and small repairs?
A service job is a smaller kind of job in the system, with its own flow and invoicing basis. A similar case is described on the page about solutions for service companies.

Where next