Hi, I'm Bálint, MSc. Architect. I work on geometry-heavy models with architects and engineers.
Structured models aligned with real construction aspects and downstream use.
Translation of design intent into fabricated items at critical, highly spatial joints.
Complete sets of plans, sections, and details prepared for coordination and fabrication.
Algorithmic speedup and translation of both standard and complex item planning.
Unitized panel claddings.
Adaptive substructures.
Envelopes, roofs, shadings.
Singular sculpture items - and more.
Multi-story facade grids.
Specific building structures.
Detailed panel items.
Millimeter-precise joints - and more.
Real-time documentation.
Concept-to-fabrication modeling.
Graph-driven axis management.
High LOD precision modeling.
Let's look at a project.
Have a junction that's been fighting you, or a structure nobody has time for? Send it over.
Get in touchI build .NET C# plugins that accelerate delivery across projects. One of them became Portia — a graph engine easing the detailing of grid structures: timber roofs, steel grids and more.
Bálint Füzes
MSc Architect & Software Developer
I’m Bálint Füzes, MSc Architect and certified software developer. I support architects and engineering teams with modeling and computation - usually at the construction-near phase of projects.
My focus is the harmonious interplay of geometry and algorithms - to expand work-in-progress designs into logically lightweight, yet highly-detailed, fabrication-ready models.
If you're looking at a model that needs to be on site in four weeks and it isn't — then yes, almost certainly. If you're at the phase where geometry needs to stop being approximate and start being exact — permit, fabrication, execution — then probably also yes. Scale doesn't really matter, building type doesn't either. What matters is whether there's a gap between where the design currently lives and where the model needs to be for the next phase - that gap is what I work in.
Honestly, however makes sense for the project. In-house, fully remote, occasionally on-site, project-based, longer-term — we'd just figure out what fits. You stay on the project, I look at what the geometry actually needs at that point, and we set something up from there. You keep full authorship and IP throughout. The overhead of adding this kind of "capacity and capability extension" to your team is genuinely minimal. Plus it mirrors the usual, fluctuating project loads of our industry.
Not at all — it's just my own toolset running in the background. What it does is make sure every dimension and geometric relationship gets validated programmatically - wherever needed. You never have to see or touch any of it, if you don't want to. What you get is clean models and plans that have been checked.
Yes, and it comes up pretty regularly. Things like document automation, viewport logic, parametric validators, project-specific solvers — components your team can use directly without knowing what's deep inside them. I always start with a mindmap of the workflow so we're aligned before a single line of code gets written. Plus everything ships with documentation and ready-made examples - you just use the plug-n-play module.
Get in touch.
Do you see an alignment or are you simply interested? Drop a line:
balint@fuzesarch.com
+36302980503
Get in touch