What I build for businesses here
Tripura work is mostly about market access — connecting bamboo, tea and handicraft producers to buyers outside the state.
Tripura's small but growing digital economy is mostly about connecting local producers — bamboo, tea, handicrafts — to markets beyond the state, plus government-adjacent service delivery.

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.
Northeast connectivity is variable, so offline tolerance should be assumed rather than treated as an enhancement.
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.
Tripura work is mostly about market access — connecting bamboo, tea and handicraft producers to buyers outside the state.
For most businesses here an existing storefront or marketplace serves better than a custom build, and I will say so. Where custom is warranted it stays deliberately small and offline-tolerant.
If a custom build is genuinely warranted, ₹2–4 lakh. Before quoting I would want to establish that an existing platform cannot do the job.
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.
Possibly, and I will say so. Below a certain scale an off-the-shelf tool serves you better than a custom build, and telling you that costs me a project but saves you money.
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.