Software shaped by the work behind the business.

Kramvia Technologies is the name this work is being built under. Today that is one person. Rishabh Gupta founded it and currently does the product design, engineering and customer conversations himself. He was born and raised in Mumbai, and holds a Bachelor’s degree in Data Science from Arizona State University in Tempe, Arizona.

• Founded and currently run by one person, with no outside team.
• In the product-building phase. Formal registration and commercial availability follow as pilot scope is agreed.
• An enquiry goes directly to the person building the product.

Pharmacy distributors often stay on software they have outgrown, because leaving is the expensive part. A move means rebuilding masters, re-entering opening stock and accepting opening balances that nobody can fully explain. The software is rarely the real obstacle. The switching cost is. Kramvia starts from that problem rather than from a feature list.

• Migration treated as a data-integrity problem, not a sales checkbox.
• The opening position should reconcile against the source system before the first new transaction is posted.
• Supported legacy identifiers stay attached to reviewed records, so staff keep the context they already recognise.
• Established products already offer migration, accounting and audit. The intended difference is how reviewable the move is, not a longer feature list.

Pharmacy workflows carry details that generic descriptions can miss: batches, expiry dates, packing units, commercial terms and financial exports from different systems. Those details shape our product discussions.

• Begin with an actual workflow and the people who use it.
• Describe the underlying records before proposing automation.
• Use representative examples to expose exceptions early.

The choice is about the scope of change your business wants to make. ERP brings operational and financial work together; Ledger is the separate accounting route when an ERP replacement is not the immediate priority.

• ERP: migration, pharmacy operations, transaction-linked accounting and audit review.
• Ledger: standalone financial imports, reconciliation and accounting development.
• No automatic data sharing or requirement to adopt both products is implied.

The website explains product direction alongside current availability. ERP enquiries concern a controlled pilot; Ledger remains in development and validation. Broader scope should be agreed when it is ready.

• Explain what the proposed evaluation includes.
• Keep roadmap intentions separate from available capabilities.
• Use review findings to guide the next stage of development.