We build the systems businesses run on.
Software, internal tools, and AI workflows. Shipped to production and supported after launch.
- OpenAI
- Anthropic
- Supabase
- Postgres
- n8n
- Make
- Slack
- Stripe
- Cal.com
- Google Workspace
What we do
Four things we build.
Software Engineering
Custom web applications, APIs and integrations, SaaS feature sprints, and modernizing systems that have outgrown themselves.
02AI Systems
Agents, retrieval and knowledge systems, document and data extraction, plus the evaluation layer that tells you whether any of it works.
03Internal Tools
Admin panels, dashboards, and workflow automation. The tools that replace the spreadsheet everyone quietly hates and the Notion nobody can find anything in.
04Web Platforms
Conversion-focused websites, lead systems, headless CMS, and the analytics and attribution to tell you what actually worked.
Selected work
Recent projects.
AI systems
Most companies have the AI tools. Almost none have them in production.
We build named systems with a defined job, wired into your tools, with evaluations so you can see whether they work.
Support Agent
Answers customer questions from your real documentation and ticket history, and escalates to a human when it isn't confident rather than guessing.
Replaces the first-response queue
Sales & Lead Agent
Qualifies inbound, answers pre-sales questions, books into your calendar, and hands warm context to whoever takes the call.
Replaces leads going cold in an inbox
Document Extraction
Turns invoices, contracts, applications, and forms into structured data your systems can act on, with a confidence threshold and a human review path.
Replaces manual data entry
How we work
How a project actually runs.
01
Scope
A conversation, then a written summary of the problem and what success looks like.
Week 0
02
Architect
We map the system, name the constraints, and send you a fixed quote with milestones.
3–5 days
03
Build
Sprints with working demos, not status reports.
2–6 weeks typical
04
Operate
Documented handover, your repo, your accounts. Then optional ongoing support.
Ongoing
Writing
Notes on the work.
Why most AI projects die between the demo and production
The demo takes an afternoon. The deployment takes three months, and almost nobody scopes it. Here's the work that sits in that gap, and why skipping it is how AI projects quietly fail.
What we hand over at the end of a project
Most agencies describe handover as a stage. Here is the actual contents of ours — architecture summary, runbook, access inventory — and why each part exists.
Automation, internal tool, or AI agent?
Three different answers to 'this process is eating our time', with very different costs. A decision framework for working out which one your problem actually needs.
Who you’ll work with
You’ll talk to the person who builds it.
No account manager, no handoff to a junior team after the pitch. Hanzla Nouman leads every engagement: scoping, architecture, and the code that ships.
Hanzla Nouman · Founder & Principal Engineer
About the studioQuestions
Before the first call.
How big is your team?
Small and senior by design. Engagements are led and built by the founder, with specialist collaborators brought in for design, content, or infrastructure when a project needs them. You will always know exactly who is working on your project.
What does an engagement cost?
Every project is quoted at a fixed price after the Architect stage, so you approve a number before anything is built. Audits are fixed-price and scoped to two weeks. Ongoing support is monthly and cancellable.
How long does it take?
Most builds run two to six weeks. Audits are two weeks. We give you a date range in the quote and tell you early if anything threatens it.
Do we own what you build?
Yes. Your repository, your hosting, your accounts, your data, from day one rather than on final payment. We hand over documentation and we don't build dependencies on us.
What happens after launch?
A documented handover: architecture summary, runbook, and access inventory. From there either you run it or we do. Both are fine, and we'd rather you chose than defaulted.
Do you work with companies outside your usual size range?
Sometimes. If a project isn't a fit we'll say so on the first call and point you somewhere better rather than take it on.
Have something that needs building?
Tell us what's not working. If we can help, we'll say how.