People ask whether BuiltOS is a third product sitting on top of Scope3D and Clickpad. It is not, and the distinction is worth getting right early. BuiltOS is the layer underneath them: the account your buildings live in, the record each one accumulates over its life, and the permissions that decide who is allowed to open it.
That matters more than it sounds, because a building is not a project that finishes. It is designed once, operated for decades, and sold more than once. At each of those handoffs the thing most likely to be lost is not the drawings — those get archived — but everything the building learned after the drawings were signed off.
Scope3D is where a building enters the system. Drawings, BIM, a PDF drawing set or a phone photo of a paper plan go in, and a measured 3D twin comes back out: rooms named, elements tagged and typed, quantities takeable straight off the model rather than paced out on site with a tape and a clipboard.
Clickpad is where the building is run once it is open. Assets carry their own service history, warranties, install dates and spend. Issues arrive by QR scan, by text message, by phone call, and leave as work orders with a vendor attached, a scope agreed and a photographic sign-off required before an invoice can move.
The two are separate products, with separate sites, separate prices and separate roadmaps, and that separation is deliberate rather than accidental. Clickpad works on buildings that have no model at all, which is most buildings. Forcing every one of them through a twin first would shrink what it can serve to a rounding error of the market.
What BuiltOS provides is the part they share. One organisation, its properties, its people, and a role for each person on each building. A contractor invited onto one property does not discover the rest of the portfolio on the way in, and an area manager sees the sites they are accountable for rather than everything the company owns.
It also provides continuity between the two. A twin authored in Scope3D can move into Clickpad whole, carrying its geometry, its storeys, its rooms and the records already hanging off them. Nothing is rebuilt on arrival and nothing has to be re-keyed by hand, which is the difference between a handoff and a fresh start.
And it provides the part owners care about most, which is that the twin belongs to whoever owns the building, for the life of the building. Export it to IFC whenever you want, including after you stop paying, and open it in Revit through its own importer. Ownership that ends when the invoice stops is not ownership; it is a rental with better branding.
There is a reason to say all of this plainly. Plenty of software promises to be the single system of record for a building and then turns out to be a place data goes in and does not come back out. The test is not what the marketing says — it is whether you can leave with everything you put in, and hand it to the next owner intact.
None of this requires you to adopt both products, or to adopt either one everywhere at once. Most portfolios start with a single building and a single problem: an operator who cannot find a service record, or an owner who cannot open the model they paid for. Both are worth solving on their own.
That is the whole of it. Two applications doing genuinely different work, one account holding what they both produce, and a building that keeps its own memory through staff turnover, management changes and sale — which is the only thing that makes any of the rest of it worth doing.