Maharashtra sends me more fintech and marketplace work than anywhere outside Karnataka. Mumbai founders usually arrive with the commercial side already worked out and a clear question about architecture — how to handle payments at volume, how to structure a marketplace ledger, whether their stack survives the next order of magnitude.
I have shipped over 70 projects, mostly for Indian founders and small product teams, plus clients in the UK and US. Everything is built and deployed by me directly — no team, nothing subcontracted. I am based in Bengaluru and work remotely across India.
Mumbai and Pune are both IST, so we overlap completely during the working day. Pune's engineering density means teams there often want a second opinion on architecture rather than a full build, which is a perfectly good way to start working together.
Multi-tenant SaaS platforms with subscriptions, auth, and admin panels — production-ready from day one.
Custom AI agents, OpenAI integrations, and workflow automation built directly into your product.
High-performance iOS & Android apps built with React Native — standalone or alongside your SaaS.
Next.js listing platform for pre-launch and under-construction Bangalore developments — unit-level inventory with per-configuration pricing and availability, and budget filtering that reasons across configurations rather than projects.
Next.js site for a curated luxury property advisory — a single search across property, location, city and builder, and a schema model that describes a consultative service rather than a listings catalogue.
WordPress build for a luxury real-estate services company across four cities — Elementor Pro templates over a JetEngine content model, JetSearch property search, and a handover the client's own team could operate.
Mumbai's fintech density means most Maharashtra work touches money movement — payment flows, reconciliation, ledgers that have to balance. Pune sends a different kind: engineering teams wanting an architecture review before they commit. I build the product side of both; regulatory guidance stays with you.
Payment work has a specific failure mode: the happy path takes a day and the other paths take a fortnight. Failed charges, partial refunds, webhook replays, reconciliation drift. I scope those explicitly rather than discovering them in production, which is why Maharashtra estimates tend to look higher than a naive quote.
A payments-heavy SaaS build runs ₹8–15 lakh because the edge cases are the work. A Pune-style architecture review is ₹1.5–3 lakh over two weeks and often saves more than it costs.
There is no team behind me and nothing is subcontracted. The person you scope the project with is the person writing the code, which removes an entire category of translation loss. The trade is capacity — I take a small number of projects at a time, and I will tell you if I cannot start when you need to.
The repository lives under your account and the cloud infrastructure is provisioned in yours. You should never be in a position where changing developer means losing your product. Handover documentation is part of the work rather than something negotiated at the end.
A deposit to start, then payments tied to milestones you can see working in a staging environment. Never the full amount upfront in either direction. If a project stops early, you keep everything built to that point.
Every project gets a written scope split into launch and later, with an explicit not-included list. That second list prevents most disputes, because disagreement almost always comes from an assumption nobody wrote down.
Yes, though I am not a compliance specialist. I build the product — payment flows, ledgers, reconciliation, dashboards — and expect you to bring the regulatory guidance. Being clear about that line early saves everyone time.
For larger engagements, yes, usually for scoping or a difficult integration. Most of the work runs remotely and there is no meaningful difference in outcome.
Let's talk.
Hiring for a senior role or have an interesting problem to solve? Drop a note — I read every message.
Prefer email? Send to dharmendrasinghyadav022@gmail.com
Reply within 24 hours. No newsletter, no automated sequence.