← All projects

In production Jan 2026 — present

LM-CRM — offline-first field CRM for pharmaceutical sales reps

Proves that a medical representative really was at that pharmacy, at that time, doing that work — on cheap Android phones with unstable LTE.

Role
Designed and built end to end (backend, mobile, web panels, deploy)
Stack
Flutter · FastAPI · PostgreSQL + PostGIS · Redis · React + Ant Design · Docker · Nginx · Firebase FCM · S3 · Sentry
daily field users
50+
visits logged per day
180+
commits (Jan–Oct 2026)
1,465
backend + mobile tests
1,052 + 2,774
roles, multi-tenant
7
Rep app: the week — 5 of 5 visits completed, each with time, target and address
Rep app: the week — 5 of 5 visits completed, each with time, target and address
Rep app: pharmacies for the day, quick-add visit per weekday
Rep app: pharmacies for the day, quick-add visit per weekday
Rep app: profile — LPU, pharmacy and doctor catalogues, reports, coaching
Rep app: profile — LPU, pharmacy and doctor catalogues, reports, coaching
Rep app: login with server reachability check (dev flavour)
Rep app: login with server reachability check (dev flavour)
Tenant admin: today's workdays, visits vs plan, pending reviews (demo tenant)
Tenant admin: today's workdays, visits vs plan, pending reviews (demo tenant)
Map: visit events with GPS distance, per rep, per day
Map: visit events with GPS distance, per rep, per day
Visits: status, target, distance to geofence, export
Visits: status, target, distance to geofence, export
Region manager web (PWA): office day, visits, approvals
Region manager web (PWA): office day, visits, approvals

The problem

Pharmaceutical companies pay medical representatives to visit doctors and pharmacies. The company sees the reports, not the visits. Existing CRMs (Quadrasoft, Proxima — $55–120 per user per month) assume connectivity; in Uzbekistan the rep is often on a cheap Android phone with LTE that drops every few minutes, so visits were logged late, from memory, or not at all. Managers could not tell a real visit from a typed one.

What I built

A multi-tenant CRM where the mobile app is the source of truth and works with no network, and the server reconciles later:

What changed

What I would do differently

The offline layer was built on top of an online-first design borrowed from the incumbents. Most of the hard bugs lived in that seam. The second time (Meros.ai) I designed offline-first from the first migration, and the sync core took a week instead of a quarter.

Private repository. I can walk through the architecture, the sync core and the fraud engine on a call, and show a demo tenant.