We built Bimvyne because we've sat in the Friday meeting where everyone was surprised.
Construction project management still runs on self-reported status. We built Bimvyne to replace that input with something that can't be gamed: the drone imagery of what's actually in place against the 4D BIM schedule.
Why we built this.
Marcus Ellison spent eight years as a project engineer on high-rise commercial work across Texas — the kind of projects where 30 floors are stacking simultaneously and six trade packages run on CPM schedules that are all interdependent. Every week, the same process: collect verbal updates from subcontractors, reconcile them against the baseline schedule, walk into the OAC meeting with a status report that was five days stale the moment it was written.
The delays were almost always visible on-site before they appeared in any report. The concrete subcontractor knew Level 6 was behind. The site superintendent knew. The PM found out the following Friday when the report landed in his inbox — by which point the sequencing decisions that would have contained the damage were already off the table.
Marcus built the first version of Bimvyne in Austin in 2025 to test one specific hypothesis: could weekly drone imagery compared directly to the 4D BIM schedule give a project manager the same information that a site walkthrough would — without requiring a site walkthrough? Not as a supplement to self-reported status. As a replacement for it as the primary input. The first real project confirmed the hypothesis. The deviations were real, and the drone found them before the sub's report acknowledged them.
What Bimvyne is not: a photo documentation tool, a 360-degree capture platform, or a project management suite. It is specifically a BIM deviation detector — a system that compares visual evidence against a schedule and tells you which elements, on which floors, are behind the planned completion percentage. That narrowness is deliberate. A tool that does one thing well is more useful to a PM on a tight schedule than one that does ten things adequately.
Construction-site experience plus computer vision depth — both on the founding team.
Marcus Ellison
CEO & Co-FounderProject engineer background on commercial high-rise construction in Texas. Spent 8 years managing trade coordination and schedule risk before building Bimvyne to fix the problem from the software side.
Priya Nambiar
CTO & Co-FounderComputer vision researcher with prior work in aerial photogrammetry and 3D reconstruction at a geospatial imaging firm. Built the point-cloud-to-BIM alignment core that powers Bimvyne's detection pipeline.
Derek Holm
Head of Product & Co-FounderConstruction technology specialist who worked on BIM implementation at two mid-size general contracting firms in the Southwest. Owns the product decisions that keep Bimvyne practical for field teams, not just PMs.
The three principles behind every feature decision.
Visual evidence over meeting notes.
Our software exists to let imagery answer questions that spreadsheets and status reports can't. If a feature doesn't tie back to visual evidence from the site, it probably doesn't belong in Bimvyne.
Specificity over dashboards.
We tell you which element on which floor is behind, not a project health score from 0 to 100. A 78/100 health score doesn't tell you what to do Monday morning. A specific deviation alert does.
PM time is the budget.
Every feature is justified by whether it saves a PM's time or reduces a rework event. A project manager who recovers two hours a week from status gathering and phone-around gets that time back for look-ahead scheduling and trade coordination decisions that actually prevent delays. That's the return we're building toward.
Tell us the floor count and what BIM format you're on.
We'll tell you if Bimvyne is the right fit before any demo. Reach us directly at [email protected] or +1 (512) 627-4271 — we respond within one business day.