An architect who builds.
Thirteen years in software, six of them as an architect, the last three putting AI into production. One person, start to finish.
Who I am
I'm Alex. I have spent thirteen years building software that other people depend on, the last six as an architect, deciding how systems fit together and what happens when they fail. For the past three years my work has been AI in production: agents that draft offers from live data, assistants that answer from a company's own knowledge, workflows that move work between tools without a person copying it across. Not demos. Systems that run every day, with logs, limits and someone accountable for them.
Archiwright is the name I work under as an independent consultant. It is one person. When you write, I read it; when something is built, I built it.
How I work
Listen first
Calls and emails until I understand how your business actually runs, not how the org chart says it does.
Find the manual work
The small repetitive tasks nobody was hired for and everybody does. They are where AI pays off first.
Build what holds
Designed like production software: clear access, approvals where they matter, tests, logs, documentation. The boring parts are what make it safe to rely on.
Hand it over
Everything runs on your accounts and belongs to you: code, data, domain, documents. Documented so another engineer could pick it up. If we stop working together, nothing stops working.
Why the name
An architect designs the structure. A wright is someone who makes things: a shipwright, a wheelwright. Most AI advice stops at the first half. I wanted a name that promised both, the thinking and the building, from the same pair of hands.