Best AI Platform for Architects: Revit, Archicad or a Standalone Tool?

Use the AI built into your BIM software first. In Revit that means Autodesk Assistant for model questions and documentation chores; in Archicad it means the AI Assistant and AI Visualizer. Buy a standalone AI platform only when it does a job the built-in one cannot, usually fast concept imagery across several programs, and only after its data terms pass.

Two caveats shape the decision. Several of these features are labelled beta or tech preview, so they can change under you, and what you get in Archicad depends on version and plan. So start from the software you already own, because the cheapest tool is the one already on the machine.

Follow me on Instagram@sagnikteaches

What each side offers, as of November 2026

This table sums up the vendors' own descriptions. Treat any feature marked preview or beta as something to test, not rely on.

Connect on LinkedInSagnik Bhattacharya

Revit: what Autodesk Assistant does

Autodesk's Revit 2027 release notes describe Assistant as an "agentic design and make partner" with three jobs: product help on Revit features and workflows, model queries that pull information out of your model, and task automation through prompts. You open it from its icon in the title bar after signing in with your Autodesk account; it runs only in Revit 2027 and later, and Autodesk notes that AI features may not be available in every region. Update 2027.2 added personalised Insights and Recommended Prompts and lets Assistant receive updates between Revit releases, and 2027.3 brought it into Dynamo. Autodesk introduced it as a tech preview in April 2026, so expect behaviour to change between updates.

Subscribe on YouTube@sagnikteaches

