Gustav I work across 3D visualization, software development, and automation - three domains that are being changed by AI at different speeds and in different ways. So I have a fairly clear view of where AI tools genuinely compress timelines, and where they are more noise than signal.
This is not a general take on AI productivity. It is specifically about how I use these tools in client work, and what that means for what I can deliver and how fast.
Research and scoping: where the biggest gains are
The first phase of any project - understanding the client's context, researching the domain, mapping what already exists and what needs to be built - used to take a significant chunk of time. For a software project, that might mean reading documentation, reviewing existing integrations, understanding the client's industry well enough to make good decisions.
AI has compressed this more than anything else. I can now get a solid understanding of a domain I am less familiar with in an hour rather than a day. I can cross-reference documentation, identify the most relevant APIs or tools, and arrive at the first scoping call with a much clearer picture of what is realistic.
The judgment about what to build and why remains entirely mine. But the background research that informs that judgment is dramatically faster.
Development: faster iteration, not replaced thinking
For software projects - custom tools, AI pipelines, automation systems - AI coding assistance has changed the rhythm of work more than the depth of it. The boilerplate that used to take an hour to write correctly takes ten minutes. The integration with an API I have not used before is faster to get working because I can iterate on the implementation with immediate feedback rather than reading documentation linearly.
What has not changed: the architecture decisions, the understanding of what the client actually needs, the edge-case handling, the security considerations. These require exactly as much thinking as they always did. AI can write code quickly. It cannot decide what the code should do.
The practical result for clients is that simple custom tools which might have taken two to three weeks now take one to two. More complex systems compress by a similar ratio. The quality ceiling has not changed - if anything it has risen, because I spend less time on mechanical tasks and more on the decisions that actually matter.
3D and visual work: different tools, different impact
In 3D visualization, AI tools have had a more targeted impact. AI-assisted texture generation, upscaling, and some parts of the post-processing pipeline have sped up specific tasks. But the core of 3D work - modelling, lighting, composition, the judgment calls about how something should look - is not something current AI tools replace or meaningfully accelerate for professional-quality output.
Where AI has genuinely helped in visual work is in the earlier stages: generating reference mood boards quickly, exploring colour and style directions in minutes rather than hours, and writing the scene descriptions and content that accompany visual deliverables. The visual work itself remains hand-crafted.
Client communication and documentation
This is an underrated area. Project proposals, scope documents, status updates, handover documentation - these are necessary, time-consuming, and rarely the most interesting part of a project. AI drafts a solid first version of most of these in a few minutes. I review, adjust the specifics, and send. What used to be an hour of writing is fifteen minutes of editing.
For clients, this means cleaner documentation, faster turnaround on proposals, and more thorough handover material - without that time coming out of the budget for the actual work.
The honest summary: AI compresses the mechanical and the routine. It has no effect on the quality of the thinking, the experience that informs decisions, or the judgment that separates good work from average work. Those still take exactly as long as they always did.
What this means if you are a client
Faster delivery does not mean cheaper work. It means the same quality of thinking and judgment is applied in less elapsed time - which has value in its own right. A project that takes three weeks instead of six means you can act on it three weeks sooner. In most business contexts, that time has real economic value.
It also means I can take on projects with tighter deadlines that I would previously have had to decline. If you have a launch date that is non-negotiable, that changes the calculation of what is possible.
What you are getting from any project I deliver is not just the output - it is the accumulated judgment from working across these domains for years, now delivered with the speed that current tools make possible. That combination is the thing worth paying for.
If you want to talk through a specific project - what it involves, what a realistic timeline looks like, and how I would approach it - get in touch. I keep scoping conversations short and direct.