Dharmendra Singh Yadav
Real products. Real clients. Production-grade code shipped from idea to launch.
Showing 1–9 of 61
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.
Next.js property portal for the Hebbal luxury corridor — eleven builder pages, faceted browse, and an editorial layer of head-to-head project comparisons aimed at buyers who already have a shortlist.
Next.js property portal for the Chikkajala–Devanahalli airport corridor — faceted browse by builder, type and status, keyword-first project URLs, and Product/Offer schema describing real inventory.
Next.js website for a fixed-scope SaaS development service — 12 service pages across 23 markets, a published week-by-week delivery timeline, and Offer, Audience and FAQPage schema on every page type.
Scroll-driven marketing site for a full-cycle IT solutions company — nine service lines across seventeen industries, built with GSAP, ScrollTrigger and Locomotive Scroll on static HTML rather than a framework.
Next.js + MongoDB marketing site for a SaaS and AI product studio — per-service and service × location pages, a blog with its own admin, and structured data on every page type, positioned around shipping a founder's MVP in about 30 days.
A full-stack React.js + Vite platform backed by Supabase that helps businesses manage bookings, appointments, inventory, vendors, orders, payments, and mini-websites across 13+ industries
Yes. Everything shown here was built by me directly. Where a project was part of a larger team effort, the case study says which parts were mine.
For open-source projects, yes — the repository is linked. Client work is under NDA, but I am happy to walk through the architecture and the decisions behind it in a conversation.
Because features tell you what was built and decisions tell you how someone thinks. If you are evaluating me for a role or a project, the reasoning behind a trade-off is more useful evidence than a screenshot.
Yes. Whether you are assessing me for a role or weighing up a similar build, the useful conversation is about the problem rather than the finished thing. Send me what you are trying to solve and I will tell you honestly how I would approach it.