Built by people who've been in the coordination meeting when the RFI call came in.
Bimvyne started with a specific observation: clash data that arrives during a GC walkthrough is clash data that already costs money. We're changing when that data gets to the team.
The problem started at a coordination meeting on a mixed-use project in Austin
Before founding Bimvyne in 2025, Marcus Ellison spent years as a BIM manager at architecture firms in Austin and Dallas. He ran coordination meetings. He ran Navisworks. He exported 300-clash reports and spent hours manually deciding what actually mattered before he could call the subconsultants. The Navisworks session was the least of it — the real problem was turning that data into something the MEP lead would act on before the next meeting.
The issue wasn't that clash detection was hard. Navisworks can find clashes. The problem was everything around the detection: which clashes were real coordination issues at the current LOD versus geometry placeholders from schematic phase, which discipline owned resolution, and whether anyone would close the loop before the GC walkthrough. An unfiltered 300-row clash export doesn't answer any of those questions.
Bimvyne is the tool Marcus wished existed during those meetings. LOD-aware severity scoring, discipline-routed assignment, and a pre-meeting digest that puts the 15 clashes that actually need resolution in front of the right people — six hours before anyone walks in the room.
The principles behind how we build
We only build for AEC. We don't sell a horizontal platform and bolt on construction use cases. Bimvyne is designed around the workflow of architecture firms who manage multi-discipline BIM coordination.
We prioritize actionable output over comprehensive reporting. A 300-clash export is not useful. The top 15 clashes that need to be resolved before next week's meeting is. We optimize for the action, not the data dump.
Marcus walks through the first clash report with every new customer personally. We're a small team. Customer conversations directly shape the product roadmap. We don't hide behind a ticketing system.
The people building Bimvyne
We're building this with customers, not ahead of them
If you're a BIM manager or project architect who runs coordination meetings, we want to talk. Your workflow shapes Bimvyne's roadmap.