WORKGOVERNMENTPROTOTYPE
Aaradhya Online Seva Kendra
A service-first digital experience for a private citizen assistance centre — built as a tenant on the SevaDesk platform, with public service discovery connected to CRM, bookings, document tracking and workforce management.
Aaradhya Online Seva Kendra — Business Website + Service Discovery + CRM + Bookings + Workforce
- Next.js 14
- React 18
- TypeScript
- Prisma 5
- PostgreSQL
- Zod
- Tailwind CSS
- GSAP
- Resend
- OpenWA
- Vercel
From problem to product
01 / The problem
A walk-in assistance centre has to explain a large, confusing government-service catalogue to someone who arrived with a problem rather than a document list. The service list lives in people's heads and on government portals, enquiries arrive unstructured, and follow-up on a pending application has no system behind it.
02 / The approach
The service catalogue was normalised once, platform-wide, and the tenant's own assisted services were layered on top of it with a per-service fee note and bookable flag. A citizen lands on a department → category → service path, reads requirements, books, then tracks. Everything a citizen does lands in the owner's CRM, and the owner's staff surface handles documents, applications and attendance.
03 / What shipped
Citizen → public tenant site at /b/{slug}
About this build
Aaradhya Online Seva Kendra is a private digital citizen assistance centre in Pimprala, Jalgaon. It is a tenant on the SevaDesk platform: the public site, the CRM, bookings, document tracking and the workforce surface are one system rather than five separate tools.
The centre assists citizens with a defined set of government services — Aadhaar, PAN, voter ID, income and caste certificates, domicile, land records, PM-Kisan, Ladki Bahin and the MahaDBT scholarship — and charges its own transparent assistance fee, always separate from any government fee.
It is a private assistance business. It is not a government body and holds no government approval, certification or authorised-centre status; the platform it runs on makes no such claim either.
WHAT THIS IS FOR
- Explains a large, confusing government-service catalogue to a citizen who arrived with a problem rather than a document list.
- Turns an unstructured walk-in enquiry into a booked, trackable application with follow-up behind it.
WHAT YOU GET FROM IT
- A department → category → service path, with each service's requirements stated before anyone walks in.
- The centre's own assistance fee is carried per service and kept visibly separate from any government fee.
- Everything a citizen does lands in the owner's CRM as the same record, so follow-up has a system behind it.
- Documents, applications and staff attendance are handled in one surface instead of a diary and a phone.
How it is structured
- Citizen → public tenant site at /b/{slug}
- Tenant website, booking and enquiry
- CRM — leads, customers, enquiries, follow-ups
- Documents, applications and escalations
- Workforce and attendance
- Owner surface at /owner/{slug}, employee surface alongside
- All of it one Next.js app and one Postgres database, separated by tenancy checks rather than by deployment
Platform capabilities
- Multi-tenant isolation re-checked per request
- Owner-authored CMS with a tolerant read path and a strict write path
- Per-category visual identity as a token object, so a new category needs no frontend code
- Server-resolved language so the first paint is already correct
What the public sees
- Department and category browsing
- Service detail with requirements
- Service search
- Booking with per-service assistance fees
- Application tracking by token
- Document upload and status
- Announcements and updates
- Scheme and portal directories
- Guidance and contact
- Marathi / English, resolved server-side with no hydration flash
What the team uses
- Owner dashboard
- CRM — leads, customers, enquiries, follow-ups, tasks
- Bookings and appointments
- Service catalogue with requirements
- Document review and status transitions
- Applications and escalations
- Announcements
- Workforce — employees, shifts, leave, holidays, locations, attendance, live view
- Transactions, reports and analytics
- Website block editor
- Team, notifications, settings
Connected systems
- WhatsApp outbound — booking notifications via an OpenWA instance
- WhatsApp inbound — gateway webhook, HMAC-SHA256 signed, timing-safe, fail-closed
- Transactional email via Resend
- Platform government-service catalogue shared across tenants
Structural facts
- Public pages
- 19
- Route segments under the tenant site
- Owner modules
- 16
- Sections of the owner surface
- Assisted services
- 12
- Tenant service overlays seeded for this centre
- Catalogue
- 27 / 41 / 71
- Departments / categories / services platform-wide
Captured from the running system
Advertisement and promotional work
Software is only half the story. These are the advertisements and promotional creatives produced to present and communicate the product.
No public tenant URL. This centre runs as a seeded tenant on a local database, and the platform's production deployment has no tenant created on it yet — so there is nothing to link to. A live link is added the moment a tenant is provisioned on production.
One message — what happens today, and what you want instead. A straight answer within a day, including when it does not need building.
← All work