Izafa LabsWebsite & Software Developer · Jaipur · India

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.

Bring me a problemFirst reply within 4 business hours · IST · Mon–FriWebsites · custom software · portfolios · startup MVPs · India

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.

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.

the build

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.

the structure

Clean scoping, clean contracts, clean handover — nothing held back as a hook.

Repositories, infrastructure, credentials, runbook. You own every asset on day one. If you want me out, you can get me out.

A quiet sequence. One that doesn’t end at handover.

  1. 01 / two doors

    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.

  2. 02 / build

    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.

  3. 03 / handover

    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.

  4. 04 / and then

    It doesn’t stop.

    The work keeps advancing. Improvements arrive whenever there’s headroom to make them — paid retainer or not; on the Advance Retainer they arrive scheduled and guaranteed. A studio of one, treating every project as part of its own permanent body of work, can afford to operate this way.

Two builds. Two more in scope. Each carries its real history.

Real builds shown as they run in production — captured plates, not mockups; 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.

STUDIRT storefront homepage — Stuart DaCosta's site with the persistent audio player docked at the bottom right
PL-005.01studirt.com · storefront home · audio player docked26·Q2
case 01shipped Q2 · 2026still advancing

STUDIRT.

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.

Next.jsSupabaseRazorpayPostgres · RLS
  1. Revision log
  2. r0125·Q4discovery — audio + storefront in one
  3. r0426·Q1audio player lifted to root layout
  4. r0726·Q1supabase RLS hardened · admin split
  5. r1126·Q2production · razorpay live
  6. still advancing
case 02own product · in betastill advancing

NyayHub.

Legal software for the Rajasthan High Court — built for how lawyers actually work in courts, including offline. My own product, currently in beta.

70 tables · 30 edge functions · 1 operator

Next.jsSupabaseIndexedDB
  1. Revision log
  2. r0125·Q3what breaks legal SaaS in courts
  3. r0325·Q4data protection · multi-tenant
  4. r0626·Q1optimization · IndexedDB-first
  5. r0926·Q2beta · 70 tables · 30 edge functions
  6. still advancing

Why this isn’t a generic firm.

  1. 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.

  2. 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.

  3. 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.

  4. The work is improved after delivery.

    Inside the Advance Retainer, improvements are scheduled and guaranteed; the AMC holds the maintenance floor. Outside of either, they still arrive whenever there’s headroom — as a matter of operating discipline, not as a billable line.

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 & 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.

Mukesh Purohit— operator · izafa labs
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

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. 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.

— email · preferred
mukesh@izafalabs.com
Pre-filled template · written context survives.
— whatsapp
+91 89493 82912
Shorter notes · IST hours.