ThinkGrades
Building an AI-native operating system for modern schools.
A production SaaS case study demonstrating how Tectrom handles complex workflows, multi-tenant security, role-specific UX, AI integration, and continuous product development.
ThinkGrades OS • Institutional Overview
Multi-tenant Academic Administration Dashboard (Anonymized View)
Identified academic score variance across physics calculus assessments. Automated review modules prepared for parent portal delivery.
From fragmented legacy tools to an active School OS.
Educational institutions often run core daily workflows across spreadsheets, paper registers, legacy ERP software, and disconnected messaging apps.
Traditional School ERP
Legacy Model- ✕ Stores static records in passive database tables
- ✕ Form-heavy administrative entry screens
- ✕ Siloed, disconnected modules requiring re-entry
- ✕ Delayed reporting generated weeks after terms end
ThinkGrades School OS
Active OS Model- ✓ Connected, event-driven academic workflows
- ✓ Role-specific experiences (Admin, Teacher PWA, Parent PWA)
- ✓ Automated mark processing & fee receipts
- ✓ Real-time insights and AI-assisted decisions
3 Representative production workflows.
A look inside the core workflow modules designed, engineered, and operated within ThinkGrades OS.
School Operations & Roster Architecture
Centralized administration for academic sessions, sections, subjects, teacher allocations, and role permissions.
Daily Attendance & Mobile Teacher/Parent PWAs
Mobile-first Progressive Web Apps engineered for fast daily classroom marking by teachers and real-time visibility for parents.
Exams, Marks Calculation & Server PDF Marksheets
Dynamic mark calculation supporting theory, oral, and practical weightages with automated PDF marksheet generation.
3 Hardest engineering challenges solved.
A detailed look into the architectural trade-offs, security models, and database challenges we solved while engineering ThinkGrades.
Secure Multi-Tenant Row Level Security (RLS)
Multiple institutions share the SaaS application database infrastructure, requiring strict tenant isolation to prevent cross-school data leakage.
Implemented school-based tenancy utilizing PostgreSQL Row-Level Security (RLS) policies in Supabase. Database queries evaluate active school membership context, enforcing tenant isolation at the database layer.
- Row-Level Security (RLS) policies enforced at database layer
- Explicit user-school membership mapping
- Super-admin tenant context switching
Complex Academic Data Modeling
School marksheets vary greatly across institutions and subjects—mixing theory, oral, practical components, and custom grading boundaries.
Engineered a flexible relational schema modeling marks as multi-part assessment components with dynamic weightages rather than hardcoding flat scores.
- Dynamic theory, oral, and practical component structures
- Configurable grading scales (letter grades, GPA, percentages)
- Flexible exam classification and term aggregations
Server-Side Report Card PDF Generation
Generating end-of-term student marksheets requires consistent printable layouts and reliable batch generation across entire classes.
Engineered a dedicated server-side Puppeteer PDF service rendering HTML/CSS templates into downloadable marksheets.
- HTML/CSS template-to-PDF rendering
- Batch marksheet generation queue
- Scalable worker service deployment
System architecture & technology stack.
Clean layered architecture connecting user interfaces, application routes, security boundaries, database tables, and external microservices.
End-to-End Data Pipeline
Frontend & Apps
- Next.js App Router
- React
- Tailwind CSS v4
- Teacher & Parent PWAs
Data & Security Layer
- Supabase PostgreSQL
- Row Level Security (RLS)
- Strict Schema Migrations
AI Layer
- OpenAI API
- Vercel AI SDK
- Structured JSON Output
Infrastructure & APIs
- Vercel Edge
- PDF Generation Service
- Web Push / VAPID
Product decisions & practical AI integration.
Key trade-offs made during product development to reduce friction, alongside practical AI assistance.
Why a dedicated Teacher PWA?
Teachers repeatedly perform a small number of high-frequency actions (attendance, homework, marks entry). Designing a dedicated PWA eliminated desktop clutter and enabled fast mobile completion.
Why simplify the Parent experience?
Parents need clear visibility into their child’s progress and fee receipts—not administrative software. We kept the parent PWA focused entirely on progress feeds and marksheets.
Why role-based interfaces?
Showing only functionality relevant to an active user role reduces cognitive load, speeds up task completion, and limits accidental administrative changes.
Why multi-tenancy from Day 1?
ThinkGrades was designed as a scalable SaaS product rather than separate software installations per school, dramatically simplifying maintenance.
Identifies score variance for early teacher intervention.
Aggregates subject performance overviews for admins.
Assists admins with legacy student data ingestion.
Current status & engineering roadmap.
Clear differentiation between deployed production modules, beta features, and planned engineering initiatives.
Core School OS
Multi-tenant RLS, operations, attendance, marks, fees & PWAs.
API Rate Limiting
Enhanced rate limiting and tenant security auditing.
Async PDF Queue
Worker queue for large-scale batch marksheet generation.
Offline PWA Sync
Background sync for attendance in low-connectivity environments.
What building ThinkGrades taught us.
Three core lessons learned while engineering multi-tenant SaaS platforms.
Complex workflows need simple interfaces.
Complexity should live inside the database and backend architecture—never on the user's screen.
Different users require different experiences.
An administrator desktop dashboard cannot simply be shrunk down and called a mobile app for teachers or parents.
Architecture decisions become product decisions.
Multi-tenancy, Row Level Security, and clean schema design directly determine how fast future features can be built.
Building a multi-tenant SaaS platform
or replacing a fragmented workflow?
Talk directly with the product engineering team behind ThinkGrades. 30-minute technical discussion • No sales handoff.