WorkWorkInfoInfoLearnLearnGet Into TouchGet Into Touch
LinkedInLinkedInResumeResume

From 400 pharmacies in Week 1 to 3,000+ today. Mero Pharmacy Manager became Nepal's leading mobile pharmacy platform

I eliminated POS training requirements and designed mobile-first inventory with smart autocomplete and notebook-style entry. 400+ pharmacies signed up in Week 1 (vs 12% competitor adoption). Today, 3,000+ pharmacies save 1.5–2 hours daily. That's ~5,250 hours recovered per day across Nepal's pharmacy sector.

Timeline12 Months(24/25)
RoleProduct Designer
PlatformAndroid/iOS
Outcome3,000+ pharmacies
Mero Pharmacy Manager app screens across sales, inventory, and customer management

Business Context

12% → 400+ → 3,000+: competitor adoption in tier-2 cities, Week 1 signups, and current platform scale

Mero Pharmacy's revenue model is advertising from pharmaceutical companies (current), with a planned transition to B2B marketplace fees (2–3% on supplier transactions). The business depends on daily active usage. Pharmacies that don't log inventory 3+ times per week don't see ad impressions and don't return.

The “POS training → desktop software → complexity” barrier kept competitor adoption at 12% across Nepal's ~15,000 registered pharmacies. Each 10-point improvement ≈ 1,500 additional pharmacies × 3 daily sessions × ad revenue. That scale matters for marketplace launch.

Key insight: The design priority wasn't feature-rich; it was habit-forming. Daily logging had to be faster than the notebook, or pharmacies would revert.

Research and Problem Discovery

Problem statement

User: Small pharmacy owners (45+ age, low digital literacy, Nepali-primary, ₹8K–₹15K Android on 2G/3G).

Action: Log daily inventory (40–60 entries), track customer dues, monitor stock, reorder from suppliers.

1. Mental model mismatch: POS grid (SKU | batch | barcode) ≠ notebook thinking (medicine → quantity → customer).

2. Input bottleneck: Typing “Esomeprazole” on ₹8K Android ≈ 18s per entry. 40 medicines/day ≈ 12 minutes of pure typing, slower than a 5-minute notebook.

3. Training barrier: Competitor POS: 4–6 hours training, 2-day setup. Owners can't afford downtime during onboarding.

Result: Digital was slower and more complex than the notebook. ~70% reverted within 2 weeks. 12% competitor adoption in tier-2 cities.

Field observation (8–10 pharmacy visits)

Visited 8–10 pharmacies across Kathmandu and Bharatpur over 2 months, observing 2–3 hours of daily operations each.

  • 6 of 8 owners opened physical notebook first when shown digital alternatives
  • All 8 pharmacies had smartphones (₹8K–₹15K range, low-end Android)
  • 2 of 8 had desktop computers; both unused
  • 7 of 8 mentioned: “I tried digital before. Too complicated. Went back to notebook within 2 weeks.”

User interviews (15–20 pharmacy owners)

30–45 minute interviews focused on workflow, pain points, and past attempts at digital systems.

  • Average training time for competitor POS: 4–6 hours
  • Average abandonment: 2 weeks post-training
“The trainer spent 4 hours teaching me, and I still forgot after he left”
“Barcode? Most medicines here don't have barcodes”
“I can't afford ₹15K for scanner hardware”
“Typing takes too long. I already know the medicine names; I just want to log quickly”

Competitor benchmark

PlatformDesktop POSDesktop + mobile webMobile appMobile-first
Training required4–6 hours3 hours2 hours<10 minutes
Hardware neededScanner (₹15K)DesktopNoneNone
Setup time2 days1 day1 hour10 minutes
Input methodTyping onlyTyping onlyTyping onlyAutocomplete + typing
LanguageEnglish onlyEnglish onlyEnglish + NepaliNepali-first
Adoption (tier-2)~8%~15%~10%400+ week 1

Options Considered and Decision

Option A

Desktop POS system

Partner with hardware vendor, subsidized barcode scanners, desktop software with full inventory analytics and reporting.

Rejected

₹28K investment barrier. 4–6 hour training. 9–12 month timeline. Doesn't address mental model mismatch.

Option B

Web app (PWA)

Mobile-responsive progressive web app, works offline, no app store download, typing with autocomplete.

Considered

No download friction, but typing still slow. No home screen presence. PWA offline harder than native.

Option C · Chosen

Mobile-first app

Native Android with smart autocomplete, notebook-style rows, offline-first sync, Nepali + English UI, SMS due reminders, and WhatsApp supplier reordering.

Selected

Autocomplete cuts typing from ~18s to under 5s per medicine; notebook layout removes cognitive load. Zero training, time-to-value from Day 1. Works on ₹8K phones with 2G.