In practice that means requests such as "how many structural columns have their base level set to Level 2?", "which views placed on sheets A101 to A110 have no view template?" or "create a door schedule sorted by level" (illustrative wording, not Autodesk's). Because it can change the model as well as read it, test each kind of action on a copy before you use it on a live job. Revit 2027 also ships a public MCP server, again a tech preview, which lets outside AI apps connect to Revit; that is a separate route from Assistant, with the outside app's own data terms.

Archicad: what the AI Assistant and Visualizer do

Graphisoft's AI Visualizer generates images, tileable textures and isolated objects from a sketch, model view or prompt, with selective edit and refine and 4x upscaling. The AI Assistant (beta) answers how-to questions from official guides, gives selected building-standards guidance and lets you interact with the model in natural language. Its Spaces feature turns your uploaded documents into a searchable knowledge base, which suits a practice standard such as a specification library; the first release accepts PDFs only, with up to 10 Spaces of 10 files each and 40 MB a file. Product and domain Q&A runs in Archicad 30 Studio and in Archicad 29 Studio and Collaborate. Agentic model editing through MCP (a connection standard that lets an AI program operate Archicad) is listed for Archicad 30 Collaborate and Max, and Graphisoft's plan page lists a company pool of AI credits: 50 per licence a month on Studio and Collaborate, 250 on Max. The assistant, Spaces and Visualizer need internet access. For offline work, Graphisoft describes connecting Archicad through its public MCP server (also in beta) to a model running locally in a tool such as LM Studio or Ollama, so the model and your prompts stay on your own hardware.

Standalone: where it still wins

Standalone render and concept tools earn their place on reach. Veras lists Revit, SketchUp, Rhino, Archicad, Vectorworks, Forma and Allplan among the programs it works with, plus a web app. Its Pro tier is listed at $348 a year per licence (the monthly rate when I last checked was $59, and the page shows regional variation, so confirm both). MyArchitectAI lists plans from $29 a month and Snaptrude lists a Pro plan at $50 a month on annual billing for early concept design. Verify any figure on the vendor page before you quote it to a partner. For a fuller render comparison, see the best AI rendering tools for small practices.

Which AI to use, by the BIM software you run today

1. Revit practice, mainly documentation work. Try Autodesk Assistant on schedule, view and sheet chores before you buy anything. Add a standalone render tool only if you produce concept imagery most weeks.
2. Archicad 30 on Studio, Collaborate or Max. The AI Visualizer is part of the plan, so run it for a month before paying for a separate image tool. If you want agentic editing, check that your plan is Collaborate or Max.
3. Archicad 29 or older. The Assistant's product Q&A is listed for 29 on Studio and Collaborate, but the updated Visualizer is listed with 30. The upgrade decision is bigger than the AI decision, so price it on its own merits.
4. Mixed software: SketchUp or Rhino for concepts, Revit or Archicad for documents. A standalone tool that works across them is the only one of the options that covers the whole chain.
5. Vectorworks or Allplan practice. This tutorial does not cover their built-in AI; check the vendor's own pages, and note that a standalone tool such as Veras lists both.
6. Sole practitioner. Put cost first. A general assistant at about $20 to $25 a month plus whatever your BIM plan already includes covers most written work, as using the AI already in your practice software before buying more argues.

What the AI costs per seat in Archicad and Revit

Neither vendor lists a separate charge for these AI features on the pages I could read, so the cost question is about plan tiers. Graphisoft publishes its tiers: a one-year Archicad subscription paid upfront lists at $2,414 a seat for Studio, $2,840 for Collaborate and $5,700 for Max, and month-to-month terms cost more ($345, $406 and $800 a month). Graphisoft calls these prices for information only and says the final price depends on your billing country, so get a written quote. Autodesk's help pages describe Assistant as part of Revit 2027, opened after signing in, and mention no extra charge; Autodesk's Revit pricing page could not be read when I checked, so take the current seat price from Autodesk or your reseller. Ask for the per-seat annual price of each tier you might need and write down the difference.

Pricing three options for a five-person Archicad practice

An illustration: the seat prices are the vendors' listed rates, while the practice, volumes and hourly figures are made up. A five-person practice has three people producing concept visuals and two focused on documentation. They run Archicad on the Studio plan and want agentic editing as well as better visuals.

• Option A, stay on the current plan, test the built-in tools. Extra cost: nothing beyond staff time. Eight hours across the team to test.
• Option B, move all five seats to Collaborate. Extra cost: five times the tier difference. At Graphisoft's listed one-year prices that is $2,840 minus $2,414, or $426 a seat, so about $2,130 a year for five seats before any reseller discount or local pricing.
• Option C, add a standalone render tool for the three visualisers. Three licences at $348 is $1,044 a year at the listed Veras Pro annual rate.

Now the benefit. Say the practice pitches for six jobs a month and each pitch needs three concept images, 18 a month. If outsourcing each image costs $150 and AI-produced images need an hour of staff time at $50, outsourcing costs $2,700 a month and in-house AI roughly $900. The saving, around $1,800 a month, dwarfs any of the three options, so the better question is which tool produces images clients accept, not which is cheapest. The same sum with your own numbers is in AI renders against outsourced visualisation.

Notice what the sum does not include: the time the team spends correcting images that misread the design. That goes in the test below.

Data and IP terms to read before geometry leaves the building

A BIM model holds a client's building, often under a confidentiality clause. Three things differ between the options.

• Training use. Graphisoft says it never uses project data or prompts to train its AI Assistant (beta) or AI Visualizer, and that it does not use project files, documentation or generated images for training. Autodesk says Assistant chat history and your prompt library are stored in the cloud against your Autodesk account and not used to train LLM models. Its general Assistant FAQ adds that prompts and conversation history may be kept for up to 45 days to diagnose issues (longer for support, security or legal reasons), are not shared with third-party model providers for training, and that de-identified or aggregated data may be used to improve the Assistant. For standalone vendors, find the answer in the terms and ask in writing.
• Where the work happens. Graphisoft's assistant, Spaces and Visualizer need internet access. That means a client whose contract bans sending drawings outside your network may rule out the cloud features. Graphisoft describes a local-model route through MCP; test it before promising it to a client, and note that when an outside AI app connects through MCP, that app's own terms govern the data it receives.
• Who owns the output and who carries the risk. Graphisoft's page does not address ownership of generated images. Some standalone terms push risk onto you, for example through a clause in which the user indemnifies the vendor. Read the indemnity and ownership clauses before you put generated images in a client deliverable.

Graphisoft also notes that you are responsible for keeping sensitive content and personal data out of prompts and uploaded documents. Put that in your practice's own rules; copyright and client data risks of AI in architecture practices covers the legal edges, and I am not giving legal advice, so ask an adviser about client contracts.

A ten-day bake-off on one live project

Run this on a copy of a finished project, so nothing can go wrong in delivery.

1. Days 1 to 2: questions. Ask the built-in assistant ten model questions whose answers you know, such as door counts on a level or views missing a template. Score right or wrong.
2. Days 3 to 4: documentation actions. Ask for a schedule, a set of views and one sheet. Compare to what a person would produce. Time both.
3. Days 5 to 6: concept images. Generate the same facade view in the built-in visualiser and a standalone tool, using the same sketch and the same words.
4. Days 7 to 8: stress. Ask for something the tool should refuse or say it cannot do. Note whether it admits it.
5. Days 9 to 10: sums. Count correction time, compare with the table of options, and decide.

Sample prompt and what you check

An illustrative prompt for the task-automation side:

Create a door schedule sorted by level, with columns for mark,
type, width, height and fire rating. Then list any doors with
no fire rating filled in.

An illustrative result: a schedule appears with 84 doors, and the assistant reports 11 with a blank fire rating. What you fix: open the schedule's filter and check the assistant did not exclude doors in a linked model or a work-in-progress phase. Then count the blanks yourself on one level. If the blank count differs, the filter or phase is wrong, and you have found the tool's limit in your own template.

The balcony that was never in the model

An illustration of how this goes wrong. A practice uses a visualiser to produce a facade image for a client meeting. The image shows a second-floor balcony and a different window rhythm that are not in the model. The client falls for the balcony and asks why it was removed. The fix is a rule: every AI concept image carries the words "indicative only" and goes next to a screenshot of the model view it came from, so a client can see which elements are design and which are decoration.

A four-level sheet set, by hand and by prompt

Before: a technician spends about two hours creating floor plan views for four levels, applying the view template, tagging rooms and placing them on sheets. After: the assistant is asked to build the Level 2 plan, then repeat it for Levels 3 and 4, and the technician spends about 30 minutes checking tags and sheet layout. If the checking takes longer than the building would have, the feature is not saving anything in your template, which is worth knowing before you plan around it. These times are illustrative; replace them with what your own test measures.

When a standalone tool is the wrong purchase

• When the built-in visualiser, tested honestly, produces images clients accept. You would be paying twice for one result.
• When a client's contract or your own policy forbids sending project geometry to a third-party cloud service. Ask before you subscribe.
• When the tool's terms push indemnity onto you and you cannot accept that.
• When only one person uses it and a general assistant can do the written part of the job.

When it is the right one

• When the practice mixes software, so one image tool covers concept work in SketchUp or Rhino and documentation in Revit or Archicad.
• When the built-in feature is only in a plan tier you do not own and the tier jump costs more than the standalone licences.
• When a particular style quality matters for pitches and your test shows the standalone tool wins on it.

Using Archicad's Spaces as a practice knowledge base

Spaces deserves its own test because it is the one built-in feature that can reflect how your practice works rather than how the software works. Upload documents you would otherwise search by hand, then ask questions of them. A filled-in illustration for a small practice:

Spaces uploaded (all as PDFs): office drawing standards, standard
notes sheet, specification clause library, layer and naming
convention.

Question: What is our standard for drawing numbering on a
three-storey residential job, and which note covers fire stopping
at party walls?

Check: open the cited document and page. If the answer names a
clause, find that clause yourself before relying on it.

What you would fix: a knowledge base reflects the documents in it, so an outdated drawing standard produces a confidently outdated answer. Put a review date on every uploaded file, and remove superseded versions rather than adding the new one beside the old. Graphisoft also advises keeping sensitive content and personal data out of uploaded documents, so leave client names and addresses out of the library and keep to templates and standards.

Seven questions for the reseller, in writing

• Which AI features does my exact version and plan include today, and which are beta or preview?
• What is the price difference per seat between the plan I have and the plan I need?
• Is there a trial of the higher plan on a copy of our own projects?
• What leaves our network when the assistant or visualiser runs, and is it stored?
• Is any of it used to train models, and where is that written?
• What happens to prompt history, saved prompts and uploaded documents if we cancel?
• Can an administrator turn each AI feature off for the whole practice?

The last question matters more than it looks. If a client's contract bans cloud tools on their project, you need a way to switch the feature off for the people on that job rather than relying on everyone remembering.

One line for the practice handbook

Illustrative wording: "AI features in our design software may be used on live projects only for questions and documentation tasks whose output a named person checks; generated images are marked indicative, never issued as design drawings, and never created from projects whose client contract restricts cloud tools." A line this short is easy to enforce and easy to review once a year when versions change.

Keeping the choice current across versions

Both vendors are moving quickly. Autodesk's tech preview and Graphisoft's beta labels, plus plan names such as Studio, Collaborate and Max, mean the answer you reach today may not hold at next year's release. Put a review in the diary for each annual version, and at each one re-read three things: what the feature says it is (preview or released), which plan includes it, and what the data statement says. For the tasks beyond BIM, such as checking drawing sets and notes, see AI checks for drawing sets and schedules, and for the wider hub of AI guidance, the AI guide.

If you would like help setting up the bake-off on your own models, that is part of what my AI implementation consultation covers.

Questions architecture practices ask before buying

Is Autodesk Assistant in Revit ready for client projects?

Autodesk introduced it as a tech preview in April 2026, it runs only in Revit 2027 and later, and Autodesk says AI features may not be available in every region. Use it on copies of models for questions, schedules and documentation chores you can verify, and keep a person checking every change it makes.

Does Archicad's AI Visualizer cost extra?

Graphisoft's AI page ties it to plans rather than listing a separate charge: the Visualizer is in Archicad 30 on the Studio, Collaborate and Max plans, which list 50, 50 and 250 AI credits per licence a month in a company pool. Ask how many credits an image uses before planning heavy use.

Will my project data train the AI?

Graphisoft states it does not use project content or prompts to train its AI Assistant (beta) or AI Visualizer. Autodesk says Assistant chat history and prompt library are not used to train LLM models, though its general Assistant FAQ allows prompts to be kept for up to 45 days for diagnostics. Standalone vendors vary, so get each answer in writing.

Can a standalone tool work with both Revit and Archicad?

Some can. Veras, for example, lists Revit, SketchUp, Rhino, Archicad, Vectorworks, Forma and Allplan among the programs it works with, plus a web app. That makes a standalone render tool attractive for a practice that mixes software, provided its terms suit your clients.

Should we wait for the AI features to leave preview?

Test now on non-critical work, but do not build fee proposals or delivery dates around a beta feature. Revisit at each annual version, because plan names, availability and capabilities are changing quickly in both products.

Further reads

• Can AI Help a Small Architecture Practice? Where It Saves Time — Where AI saves a small practice time beyond rendering.
• How Much Does AI Cost a Small Architecture Practice per Month? — A monthly cost view of AI across the whole practice.
• AI Tools for Architects 2026: A Toolkit From Brief to Handover — Which AI tool fits which project stage from brief to handover.
• AI Policy for Architects: A Ready-to-Use Checklist and Clauses — Clauses for an AI policy covering client data and images.
• AI Floor Plan Generation for Architects: Where It Fails a Real Brief — Where generated floor plans fail a real brief.
• AI Programs for Architects: Room Data Sheets From a Client Brief — A document job a general assistant handles well.
• Top AI Tools for Architects: Eight Compared by Job and Price — Eight AI tools matched to five practice jobs, with USD entry prices, plan limits and a monthly cost for a five-person practice.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Autodesk Revit 2027 release notes and Autodesk Assistant help articles; Graphisoft AI Solutions, Archicad plan and pricing pages and Archicad 30 AI Assistant help; Chaos Veras page; MyArchitectAI and Snaptrude pricing pages.