The Cost of AI

The Cost of AI
Beating a dead horse
Truth be told, this horse couldn't have been dead for that long either. The whole Agentic thing is no more than a couple of years old, right? Just think about your personal first touch with the Agent - was it a Midjourney fling back in 2024? I wasn't using Claude Code well into 2026.
So, the point I want to make in this post should be fairly new - and at least to me, it is. Even though it feels so obvious, and so redundant, and so outdated at this point:
AI is a tool, don't let it take away your creativity.
And why is that? Because I am (you are) lazy. We are optimization machines; we know how to cut a corner if we see one. But a lot of times, the point is that things need to be hard, to be worth it. Learning, for example - it turns out that when the process feels hard, that's when it really matters, that's when learning occurs.
When you sweat.
When you suffer.
And what's creativity if not a constant struggle, a battle with the unknown, with the uncertainty. The fear of being judged for being novel. And what is AI? A pattern regurgitation algorithm that gives you the mean result, the average. Not only does it require something already existing (check out how an AI attempted to cheat on StarCraft by stealing a human's work), but it kind of is the middle of the road.
As a result, I am now skipping any post that reads like:
Especially if something in that post has just "landed" somewhere "quietly". Because this tells me 2 things about the person behind the post:
- They are lazy
- They are scared
And perhaps there is little I want to learn from that person.
What I do want to see is that someone spent actual time! Has suffered, has sweated, has cared for the product that came under their fingers. Even if it's flawed, even if it's imperfect.

And, in the immoral words of my dear friend, ChatGPT - "And here is why this is important".
What are we paying for?
I am far from saying that AI is of no use. Or harmful, or that it should go away. It's like arguing that electricity is bad for us, that roads are harming the environment, or that internet was an invention of Satan.
AI is infrastructure
That's my hot take. It's not that hot either ... not even lukewarm. But blaming infrastructure is like blaming the weather - it's pointless, yet you can't help it, now can you mate.
So, it's really the cost of that infrastructure I am discussing here. And it's up to you what you use yours for and if you have the money to support it. You can look at funny cat videos all day every day, but the moment they start charging per kitty token, then .. well you'll swap over to dogs, if that's still free.
From seats to usage ... to ?
It used to be that we pay once and we own the damn thing. We then started paying for the update - that's fair, someone works to make it happen after all. Then what? Right - subscription time - and I don't need my click-to-cancel-you-Adobe. But ... we found the value in that as well, didn't we? So, sure thing. Give me them 10 seats of your best software, kind Sir, and thank you very much! I can now do a yearly budget that looks scary, but at least somewhat predictable.
Enter usage. 5 tokens. 100'000 tokens. Your cooldown period ends in 5 hours.

I don't want to make a huge literature point around this - it's as simple as "you cannot predict your usage". You get cut off mid-stream, you can't finish what you started, or at least not in time. And you become vulnerable to a payment model you have no control over.
And this is why it's important.
The thing is, much like before, the price is justified .. in a way. Someone's got to pay the piper, at the end of the day. Autodesk hinted at this: about 17% of its revenue already comes from usage-based models, and its CFO has said heavier AI automation will be priced on usage too (the official Autodesk Q4 FY26 Earnings Call can be found here). But that's not the end of it. Autodesk is changing the Data Model API pricing too - from October 6th, anything pulled out of the AEC Data Model beyond your subscription's allowance gets metered (Data Model APIs included with subscriptions, plus flexible ways to scale). There is that additional cost we need to think about. Because this is how it goes (and where it came from):
We pay Autodesk -> Autodesk pays Amazon for AWS / Amazon Bedrock -> Bedrock serves the frontier models behind the Autodesk Assistant
The practical thing to do is this - check your allowance, audit what pulls from the AEC Data Model.
The main problem, the way I see it, is when those frontier models start becoming more expensive. The above cascade will remain, and our already uncertain bill will have to readjust.
There is a counter argument to be made here - the cost of AI is not static. We could make the assumption that, so far, it was the tech money bankrolling the initial stages of the AI infrastructure - Microsoft, Google, etc. However, this process has had the effect of decreasing the cost of compute already. Here is a self-explanatory image from a very informative article by Ruben Hassid from How to Ai:

