Building a tech-driven student accommodation ecosystem in Delhi NCR — from PG discovery to managed operations, staff tooling, and admin infrastructure.
- Year
- 2024
- Role
- CTO
- Client
- Nestingo
- Duration
- Multi-year build
- Product Architecture
- Engineering Leadership
- Operations
- Multi-platform Systems
- Startup Execution
CTO · STARTUP
Nestingo — A Managed Student Accommodation Ecosystem
Technology-first PG & hostel platform · Delhi NCR · Operations + product
Nestingo was built to fix the fragmented, trust-deficient PG and hostel market in Delhi NCR — helping students, professionals, parents, and migrating tenants find verified, broker-free accommodation with transparency and human support. As CTO, I led product architecture, technical execution, team scaling, and the systems that turned startup vision into operational software.
Platforms
3+
Focus
Delhi NCR
Model
Zero brokerage
Team
CTO + devs
Introduction & Product Vision
Nestingo started as a PG discovery platform and evolved toward a managed accommodation network — positioning itself not as another listing site, but as an operator invested in resident experience, verification, and end-to-end support.
The ecosystem included a public website for acquisition and discovery, a staff operations panel for visits and leads, and an admin dashboard for property inventory, bookings, CMS, and business operations — reducing daily dependency on engineering for routine tasks.
Market opportunity was especially strong in Delhi NCR: massive student migration (including Delhi University), major corporate hubs, and PG infrastructure that remained largely unorganized and offline-first.
- Role
- CTO
- Region
- Delhi NCR
- Brokers
- Zero fee
- Long-term vision
- GigVid
Core Problems in the Market
User trust & transparency
Students and professionals faced fake listings, hidden brokerage, poor hygiene, unsafe stays, and no standardized booking — parents and tenants needed high trust before committing.
Operator digitization gap
PG owners struggled with low occupancy, weak digital presence, manual operations, and no structured lead management or marketing systems.
Fragmented inventory
Room availability changed constantly. Keeping listings, staff workflows, and booking state aligned across platforms was operationally difficult.
Scaling operations
Every property required custom onboarding, verification, and operational adaptation — staff coordination and internal tooling became critical infrastructure, not optional extras.
Product Ecosystem I Architected
Public Website — Discovery & Conversion
Built the primary acquisition engine: locality search, gender and sharing filters, property comparison, amenities, maps, standardized listing pages (galleries, pricing, house rules, food options), visit scheduling, inquiry flows, and mobile-first auth (phone OTP, Google sign-in) optimized for students.
Mobile Authentication
Phone OTP and Google sign-in flows designed for a student-first, mobile-heavy audience — low friction onboarding before search, saves, and visit requests.
Staff Operations Panel
Operational backbone for PG visits, lead coordination, property verification, student onboarding, follow-ups, booking coordination, and query handling — enabling Nestingo to run as a process-driven service company, not a passive marketplace.
Admin Dashboard
Centralized property management (galleries, amenities, pricing, inventory), user and staff roles, lead and booking pipelines, visit scheduling, and CMS for homepage, FAQs, testimonials, and campaigns.
PG Captain Model
Hybrid tech + human operations: local guidance, visit assistance, and accommodation consulting at no extra charge — increasing trust, conversion, and retention versus broker-only or listing-only competitors.
Engineering Team Expansion
Hired two developers to parallelize frontend and backend work — reducing bottlenecks, accelerating admin and staff tooling, and improving iteration speed on the public product. A major inflection point for delivery and operational support.
Product Screens
Landing & Discovery
Homepage and entry into locality-based PG search across Delhi NCR.
Sign In & Onboarding
Mobile-first authentication with OTP and Google sign-in.
Property Detail — Overview
Standardized listing layout with galleries, pricing, and trust signals.
Property Detail — Amenities & Rules
Structured amenities, food options, and house rules for transparent comparison.
Property Detail — Booking & Inquiry
Visit scheduling and inquiry flows tied to operational follow-up.
Technology vs. Traditional Market
Discovery
Replaced offline brokers with searchable, filterable digital property discovery.
- Locality search
- Gender & sharing filters
- Maps
Trust
Verification workflows and structured listing data instead of fake or opaque postings.
- Verified PGs
- Guided visits
- Standardized pages
Operations
Lead management, visit booking, and staff dashboards for coordinated execution.
- Inquiry pipeline
- Visit scheduling
- Staff panel
Inventory
Admin-controlled room inventory and pricing visibility across the ecosystem.
- Property CMS
- Inventory sync
- Role permissions
Business & Scale Vision
Phase 1 target
150 beds
Initial managed operations scale outlined in investor planning.
Year 3 ambition
1,000+ beds
Path toward a broader managed PG network beyond discovery-only.
Break-even focus
~75% occupancy
Operational discipline tied to profitability in managed accommodation.
Positioning
Operator-first
Competed on operations, food, maintenance, and resident experience — not aggregation alone.
CTO Outcomes & Learnings
Technical leadership
Team + delivery
Hiring developers, managing execution, and converting vision into shippable multi-role systems.
Product architecture
3 platforms
Public site, staff ops, and admin infrastructure with booking and lead workflows end to end.
Startup execution
MVP → scale
Lean build, operational software design, and adaptation to real-world PG market constraints.
Strategic thinking
Ecosystem vision
Long-term GigVid direction — using stable accommodation cashflows to fund a video-first gig marketplace.
“Nestingo was not just a listing platform — it was an attempt to own the resident experience through technology, verification, and operational systems working together.”
Building operational products as CTO?
I architect multi-platform startups, scale engineering teams, and ship the internal tooling that offline industries need to run digitally.