Case Studies

How Students Built Real Projects

Every case study shows the full journey: what problem was solved, which tech was used, how the architecture works, and what results were achieved. No toy demos.

Start Your Project → Read Case Studies ↓
Student Work

Real Problems. Real Solutions. Real Results.

RAG System
Legal Document Q&A Assistant
Built by: Aditya M. · Module: LLMs & RAG · Duration: 3 weeks

Problem

A mid-size law firm in Lucknow spends 8+ hours per case manually searching through hundreds of contracts, NDAs, and legal agreements to find relevant clauses. Junior associates waste 40% of billable hours on document review instead of client work.

Solution

Built a RAG (Retrieval-Augmented Generation) system that ingests PDF legal documents, chunks them intelligently, stores vector embeddings, and answers natural language questions with cited sources. The system returns answers in under 3 seconds with accuracy above 92%.

Architecture

PDF Upload → Text Extraction (PyPDF2) ↓ Chunking (512 tokens, 50 overlap) ↓ Embeddings (Gemini text-embedding) ↓ pgvector (PostgreSQL vector store) ↓ Hybrid Search (semantic + keyword) ↓ LLM Answer (Gemini 2.5 Flash) ↓ Response + Source Citations

Tech Stack

  • Backend: Python, FastAPI
  • LLM: Gemini 2.5 Flash
  • Embeddings: Gemini text-embedding-004
  • Vector DB: pgvector (PostgreSQL)
  • Search: Hybrid (semantic + BM25 keyword)
  • Frontend: Streamlit dashboard
  • Deploy: Docker on AWS EC2

Results

  • Document review time reduced from 8 hours → 45 minutes per case
  • 92% answer accuracy (validated by senior partner)
  • Handles 200+ PDFs with <3 second response time
  • Now used daily by 12 associates at the firm

Key Learning

The student learned chunking strategies, hybrid search, pgvector indexing, and how to build a production RAG system with proper source citation — not just a chatbot wrapper.

AI Agent
E-Commerce Sales Intelligence Agent
Built by: Priya S. · Module: AI Agents · Duration: 2 weeks

Problem

An e-commerce startup tracks sales across 3 platforms (Shopify, Amazon, Flipkart). The founder manually exports CSVs daily, spends 2 hours compiling reports, and still misses trends. They need a system that can answer "What sold best this week?" in natural language.

Solution

Built a multi-tool AI agent that connects to Shopify API, queries a PostgreSQL database, performs web searches for competitor pricing, and generates automated Slack reports. The agent reasons through complex queries like "Compare our top 5 products vs Amazon prices and suggest repricing."

Architecture

User Query (Natural Language) ↓ Agent Controller (LangChain + Gemini) ↓ ┌─────────┬──────────┬──────────┐ │ Tool 1 │ Tool 2 │ Tool 3 │ │Shopify │ SQL DB │ Web Search│ │ API │PostgreSQL│ SerpAPI │ └─────────┴──────────┴──────────┘ ↓ Reasoning + Tool Selection Loop ↓ Structured Report + Slack Alert

Tech Stack

  • Agent Framework: LangChain Agents
  • LLM: Gemini 2.5 Flash
  • Tools: Shopify API, PostgreSQL, SerpAPI
  • Messaging: Slack Webhook
  • Scheduling: Cron (daily reports)
  • Deploy: Docker + AWS Lambda

Results

  • Reporting time reduced from 2 hours/day → 0 (automated)
  • Agent catches pricing gaps within 1 hour vs. next-day manual check
  • Revenue increased 12% in first month from faster repricing
  • Founder now asks questions via WhatsApp instead of Excel

Key Learning

The student mastered tool integration, agent reasoning loops, API authentication, and building a system that actually runs in production — not just a demo.

ML Pipeline
Customer Churn Prediction + FastAPI
Built by: Rahul K. · Module: Machine Learning · Duration: 2 weeks

Problem

A SaaS company with 15,000 users has a 28% annual churn rate. They know churn is expensive but have no way to predict which users will leave. Customer success team reacts after cancellation, not before.

Solution

Built an ML pipeline that ingests user activity logs, engineers features (login frequency, feature usage, support tickets), trains a gradient boosting model, and serves predictions via a FastAPI endpoint. The model flags at-risk users 30 days before likely churn with 87% precision.

Architecture

User Activity Logs (CSV/API) ↓ Feature Engineering (Pandas) ↓ Train/Test Split + Cross-Validation ↓ XGBoost + Hyperparameter Tuning ↓ MLflow Experiment Tracking ↓ Model Artifact (pickle) ↓ FastAPI Endpoint (/predict) ↓ Dashboard (Plotly + Streamlit)

Tech Stack

  • ML: XGBoost, scikit-learn
  • Tracking: MLflow
  • API: FastAPI + Pydantic
  • Dashboard: Streamlit + Plotly
  • Data: Pandas, NumPy
  • Deploy: Docker + Render

Results

  • 87% precision on churn prediction (top 20% flagged users account for 68% of actual churn)
  • Customer success team now proactively reaches out to at-risk users
  • Churn reduced from 28% → 19% in first quarter of deployment
  • Student's project was featured in college placement portfolio

Key Learning

The student learned the full ML lifecycle: data cleaning, feature engineering, model selection, experiment tracking with MLflow, API deployment, and monitoring model performance over time.

