Hi, I'm Bálint. I provide embedded Revit and Rhino modeling capacity for architectural teams as a subcontractor, backed by production-safe C# algorithms.
High-precision 3D BIM modeling from concept to fabrication.
Automation-based documentation output.
Grasshopper and C# coding for reusable geometric logic.
Concept-to-fabrication modeling.
Real-time documentation.
Parametric model control.
Deadlines often force trade-offs between speed, precision, and model reliability.
Geometry that works early can become fragile during coordination and documentation.
Repetitive modeling and drawing tasks consume time better spent on design decisions.
To speed up modeling and extend my in-house BIM library, I code reusable, OOP .NET C# modules for the Rhino & Revit API-s, developed across multiple projects in a reusable way.
Bálint Füzes
MSc Architect & Software Developer
I’m Bálint Füzes, an MSc Architect and certified software developer. I provide specialized modeling expertise for AEC teams, utilizing professional software development as the essential backbone for every project. I focus primarily on building skins and their support structures, with a passion for turning complex virtual geometry into physically realized architecture.
I collaborate with AEC teams of all sizes, from individual designers to large firms (100+ people).The best fit is typically mid-scale offices (12–60 people) with a basic parametric foundation that need additional capacity and technical depth for intensive modeling, coordination, or delivery-critical work.
No. Code-supported modeling and structured workflows are often just as valuable on geometrically standard projects — enabling quantitative checks, reducing repetitive work, and keeping models reliable as projects scale and deadlines tighten.
I work as a technical back office — similar to an in-house team member working remotely — focusing on modeling, parametrics, and BIM workflows.
You retain full project authority, design authorship, and intellectual property at all times.
Meeting frequency (online or in person) is adapted to the needs and phase of each project.
Typically early enough that technical decisions are still flexible — but I also join projects later when geometry, BIM, or documentation needs stabilizing before delivery.
Both are possible. I regularly support clearly defined, short-term project tasks, but I also collaborate on longer-term development, research, or workflow refinement when it makes sense.
The scope and duration are always aligned with the project’s actual needs.
No. Parametric or code-based solutions are kept lightweight, transparent, and easy to integrate.
I often reuse or adapt existing tools, and I’m happy to share what is already built so your team can immediately benefit.
The goal is practical support — not long, expensive, or hard-to-maintain systems.
Let's discuss your next project!
I’m happy to take a short look at your project and point out where technical input could support it. Feel free to reach out:
balint@fuzesarch.com
+36302980503
