just shipped the core of Skillship — an AI-powered LMS built for schools.

One platform, many schools, and one rule that shaped every decision: School A must never see School B's data. Tenant-scoped models, filtered querysets at the base class, UUIDs everywhere.

Four AI features live: — Career Pilot: personalised career paths for students — Question generator: chapter PDF in, board-aligned MCQs out — Adaptive quizzes: difficulty follows actual performance — Semantic search: teachers ask in plain English, pgvector finds the material

Django + DRF for the LMS core, a separate FastAPI service for all AI work (Gemini + a pgvector RAG pipeline), Next.js 14 on the front. Django brokers every AI call — the AI layer never touches the browser.

The hard part wasn't the AI. It was making multi-tenancy boring enough that no future dev can leak a school's data by accident.

Open for new work — full-stack builds, AI integrations, RAG pipelines, multi-tenant SaaS. Send me a project.

The tenant boundary is where I'd put the first failure test. I'd try to make a user from one school retrieve another school's record before I trusted any of the AI features.

I built this because I was annoyed.

I was paying monthly for a study library seat, and I still couldn't reliably tell if a seat would be free when I showed up. No way to check online, no way to book ahead just calling around or walking in and hoping. I figured if this was frustrating me, it was frustrating thousands of students across India who rent library/reading-room seats the same way.

So I built Studoo (https://studoo.aithro.in/ ) and Padhloo (https://padhloo.aithro.in/ ) two connected products at Aithro (https://aithro.in/products) -

Padhloo (student side): search study spaces by city/price/amenities, see a live seat map, request a specific seat for 1-12 months, and track your bookings, dues, and payments in one place. It also gamifies actually showing up — QR check-in/out, study streaks, points, badges, a leaderboard — so students stay consistent, not just book-and-forget.

Studoo (owner side): the dashboard library/reading-room owners use to list their space, manage seat inventory and pricing per slot, approve or reject booking requests, chase due payments automatically, and see real analytics (occupancy, revenue, which slots to reprice). Free tier + two paid plans. You can see product demo video here - https://youtu.be/9Yex73MIYqQ?si=jfWqLxisRTM9N_28

I designed and built the full product end-to-end — the booking/approval workflow, the seat-and-slot inventory model, the QR-based geofenced attendance system, the payments/dues tracking, the subscription tiers, and the whole gamification layer (points, streaks, badges) on the student side.

Where it stands:

Got our first paying customer, a real library owner in Patna paying for the Growth plan, which is the moment this stopped being a side project and started being a business.

Reached the Grand Finale of Empresario 2026 (IIT Kharagpur E-Cell), selected out of 3,000+ global registrations.

Won the Platinum Jubilee Innovation Challenge (Deep Tech) at IIT Kharagpur's 75th anniversary event.

What I'm good at, based on building this: turning a messy real-world workflow (owner approves seat → student pays offline → both sides need to trust the same numbers) into a system that's simple enough for a small business owner with no tech background to actually use — while still handling the edge cases (partial payments, overlapping slots, expiring bookings, geofenced check-ins) correctly under the hood.

If you're a small business or founder who needs a web app or an AI-automation workflow built and shipped fast, not just prototyped that's exactly the kind of problem I like solving. Happy to talk about your project.