Are all of these projects actually live?

Four of the five are. Dwarka Bricks, Expert Tutorials, Prominence Football Academy, and Velmora are on public URLs you can open right now. Nexli is in private testing inside one school. It is not publicly launched yet.

Why is Nexli not public?

Shipping software for a school is not the same as shipping a product page. Until the system has survived a full academic cycle with real teachers, real accountants, and real parents using it on the same day, it stays in private testing. The pressure inside one building is the best version control there is.

What stack do you usually pick?

TypeScript and Next.js for product surfaces, React for component-heavy UIs, Tailwind for design system speed, Firebase or SQL for data depending on what the system needs, Vercel for deployment. Lua for the Roblox work. Stack follows problem, not the other way around.

Can I commission a site like Dwarka Bricks?

Yes, but only if the brief is interesting and the operator behind it is serious about ownership. I do not run a template farm. The contact page has the direct line.

Do you have case studies?

Each project on this page is its own case study. The pattern is consistent: a clear problem, a structured response, real deployment, and an honest list of what the system does well versus what it is still learning to do.

How do you decide what to build next?

Two filters. Does it teach me something I do not already know how to do, and does it ship to real users at the end. If the answer to both is yes, it goes on the list.

Projects

Every system on this page is a real deployment.

Four are on public URLs. One is inside a school in private testing. Each one taught me something I did not already know. Each one had to survive an audience that was not me.

I do not build for review screens. The work below is what happens when the rule is, finish it, deploy it, and let it meet someone who did not ask for it nicely. The set is small on purpose. I would rather ship five things that hold up than thirty that almost do.

01
Dwarka Bricks
A hyper-local real estate platform for one district of Delhi.
Live2025Real estate platform
Open the live site
Dwarka BricksImage coming
Buy, rent, and sell across the 22 sectors of Dwarka. Sector filters, budget ranges, verified listings, direct agent contact, no middlemen.
Most property portals in India try to serve every city at once. Dwarka Bricks does the opposite. It commits to one district, learns it deeply, and verifies the listings on the ground. The site is the surface; the value is the local network behind it.
Search is structured around the things buyers in Dwarka actually filter by: sector number, property type, budget band. Each listing pulls through verification status and connects directly to the agent on WhatsApp, removing the layer of brokers that usually sits between the buyer and the owner.
On the engineering side, the site uses a clean Next.js + Firebase stack with sector-aware routing and an admin layer for adding, verifying, and retiring listings. The visual identity stays neutral so the property photography does the talking.
What it does well
22 sectors, structured filters
Verified listings only
Direct agent contact, no middle layer
Sector-aware routing and SEO
Next.jsTypeScriptTailwindFirebaseVercel
02
Expert Tutorials
A CBSE coaching institute's full digital presence.
Live2024Education website
Open the live site
Expert TutorialsImage coming
Site, content, and structure for a Dwarka coaching center covering classes 6 to 12. Courses, methodology, faculty intro, transparent reach to parents.
Expert Tutorials needed more than a brochure site. The institute runs structured testing, doubt sessions, and four programs across foundation, board prep, and commerce. The site had to communicate that structure clearly without burying parents in marketing copy.
I built it around four pillars: clarity on what is taught, transparency on how it is taught, accessibility for parents who want details before committing, and proof through the director's introduction and the methodology block. Course cards are scannable in seconds; the FAQ section answers the questions parents actually ask, in the order they ask them.
Beyond the site, I joined Expert Tutorials as a weekend instructor for AI, Informatics Practices, Computer Science, and programming languages. Building the platform and teaching on it gave me an unusual feedback loop on what works.
What it does well
Classes 6 to 12, four structured programs
Director introduction, methodology block, FAQ-first design
Local SEO targeting Dwarka sectors and nearby pincodes
I teach on weekends, so I rebuild what does not work
Next.jsTypeScriptTailwindVercel
03
Prominence Football Academy
A football academy's online presence.
Live2025Sports academy website
Open the live site
Prominence Football AcademyImage coming
Programs, coaching philosophy, schedule, and registration for a youth football academy.
A youth football academy lives or dies on trust. Parents are sending their children into a structured environment, and they want to see the program, the coaching philosophy, and the schedule before they sign up. The site sets that tone in the first scroll.
Structurally it follows the same instinct as the rest of my client work: clear hierarchy, real photography, no jargon. Program tiers, age groups, training schedule, and a registration flow that does not waste anyone's time.
The site is live. Coaching staff bios, age-group programs, and the seasonal calendar are wired in. The registration flow lands directly with the academy's operators, so a parent's first message is the same message the head coach reads.
What it does well
Program tiers and schedule front and center
Trust-first hierarchy designed for parents
Registration flow shipped, no friction
Age-group programs, coaching staff, and seasonal calendar live
Next.jsTypeScriptTailwindVercel
04
Velmora
My Roblox game.
Live2025Game
Open the live site
VelmoraImage coming
Velmora is a Roblox project under the username @yashveersinghrajpoot. A different surface to build for, with its own constraints and audience.
Web is not the only place I ship. Velmora is my Roblox project, built on a platform with a completely different set of constraints: a sandboxed scripting environment, an established player base with strong expectations, and a publishing pipeline that has nothing to do with Vercel.
Working in Roblox forces a different kind of thinking. Physics, collision logic, and player state matter in a way they do not on a static product page. Lua replaces TypeScript. The tooling is unfamiliar. That is exactly the point. Building in an environment I did not grow up in keeps my instincts honest.
Velmora lives under the @yashveersinghrajpoot Roblox profile. The work is iterative: ship a loop, watch players push on it, fix the thing that breaks first. The result is a small piece of evidence that the lab is not limited to the web stack.
What it does well
Built and published on Roblox
Username: @yashveersinghrajpoot
Lua scripting, in-engine physics, player state
Iterative release loop driven by real player behavior
Roblox StudioLua
05
Nexli
A full-stack school management system. Private testing.
Private testing2025 to presentInternal product
NexliImage coming
Seven login types. Attendance, marks, fees, report cards, question bank workflows. Not publicly launched. I am running it inside one school first to see what breaks before it goes wider.
Nexli is the largest system I have built so far. It is a full-stack platform that replaces the physical registers, broken spreadsheets, and disconnected workflows that most schools still run on. Seven login types: Superadmin, Principal, HOD, Coordinator, Teacher, Accountant, Parent. Each has its own surface, its own permissions, and its own view of the same shared data.
On the academic side it handles attendance with at-risk flagging when a student dips below the threshold, marks entry per subject, paper generation off a managed question bank, and PDF report card generation per student. On the operational side it handles fee collection with an automatic ledger, parent-teacher messaging, and announcements that route to the right roles.
It is not publicly launched. I am keeping it in private testing inside one school first, because shipping software for an institution is not the same as shipping a product page. There are workflows that only surface when a real principal, a real accountant, and a real parent are using the system on the same day. The product gets stronger by living inside that pressure before anyone else touches it.
What it does well
7 roles with isolated permission surfaces
Attendance with at-risk flagging under 75%
Fee ledger, PDF report cards, question bank
Real-time Firestore sync across stakeholders
Private testing in production with a partner school
React 19TypeScriptFirebase FirestoreFirebase AuthViteVercel

Want to see the engine, not the output?

The Systems folder breaks down the stack, the tools, the architecture patterns, and the engineering capabilities the work above is built on. The Journey folder traces how it all compounded year by year.

Open the stack Read the journey

FAQ

Every system on this page is a real deployment.

What it does well

What it does well

What it does well

What it does well

What it does well

Want to see the engine, not the output?