Independent AI engineering studio
AI systems that ship and keep working
A one-person AI engineering studio. The same engineer designs the system, builds it, and stays to keep it working.
Inside the engineering — recorded on a real AURAZ TECH build, not a mock-up.
What we build
Three problems we get asked for most
Every engagement starts with the same question: what is this actually costing you?
Retrieval that admits ignorance
Chatbots grounded in your documents that cite their source and refuse cleanly when the answer is not there.
Voice that hands over well
Agents that qualify, book, and pass to your team with the context already collected.
Automation that stays auditable
A human checkpoint before anything irreversible, and a failure log you can actually read.
What we build
Seven things we are asked to build
Most clients arrive with a sentence, not a service name. Start with the sentence that sounds like your week. Open it when you want the full scope, the deliverables and the honest limits.
The index
07 SERVICES
- Website DevelopmentWe get visitors, but no enquiries.
- Web App DevelopmentThe business runs on spreadsheets and email.
- AutomationWe retype the same data between systems every week.
- RAG Chatbot IntegrationCustomers ask the same questions and we answer them by hand.
- Voice AI AgentsWe miss calls because nobody can pick up.
- AI-Driven Design and Content GenerationWe need to publish consistently without a designer.
- HostingOur site goes down and nobody notices.
Not sure which one fits?
Describe the problem rather than the solution. A short call is usually enough to point at the right first step, even when that step is smaller than you expected.
Watch first
Ninety seconds with the people who would do the work
A short film about how we work and what we would build for you. Sound on — it is worth hearing.
Right-click or long-press the film to pause. Your next click resumes it.
Sound on / No sign-up
What we build with
A stack we can actually defend
Every tool below is one we use to deliver work. If we say we can build it, it is because this is how we build it.
- HTML
- CSS
- JavaScript
- TypeScript
- React
- Context7
- Tailwind CSS
- Next.js
- Generative AI
- Agentic AI
- Digital FTEs
- ElevenLabs
- n8n
- Cursor
- OpenCode
- ChatGPT
- Claude
- Gemini
- Designing
- Canva
- Image Generation
- NotebookLM
- Google Flow
- Agent Factory
24 tools
The list changes when the work changes.
How we work
Six things that are different here
Not claims about quality. Working practices you can hold us to, stated plainly enough that you could tell us we were doing them wrong.
No account manager in between
You talk to the person writing the code. There is no account manager between you and the engineer who has to make the thing work.
Plain language, before proposals
You get a written explanation of what we would do and why, in words you can check, before anyone mentions a price.
Documentation as part of the work
Every engagement ends with a handover session and written documentation. Not a separate line item, and not optional.
No lock-in by design
The code lives in a repository that belongs to you. Any competent developer can pick it up from what we leave behind.
We say no sometimes
If a smaller first step serves you better than the full build, or a feature is not worth its running cost, we will tell you.
Accessibility is not a phase
Contrast, keyboard operation and screen-reader support are built into the components from the first commit, not retrofitted.
By the numbers
What we can tell you honestly today
Every figure here is counted from the work itself rather than claimed, which is why we will not put a client-result number on this page. We answer enquiries within one business day.
How an engagement runs
No surprises about how we work
The sequence below is the same whether the project is a website or a voice agent. You always know which step you are on and what you get at the end of it.
The line fills as you read, and each step lights up when the connector reaches it — so the four stages read as one movement rather than as four separate blocks.
Discovery first, always
Before any estimate we document how the work actually happens today. The written output is yours even if you never build with us.
A written description of the problem
Prototype before commitment
For anything beyond a website, you see something running before the full build is funded.
Something you can click, before you commit
Fortnightly reviews
Short cycles with something working each time, so a wrong assumption surfaces in two weeks rather than two months.
Working software every two weeks
Handover, documented
Recorded walkthrough plus written documentation. Ordinary, not an event.
A repository, a recording, and written docs
Who you work with
One person, not a department
Every AURAZ TECH project is designed, built and delivered by the founder directly. There is no account manager between you and the person responsible for whether it works.
Read our story
Also from us
AURAZ ACADEMY
The same work, taught openly. Our YouTube channel covers the engineering behind these services, including the parts that go wrong.
Watch on @aurazacademy
Next step
Tell us what you are trying to do
A short description of the problem is more useful than a detailed specification. If you are not sure what you need, that is completely fine.
We reply within one business day.