BuiltBot

The AI agent that runs the building with you.

The agent for your building

BuiltBot knows the building and handles what it needs.

Text it the moment something comes up. It already knows the equipment, who serviced what and when, and what is still under warranty. It writes the job up, sources the vendor, brings the prices back, and stays on it until it is closed out.

Book a callSee a thread
12:12
BuiltBot

iMessage
Today 12:12

ac in 103 is dead
Room 103, Amana PTC153G35AXXX. Two vendors service it.
Earliest is 1:30 PM at $185. Book it?
yes

Read

Booked ✅
I’ll file the invoice and update the record when it closes out.
+iMessage
Demo · example conversation

The numbers

Already running, already being used.

Every figure here comes from buildings operating on BuiltOS right now.

500+Buildings BuiltOS runs today, from single sites to portfolios.
12,000+Interactions a month, already landing on exact assets.
Any hourIt answers at eleven at night. It does not keep office hours.
No appIt works in the messages your team already sends.
Hotels, QSR, fuel, fitness and retail. One building or two hundred, and nothing changes shape when the second one arrives.

It already knows

Standing at a dead unit wondering who touched it last?

12:12
BuiltBot

iMessage
Today 12:12

whats still under warranty in the kitchen
Three units.
Walk-in cooler, parts to Mar 2027. Combi oven, parts and labour to Nov 2026.
The fryer expired in June, so the next repair on that one is billable.
who did the oven last time
Forecourt Services, April, $412. Same tech is still on the account.
+iMessage
Demo · example conversation

Ask BuiltBot. It knows the model, the serial, who serviced it, what that cost, and whether it is still covered. Same for every asset on the site, and for the room it sits in.

The record is not something anyone sat down and typed in. It is what the last job left behind.

Live today

A generic assistant knows language. This one knows this building.

Say it out loud

Things people actually text it.

No categories, no forms, no job number. You send the sentence you would have said to a person, and BuiltBot works out the rest.

ac in 103 is dead

It knows Room 103 has a PTAC, asks for the label if the model is not on file yet, and has two vendors who service it. 47 other rooms use the same unit.

how much carpet for floor 4

18,420 sq ft, measured off the actual surfaces rather than paced out. With waste, the number you actually order.

who serviced the rooftop unit last time

Every vendor who has touched it, what they did and what it cost. You stop being the filing cabinet.

is the combi oven still under warranty

Parts and labour run out on different days, and different companies owe you each one. Check before you pay for a repair you already own.

[photo] what is this and is it urgent

Send the picture instead of describing it. It tells you what it is looking at, and whether it waits until Monday.

412 shower isn’t draining

Logged against the room, with the note that maintenance cleared the same drain 61 days ago. On the third time it flags a camera inspection.

what should this cost

What the same work has run across your portfolio, before you approve anything.

how many filters are due this month

186, with last cycle’s price beside it to compare against.

remind me before the elevator inspection

Built off the equipment actually on site, on the interval that equipment requires. You get the nudge, not the bill.

[invoice.pdf]

Filed against the asset, read straight off the document. If a line is unclear it asks you one question rather than handing you a form.

what have we spent on this property this year

Split by trade, with the record behind every line.

water through the ceiling in 214

It knows the isolation valve for that stack and dispatches inside your emergency policy. Any hour.

BuiltBot does the working out, the writing up and the chasing. You approve every dollar before it is spent.

Start to finish

Four steps, and you only do the first one.

01

You text it

One sentence, a photo or a document. iMessage, SMS or WhatsApp. Nothing to install.

02

It works out what you meant

Which property, which asset, what was done to it last time and what is still covered.

03

The work gets done around you

Written up properly, the right vendor found and priced, the follow-ups chased. You are not in that part.

04

It comes back for your yes

Options side by side, in plain words, with the price. Nothing is booked until you pick one.

Two halves

It knows the building. It goes to bat for you.

One half is memory, kept against the asset instead of in somebody’s head. The other half is muscle: when something needs doing, it writes the job up, finds the right people, and stays on them until it is done.

Memory

It remembers so nobody has to

Every asset, every repair, every warranty date and every invoice, kept against the thing itself.

  • Which rooftop unit you own, down to model and serial
  • When it was last serviced, by whom, and what it cost
  • Whether it is still covered, before you pay for a callout
  • Where the isolation valve is, in words anyone can follow
Muscle

It goes and gets it done

Tell it what is wrong in your own words. It writes the job up, sources the vendor, and the answers land side by side against one scope.

  • Vendors sourced and compared against one scope
  • When somebody goes quiet, BuiltBot gets back on them
  • Scheduled around occupancy, not around the contractor
  • Nothing is booked and nothing is spent until you say so

The threads

One message in. BuiltBot takes it from there.

Six conversations, in the order capability builds. Everything stays in one thread, whether it started on a phone or on the web.

12:12
BuiltBot

iMessage
Today 12:12

ac in 103 is dead
Room 103 has a PTAC on record but no model yet.
Send me a photo of the label.
PTC153G35AXXX
Amana PTC153G35AXXX. Added to Room 103 ✅
47 other rooms use this model.
+iMessage
Learns the assetA photo of the label, and the record fills itself in.
12:12
BuiltBot

iMessage
Today 12:12

