Urban Web Host
How we actually work
“AI-assisted” can mean a lot of things. Here's specifically what it means when you book a session with us.
The brief comes before the session
Every engagement starts with a structured intake, turned into an internal engineering brief. Your engineer walks in with context — the session isn't spent re-explaining what you already told us.
AI-assisted, human-judged
Our engineers use AI coding tools deliberately — for speed on well-understood problems — but every line that ships is reviewed by the engineer running your session. The AI doesn't get the final say.
Scope is explicit, always
What's in a session is agreed before it starts. If the work grows beyond that, it becomes a new booking or an approved change request — never a silent scope creep you get billed for later.
Deliverables are inspectable, not just described
Working code, repo links, and deployment records land in your workspace as the session happens — you can verify what was built, not just take our word for it.
Security is part of the build, not a phase after
Credential handling, access scoping, and basic hardening are considered during the session itself, not bolted on afterward.
Drawing the line precisely
Where AI helps, and where a human always decides
AI accelerates
- Boilerplate, scaffolding, and repetitive code patterns
- Drafting tests once the approach is agreed
- Searching a large or unfamiliar codebase quickly
- First-pass documentation and comments
An engineer always decides
- What actually gets built, and why
- Whether generated code is correct, secure, and worth keeping
- Anything touching credentials, payments, or user data
- What ships in your session, and what doesn't
This is the same distinction behind our Rescue AI Projects service — most of what we fix is code an AI tool wrote unsupervised.