realBIM

The company appears to be a solo-built, self-funded project named realBIM, which the author describes as an online collaborative BIM platform aiming to unify modeling, engineering calculations, cost estimation, and AI in a browser-based environment. The author states that it is built using a stack including React, Next.js, Three.js, PostgreSQL, liveblocks, Watermelon, and OpenAI tools, with a focus on simplifying professional workflows through real-time collaboration and AI integration.

What changed: The project was submitted to the OpenAI 2026 hackathon by a single founder, Mike Repolusk, who claims to have taught himself full-stack development over three years using ChatGPT and Scrimba. It is presented as a prototype demonstrating core BIM workflows in a browser-based environment.

The most important open question: Is there evidence of traction or early validation from engineering firms that would suggest real market demand for this platform?

Note: This analysis is based solely on the self-reported description provided by the author. No external verification, revenue data, customer list, or traction metrics are available.

• The description states that realBIM is a browser-based collaborative BIM platform.
• It aims to bring together modeling, engineering calculations, cost estimation, project data, and AI in one shared workspace.
• It stores structured building data, rather than large BIM files, generating 3D models, calculations, costs, diagrams, and reports from the same source.
• The platform supports:
  • Importing and calibrating PDF floor plans
  • Creating rooms and layouts
  • Placing building components
  • Storing structured project data
  • Preparing engineering calculations
  • Generating cost estimates

Inference: Based on the description, realBIM is a prototype tool designed to simplify BIM workflows by centralizing data and enabling live collaboration in the browser. It is not yet a production-ready product.

• The author positions realBIM as an online operating system for construction, where all disciplines collaborate on one live model.
• It is described as a platform that makes construction projects feel less like file exchange and more like collaborating in an online multiplayer game.
• The author claims that the construction industry does not need another file format—it needs a new way of working.
• Key positioning elements:
  • One project. One model. One source of truth.
  • Focus on collaboration, intelligence, and connection across disciplines.
  • Aims to be an operating system for the construction industry, from sketch to building operation.

Claim: The author asserts that realBIM will become a foundational platform for digital construction, but this is not substantiated with evidence of adoption or traction.

• The description states that realBIM targets:
  • Engineering companies
  • Architects
  • MEP/HVAC companies
• These stakeholders are described as potential users who can test the platform, provide feedback, and help shape its future.
• The author notes that the goal is to validate productivity gains on real projects.

Inference: The ICP appears to be early-stage engineering professionals or firms involved in construction planning and design. However, no evidence of actual customers or use cases beyond testing exists.

• No information is provided about pricing, monetization strategy, or business model.
• The author mentions that the platform is being validated with real projects but does not describe how this will translate into revenue or customer acquisition.

Not evidenced: There is no evidence of a defined business model or pricing structure.

• Built using:
  • Frontend: React, Next.js, TypeScript, Three.js, Tailwind CSS, shadcn/ui
  • Backend: PostgreSQL, liveblocks, Watermelon, .fraq
  • AI: OpenAI tools (Codex, ChatGPT)
• The platform is described as browser-based, storing structured data instead of large BIM files.
• Key technical features include:
  • Real-time collaboration
  • Rendering large building models smoothly in the browser
  • Room recognition from floor plans
  • Live engineering calculations
  • IFC compatibility

Inference: The tech stack suggests a modern, full-stack SaaS approach with real-time capabilities and AI integration. However, no production deployment or scalability data is provided.

• The project is described as a working prototype that demonstrates core BIM workflows.
• It has been developed over three years by one person (Mike Repolusk).
• The author states that the next milestone is to complete the MVP and validate it with engineering companies on real projects.
• No evidence of:
  • Customers
  • Revenue
  • Usage metrics
  • Product-market fit validation

Not evidenced: There is no traction or maturity data beyond a prototype.

• The description does not mention any competitors or direct market positioning against existing BIM tools.
• It implies that current BIM platforms are fragmented and inefficient, with disconnected workflows involving PDFs, emails, and duplicated data.
• The author positions realBIM as an alternative to traditional file-based collaboration.

Not evidenced: No competitive landscape or comparison to existing players in the BIM space is provided.

• Single-founder project: Only one person is involved, which raises concerns about execution capacity and scalability.
• Prototype-only status: The platform is described as a prototype, not yet production-ready.
• No revenue or customer data: No evidence of monetization, adoption, or traction.
• Unproven market demand: While the author seeks feedback from engineers, there is no indication that this feedback has led to actual product-market fit or commercial interest.
• High technical complexity: The challenges listed (rendering large models, live calculations, IFC compatibility) suggest a complex domain with high development risk.

Inference: The project is in an early stage and lacks validation. Risks include execution risk, lack of traction, and potential difficulty in scaling or monetizing the concept.

1. What specific engineering firms have you engaged with for testing? What feedback did they provide?
2. How do you plan to validate productivity gains on real projects?
3. Are there any early adopters or pilot customers who are willing to share their experience?
4. What is the current roadmap for MVP completion and production release?
5. Do you have a clear path to monetization or customer acquisition beyond feedback loops?
6. How do you plan to scale beyond a single developer, especially given the technical complexity of BIM?