ArchiCAD vs Revit for Small Practices: The Licence and Interoperability Question

The ArchiCAD vs Revit question doesn’t get settled the way it does in a large practice. You’re not buying seats in the hundreds or negotiating an enterprise agreement. You’re buying one or two licences, and you’re buying them for the next five years of projects — which means the question isn’t which platform models best. It’s which platform your consultants can actually open.

That’s the whole decision in one line. Graphisoft positions ArchiCAD around OpenBIM workflows and a single integrated model; Autodesk’s Revit is the format most of your structural and MEP consultants already run. Both are defensible. The mistake is choosing on modelling features and discovering the interoperability cost on your first coordinated project.

What ArchiCAD actually promises

Graphisoft’s own product page describes ArchiCAD as a BIM environment for architects, designers and engineers, built around familiar tools — Walls, Windows, Roofs, Stairs, Railings, Curtain Walls — that produce a complete Building Information Model rather than a drawing set with a model bolted on.

The pitch that matters to a small studio is the documentation link. Graphisoft says you annotate once and the drawings stay current as the model changes, with clash detection and issue tracking running across BIMx and ArchiCAD. For a practice where one person is both designer and documenter, that’s the difference between a Saturday of drawing updates and not having one.

Graphisoft also lists an AI Assistant in beta, energy analysis and LCA tools, and BIMcloud for hosting a central model with live updates. Treat the beta label literally: it’s a direction, not a reason to sign.

The ArchiCAD vs Revit interoperability question, honestly

OpenBIM is the argument you’ll hear most often for ArchiCAD in a small practice. It’s a real argument, but it’s narrower than it sounds.

Archicad 22’s release notes, as catalogued by ArchDaily, describe improved import and export of element properties through IFC, with better accuracy for Building Materials, compound skins and complex profile parts in IFC2x3 and IFC4. That matters because schedules, calculations and cost estimates depend on that data surviving the round trip.

The same release introduced a “Deconstructor” feature that pushes ArchiCAD element data out to Rhino and Grasshopper for optimisation work. Useful if you do facade or performance studies. Irrelevant if you don’t.

Here’s the part the marketing skips. IFC round-tripping is only as good as the receiving end. If your structural engineer works in Revit and re-models what you send, you’ve paid for interoperability you aren’t getting. Before you commit, send one real project — not a test cube — to your two most important consultants and ask them to open it and report what broke.

The CDE problem neither platform solves

Whichever authoring tool you choose, the files have to live somewhere. BIMcollab’s own writing on common data environments names the two failure modes plainly: folder-based systems with little metadata descend into chaos, and closed CDEs lock teams into a limited toolset and a lowest-common-denominator way of managing data.

That second trap is the one small practices fall into quietly. A closed CDE feels safe until a client insists you onboard to their platform, and you’re maintaining multiple databases and learning a new system for every job.

BIMcollab sells its platform in tiers — an essentials coordination hub, a version with automated workflows and integrations, and a top tier for complex projects with governance — according to its plans page. The tiering is the point: coordination tooling is a separate line item from your authoring licence, and a small practice should budget for both.

What each choice costs you in practice

Neither Graphisoft nor Autodesk publishes a single universal price — both sell through regional resellers and subscription terms that vary. So the honest comparison isn’t a number. It’s what each decision commits you to.

If you’re already modelling in Autodesk Revit, the switching case has to be strong. The cost isn’t the licence — it’s the two projects where you’re slower while you relearn how walls, schedules and sheet sets behave.

The decision rule for a two-to-ten person studio

Choose the platform your consultants already run, unless you have a specific reason not to. That’s the unglamorous answer, and for most small practices it’s the right one.

Pick ArchiCAD when you’re the originator of the model, your coordination is genuinely IFC-based, and you want documentation and design in one place without a second toolchain. Pick Revit when your structural and MEP collaborators are Revit-native and you’d rather not be the one converting files on every issue.

Either way, run the same test before you sign. Take a live project, export it, and send it to a consultant who doesn’t know you’re evaluating. What comes back tells you more than any feature list.

The licence is the cheap part. The interoperability is what you live with.

Sources

• Graphisoft — Archicad
• ArchDaily — Virtual Building Software: Archicad 22
• BIMcollab — Is your CDE trapping, or transforming, your business?
• BIMcollab — Platform plans