Ontologic builds workflow systems for the built environment.
Ontologic helps AEC teams turn fragmented design processes, computational workflows, BIM data and AI experiments into practical systems that improve real project work.
Why Ontologic exists
The AEC industry does not lack tools. It lacks connected workflows.
Architecture and real estate projects generate models, drawings, spreadsheets, calculations, assumptions and decisions. But too often, that information remains scattered across files and tools.
Ontologic exists to close that gap: connecting design logic, project data, BIM, automation and AI into systems that are actually usable by project teams.
What Ontologic combines
A hybrid practice between architecture and software
Ontologic operates at the intersection of domain knowledge and technical implementation. That is where most valuable AEC workflow opportunities live.
Architecture
Grounded in real architectural practice, project constraints, design logic and the messy reality of AEC workflows.
Computational Design
Using parametric thinking, Grasshopper, data structures and automation to create more leverage in design work.
Software Systems
Building web-based tools, dashboards, databases and interfaces that make project intelligence accessible.
AI Workflows
Applying AI as a practical workflow layer for research, design exploration, documentation and decision support.
Founder / Architect / Developer
Built by someone who understands both design practice and code.
Ontologic is founded by Marijn Luijmes, an architect and self-taught software developer based in Amsterdam. The work combines architectural practice, computational design, BIM, Grasshopper, web development and AI workflows.
Start a ConversationArchitecture practice
Experience in architectural design, housing, transformation projects, public buildings and real project delivery.
Parametric workflows
Building Grasshopper, Rhino and computational design workflows for design exploration, automation and project analysis.
AEC software
Developing web applications, dashboards, data tools and collaboration platforms for project information.
Ontologic
Combining architectural domain knowledge with software and AI to help AEC teams build better workflow systems.
Principles
How Ontologic thinks
These principles shape the services, content, courses and software direction of Ontologic.
Systems over scripts
A one-off script can solve a task. A good system changes how a team works across projects.
Practical before abstract
The best digital workflows start from real project friction: repeated work, unclear data and slow decisions.
Data should travel
Project information should not stay trapped in screenshots, spreadsheets, model files or isolated tools.
Knowledge compounds
Sharing workflows, videos and ideas for free helps raise the baseline of digital capability in AEC.
Focus areas
The work sits between workflow design, data and implementation.
Ontologic is especially useful when a team already feels that better digital workflows are possible, but needs help turning that intuition into something concrete, usable and scalable.
Who Ontologic helps
For teams that want digital workflows to become practical
Architecture firms
Studios that want to make computational design, BIM and automation more usable inside daily project work.
Real estate developers
Teams that need clearer feasibility studies, dashboards, project data and design option comparisons.
AEC innovation teams
Digital, BIM and innovation teams looking to prototype, validate and scale new workflow systems.
Free knowledge
Sharing knowledge is part of the mission.
Ontologic publishes videos, thoughts and learning resources because digital capability in AEC should not be hidden behind closed workflows. Free content helps more architects, designers and teams understand what is possible.
Have a workflow, tool idea or digital bottleneck?
The best starting point is a conversation about where your team loses time, where data gets fragmented and where a better system could create leverage.
Map the current workflow and bottlenecks.
Identify what data, models and tools are involved.
Find the simplest useful system to prototype first.