how much carpet for floor 4
18,420 sq ft of carpeted area, measured off the actual surfaces.
With 8% waste, plan for 19,894 sq ft.
show me

Read

app.builtos.com/twin/floor-4
Want me to turn that into an RFQ?
yes
Out to three flooring vendors ✅ Bids come back in this thread.
+iMessage
Measures the spaceQuantities off the real geometry, not off a tape measure.
12:12
BuiltBot

iMessage
Today 12:12

412 shower isn’t draining
Logged against Room 412.
Maintenance cleared the same drain 61 days ago.
I’ve reopened the issue and attached the previous notes ✅
thanks
If it recurs a third time I’ll flag it for a camera inspection.
+iMessage
Takes staff reportsIt already knows it has seen this one before.
12:12
BuiltBot

iMessage
Today 12:12

186 PTAC filters are due next month.
Last cycle cost $7,840.
Filters $5,600, installation $1,900. Total $7,500, 4% under last cycle.
approve

Read

Ordered and scheduled ✅
I’ll verify completion and update all 186 asset records.
+iMessage
Asks before it spendsWith the price, and last cycle to compare against.
12:12
BuiltBot

iMessage
Today 12:12

water coming through the ceiling in 214
Treating that as life-safety. Dispatching your preferred plumber now.
The isolation valve for 210 to 218 is in the second-floor east service closet.
app.builtos.com/twin/valve-2e
Crew confirmed, 40 minutes out ✅
Emergency dispatch is inside your standing limit, so nothing needed approval.
+iMessage
Moves on emergenciesInside the policy you set once, without waiting.
12:12
BuiltBot

iMessage
Today 12:12

anything i should know this week
Three things.
AHU-3 has had three service events in 14 months, two on the blower. $6,840 spent. I’d replace rather than repair again.
The elevator inspection is due in 11 days.
186 filters are due. I can price them against last cycle.
do all three
On it ✅ I’ll come back with the replacement comparison first.
+iMessage
Tells you what you did not askThe week ahead, unprompted.

Live today  the records, the reasoning and the vendor work. Next texting as the way in.

A chatbot answers the question. This one gets somebody to show up.

How it actually works

Why not a work-order form?

Every facilities team already has one. It is the thing nobody fills in properly, because it asks the reporter to be the dispatcher.

A form

asks you to already know

  • which category the problem belongs to
  • which asset and which room
  • how urgent it is on someone else’s scale
  • which trade it should go to
A message

asks BuiltBot to work it out

  • you describe what you noticed
  • it matches that to the asset already on file
  • it asks the one or two questions that matter
  • it opens the job and keeps the history

Who this is for

Four people who recognise themselves.

You inherited the building.

Nothing is written down, and the person who knew where everything was has left. Photograph what is there and BuiltBot builds the record as you go.

You run several sites.

The same equipment, the same failures, and no shared memory between them. One record format across all of them, and the second site costs nothing to add.

Your team texts you at eleven at night.

Every report already arrives as a message. None of them land anywhere. Now each one opens against the exact asset, with its history attached.

You are tired of being the dispatcher.

Chasing the quote, chasing the date, chasing the contractor who said Tuesday. BuiltBot takes the chasing and hands the decisions back.

Straight answers

The questions people ask first.

Can we use BuiltBot today?
BuiltOS runs 500+ buildings today, and the agent already answers from those records on the web. Texting is how we are opening it next, property by property. Tell us about the building and we will say where yours stands.
How do we message it?
iMessage, SMS or WhatsApp, from the number your team already texts from. Nothing to install and no password: the number is the login.
How does it know about our rooftop unit if nobody told it?
From what you give it and what it picks up as it goes. A photo of the nameplate gets the make, model and serial. An invoice gets the date, the vendor and the cost. After that, every job you run through it adds to the record without anyone filing anything.
Do we need a 3D model first?
No, and this is the part most people expect to be a blocker. A building goes live on QR tags, a staff directory and vendors. The twin is an upgrade BuiltBot uses when one exists, never a requirement to start.
What will it cost?
A subscription per building by size, and the agentic work is metered, because a round of vendor outreach costs real money to run. Reading and remembering are not metered.
Does it spend money on our behalf?
Only inside limits you set, and it tells you first. It proposes the work in writing with the price, and waits. Routine purchases under your threshold go through automatically, because you decided once that they could.
Who sees our building information?
You, and whoever you invite. Roles are set per property, a vendor sees only the job you send them, and a contractor never sees what the roof cost.
What about a full renovation or a PIP?
Scope3D handles the model and the scope for changing the building. BuiltBot picks it up the day the last trade leaves, and keeps the record current for the next cycle.

Three products, one record

Where BuiltBot sits.

One building record underneath. Three ways of working with it, and you do not need all three to start.

BuiltBotBuiltBot

Text the building. It remembers what happened, and it gets the work done.

You are here
Scope3DScope3D

Build the twin and change it: geometry, finishes, furniture and takeoffs.

Visit scope3d.com
ClickpadClickpad

Run what is inside it: assets, work orders, vendors and spend.

Visit clickpad.com
BuiltBot is the way in. The record underneath is what makes it worth asking.
Two Products

One operating system for every building you own

Built in Scope3D, run in Clickpad, owned for life

Book a Call
See the Case Studies