Skip to content
HMRC CIS return month ending 5 Aug · due Wed 19 Aug 12 days
CIS return due Wed 19 Aug 12 daysCDM 2015, RIDDOR and the compliance registers, built in rather than bolted onUnlimited users, every module, £0 per helmet30+ modules, one login, and the 15-app stack retiredQuickBooks, OneDrive, WhatsApp and email, wired into the jobGlove-friendly field app, QR-first, timed by the server not the phoneExpired subcontractor insurance drops a firm out of approved status overnightFree migration from whatever you run todayUK built, UK support desk, UK hours30-day free trial, no card, no obligation
Start the 30-day trial
Book a demo→
Integrations

Works with the systems
you already run.

Most contracting software promises integration and delivers a spreadsheet. Unibuild is built as one system, so there is less to join up in the first place. Where it does reach outside itself, this page tells you exactly how far each connection goes, including the one that is still a pilot and the ones that do not exist.

Ask about your systems → See the platform
587 invoices forwarded automatically 1,783 emails logged 81 API endpoints in production one pilot, named as one
The honest maturity table

Every connection, and how
far it actually goes.

A logo wall tells you nothing. This tells you what happens, what does not, and which of them we would build for you.

Bookkeeping capture · In daily use
Approved supplier invoices, credit notes and travel orders are emailed to your bookkeeping capture inbox from inside the purchase order record, with the order number, supplier, project and both values already stated in the message body. Each record is flagged as sent so nothing goes twice, and the purchase order list shows a traffic light for what has gone and what is still pending. In the construction deployment, 587 of 711 supplier invoices have been forwarded this way. This is the strongest integration story the platform has, and it deserves more prominence than QuickBooks.
Microsoft OneDrive · In use
One action on the project record creates your standard folder tree in your own Microsoft tenant, uploads your template documents into it, handles large files, retries the ones that fail, then requests a share link and stores it on the job. The template in live use runs to 52 folders and 185 files, including the full operating and maintenance skeleton. What it does not do is synchronise files back into Unibuild. OneDrive is the document store; Unibuild is the record of the work.
Transactional email · In daily use
Every message the platform sends goes through one service on one verified sending domain, and every message is written to a log with the recipient, the subject, the attachment, the exact content and the send result. 1,783 messages logged. When a client says a certificate never arrived, you open the log rather than your sent items.
Push notifications · In daily use
Notifications to named users on registered devices, with a distinct tone per event family and a deep link that opens the approval screen itself rather than the app's home page. 5,478 sent and logged across 112 registered devices. Every one is logged with its recipients, its content and the provider's response.
WhatsApp alerts · Narrow, and deliberately so
Outbound template messages to a list of numbers you maintain, so a near miss or an accident reaches a safety manager who may never open the app. It is not a WhatsApp Business integration and it is not a two way channel. Inbound replies are captured and nothing acts on them. The point is to stop the operational record living in WhatsApp, not to move Unibuild into it.
QuickBooks Online · Pilot, and not currently connected
A working one way push of individual sales invoices: the customer is matched or created, the transaction is posted, and the reference comes back onto the Unibuild record, after which the invoice locks so the two cannot drift apart. It has been proved end to end. In the construction deployment it is not authorised today, one invoice has ever been synced, and the page carries an in progress label written by the developer. We describe it as a pilot because that is what it is.
Weather · Available to the app
A forecast lookup the field app can call. The weather value stored on a site diary is the one the diary author records. We are not going to describe weather as automatically captured, because it is not.
QR generation and geocoding · In daily use
Branded codes generated and cached on the platform with a second provider as automatic fallback, so a reprint costs nothing and looks identical. Punch in coordinates are resolved to a street address for the office view.
Sage, Xero and payroll · Do not exist
There is no Sage connection, no Xero connection, no payroll integration and no payroll export file, not even a comma separated one. If you run Sage or Xero, connecting them is a scoped piece of work on the implementation and we would rather quote it honestly than let you discover the gap after signature.
Why there is less to integrate

The integration you do not
have to buy is the one
between your own systems.

Most contracting firms do not suffer from a lack of software. They suffer from having five pieces of it that do not speak to each other, plus the spreadsheets that exist purely to move information between them.

One database
underneath

Design

Sixty-seven of the platform's tables carry the project reference, so the estimate, the hours, the orders, the deliveries, the photographs, the certificates and the costs are genuinely attached to the same record rather than sitting alongside it.

No sync step to failLive

A proven
API

Built

Eighty-one token authenticated endpoint controllers already carry the mobile app and the client app in daily production. Bespoke connection work builds on a data layer that is proven rather than on a specification.

Not a greenfield projectLive

Everything
logged

Evidence

The email log, the notification log, the sync log with its request and response payloads, and the inbound request log with the user, device and payload. Integration disputes are settled with evidence rather than assertion.

73,351 requests loggedLive

Your systems are
a scope item

Honest

Where a connection does not exist, it is development work we do as part of the engagement rather than a roadmap promise. We would rather price it at the start than imply a checkbox.

Quoted, not promisedScope
For your data protection assessment

The list your DPO will
ask for, published
before they ask.

