When we started, the obvious move was to resell an existing GPS platform. White-label it, put our name on it, sign up customers. Cheaper, faster, less risk. We tried that for about six months before we gave up and built our own.
The platforms available were built for flat roads, stable connectivity, and English-speaking users. Nepal has none of those. A vehicle going from Kathmandu to a hilly district drops signal a dozen times. Drivers speak Nepali or Hindi, not English. Government clients need reports in Bikram Sambat dates, not Gregorian. Every time we hit one of these walls with the white-label platform, the answer was "not on our roadmap." After the third time, we decided our roadmap was the only one that mattered.
Building it ourselves meant solving problems that do not exist in most telematics markets. Buffering GPS points during signal loss and flushing them in order on reconnect. A full Bikram Sambat calendar conversion layer because every government report runs on BS dates. Nepali and Hindi UI because a dispatcher in Butwal should not need to know English to read an alert. None of this is glamorous engineering but all of it is the difference between a product that works here and one that does not.
Two years later NepTrack with Smart Mobility and GPS vehicle Tracking is live with paying customers across private fleets, schools, and municipal transport. The reseller route would have been faster to start. It would also have meant building someone else's product forever. For a market this specific, owning the stack was the only way to actually serve it.
Two years later NepTrack is live with paying customers across private fleets, schools, and municipal transport. The reseller route would have been faster to start. It would also have meant building someone else's product forever. For a market this specific, owning the stack was the only way to actually serve it.
