Bálint Füzes working — architect & coder combining design and algorithmsBálint Füzes working — architect & coder combining design and algorithms

Construction-ready BIM geometry.

Hi, I'm Bálint, MSc. Architect. I take on geometry-heavy 3D modeling work so you can focus on design.

As projects evolve to construction, geometry must become perfect.

Think of it as your extra arm for modeling - like other disciplines on the project.

I extend your environment (Revit, Rhino, etc.) without adaptation on your end.

Every dimension gets code-validated, eliminating donwstream site errors.

I take design intent where it is now and work it into construction-ready models and plans.

I usually get involved when a project starts to strain — a roof needs remodeling for permit, a repetitive structure that wants to be done by code, or a detail no one has time for.

12+ years experience across architectural projects— from standard production volumes to detailed one-offs, mostly at the phases where geometric precision starts to matter.

GroupDyer
BanatiHartvig
S39
PaulinyiAndPartners
DNBS
Equinox
AJS
T//O
GroupDyer
BanatiHartvig
S39
PaulinyiAndPartners
DNBS
Equinox
AJS
T//O
GroupDyer
BanatiHartvig
S39
PaulinyiAndPartners
DNBS
Equinox
AJS
T//O
GroupDyer
BanatiHartvig
S39
PaulinyiAndPartners
DNBS
Equinox
AJS
T//O
GroupDyer
BanatiHartvig
S39
PaulinyiAndPartners
DNBS
Equinox
AJS
T//O
GroupDyer
BanatiHartvig
S39
PaulinyiAndPartners
DNBS
Equinox
AJS
T//O
Models.

BIM modeling.

Structured models aligned with real construction aspects and downstream use.

Details.

Junction development.

Translation of design intent into fabricated items at critical, highly spatial joints.

Sheets.

Execution drawings.

Complete sets of plans, sections, and details prepared for coordination and fabrication.

Transfer.

Interdisciplinary coordination.

Preparation of results for civil, MEP, façade, and subcontractor handover.

Logic.

Model rationalization.

Algorithmic translation of complex or non-standard designs into consistent items.

Extension.

Project continuation.

Takeover of existing models for development into execution plans.

References.

SwissKrono.

Real-time documentation.

Weave.

Concept-to-fabrication modeling.

See projects

Modules.

Roof grids.

Graph-driven axis management.

Junction details.

High LOD precision modeling.

See all modules

Send over something tricky.

Have a junction that's been fighting you, or a repetitive structure nobody has solved cleanly yet? Send the geometry — I'll show you the approach, with a typical reply in a few hours.

balint@fuzesarch.com
+36302980503

Get in touch

How I work.

High-precision geometries stabilized by modular templates and algorithmic validation. You keep creative authorship and IP, while I work the technical angle. Codes are my optional tools, never your worry.

Types.

Exterior to interior.

Unitized panel claddings.
Adaptive substructures.
Envelopes, roofs, shadings.
Singular sculpture items - and more.

Scales.

Structures to details.

Multi-story facade grids.
Specific building structures.
Detailed panel items.
Millimeter-precise joints - and more.

Platforms.

Native models and transfer.

BIM-compliant LOD 400 Revit models.
Programmatically controlled Rhino shapes.
Bidirectional ArchiCad data transfer.

Setups.

Flexible collaboration.

Rapid drafting surges on deadlines.
Specific module deployments.
Multi-year project partnerships.

Rhino nodes and
Revit commands.

Over time, I’ve built a set of reusable .NET C# components that speed up delivery across projects. One of them grew into Portia — a publicly available graph logic. It accelerates the planning of grid-like constructions (timber roofs, steel grids, etc.) into an adaptive engine.

See PORTIA ecosystem
public class Task_NodesByWrap<TNode, TEdge> : Task_ByWrap<TNode, TEdge>
 where TNode : GraphNode
 where TEdge : GraphEdge<TNode>
{
public override List<IGraphQuery> Queries =>
new List<IGraphQuery>
{
 
new GenericQuery<IEnumerable<int>, TNode, TEdge>(
(graph) => graph
.Vertices
.Where(node => node.IsWrapped)
.Select(x => x.GraphIdentity.Index),
ComponentHelp.SetList,
"WrappedNodeIndices"),
  };
Heteroptera
Blender
vRay
Git
JSON
systemAnnotations
vectorFields
fluentValidation
Galapagos
geneticSharp
graphMapper
quickGraph
Heteroptera
Blender
vRay
Git
JSON
systemAnnotations
vectorFields
fluentValidation
Galapagos
geneticSharp
graphMapper
quickGraph
Heteroptera
Blender
vRay
Git
JSON
systemAnnotations
vectorFields
fluentValidation
Galapagos
geneticSharp
graphMapper
quickGraph
Heteroptera
Blender
vRay
Git
JSON
systemAnnotations
vectorFields
fluentValidation
Galapagos
geneticSharp
graphMapper
quickGraph
Heteroptera
Blender
vRay
Git
JSON
systemAnnotations
vectorFields
fluentValidation
Galapagos
geneticSharp
graphMapper
quickGraph

A little bit about me.

Bálint Füzes working — architect & coder combining design and algorithms

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.

Is this relevant for you?

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.

How could we actually work together?

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.

Do you need to understand any code?

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.

Can I build something specific for your workflows?

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.

Let's talk about your project.

Do you see a capability alignment or are you simply interested? Drop a line:

balint@fuzesarch.com
+36302980503

Get in touch