Most firms run on fifteen apps stitched together with WhatsApp, spreadsheets and goodwill. Unibuild is one platform, one login, one number everyone in the firm trusts. It is bespoke, shaped to the way your firm works, and your staff use an app under your own name.
Two minutes, and no rate card to decode. Unlimited users, so the answer does not move when you take on a team of twelve.
One login in place of the timesheet app, the spreadsheet, the permit pad and the shared drive. Thirty-plus modules, seventeen of which use AI on a real job, from compliance and paperwork through to cost and reporting. What it does inside them is shown in the demo, and the families it runs in are on the AI page. AI document review checks RAMS, estimates, quotations and tenders before they go out. Anything you need is built for you, inside the monthly fee.
Use the lot or use the four you actually need. Either way the records sit in the same database and the people log in once, so a figure entered on site is the figure the office invoices against. The nine below are where most firms start.
Who is on which site, who clocked in, who is off sick, who is on holiday, who has a ticket expiring on the 19th. One roster, with a timesheet inside it.
RAMS, toolbox talks, inductions, near-misses, RIDDOR. The bits that win you the next tender if you can produce them, and lose you a job if you cannot.
The plan against the actual. Site diaries, day works, drawings, variations and the photograph trail behind every line. What the contracts manager walks through every Monday.
Applications for payment, retention, aged debt and a live cost position. The commercial side of the business, running on one ledger since 2016.
Three pages, scoped to one company. They read the order you actually issued, raise their invoice against it, and watch it move from pending to approved to paid.
The register of what you own and what you hire. PAT and LOLER dates, serial numbers, bin locations and where every tower is standing this week.
From a measure to a written quote your client signs. Reusable line items, mark-up rules, tender packs and the gross margin on the page before you send it.
The operational record stops living in a group chat. Requests, sign-offs and photographs sit against the project, and the decisions that hold work up arrive in one queue.
Nobody types anything into these. The management picture is assembled from work your team recorded while doing their own jobs, which is why it is current to the hour and why one person's absence does not stop the numbers appearing.
Everyone on the firm logs in to the same Unibuild, but the first screen is different depending on what they came to do. The director sees the position. The site manager sees today's gate. The accounts clerk sees what is due. Same records, six different sets of pages, granted per person.
The first thing a director sees is the job position as it stands today rather than at the final account. Cost to date, committed spend, aged debt by the manager responsible, and what is waiting on a decision. Click any total and you are looking at the timesheet, the order or the valuation it came from.
The panel above illustrates the kind of line each person opens. It is drawn, not a screenshot of a customer's data.
Every step below is a thing live customers do on an ordinary working day. It is a composite rather than one firm's diary, because we describe a client's business only in the shape they have agreed to. What it shows is the mechanism: one tap, one record, and nothing typed a second time.
The operative opens your app and scans a laminated poster on the site board. A photograph is taken, the location is checked within 100 metres of the site and recorded, and the clock-in time is fixed at the scan rather than read from the handset. The RAMS for that trade is signed on the same screen.
Taken where they were taken, dated, attached to the job. They sit as pending rather than published, so the office decides what the client sees. Nothing reaches a customer automatically.
Raised at the merchant's counter against the job. A named approver sees the project, the supplier and the value, and answers. The order number is issued only on approval, so nothing is bought without one.
The picker chooses the serial number going out and the bin it comes from, and cannot over-allocate. The receiver signs on the phone, the plant reassigns to that job and the stock moves itself. There is no posting step to forget.
Signed at the point of delivery by the person it was delivered to, filed against the site, the trade and the operative, with the date it actually happened. No sheet going round on a clipboard and no signature added later by somebody who was not there.
Raised by the subcontractor in their own portal against one of their own orders, so the project comes from the order rather than being typed. The queue shows the order value beside everything already invoiced against it, which is how a second invoice for the same work gets caught before it is paid.
Trades on site and how many of each, the weather, and what happened. About two minutes. In eighteen months, when somebody argues about a delay, this is the contemporaneous record that answers it, and it exists because it was never assembled after the fact.
Unibuild is one system on one database, so most of what other platforms have to synchronise is the same record. Where it does reach outside itself, these are the connections in use. The integrations page sets out what each one does.
Where a claim below can be verified, it is stated exactly. Where it cannot, it is not stated at all. If a procurement questionnaire needs any of this in writing, ask and you get it in writing rather than as a web page.
Held in London. Data does not leave the United Kingdom. We do not use third-party trackers, ad-tech or analytics brokers.
London · UK onlyEncrypted when stored and when sent. Backup and key management arrangements are set out in the agreement, where they can be held to, rather than summarised here.
Encrypted throughoutSingle sign-on with Microsoft 365 and Google Workspace, with MFA available on top. Permissions are granted per person, page by page, rather than inherited from a role, and every entry carries an audit trail.
SSO · MFA · per personGDPR by default, ICO registered, Cyber Essentials Plus, ISO 27001 in progress. Sub-processors listed in the DPA, not hidden in the small print.
GDPR · ICO · CE+Who did what and when, on every approval, sign-off and change, and nothing is overwritten. Permits, RAMS and toolbox talks are locked when submitted and need a new version to amend. 275 of 295 tables carry audit columns.
Nothing overwrittenLondon office, UK working hours, phone, email and WhatsApp. Answered by a person who has read your account first. No tier one queue.
London · UK hoursYour records are yours. Export everything as CSV, XML, JSON and PDF, one click, any time. Leave and we hand back a tidy bundle within five working days.
Export · 1 clickSame release for every customer. No premium tier holding the good features back. The field app is version gated on the server, so adding a module does not mean updating every handset on a coordinated date.
All customers, same buildYou go live in stages, worst pain first, rather than on one switchover date. Most firms go live in about two weeks. The shape below is how the featured deployments were actually built, and the programme with dates on it is agreed after scoping. How implementation works sets it out in full.
Same platform, same records. How people reach it, what it produces, and what it connects to.
The full list is at /faqs, and every published figure is on the facts page.
UK-built · CDM · CIS · MTD