Hello There!
See your building as a living 3D twin you own.
Hello There!
See your building as a living 3D twin you own.
“The cost ends up on the thing that broke, not in somebody's inbox.”
One record, raised to closed
The vendor works from a job link that expires
Raised from a ticket, dispatched, completed, invoiced, and booked against the asset
The same record the whole way, so nobody rebuilds the job in a spreadsheet at the end of it.
A ticket becomes a work order with
the scope already drafted.
Dispatch it by email or text, or put
the same written scope out to bid.
Completion, invoice, receipt, and the
money against the asset itself.
What the record carries, from the ticket that started it to the money it cost.
It keeps the ticket it came from, the property, the location and the asset — so none of that is typed twice or lost between two systems.
Title, scope of work, trade category, materials with quantities and an estimated cost, a cost range, an hours range, permits and safety notes. Your edit is the version that goes out.
Generate a step-by-step guide for the job, for your own maintenance person or for a crew who has never been in this building.
Internal work and vendor work each get their own tab on the work-order board, so the two do not hide each other. One record underneath both.
Pending, soliciting, bids received, awarded, in progress, pending confirmation, completed. The stage is on the job, not in somebody's memory of last Tuesday.
Labour, materials and the invoice total are logged against the asset and the property, so the next person can see what this unit has already cost before deciding to repair it again.
How a trade gets in, gets the job, prices it and gets paid.
Send a trade a tokenised invite, or a one-time code that expires in ten minutes. Nobody has to be set up by you first.
Company details, trades and their own team, entered by the people who actually know them rather than copied off an email by you.
Their jobs, each job's detail, completion, invoices, their team and their profile — in their own portal, not as a seat inside your account.
Several trades price the one written scope, with a reminder after 24 quiet hours and a notification the moment a bid arrives.
Or put the job in front of every vendor with access to your organisation at once, and count how many were reached.
A card pre-authorisation can be taken when a bid is accepted and finalised into an invoice once the job is done, so the money is arranged before the van is booked.
Every bid on one screen, with the count, the lowest and the average across the top. The figures below illustrate the shape of the comparison — they are not a customer's job.
| Vendor | Bid | Estimated hours | Available from | Rating | Jobs done |
|---|---|---|---|---|---|
| Vendor A | $2,180 | 8 | 18 March | 4.4 | 21 |
| Vendor B | $2,640 | 5 | 9 March | 4.9 | 148 |
| Vendor C | $3,110 | 6 | 11 March | 4.8 | 106 |
| Across the three | Lowest $2,180 · average $2,643 | 5 to 8 | 9 to 18 March | — | — |
Bids sort cheapest first, which is not the same as ranked — the cheapest here is a week later than the dearest, on a fifth of the job history. Each bid carries a status of submitted, accepted or declined, and accepting one declines the rest and moves the work order to awarded in a single action. The outcome this machinery produces is the one the warehouse door story describes: three comparable quotes, priced off one written scope, without a site visit each.
Where a job starts, what the trade has to sign up to, how quotes get collected, and where the money lands afterwards.
Contact us
From a ticket. Somebody scans the code on the wall, texts, or calls it in, and that ticket carries the property, the location and often the asset with it. A scope you priced on the model gets there the same way.
No. Dispatch sends them a job link, and the completion and the invoice are submitted through that link. It belongs to that one job and it expires. A trade who works for you often can register instead and get a portal of their own.
You put the one written scope out to bid rather than describing the job three times. A reminder goes out after 24 quiet hours, you are notified as each bid lands, and they arrive on one screen with the count, the lowest and the average. They are comparable because every bidder priced the same quantities.
Completion carries labour hours, labour cost and material cost. The invoice carries its number, its amount and its line items, and you review it before accepting it. A photographed receipt is read into the store, the date, each line with its quantity and part number, the tax and the total. All of it is logged against the asset.
Yes, and it can book the cost too. It separates reading from writing, proposes in ask, draft or do mode, and every write is confirmed by you before it happens: raise the work order, log its cost, add the invoice or the receipt, request the approval.
It is in pilot. The building writing to people itself — chasing a reply, escalating when nobody answers — is early access, running in shadow mode: it records what it would have sent and sends nothing until texting is switched on for that one property. Bid reminders and dispatch notifications are the part that runs today.
Bring one repair you are about to send out. We will raise it, price it with your own trades and close it against the asset, in front of you.