According to this research, the cost of AI is decreasing at such a rapid pace that it will soon be "too cheap to meter".
Is AI the new UI?
My main point is this - let's try to be reasonable. I try not to use AI for things that I can use traditional toolage for. If there is a button for it - use the button!! Don't type it in a chat box if you can clickity-click-click your work in the same amount of time.
In that regard, I distrust AI wrappers replacing identical and already existing functionality. Anything you can already do and doesn't take much time - just skip the AI offer altogether, I sincerely believe that it is not worth it!
On the other hand, if AI is indispensable to a novel workflow you simply can't do without - no brainer, use that AI path! Combining multiple steps into a cohesive workflow - right on, friend! Even when giving a much simpler user interaction to a complex interface - count me in, as I believe this is another valid case for the use of AI.
My rule of thumb
Autodesk Assistant (AA)? Yes, sir! Autodesk is clearly positioning it as the thread that runs through its whole platform. At AU 2026 it previewed an agentic Assistant working across Forma, Fusion and Flow, plus Assistant Builder, a way for customers and partners to plug their own agents into it. Arcadis is already doing exactly that, connecting its own MCP tools to Autodesk Assistant "while retaining full ownership of what it builds". My read: AA is about to become the glue that binds Forma together.
As of Revit 2027, AA ships with Revit, folded under your existing bill - use, use, use! And if that's not enough, or you are worried that the AA is "too safe" and won't do any write requests, Dynamo now has a read-write MCP that you can absolutely make use of! (The read-write comes not from the MCP itself, but from the fact that you can use the MCP to compose a Dynamo graph that will then execute the write task for you).
In general:
If it's 10 times faster, and if I can trust the output, and if I can double-check it - then use it.
Good use cases:
- (vibe) Coding - absolutely outstanding, but you have to remain the architect
- Research - deep or wide
- Document formatting, document checking, second pair of eyes
Bad use cases:
- Authoring emails, social media, blog posts
- Design authoring
- Ideation and reasoning, as the final judge (sparring partner is totally cool in my book)
Anything that serves me and saves my time - yes! Anything facing outward - nah, not so fast little agent.
Why is that? Because, for heaven's sake, what are we even doing here? The freaking Matrix?! I didn't create a life and a career to be lived by some swarm of agents. I want my life to be lived by me, fully. That includes any creative endeavours, and mostly my interactions with others.
If anything, the last couple of years have made it easier to come to terms with my personal imperfection. I don't know about you out there, but this kid right here - far from a finished product! I bring so much crap with me, all the time. And my emails suffer from it. And my social persona suffers from it. And so, I burn bridges. But at least I get to live my version of this life.
A smart way to use AI in the AEC industry
The way forward is this, in my opinion - use AI as an agent of democratization of code creation. Where possible, automate your own workflows using the frontier model of your flavour, to the expense you are comfortable with. Vibe code. Create workflows. Connect APIs in a way that you wished you could in the past but didn't have the capacity to do, or the time, or money. Use the awesome, free MCP servers available both from Autodesk, and free 3rd party community or proprietary efforts. Wrap it in a robust old-school software, cloud-based or otherwise. Make sure you know your long-term spend, once the AI layer is no longer there. And have fun doing it!
Final words
I realize the above reads a bit personal. And that's because it is. I am an early adopter, a fast consumer of tech, a firm believer in BIM way before BIM was cool, and I dislike hype. As such, I don't see a future without AI, but in the current state of affairs (circa end of 2026) there is so much nonsense in the air, that even my FOMO has a fear of missing out.
You can find a structured and practical guide on how we in Archilizer use AI in our latest blog post: AI in Architecture: A Practical Field Guide for Practice Leaders. I did say it was practical.


