What I build for businesses here
Northeast products are often the first digital option in their category for a large regional population. Connectivity is genuinely variable, which should be a starting assumption rather than an edge case.
Assam and the wider Northeast are one of India's least-served technology markets, which is exactly why the products being built there are interesting — often the first digital option in their category for a large regional population.

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.
Connectivity across the Northeast is genuinely variable, which should shape architecture: offline-capable flows, small payloads and graceful degradation rather than assuming a stable connection.
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.
Northeast products are often the first digital option in their category for a large regional population. Connectivity is genuinely variable, which should be a starting assumption rather than an edge case.
Offline-first data capture, small payloads, and interfaces that behave sensibly when the connection drops mid-action. That is a design decision made at the start, not a patch afterwards.
A product built offline-tolerant from the start runs ₹4–8 lakh. Retrofitting offline capability afterwards typically costs more than building it in, which is why it is worth deciding early.
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.
No. Same timezone, and everything runs remotely with a staging environment you can check any time. I have never found geography inside India to affect a project's outcome.
Yes, and for the Northeast it should be a starting assumption — offline-first data handling, small bundles and interfaces that behave sensibly when the connection drops mid-action.
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.