CUSTOM SOFTWARE · DRAWN, BUILT, HANDED OVER
One operator. One drawing. One build, properly. Reply within 4 business hours.
You hired an agency.
They sold you their stack.
Good. Let’s start over.
They built what they already knew how to build. You’re here because it didn’t work. I draw the system first. I build what your problem actually needs. I hand it over and walk away. No retainers. No lock-in. No bullshit.
We draw before we build.
Caption · how to read this dossier
One operator. One drawing. One build, properly. Yours from day one.
- BAY A · DRAW
- observe · measure · page
- BAY B · BUILD
- from the drawing, not around it
- BAY C · HAND OVER
- so I can leave, cleanly
A template is not architecture.
There is a kind of agency in this country that has built its entire business on selling templates. They have a stack they reuse, a process they sell as bespoke, and a maintenance retainer designed so you cannot leave. They will not listen to your problem because their margin depends on not listening. Most people who land on this file have already paid one of those agencies. That is why they are here. A template is not architecture.
TEMPLATE BUILDIRR · 03.A
Shipped fast, because they already knew what they would ship. Identical to the build before yours. Identical to the build after.
DRAWN BUILDREL · 03.B
Shipped slow, because the problem deserved a drawing. Specific to your constraints. Documented end to end. Yours from day one.
Four steps.
Same four, every time.
OBSERVE
Sit with the system as it actually runs. Watch the people who use it lose time to it. No assumptions yet.
DRAW
A single sheet that describes the system in full — boundaries, data, failure modes. You sign it. I build from it.
BUILD
From the drawing, not around it. Every deviation is a redraw, in writing, before any code moves.
HAND OVER
Code, runbook, architecture doc, onboarding. You own every asset on day one. I can leave; you keep running.
Before any code is written, I produce a single page — a drawing — that describes the system in full. You sign it. I build from it. If we drift, I show you the deviation and redraw. No surprises, no creep, no handwave.
Receipts.
Two builds. Drawings exposed. Trade-offs visible.
A note on what’s visible here. A lot of the work I’m doing right now is for independent musicians, labels, and the people around them. Not because that’s the only thing I do — I’ll build for any business that needs the system drawn before it’s built — but because Indian indie music is technically underserved in a way I find interesting, and the trust runs both ways. Some of the receipts below are from that world. The same drawings would have been made for a D2C brand, a SaaS, or a clinic with the same problems.
A film composer’s storefront. Persistent audio across pages, custom checkout for sample packs and stems, admin dashboard.
- r0125·Q4discovery — audio + storefront in one
- r0426·Q1audio player lifted to root layout
- r0726·Q1supabase RLS + admin split
- r1126·Q2production · razorpay live
- Sector
- Music · D2C
- Scope
- Web · Audio · Shop
- Engineers
- 1
- Shipped
- Q2 · 2026
- Stack
- Next / Supabase / Razorpay
- Status
- Production hardening
Legal SaaS for Rajasthan High Court. Multi-tenant isolation, IndexedDB-first UI for the moment court Wi-Fi cuts out.
- r0125·Q3what breaks legal SaaS in courts
- r0325·Q4data protection plan 1 · multi-tenant
- r0626·Q1optimization plan 1 · indexeddb-first
- r0926·Q2beta · 70 tables · 30 edge functions
- Sector
- Legal · SaaS
- Scope
- Web · Multi-tenant
- Engineers
- 1
- Shipped
- Q2 · 2026 (beta)
- Stack
- Next / Supabase / IndexedDB
- Tenancy
- RLS isolation
How an engagement
starts.
Every engagement begins with a Discovery Sprint. Two weeks. Fixed scope.
- DWGOne architectural drawing of your system, signed and dated, at A3 size. PDF if you’re remote. Printed and delivered if you’re in Jaipur.
- DOCA supporting written architecture document.
- QTEA fixed-price build quote.
- RECAn honest recommendation, including whether to build with me or not.
You can leave with the drawing and never build with me. Most clients won’t. The ones who do, sign at the price the drawing concludes. Discovery is paid; the build is fixed-price from the drawing. As a band, Discovery sits in five figures INR; build engagements run from mid five to seven, depending on scope.
Reply within 4 business hours. First call is 30 minutes, in writing or on video.
Working principles,
made explicit.
Method and scope are public. Pricing lives in the proposal because every drawing concludes a different number.
this is the whole pitch, reallyEvery engagement ships a written architecture document, an operational runbook, and an onboarding for whoever takes it over. Code is easy. Knowledge transfer is the hard part.
I’ve been burned by the other sideIf I build it, I document it. If I document it, someone else can run it. I don’t do lock-in through obscurity. If you want me out, you can get me out.
the opposite of most agenciesI build Claude-native where the task actually benefits — intake, classification, drafting. I do not sprinkle chatbots on things. The test is: does it remove real work?
and not a ChatGPT wrapperI do not sell Next.js. I do not sell Supabase. I do not sell WordPress. I sell the result of looking at your problem and choosing the right tools for it. Sometimes that’s a custom build. Sometimes it’s a no-code stitch. Sometimes the answer is don’t build, and I will tell you that too.
the tool is downstream of the briefIzafa Labs is one person. Mukesh Purohit. You talk to the person building it. There is no account manager. No junior dev assigned to your build because the senior was double-booked. No project coordinator who will get back to you tomorrow. This is the trade-off. It is also the point.
the constraint is the featureIf a Shopify theme is what you actually need, I will say so. If a freelancer at a fraction of the cost will solve your problem, I will say so. The Discovery Sprint exists partly so I can answer this question honestly. The drawing tells both of us what the right next step is — and sometimes the right next step is not me.
the public commitment is the point// OPERATORMukesh Purohit. I write code, draw systems, and read building codes for fun. I work from a small studio in Jaipur because the Jaipur evening light is the best light for thinking. I’ve shipped storefronts, a legal SaaS now in beta inside the Rajasthan High Court, and a fair number of things I never let go live because they weren’t the right answer. I like work that survives me.
Who this isn’t for.
If you need a site in a week or a maintenance retainer that quietly never ends — those are real services and good agencies provide them. I’m not the right fit.
Channel · open · awaiting transmission
Establish
contact.
First call · 30 minutes · in writing or on video. Bring the problem. I will tell you whether a Discovery Sprint is the right next step.
Or send the brief in writing — I read everything.
// END OF FILE · TAKE A LINE WITH YOU
The drawing is not the building. But no building stands without one.
Izafa · ezāfe · the construct that joins two words into a third meaning. Drawing and build, joined.