Izafa — Urdu for advancement, increase
Izafa Labs: software studio in Jaipur
A software studio in Jaipur, run by Mukesh Purohit. Seven stops, seven questions answered.
§ 01 · Patrika Gate · Jaipur · serving all of India
Opening clause
I build the software a business runs on — and I don’t walk away when it ships.
I’m Mukesh Purohit — a website developer and software engineer based in Jaipur, building for clients across India. You get the build and the structure around it — payments, agreements, data architecture — from one person.
What I build
Storefronts, booking systems and the internal tools a business runs on, for clients anywhere in India. The work keeps getting better long after the invoice clears. Websites · custom software · portfolios · startup MVPs.
First reply
First reply within 4 business hours · IST · Mon–Fri.
§ 02 · Jal Mahal
The offer
One person. Both halves of the problem, handled by the same head.
Most web development studios stop at the code. I don’t — I write the contracts too.
Background
Before starting this software development practice in Jaipur, I was Head of Operations & Legal at a financial services firm. I hold a master’s in corporate & finance law. That competence shows up where it’s useful: in clean scoping for startup founders, in service agreements written against the actual build, in payment terms that don’t leave you stuck.
i. The build · code
Production software — shipped against an architecture, not guesswork.
A storefront with persistent audio. A legal SaaS that survives courtroom Wi-Fi. The artifact you can run.
ii. The structure · contract
Clean scoping, clean contracts, clean handover — nothing held back as a hook.
Repositories, infrastructure, credentials, runbook. You own every asset at handover. If you want me out, you can get me out.
§ 03 · Johari Bazaar · INR
Published prices
Tagged, not hidden.
Known shapes start at a published price. Pick one to ask about it.
§ 04 · Jantar Mantar
How it works
A quiet sequence. One that doesn’t end at handover.
01 · Two doors · two ways in
Known shape? Fixed scope, fixed price, we start.
A storefront, a booking system, an AI-search presence — builds whose shape is already known start at a published price and a published timeline, no discovery fee. Unknown shape? Two weeks of paid discovery first: I map your system on paper before any code is written, and the drawing is yours either way — with a fixed-price quote, whether or not you build it with me. Operations systems typically land at ₹75,000–₹2,00,000; the drawing decides.
02 · Build · scoped · fixed
Build — against the architecture, not against guesswork.
Production websites and software shipped against the agreed scope. Weekly written updates, no agency theatre. The stack is chosen for the problem and never sold to you.
03 · Handover · ownership · clean
Handover — you own every asset.
Repositories, infrastructure, credentials, runbook, contracts and data schema — handed across. No lock-in, no proprietary middle layer only I can maintain.
04 · And then · still advancing
It doesn’t stop.
The work keeps advancing. On the Advance Retainer, improvements arrive on a schedule and are guaranteed in writing; under the AMC, the system is kept patched and watched. A studio of one, treating every project as part of its own permanent body of work, has every reason to keep it good.
§ 05 · Chand Baori
Operating notes
Why this isn’t a generic firm.
i.
Documentation is part of the handover.
Every build ships with a written runbook: how it’s structured, where the levers are, what to do when something breaks. Not a README — a document a non-technical owner can read.
ii.
No lock-in.
You own the repository, infrastructure, credentials, database, and contracts. Nothing is held back as a maintenance hook. If you want to leave, you can.
iii.
The stack is chosen, not sold.
Next.js and Supabase, because they fit the problems I take on. When they don’t fit, I say so. No resale incentive bends the recommendation.
iv.
The work is improved after delivery.
Inside the Advance Retainer, improvements are scheduled and guaranteed; the AMC holds the maintenance floor. Anything beyond those is scoped and priced in writing first.
§ 06 · Hawa Mahal
The operator
The person who answers the email is the one who writes the code.
I write code and I read contracts. Before Izafa Labs I was Head of Operations and Legal at a financial services firm; I hold an LL.M. in corporate and finance law. I’ve shipped a storefront for a film composer and built case-management software for advocates at the Rajasthan High Court, now in beta. I work from Jaipur, and I keep working on things after they ship — the work is the only honest advertisement I have.
On record — Mukesh Purohit
Operator of record: Izafa Labs Private Limited · inc. 2026. Station: Jaipur · 26.9124° N · 75.7873° E. Registers: code · contracts · architecture. Status: still advancing.
- Previously
- Head of Operations & Legal · financial services
- Credential
- LL.M., corporate & finance law
- Working stack
- Next.js · Supabase · Postgres · Razorpay
- Based
- Jaipur, India · solo practice
§ 07 · Dak Ghar
Contact
Bring me the problem.
I’ll write back inside 4 business hours.
Short notes are better than long ones. What you’re building, what’s in the way, when you need it. Email or WhatsApp — or the short form on the engagement page. No funnel. The first reply comes from me — not an assistant, not a calendar link. Business hours are IST, Monday–Friday, 09:00–18:00.
Colophon
Izafa — Urdu for advancement, increase. The studio is named after the one thing it owes you. For the avoidance of doubt — Izafa Labs is a software studio and does not provide legal services. The operator’s legal background informs how the studio scopes and contracts software work; nothing on this site constitutes legal advice or a regulated legal offering.