Behind the scenes · AI in the studio

How AI Speeds Up Our Work (and Where We Don't Let It Decide)

Daniel Hauser
· 3 min read
How AI Speeds Up Our Work (and Where We Don't Let It Decide)

The website you're reading right now was built in two days. Eight languages, fourteen projects, five service pages, an enquiry form with emails, and structured data for search engines. Not because we were in a rush, but because we work with AI differently than we did a year ago.

2 daysfrom brief to a website in 8 languages
7translations running in parallel
168URLs checked by script
1human who makes the decisions

AI as a colleague, not a button

We don't use AI to "generate a website". We work with an AI agent that can read code, run commands, open a browser and check its own work. It gets its brief in Czech, like a colleague would: "look at the old site, carry over the content, show more visuals and add our websites". Then it asks questions, makes suggestions and shows work in progress.

The difference lies in who does what. Daniel sets the direction, the taste and what's true. The agent handles the routine that would otherwise take a person hours: downloading and converting images, taking website screenshots, translating, checking, and making repetitive edits across dozens of pages.

DHMO website homepage
This website: from the first brief to eight language versions in two days.

How we work

  • Brief and research: the agent goes through the old site and source materials, downloads the visuals and writes up what it found.
  • Design and build: design and code take shape piece by piece, and we review every step in the browser.
  • Translations: seven languages run in parallel, each in its own agent, with automated checks that nothing is missing.
  • Quality control: scripts crawl every page, link, SEO setting and HTML validity. Errors get fixed before the client ever sees them.
  • Versioning: every change is saved to the history on GitHub, so anything can be rolled back at any time.

What we built to make it work

The model alone isn't enough. Over time, we've built an environment around AI in which it delivers reliable results:

  • Project memory and rules: whatever the agent learns or we tell it ("don't mention this number", "never build while the dev server is running") it still remembers the next day.
  • Custom check scripts: an SEO audit of every URL, a check for untranslated text, and measurements to catch overlapping elements at any screen width.
  • Our own tools: ClientDeck for running marketing with an AI audit, and our own hosting panel that deploys the website straight from GitHub.
  • Automated screenshots and images: screenshots of client websites, and photo optimisation for both the web and email.
Service page in German
Every page exists in eight languages. Translations are also guarded by automated checks of structure and untranslated words.

Where AI doesn't get the final say

This is the important part. AI is fast, but left unsupervised it can make things up. That's why a few firm rules apply:

  • No invented facts. Numbers, references and claims about clients are supplied and approved by a human. If we don't know something, we'd rather not write it.
  • Decisions on concept, taste and tone are made by Daniel. AI offers options, not the outcome.
  • Irreversible steps, such as deleting, deploying or sending, are always confirmed by a human.
  • Every text and every screen goes through human review before a client or the public sees it.
AI isn't taking our work. It's taking the boring part. We put the time saved into ideas, details and conversations with clients.

What it means for clients

Shorter timelines and more options to compare. Fewer errors, because checks run automatically and thoroughly. And above all, more time for what AI can't do: understand what the client truly needs and design it so that it works.

Have a similar project?

Write a few lines about what you need. I will get back to you personally.

Discuss a project

More articles

Rebon: a brand for a product the customer does not understand

Rebon: a brand for a product the customer does not understand

How to design a brand and a store for domestic water filtration so a layperson grasps what they are buying. From the logotype through product visuals to the design of the whole site.

A website that AI can read: what it means for design and build

A website that AI can read: what it means for design and build

A good-looking page can reach a machine empty. Four design decisions that cause it, and why none of this means building boring websites.

Google will take your videos itself. The brand stops deciding what represents it

Google will take your videos itself. The brand stops deciding what represents it

Since 23 October, Performance Max can pull up to ten videos from your social accounts and site into your ads. This is not an ad setting, it is a question of running a brand.

A Brand That Can Take Several Markets

A Brand That Can Take Several Markets

In an expansion the brand usually breaks before the campaigns do. What has to stay the same in every country, what has to bend, and why it is decided at the first pack rather than at the fifth market.

Packaging That Has to Work as a Thumbnail Too

Packaging That Has to Work as a Thumbnail Too

Most people now see packaging first as a small square in a comparison listing, not on a shelf. What survives being shrunk, what is lost, and why it has to be decided before anything is drawn.

Handmade vs AI-Perfect: Why Imperfection Is Coming Back

Handmade vs AI-Perfect: Why Imperfection Is Coming Back

When anyone can generate a smooth visual, smoothness stops meaning care. What that does to brands, where we let AI into our work and where a hand still touches paper.

Small Studio or Big Agency? What You're Really Paying For

Small Studio or Big Agency? What You're Really Paying For

Why one experienced person with modern tools and a network of specialists often delivers more than a big agency, and why clients keep returning for years.

AXA Racing: Three Brands, One Website, a Custom Platform in Days

AXA Racing: Three Brands, One Website, a Custom Platform in Days

How we merged data from Polaris, CFMOTO and GOES into one dealer website with its own admin. Built on Next.js, first version live in three days.