These are the third parties data can pass through. Nothing else leaves the platform. We will give you the same list in writing, with the contractual terms, for your record of processing activities.

Always

Transactional email providerPush notification providerQR code generationGeocoding for punch locations

Where enabled

Microsoft, for OneDrive storageYour bookkeeping capture serviceWhatsApp messaging providerWeather service

Optional

QuickBooks, where the pilot is switched onThe AI provider, where the AI features are enabled

Never sent

Database credentialsService keysConfiguration filesAny column whose name suggests a password, token or secret
On the AI features specifically

Two narrow features call an external model: a quotation quality check, and a read only assistant that answers questions by querying your own records. Both can simply be switched off, and nothing else in Unibuild depends on them. Where they are enabled, the quotation check sends the quotation including your pricing, and the assistant sends whatever a query returns. Credentials and configuration are excluded and redacted before anything is sent. If that exchange is not acceptable to you, say so and we will turn them off rather than argue about it.

Office desk with paperwork and a laptop
587Supplier invoices forwarded to bookkeeping
1,161Logged emails carrying an attachment
112Registered devices receiving push

Counted in the construction deployment, July 2026.

What we will not claim

Six phrases you will not
find anywhere on this site.

Each of these is a sentence a competitor would write. Each one is false for this platform.

01
Integrates with QuickBooks
Without qualification, no. The accurate phrasing is a one way push of individual sales invoices, at pilot stage, not currently authorised in the live deployment. Overstating this is the fastest way to lose a finance director.
02
Integrates with Sage or Xero
Neither exists anywhere in the code. Not a partial connection, not a beta, nothing. Both are buildable and both would be scoped and priced.
03
Payroll integration
There is no payroll output file at all. What exists is approved hours per person per month, split across normal, time and a half, double time, travel and adjustment, plus a payslip style document. Today somebody reads those and enters them. The hard part is done; the file format is not.
04
SFG20 integration
Unibuild holds your own SFG20 schedule documents against the right asset. It does not pull task lists or revisions from BESA. FM buyers know the difference and will test it.
05
REFCOM integration
The platform produces a REFCOM presented record log book. It does not submit anything to any registration body, and no part of the platform notifies a scheme on your behalf.
06
Automatic retry and delivery confirmation
A failed send is logged with the reason and is visible, and resending is a human action. The email log records that the provider accepted the message, which is not the same as it being delivered, opened or read. We will not describe it as either.

Everything in the maturity table above is running in a live business today. None of these six is.

Questions

The ones a finance director
asks in the first ten minutes.

Does it talk to our accounts package?+
It depends which one, and we will be straight with you. Unibuild sends supplier invoices, credit notes and travel orders into a bookkeeping capture service by email, with the purchase order context attached, and that is live and in daily use. It has a working one way connection into QuickBooks Online for sales invoices, currently at pilot stage and not authorised in the live deployment. There is no Sage or Xero connection today. If you run Sage or Xero, connecting them is a scoped piece of work on the implementation, and we would rather quote it honestly than let you discover the gap after signature.
Is this a proper OneDrive integration or just a link field?+
Both are there, and the difference matters. There is a manual link field for a folder you already have. There is also a real connection to your Microsoft tenant that creates your standard project folder tree, uploads your template documents into it, handles large files and retries the ones that fail, then requests a share link and stores it on the job. What it does not do is synchronise files back into Unibuild. OneDrive is the document store; Unibuild is the record of the work.
We already use WhatsApp for everything. Does Unibuild replace that?+
No, and we would not claim it does. Unibuild sends WhatsApp alerts through approved message templates to a list of numbers you maintain, for things like accidents, near misses and punch in events. It captures replies and nothing acts on them. There is no WhatsApp inbox in the portal and no conversation thread. The point is to stop the operational record living in WhatsApp, not to move Unibuild into it. Photographs, sign offs, diaries and reports belong on the job record where they can be found in two years.
Our engineers will not use anything complicated. Is any of this their problem?+
None of it. An engineer never sees an integration. They fill in the record, sign on the screen and move on. The certificate is produced, the notification reaches the office, the invoice paperwork reaches the bookkeeper, and every one of those steps is logged behind the scenes.
What happens to our existing folder structure?+
Your folder structure becomes the template that gets replicated for every new project, so you are not adopting somebody else's filing. If you would rather Unibuild did not touch your folders at all, paste your existing project folder link onto the project record and it will hold that as the link from the job to the documents. If you are on a different platform entirely, the connector is a defined piece of development rather than an unknown, and it would be scoped and priced before you commit.
If an integration fails, how would we know?+
Today a failed send returns an error to the person at the time and is written to the log, and the purchase order list shows a traffic light for what has gone across and what has not. There is no background monitoring, so a systematic failure would be noticed by somebody looking at those indicators rather than by an alert. Building failure alerting is a small piece of work and it is on the list of things worth doing before a client with high volume goes live.
Next step

Bring us the list of
systems you already run.

The promise No integration is claimed on this site that we cannot demonstrate Including the ones that are pilots
Ask about your systems → How implementation works
Phone · UK hours
+44 7587 557546
Email
[email protected]
The whole thing
Platform overview
Demo calendar
unibuild.co.uk/demo