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. Websites, portfolios, ecommerce storefronts, custom software, startup MVPs — whether you’re a new founder in Mumbai, a D2C brand in Bangalore, or a business in Delhi that needs a system built right. The work keeps getting better long after the invoice clears.
Most web development studios stop at the code. I don’t — I write the contracts too.
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.
A storefront with persistent audio. A legal SaaS that survives courtroom Wi-Fi. The artifact you can run.
Repositories, infrastructure, credentials, runbook. You own every asset on day one. If you want me out, you can get me out.
I map your system on paper before any code is written. Whether you’re a startup founder or an established business, you leave with a written architecture and a fixed-price quote for the build — whether or not you build it with me. The artifact is yours either way.
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.
Repositories, infrastructure, credentials, runbook, contracts and data schema — handed across. No lock-in, no proprietary middle layer only I can maintain.
The work keeps advancing. Improvements arrive whenever there’s time to make them — paid retainer or not. A studio of one, treating every project as part of its own permanent body of work, can afford to operate this way.
Real builds with their real revision logs — no screenshots standing in for the work, no testimonials standing in for the builds. The work speaks for itself.
Each project carries its real revision log: id, quarter, the actual change. Every list ends with the same marker — still advancing— because the work is never abandoned.
A film composer's storefront. Catalog, audio preview at the layout root, checkout, and admin — built so one person can run it without a team.
Legal software for the Rajasthan High Court — built for how lawyers actually work in courts, including offline. My own product, currently in beta.
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.
You own the repository, infrastructure, credentials, database, and contracts. Nothing is held back as a maintenance hook. If you want to leave, you can.
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.
Inside an Annual Maintenance Contract or a retainer. Outside of one, improvements still arrive whenever there’s headroom — as a matter of operating discipline, not as a billable line.
I write code and I read contracts. Before Izafa Labs I was Head of Operations & Legal at a financial services firm; I hold a master’s in corporate & finance law. I’ve shipped a storefront and a legal SaaS now in beta inside the Rajasthan High Court. I work alone, from Jaipur, and I keep working on things after they ship — the work is the only honest advertisement I have.
Short notes are better than long ones. What you’re building, what’s in the way, when you need it. No form, 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.