Studio hours 09:30–18:30 IST · +91 80 4718 2260
Studio · established 2016 · ten years in production
Urban Coding Labs is a small engineering studio. We take a product brief and carry it through design, build and the boring part nobody sells you: hosting, permissions, migrations, and someone answering when it breaks at 2am.
What we take on
Most briefs are a mix of all three. We would rather do those well than offer a mobile app, a chatbot and a blockchain pilot.
01
Marketing sites, campaign pages, documentation.
Sites that load fast on a phone on mobile data, rank without tricks, and can be updated by the marketing team without opening a ticket. Built as a component system, not a page pile.
What ships
02
Internal tools, dashboards, platform products.
The system your operations team lives in all day. We model the workflow first, then build the screens around it — with audit trails, roles and the exports people keep asking for in month six.
What ships
03
Member, dealer, student, patient and vendor logins.
Portals fail on the unglamorous parts: thousands of accounts, forgotten passwords, documents per role, payments and the report a director wants on Friday. That is the brief, and it is the one we like.
What ships
Ten years
The studio opened with two people and one client who needed a booking system. Ten years on, the same discipline applies: ship in slices, keep the logs readable, and never leave a customer holding a system nobody maintains.
Ten years is the useful part of a portfolio. It means we have seen our own code through a price increase, a database migration, a rebrand, three hosting moves and a shutdown nobody planned for — and documented what broke each time.
Nothing here is a case study written after the invoice. It is work that is still answering the phone.
10years
Continuous delivery since 2016
Same studio, same phone number.
184
Releases shipped
Average 18 per year across active products.
41
Products still running
Built by us, maintained by us.
3.8yr
Median client relationship
Longest: nine years and counting.
2016
Studio opens
Two engineers, one booking system for a 40-clinic chain, and a spreadsheet that ran billing for three years.
2018
First portal
A dealer network of 1,200 logins. Learned the hard way that permissions belong in the database, not the UI.
2020
Everything remote
Rebuilt hosting so clients could work from home. Moved 30 products to managed containers with proper backups.
2022
Platform team
Started shipping one codebase to many sites: the campus platform now runs 7 institutional rebrands.
2024
Ten-person studio
Added a dedicated operations rota. On-call stopped being whatever the founders were doing on Sunday.
2026
Year ten
184 releases, 41 products live, and a written runbook for every one of them.
What we build with
We pick boring technology on purpose. If your project needs something new, we will say so and say why.
How the work goes
Every stage ends with something you can open, read or click. Nothing gets built on a description of a description.
01
3–5 days
One working session with the people who will use the system, not just whoever signed the contract. Output: a written scope, the data model, and a list of what we are deliberately not doing.
02
1 week
Screens in greyscale, the API surface, the permission matrix, hosting shape and cost. Reviewed before a line of production code exists, because changing a diagram is cheap.
03
the bulk of it
Something demoable every Friday on a staging URL you can open. Tests around the flows that move money or data. You see the product grow instead of a reveal at week twelve.
04
ongoing
Runbook, credentials in your vault, admin training, monitoring dashboards. Then a retainer if you want one — or a clean exit with the repository and infrastructure in your name.
Selected work
Names shared with permission. Metrics are from the client’s own analytics or our monitoring, taken at the time of writing.
Portal development
2023
Regional auto components network
1,240 dealer logins moved off email and a shared Excel file. Order placement, credit limits, scheme payouts and per-dealer document vaults.
Website development
2022
Education group, 7 institutions
One codebase, seven sites, per-institution theming and content approval. Marketing teams publish without engineering help.
Software development
2021
Cold-chain distributor
Dispatch board, driver app, temperature exception alerts and freight billing. Runs the daily movement of 300 vehicles.
Portal development
2019
Multi-city clinic chain
Appointment history, reports per patient, consent tracking and staff role boundaries. Built with an audit log on every read.
Portal development
2024
Professional association
Renewals, tiered dues, invoice reconciliation and a committee console. Renewal window now handles 4,000 members without a spreadsheet.
Website development
2020
QSR franchise, 210 outlets
Per-outlet menus, regional pricing and a locator that survived being linked from a food-delivery aggregator during a sale weekend.
Ask for the full reference listClient references available on request
In their words
We had been through two agencies before. The difference was that UCL wrote down what they were not going to build, and then stuck to it.
Our marketing team publishes every day now. I have not opened a Jira ticket about the website in fourteen months.
They handed over the infrastructure, the vault and a runbook on the last day of the project. Nobody does that.
Ways to work with us
All of them include a written scope before anything starts, and all of them let you leave with everything in your name.
One product, defined outcome, dated launch.
from ₹2.4 lakh
A roadmap that changes as you learn.
from ₹5.2 lakh / month
Someone else built it and it has to keep working.
from ₹45,000 / month
We do not quote without a discovery session. Anyone who does is guessing, and you will pay for the guess later.
Questions we get
A marketing site with a real design system, CMS and performance work starts around ₹2.4 lakh and takes four to eight weeks. A brochure page with no content workflow is cheaper, and we will say so if that is what you need.
Often. We join as the product engineering layer, work inside your board and repository, and write documentation your developers can pick up. Several retainers are exactly that arrangement.
Nothing, because you never needed us to be there. Repositories, cloud accounts, domains and data are in your name from day one. Handover includes a runbook and a rehearsal of a restore.
Roles and permissions enforced in the database layer, secrets in a vault you control, dependencies updated on a schedule, audit logs on any read of personal data, and off-site backups tested quarterly rather than assumed.
Yes, and roughly a third of the work is that. We start with a two-week paid audit: architecture, code, hosting and risk list. After that you decide whether to rebuild, extend or stay.
Discovery usually begins within two weeks. Full builds queue by quarter — December currently has two slots open.
Contact
One form, one email, one phone number. An engineer reads every enquiry and replies within one working day — including the ones we are not a fit for.
Phone
Studio hours 09:30–18:30 IST, Monday to Friday. On-call for retainer clients runs 24/7.
Studio
Level 3, 44 Cotton Court
Ashok Nagar, Bengaluru 560025, India
Visitors by appointment — there is no reception desk.
Elsewhere