About
Why BIMpossible exists.
Spend 22 years inside AEC and you notice the same bottleneck on every project: the people who need model data can't get it themselves. They ask the BIM manager. The BIM manager opens Revit, pulls the data, exports it, sends it. Repeat — across dozens of projects, forever. The constraint isn't the software. It's that Revit is the only door, and only a few people hold the key.
Revit is excellent at modeling and miserable at managing data. Autodesk's cloud is great for storing files and poor as a daily working interface. The gap between them — running schedules, enforcing standards, letting non-Revit colleagues participate — is real, it grows with the firm, and it's the same in every discipline that uses Revit.
BIMpossible is the layer that fills that gap: a web platform that pulls model data out of Autodesk's cloud and makes it usable by anyone who can read a spreadsheet. Not a Revit replacement. Not another add-in. The operational data layer a firm owns and shapes for itself.
Why now
This wasn't buildable three years ago.
Three shifts lined up at once and changed what deep domain knowledge and modern tooling can ship.
Mature APIs
Autodesk Platform Services grew up
What was a research project five years ago is production-ready today. The cloud APIs to read model data reliably finally exist and are stable enough to build a platform on.
AI-assisted build
Deep domain knowledge can become software
Modern AI development tools collapsed the time to write real web-application code. Work that used to demand a large, specialized team is now within reach of people with deep AEC domain knowledge — which is exactly where BIMpossible comes from.
Containerization
Build once, run anywhere
Docker removed the deployment friction. The same platform runs on a spare machine today and a cloud host tomorrow with no rewrite — so infrastructure cost stays near zero early.
Where it stands
Honest about the stage.
BIMpossible is real, working software — used in production today, not a mockup. It's also early. The read-only data dashboard is live; the bigger roadmap (full spreadsheet power, change tracking, approval-gated write-back) is ahead, built one workflow at a time on the same foundation.
It started inside one firm, as the proving ground for the idea. But it was built discipline-neutral by design — architectural, structural, mechanical, electrical, plumbing, civil, fire protection, interiors. The first workflows came from one discipline; the platform was never meant for one trade. It's the layer the whole AEC industry has wanted and, until recently, had no practical path to building.
Where it comes from
Built from inside the job.
BIMpossible comes out of real BIM-management practice — 22 years of watching capable people wait on model data they should have been able to pull themselves. It's shaped around how firms actually work, built by a working BIM manager who got tired of being the only door to the data, and used on live projects rather than demoed in a vacuum.
Curious where this goes?
Whether you're a BIM manager drowning in data requests or a principal weighing build-vs-buy, I'd like to hear how your firm works.