[ FOR FACILITIES AND PROPERTY ]

Give every fault a history.

Somebody already attends every fault a tenant reports. The problem is that the attendance is the whole record: the same air handling unit has been fixed four times this year and each visit looked like the first one. Describe how your team runs and you get the tables, the forms, a phone app for the engineers and the reports, already filled with properties and assets like yours.

NO CARDNO REAL DATA NEEDED
[ THE PROBLEM ]

Every tool you tried made you work its way.

Somebody had to retype every name and certificate before it did anything at all, and that job never got finished. The big suite was too rigid, the build-it-yourself tools were too empty, and you went back to the spreadsheet that at least already had everything in it.

Gobuso starts from the other end. Your files first. Then a plan in plain English you can change. Then working software, the same day.

0
staff to retype before it works
4
questions, then it builds
1
afternoon from your files to working software
1
set of data under every tool you add
[ START FROM ONE OF THESE ]

Pick the one that costs you the most. It builds it now.

No sign-up and no data of yours. It designs the tables, builds the app and fills it with a company that looks like yours.

[ HOW IT RUNS ]

From one sentence to the number you needed.

Five moments, in order. Nothing here is a mock-up of a different product: it is the same builder the button above opens.

STAGE 01

One sentence, typed by the facilities manager.

[ WHAT DOES YOUR COMPANY DO, AND WHAT DO YOU NEED TO FIX? ]

We look after 20 commercial properties with a team of 12. A tenant reports a fault and somebody attends and fixes it. The same air handling unit has been fixed four times this year. Nothing has a history behind it.

FacilitiesHVACCleaningSecurity
Build it →
No form to fillShe describes the unit she keeps paying to fix. No template to pick.
Four questions, then it buildsThe trade chip is the only thing she taps. The rest it works out.
STAGE 02

It says what it will build, then opens it.

THE DRAFT · 4 TABLES · ~40 SECONDS
Repairs
THE RECORD · 2 FORMS
Properties
so an access code is stored once, not on every repair
Assets
so one unit keeps one history, whoever attends it
Contractors and their insurance dates, set up for you and ready to edit
REPAIRS · 4,760 RECORDS
Repairs
PropertyAssetRaisedClosed
Kestrel HouseAHU-218 SepYes
Mallow CourtLift 117 SepYes
Kestrel HouseAHU-212 SepNo
Weir BuildingsBoiler 311 SepYes
Plain English firstNothing exists yet. Type contractors sign in at the property and it rebuilds.
Separate on purposeAssets stand on their own, so one unit keeps one history across years.
STAGE 03

The engineer closes it on the roof, with the tenant there.

REPAIRS / KESTREL HOUSE
Close the repair
Grainne, on a phone, on the roof of Kestrel House · 11:26
Asset
AHU-2, fourth floor
Fault found
Drive belt gone again
Parts fitted
1 × drive belt
Signed by
D. Whelan, tenant
Tenant signature
→ REPAIR CLOSED · FOURTH ON THIS ASSET
Her form, not everyone’sFour fields. The office raised the fault on a different form.
It counts as it is signedThe fourth visit to this unit says so on the screen, not at year end.
STAGE 04

Every repair lands on the asset that had it.

ASSETS / AHU-2 · 2026-09-18
AHU-2, Kestrel House

Every repair on this asset

4 THIS YEAR
18 Sep · Drive beltClosed
12 Sep · Drive beltOpen
06 Jun · Drive beltClosed
21 Feb · BearingClosed
Not an inbox of emailsA record with a history behind it. That is how a pattern appears.
The finding shows itselfFour repairs this year, three of them the same drive belt.
STAGE 05

And the asset that keeps failing has a name.

WHICH ASSETS KEEP COMING BACK?
4×

repairs on one air handling unit this year.

Before this, every visit looked like the first one.

AHU-24
Lift 13
Boiler 32
Other1

Three of AHU-2’s four are the same drive belt. That is a pulley out of line, and a morning with an alignment gauge would have ended it in February.

Chosen before it was builtShe said what she needed to know in stage one, so the report already exists.
It shows its workingEvery number opens into the repairs behind it, with the parts attached.
[ WHAT CHANGES ]

What actually changes on Monday.

An asset spreadsheet nobody trusts
SUITERetype 1,140 assets before day one
GOBUSOUpload it as-is, review what it read
Reactive and planned work are different jobs
SUITEOne work order form for both
GOBUSODescribe each one, read it back, change it
The plant room is in a basement
SUITEShe writes it on the docket again
GOBUSOFill offline, syncs when she surfaces
The landlord asks what this unit has cost
SUITEGo and find the invoices
GOBUSOOpen the asset, read its history
[ COMMON QUESTIONS ]
Our engineers are not office people.
They do not have to be. The engineer sees four fields on a phone at the asset and a box for the tenant to sign. Everything long and awkward stays in the office form, which she never opens.
Our asset list is years out of date.
Then it is a starting point rather than a source of truth, and that is how it is treated. Upload it, correct what it read, and the list gets better every time an engineer closes a repair on an asset that was not where the spreadsheet said.
We already have four years of data.
That is the starting point, not the obstacle. Upload the asset register, the service contracts and the scanned contractor insurance exactly as they are, and you check what it read before anything is saved.
What if the AI gets it wrong?
It will, sometimes. That is why nothing is saved until you have read it and said yes. Checking its work is a step in the product, not an afterthought.
[ GO BUILD SOMETHING ]

Build your first one
this afternoon.

Four questions, a plan you can read and change, then working software.