Hamro Driving
Hamro Driving is a multi-tenant SaaS platform that replaces the spreadsheets, receipt books and WhatsApp threads most driving schools still run on. Every school gets its own secure workspace never sees another school's data. and Inside that workspace, a school runs its entire operation. Admins enrol students with photos and citizenship documents, assign them a lesson package and licence category (car, bike, scooter, truck or bus), and track attendance, trials and licence exams through to completion. Bookings are scheduled ahead of time, then handed to a live Active Sessions board that shows every lesson in progress with a running countdown, one-click instructor or vehicle swaps, and a voice alert when a slot ends. Instructors get profiles, daily attendance and monthly salary runs. Vehicles get service history and automatic bluebook and insurance alerts seven days before they lapse the renewals schools most often miss. — The money side is where we made our most deliberate design decision: invoices are derived, never generated. A student's balance is computed live from their package fee, discount and payments, so the profile page, the printed invoice and the fees report can never drift apart. Around it sits a full finance module income and expense ledgers, debtors and creditors with printable statements, and ten date-filtered reports that export to CSV. - We designed and built the entire product end to end: the animated marketing site, the three-tier role system (platform owner, school admin, and staff with per-module access), the subscription engine that gates navigation and API access from a single feature catalogue, online plan renewals through Khalti, and Driver Dai - a bilingual Nepali/English AI assistant that answers questions about a school's own data using read-only tools locked to that school server-side.
Visit live site- category
- SAAS, WEB
- duration
- ~ 6 weeks
- team
- 4 in-house
- status
- shipped

What we shipped.
We ran Hamro Driving end to end — discovery and scoping, interface design, engineering, QA, and launch. Work moved in short review cycles, so the client saw a working build at every stage instead of a document describing one, and decisions were made against something they could actually click through.
Every build decision was made with the client's long-term ownership in mind: a typed and documented codebase, automated deployments, and analytics and error monitoring wired in before launch. The client owns the source outright, and we stay available for support and iteration after handover.
- Design system + style guide
- Production codebase (TypeScript)
- Admin dashboard
- CI / CD pipelines
- Analytics + observability
- Documentation + handover
Have an idea worth shipping?
Tell us what you're building. We'll respond within one business day with a scoping plan, a timeline, and a fixed quote.