Business Intelligence
Hospital Operations Dashboard
Built by: Sneha R. · Module: Power BI & Analytics · Duration: 1.5 weeks

Problem

A 200-bed hospital in Lucknow tracks patient admissions, bed occupancy, doctor schedules, and billing in separate Excel sheets. The administrator spends 3 hours daily compiling reports for the management. Decisions are made on outdated data.

Solution

Built a Power BI dashboard that connects to their MySQL database, visualizes real-time bed occupancy, patient flow, revenue by department, and doctor utilization. Management now gets a live dashboard instead of daily Excel reports.

Architecture

MySQL Database (Hospital ERP) ↓ Power BI DirectQuery Connection ↓ Data Model (Star Schema) ↓ ┌──────────┬──────────┬──────────┐ │ Bed │ Patient │ Revenue │ │Occupancy │ Flow │ by Dept │ └──────────┴──────────┴──────────┘ ↓ Executive Dashboard + Alerts

Tech Stack

  • BI Tool: Power BI (DirectQuery)
  • Database: MySQL
  • Modeling: Star Schema, DAX measures
  • Automation: Power Automate (email alerts)
  • Scheduling: Daily data refresh

Results

  • Reporting time reduced from 3 hours/day → real-time (0 manual work)
  • Bed occupancy utilization improved 15% through visibility
  • Management now makes decisions on same-day data
  • Dashboard accessed by 8 department heads daily

Key Learning

The student learned data modeling, DAX calculations, DirectQuery vs Import mode tradeoffs, and how to design dashboards that non-technical stakeholders actually use.

Full-Stack AI
AI-Powered Resume Screening Tool
Built by: Amit J. · Module: LLMs + Production · Duration: 3 weeks

Problem

A recruitment agency screens 500+ resumes per week for tech roles. Manual screening takes 40 hours/week. They need an AI tool that parses resumes, matches skills to job descriptions, and ranks candidates — with a web interface for their team.

Solution

Built a full-stack AI application: frontend React form for uploading resumes, backend FastAPI with LLM-powered parsing, skill extraction, job matching scoring, and a dashboard showing ranked candidates. Deployed with Docker and CI/CD.

Architecture

React Frontend (File Upload) ↓ FastAPI Backend ↓ PDF → Text (PyPDF2) ↓ LLM Skill Extraction (Gemini) ↓ Embedding + Similarity Search ↓ Candidate Ranking Score ↓ Dashboard (Ranked Results + Export)

Tech Stack

  • Frontend: React, Tailwind CSS
  • Backend: FastAPI, Python
  • LLM: Gemini 2.5 Flash (skill extraction)
  • Vector DB: FAISS (in-memory)
  • Deploy: Docker + GitHub Actions + Render
  • CI/CD: Automated test + deploy on push

Results

  • Screening time reduced from 40 hours/week → 4 hours/week
  • 92% match accuracy validated against human recruiters
  • Handles 200+ resumes in under 10 minutes
  • Agency now offers AI screening as a premium service to clients

Key Learning

The student learned the full-stack AI workflow: React frontend, FastAPI backend, LLM integration, vector search, Docker containerization, GitHub Actions CI/CD, and production deployment — the complete AI engineer skill set.

AI Chatbot
Multi-Model Lead Capture Chatbot
Built by: Vikram P. · Module: LLMs & Deployment · Duration: 2 weeks

Problem

A coaching institute gets 50+ WhatsApp inquiries daily. The owner can't respond to all of them instantly. Many leads go cold because of 2-4 hour response delays. They need a 24/7 chatbot that answers FAQs and captures leads.

Solution

Built a multi-model chatbot with intelligent fallback chain (Gemini → Llama → Qwen → Phi), resume parsing, lead capture form, and WhatsApp integration. The chatbot handles 80% of queries without human intervention and sends hot leads directly to the owner's phone.

Architecture

User Message ↓ Intent Detection + Mode Toggle ↓ ┌─────────────────────────────┐ │ Model Chain (Fallback) │ │ Gemini 2.5 Flash (primary) │ │ → Llama 3.1 8B (backup) │ │ → Qwen3 8B (backup) │ │ → Phi-4 (final fallback) │ └─────────────────────────────┘ ↓ Lead Capture (Form + Google Sheets) ↓ WhatsApp Notification (Owner)

Tech Stack

  • LLMs: Gemini, OpenRouter (Llama, Qwen, Phi)
  • Backend: Node.js + Express
  • Lead Capture: Google Apps Script → Sheets
  • Notifications: WhatsApp webhook
  • Analytics: GA4 event tracking
  • Deploy: Render (auto-deploy from GitHub)

Results

  • 80% of queries handled without human intervention
  • Lead response time reduced from 2-4 hours → instant
  • 35% more leads captured (form vs. WhatsApp message)
  • Owner now receives hot leads via WhatsApp notification within 30 seconds

Key Learning

The student learned multi-model orchestration, fallback chains, lead capture workflows, webhook integration, and building a chatbot that serves a real business need — not just a toy chatbot demo.

Ready to Build Your Own Project?

Every DSWallah student builds 5+ production-grade projects in 12 weeks. Start with a free demo class and see what you'll create.

Start Free Demo → See All Projects →