Why mobile-first won

  • Addresses root cause: autocomplete cuts typing from ~18s to under 5s; notebook rows remove cognitive load
  • Time-to-value from Day 1: owners reported 1.5–2 hours saved daily vs manual bookkeeping
  • Zero training: layout reads like a notebook; autocomplete works like familiar search
  • Works on existing infrastructure: ₹8K Android and 2G; no scanner or desktop required
  • Habit-forming: faster daily logging builds retention for ads and future marketplace fees

Tradeoff: what we gave up

Analytics depth

Lost: Profit margins, trend analysis, SKU-level insights.
Why acceptable: Owners asked for simplicity, not dashboards. Analytics add cognitive load.
Revisit when: Adoption >50% and owners request monthly sales trends.

Barcode scanning

Lost: Fast input for medicines with barcodes.
Why acceptable: 60–70% of tier-2 inventory is gray-market with no barcodes. Autocomplete works for every medicine name.
Revisit when: Urban users with barcode availability >40% of base.

Multi-user / multi-location

Lost: Chains with multiple locations or staff on one account.
Why acceptable: 89% of Nepal pharmacies are single-location, owner-operated.
Revisit when: Pharmacy chains become >20% of paid subscribers.

Real-time supplier integration

Lost: One-click reordering via supplier APIs.
Why acceptable: Tier-2 suppliers use WhatsApp, not portals. Integrations = 6–9 months.
Revisit when: B2B marketplace phase (Year 2).

The app that replaces the notebook must be simpler than the notebook, not more complex.

The Design and Decision by Decision

Screen 1 of 5

Screen 1: Home dashboard

Weekly totals on open

Decision

Put last-week NPR total and a sales vs expenses split card above every shortcut on home.

Why

Owners open the app to answer one question first: How is my shop doing? Summary up top matches that habit without opening reports.

Rejected

Analytics dashboard with charts that needed a training session to read.

Mero Pharmacy Manager home screen with weekly NPR totals, services grid, and bottom navigation

Services grid for daily tasks

Decision

Four equal-weight tiles: Price list, Sales & Expenditure, Customer Record Management, and Request A Feature.

Why

eSewa-style grids are already familiar in tier-2 Nepal. One tap per daily workflow beats hunting nested menus.

Rejected

Hamburger menu with workflows buried two or three levels deep.

The Outcome

Beta testing (5 pharmacies, 8 weeks)

Ran beta with 5 pharmacies, visiting weekly to observe real usage and collect feedback.

  • Week 1: All 5 pharmacies set up in <10 minutes (vs 4–6 hours for POS)
  • Week 2: 4 of 5 asked: “Can it auto-suggest after a few letters?” Typing full medicine names was taking too long
  • Week 4: 5 of 5 reported 1.5–2 hours/day saved vs notebook
  • Week 8: 5 of 5 still using daily (90% retention vs ~30% competitor benchmark)

Smart autocomplete wasn't a nice-to-have; it was essential. Typing "Paracetamol" on ₹8K Android took ~18s. Suggestions after 3–4 characters cut entry to under 5s, roughly 70% faster.

From Pilot to Platform: 7.5x Growth

Week 1

400

pharmacies
Month 3

~900

estimated
Month 6

~1,800

estimated
Current

3,000+

active

Market penetration: From 2.7% (Week 1) to 20% of Nepal's ~15,000 pharmacies

Context: Competitor POS systems achieved only 12% adoption after years in market. Mero Pharmacy reached 20% penetration, becoming Nepal's largest mobile-first pharmacy platform.

Time Savings at Platform Scale

Per pharmacy

1.5–2

Hours saved daily

Validated across 5 beta pharmacies over 8 weeks. Manual bookkeeping: 2–3 hours/day. With app: 30–45 minutes.
Platform-wide

5,250

Hours saved daily

3,000+ pharmacies × 1.75 hrs avg = 5,250 hours/day. Annual: 1.9M hours = ₹383M in reclaimed labor time.

Business Validation: From Free to Platform

Current: 3,000+ pharmacies using the free app (ad-supported from pharmaceutical companies)

Platform scale achieved: Ready for B2B marketplace transition (connecting pharmacies with wholesalers)

Projected Year 2 revenue:

  • 3,000 pharmacies × ₹50,000 avg monthly supplier orders
  • 2–3% transaction fee
  • Potential: ₹3–4.5M monthly GMV (₹36–54M annually)

The 7.5x growth from launch validates the core hypothesis: Nepal's tier-2 pharmacies needed mobile-first, not desktop POS.

Next case study

1 min read
Saharamind
siddart

© 2026 Sidd Art | All Rights Reserved.

Last updated on Jan 01, 2026

Discover me:

  • Linkedin
  • Instagram
  • Figma Profile
  • Resume

Resources

  • Info
  • Learn
  • Articles

Products

  • Stacklite.live
  • Polaroid Camera