In August I wrote that BIM 2.0 is largely a set of tools built around the system it was supposed to replace. Every one of them connects to Revit in some form. At Rhino World 2026, two of them were showing how they connect to something else.
Motif and Qonic both had stands on the expo floor, and both were there to show how work gets from Rhino into their platforms. In the practices most likely to try a new BIM tool, the ones with computational design teams and hybrid Rhino and Revit workflows, Rhino is where much of the design happens. If the route from Rhino to a drawing set runs through Motif or Qonic, Revit isn't on it.
Motif was showing Motif Design, the agent-native platform it launched on 8 September. It's a separate product from Motif Review, the company's earlier review and collaboration tool, but the Rhino connection works on the same principle. A connector runs inside Rhino, or Revit, and streams the model into Motif without export or conversion. After the first load, only the changes are sent. Once the model is in Motif, its information can be mapped onto Motif's own building objects or left in its original schema.
Motif's sheets are live views of the model rather than extracts, so what streams in from Rhino carries through to the drawings. When AEC Magazine looked inside Motif in September, that included Rhino geometry taken through to shop drawings, with element counts and lengths, without going via Revit. The Rhino model stays the design model. Motif documents it.
Motif doesn't have an automatic dimensioning tool in the sense a BIM 1.0 system does. Instead, dimensioning is fully configurable through the agent. You tell it how your firm dimensions. I think that's right. It also means a practice that wants to test Motif has work to do first, which is the subject of my next post.
Qonic was showing a feature still in beta: a Grasshopper component that publishes directly into Qonic. Like Motif's connectors, it sends only the changes after the first connection, which keeps the link responsive while the script is still being worked on.
Once you're happy with a design in Rhino, a complicated facade for example, you bake it into Qonic. The elements become Qonic elements, and materials and IFC types can be applied. Rhino still has no native IFC export, a request that has sat on McNeel's own forum since 2021. Qonic is built on IFC, so once baked, the facade is IFC.
Geometry that leaves Grasshopper tends to arrive somewhere else as a large number of separate objects. The script knew which panels were the same. The export doesn't. Qonic's component system, which I wrote about when it launched in August, can take one small part of the import, turn it into a component, and have it associate itself with every other matching instance. A facade that arrived as geometry becomes a set of building elements with a single point of control.
This is the detailed design work I called the missing middle in August, and it's where Qonic has aimed from the start.
Motif and Qonic are answering the same question. Where does the Rhino model stop and the building model start?
Motif's answer is that it doesn't have to stop. The model keeps streaming, mapped onto Motif's objects or not, and the drawings follow. Qonic's answer is that there's a moment when a design is ready to become building elements, and the tool should make that moment easy and keep the structure the script already had. A practice that keeps changing geometry until the week before issue will want the first. One that hands a settled design to a team who develop it in detail will want the second.
I attended Rhino World 2026, just outside Barcelona, on behalf of AEC Magazine. Look out for my full coverage in the Nov/Dec issue.