Where AI-assisted tooling helps, where it does not, and why the creative decisions stay with a person.
Most studios are quiet about this, which is odd, because clients are asking. So here is a straight answer: yes, we use AI-assisted tooling. Here is exactly where, exactly where we do not, and why the distinction matters to what you get.
Two reasons. You are paying for the result, and you are entitled to know how it was made. And the studios being coy about it tend to be the ones using it worst, because pretending you are not using a tool means never developing judgement about when it is wrong.
The repetitive parts. Every site needs a great deal of code that is necessary and completely unoriginal. Form handling, responsive layout scaffolding, the plumbing that makes a contact form send reliably. Nobody's website is better because that was typed by hand.
Checking work. Reading back over your own code is a poor way to find your own mistakes, because you read what you meant rather than what you wrote. A second pass catches the small things: an unescaped output, a missing edge case, a form that breaks on an apostrophe.
First drafts of structure. Getting from a blank page to something to argue with is faster than getting from a blank page to something finished. The draft is almost never what ships, but it is a better starting point than nothing.
Doing the boring thing properly. Mapping ninety redirects during a migration, or checking every page for a broken link. This is exactly the work humans skimp on when tired, and skimping is how a rebuild loses its rankings.
Knowing what your business needs. No tool can sit in a conversation, notice you mention the same customer complaint three times, and work out that it belongs on the homepage. That comes from listening, and it is most of what makes a site work.
Deciding what the site should say. Anything generated will produce competent, generic copy that reads like every other site in your industry. The thing that makes your site persuasive is usually specific: an oddity of how you work, a number you can stand behind, a way of explaining something nobody else bothers with. Those come out of your head, not a machine's.
Design judgement. What the visitor sees first, what gets cut, what earns the largest thing on the page. Those are decisions about your business, made by someone who understands it.
Knowing when something is wrong. This is the important one. These tools are confidently wrong on a regular basis, and confidently wrong code looks exactly like confidently right code. Everything gets read, tested and understood by a person before it goes near your site. If we cannot explain why a piece of code is there, it does not ship.
Entirely with us. If something breaks, "the tool wrote it" is not an explanation, it is an excuse, and it would not be one we would accept from a contractor either.
Everything on your site is something we have read, understood and are prepared to defend. That is the actual standard, and it does not change based on how any particular line got typed.
In practice it means builds come in faster than they would have five years ago, and the time saved goes into the parts that need a person. More time on what the site should say. More time testing on real devices. More time on the migration work that protects your rankings.
It does not mean cheaper by default, because the expensive part of a website was never the typing. It was working out what to build, and that has not changed.
If you were hiring us and asked this question, the answer you deserve is: we use good tools, we understand everything we ship, and the decisions that shape your site are made by a person who has spoken to you.
That is what we would want to hear, so that is what we say. More on how we work is on the about page, and if you would rather just ask, get in touch.