Start a project.

Every engagement begins with a Discovery Sprint. Two weeks. Fixed scope. The deliverable is a signed A3 architectural drawing of your system, a supporting written architecture document, a fixed-price build quote, and an honest recommendation — including whether to build with me or not. Discovery is paid; the number lives in the proposal, not on this page.

Every Izafa Labs build ships with a twelve-month annual support contract. It covers security patches, dependency updates, SSL renewal, DNS management, uptime monitoring, and a 48-hour response window for critical bugs. New feature development, design changes, and third-party API migrations are scoped separately. The contract terms are in writing before the engagement starts.

Engagements are invoiced in milestone tranches defined in the Discovery Sprint quote. There are no monthly retainers and no hidden costs. The schedule is in the proposal you sign before kickoff.

Two weeks, fixed scope. You receive a single A3 architectural drawing of your system — signed, dated, delivered as PDF (or printed if you’re in Jaipur) — a supporting written architecture document, a fixed-price build quote, and an honest recommendation. 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.

Every inquiry receives a reply within 4 business hours. After the first call, a Discovery Sprint proposal arrives within 5 business days.

If a Shopify theme is what your problem actually demands, I will tell you so during the first call and you should hire a Shopify partner instead — there are good ones. The Discovery Sprint is partly designed to answer that question honestly. Most clients land here because templates already failed them; some of them don’t need a custom build either.

Data Protection Plan 1 is the multi-tenant data segregation standard I apply to every multi-tenant build. It enforces row-level security at the database layer, separate authentication scopes per tenant, and a documented audit trail. Every engagement that handles tenant data ships with a written architecture document describing how Plan 1 is implemented.

Yes. Refunds are calculated against milestones. If I miss a committed milestone date materially and without prior notice, the client is owed a pro-rata refund as set out in the executed Master Services Agreement. Paid milestones already delivered are non-refundable.

The client. Final deliverables — code, designs, copy, documentation — transfer to the client on full payment. Pre-existing Izafa Labs tooling and third-party libraries remain under their respective licenses.

Yes. Mutual confidentiality obligations apply for the duration of every engagement and a defined period thereafter, as set out in the executed agreement or counterparty NDA. I’m happy to sign reasonable client-supplied NDAs.

The working studio is in Jaipur, Rajasthan, India. The legal entity is registered in Jodhpur, Rajasthan. Work happens in IST (UTC+5:30), with overlap windows scheduled per engagement for clients in Mumbai, Bangalore, Singapore, London, and the United States.

One at a time. Izafa Labs is one operator — Mukesh Purohit. You talk to the person building it. There is no account manager, no junior dev assigned because the senior was double-booked, no coordinator who will get back to you tomorrow. The slot constraint is what lets me deliver what I promise.

Optimization Plan 1 is the frontend performance standard I apply to every engagement built for constrained network conditions. It specifies cache-first rendering, IndexedDB-first UI state, non-blocking realtime updates, and aggressive query invalidation reduction. The default state assumption is offline; the network is treated as enhancement, not requirement. NyayHub — built for court environments where Wi-Fi cuts out mid-hearing — is the reference implementation.