What I build for businesses here
Indore products usually serve tier-2 and tier-3 markets directly, which is a genuinely different design problem — app size, offline behaviour and data cost become product requirements rather than optimisations.
Indore has become a genuine startup hub in the last few years, and it is where most of my Madhya Pradesh conversations start. The products tend to serve tier-2 and tier-3 markets directly, which is a genuinely different design problem from building for metro users.

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.
Building for tier-2 and tier-3 users means treating app size, offline behaviour and data cost as product requirements rather than optimisations. That is a constraint I enjoy — it forces better engineering.
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.
Indore products usually serve tier-2 and tier-3 markets directly, which is a genuinely different design problem — app size, offline behaviour and data cost become product requirements rather than optimisations.
I test on the device tier your users actually own rather than a flagship, because that is where these products fail. A build that works on a three-year-old mid-range Android will work everywhere; the reverse is not true.
A tier-2-focused mobile product runs ₹4–8 lakh. The optimisation work — bundle size, offline flows — is perhaps a fifth of that and is not optional for this market.
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, and it changes the technical decisions substantially — smaller bundles, offline-first flows, regional language support, and testing on the device tier your users actually own rather than a flagship.
No — several strong Indian products started by serving a tier-2 market well before expanding. Building for a market you understand beats building for one you have read about.
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.