The asset register you were
iAsBuilt reads the drawings, O&M manuals, and specs you already have, identifies the assets inside, and tags them. Looking anything up takes seconds, not an afternoon.
Built for the teams that run campuses, hospitals, and property portfolios. No asset spreadsheet required.
PLACEHOLDER
Reserved for customer logos.
The register either exists or it doesn't.
The platforms you're being quoted improve a register you already built. iAsBuilt is for the buildings that don't have one, just a shelf of handover documents nobody can search. That gap doesn't close by increments... it closes the day the register exists.
Day one with the platforms you're being quoted
- Chase down spreadsheets, old exports, and whoever last knew the equipment list.
- Weeks of manual entry before anyone gets a single answer out of the system.
- A register that starts drifting stale the day the import finishes.
From a stack of PDFs to a tagged asset register.
Nobody types the register in. The documents do the work, and the AI does exactly three jobs: identify, tag, look up. That's it.
Upload the handover set
As-built drawings, O&M manuals, specs. The paperwork goes in as-is, no cleanup pass first.
AI identifies and tags the assets
It reads the documents, finds the equipment inside, and tags each asset to the pages that describe it. Every tag stays checkable against its source page, and every entry stays editable.
Look anything up in seconds
Search for an asset, get its drawing, manual, and spec. On a laptop in the office or a phone in the plant room.
The platforms you're being quoted assume your asset data already exists.
Asset management usually begins with a data-entry project: weeks of typing before the system gives anything back. iAsBuilt begins with the paperwork the building was handed over with, so the first thing your team does is look something up, not type something in.
Document-access tools stop at digitising the binder: scan it, browse it, done. iAsBuilt builds what they don't... a structured, permissioned asset register where every entry can show the page it came from.
See it on your own handover set.
Book a demoRun the building from its own paperwork.
Everything below is in the product today. Speed is what the demo shows... risk and scale are what carry the budget conversation.
Speed
One searchable document hub
As-builts, O&M manuals, specs, and drawings in one place, indexed and previewable instead of boxed and forgotten.
Risk
Access you can account for
Permissions are granular by user group and item group, and one screen shows every grant. Contractors get exactly what they need and nothing else.
Scale
Organized the way buildings are
Properties, floors, and spaces, the same structure on every building, so the tenth property takes less setting up than the first.
Decision
Assets that carry their paperwork
The manual sits one tap from the equipment it belongs to, so the call made in the plant room is made on the spec, not on memory.
Productivity
A plan viewer built for lookup
Open the right sheet fast and work from it on site, without hauling a roll of drawings around.
Cost
Tasks with their context attached
Work gets created and tracked with its thread to the asset and space intact, so nobody makes a second trip for context that got lost.
[A real customer, in their own words, on what changed for their team once the documents started answering back.]
[Name] · [Role] · [Organization]
What IT and procurement will ask.
We're asking you to upload a building's whole document set, so here are the plain answers up front. Forward this section as-is.
Where do the documents live?
Stateful data sits in OVH's Québec datacenter, with static assets and email on AWS in Canada and the US. The full subprocessor list is on our legal pages.
Does anything train on our documents?
Ask it at the demo and you'll get the answer in writing. It's the right question, and it deserves better than a marketing page's word.
Who owns the data, and can we get it back?
You do. The terms put it in one line: Customer owns Customer Content. Originals stay downloadable document by document, and on termination content is returned or deleted.
How long before it's useful?
The demo already runs on documents you bring, so you see the first real lookup before you've signed anything. After that, value arrives with the paperwork you upload, not with an implementation calendar.
What does it integrate with?
Today iAsBuilt runs beside your systems as the document layer rather than plugging into them. Integrations are a roadmap conversation, and we'll be plain about what's wired.
What does it cost?
Pricing is a first-call answer. You'll have the model before we ask you for anything.
Where iAsBuilt goes next.
In design now, not in the product yet.
Work orders
Maintenance work raised, assigned, and closed against the tagged register.
Sensor & condition data
Live readings landing on the same assets the documents defined.
Analytics
A clear read on the portfolio once the register and the work share one home.
Where iAsBuilt fits.
Is iAsBuilt a CMMS or an EAM?
Neither, on day one. It's document-first asset management: the register grows out of your documents instead of a data-entry project. Work management is on the roadmap, so it grows toward those categories rather than starting from them.
What do we need to get started?
Documents. As-builts, O&M manuals, specs, in whatever files are sitting on the shared drive. No asset spreadsheet, no export from the old system.
What does the AI actually do?
It reads your documents, identifies the assets inside, tags them, and makes looking up their documentation fast. No predictions, no anomaly detection, no agents.
What happens when the AI gets one wrong?
You'll catch it, because every tag sits next to its source: each asset links to the exact page it came from, so checking a tag is one tap. And nothing is locked. Every asset, tag, and link stays editable, so a wrong call is an edit, not a support ticket.
Who can see our documents?
Only who you say. Access is permissioned by user group and item group, and one screen shows exactly who holds which access.
Does it replace what we run today?
It doesn't have to. iAsBuilt runs beside whatever you have as the document layer, because that's the part nothing else covers.
What formats does it take?
PDF drawings and documents, which is what most handover sets are. Bring what you have and we'll look at it together.
What does looking things up cost now?
Your number, not ours. Nothing leaves this page.
Fill in all three and the number appears here.
Whatever it says, write it down. It's the before.
See your own as-builts become an asset register.
Bring a few documents. We'll walk through them in the product, not in a slide deck.
- A walkthrough on your documents, not canned data
- Straight answers on what's in the product today and what's coming
- Your security and access questions answered up front
Before the demo, time one lookup: how long from question to the right page of the right manual? Bring the number. That's the one we want to beat.