Based in Bengaluru · Working with Madhya Pradesh

Full-Stack & AI Development in Madhya Pradesh

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.

Working with me

  • You work directly with me — nothing is passed on
  • Based in Bengaluru, IST overlap
  • Code lives in your repository from day one
  • Staged payments tied to deliverables
Madhya Pradesh — full-stack and AI development services by Dharmendra Singh Yadav

Track record

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.

How we'd work together

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.

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.

How a project runs

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.

What it costs

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.

How I work

You work with me directly

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.

Your code, your infrastructure, from day one

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.

Payments staged against deliverables

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.

Scope written down, including what is excluded

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.

Working with me in Madhya Pradesh

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.

Building production-grade SaaS, AI agents and mobile apps end-to-end.

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

Send a message from this page

Reply within 24 hours. No newsletter, no automated sequence.