Overview
Why nobody publishes a price, and what to do about it
A single branch pathology lab with manual result entry and a two hundred test menu, and a three branch diagnostic centre with collection centres, six analyser interfaces, and credit accounts with fourteen referring hospitals, are not the same purchase. They differ by more than an order of magnitude in setup work, and almost all of that difference is in configuration and data rather than in software. That is why a published package price in this category is usually either meaningless or a starting point designed to be exceeded.
The more useful way to think about it is one-time cost against recurring cost. One-time covers implementation: loading your test catalogue, reference ranges, panels and rate lists, formatting your report layouts on your letterhead, migrating your active patient list, configuring roles and billing rules, connecting analysers, and training each role on its own screens. Recurring covers the licence or subscription, hosting if we host it, support, and updates. A quotation that does not separate these two is not comparable to one that does.
The cost drivers that move the number most, roughly in order, are: how many users and counters need access, how many branches and collection centres you run, whether analyser interfacing is required and for how many machines, how clean your existing test catalogue and rate list are, whether you host it yourself or we host it, and how much historical data you want migrated. Interfacing and catalogue cleanup are the two that most often surprise buyers, because both are quoted as software and delivered as weeks of careful work.
For comparison against the alternative: commissioning custom software in Nepal typically starts around NPR 200,000 for a focused first version and runs from around NPR 600,000 upward for multi department systems, and a lab system is not a small build. Adopting an existing product such as Nidanyo is quoted by lab size and modules and is substantially cheaper than commissioning the equivalent, which is the usual reason labs adopt rather than build.
Worth reading alongside this: software development in Nepal, our software products, and web development company in Nepal.