Monastirev
Data Nexus delivered a full operational and product system rebuild for a federal pharmacy e-commerce platform, including smart filters, dual pricing, UX redesign, and efficiency gains without budget growth.

- Client
- Monastirev
- Year
- 2022
- Duration
- 7 months
- Scope
- CRM, Marketing, E-commerce, SaaS
Invariant
Medical logic — dose, form, prescription status, patient age — belongs to the catalogue, not to the filter interface.
Operational Rebuild & Product Transformation for a National Pharmacy E-Commerce Platform
The client approached Data Nexus in a state of acute operational fragmentation.
Processes were unsynchronized, responsibilities overlapped, teams operated in a reactive “firefighting mode,” and the digital product (website + mobile apps) had accumulated years of technical debt and UX degradation.
Incoming requests were scattered across departments, prioritization was inconsistent, and critical decisions were bottlenecked by a small number of overloaded specialists.
Simultaneously, the product experience suffered from outdated UX patterns, non-contextual filters, overloaded PDPs, lack of a consistent design system, and the inability to extend the mobile app due to platform limitations.
The mandate was clear:
restore operational discipline, rebuild product architecture, redesign the entire digital experience, and do it all without increasing budgets.
Data Nexus treated the engagement as a full-scale operational and product crisis requiring structural intervention, architectural clarity, and disciplined execution.

What Data Nexus Did?
1. Fragmented operational model
No consolidated intake process
Scattered communication channels
Overlapping responsibilities
Two severe bottlenecks: analytics & testing
No unified governance over website and applications
2. Outdated product architecture
Category structure inconsistently defined
Filters did not reflect medical logic or customer intent
PDPs overloaded with unstructured content
No clear logic for dual pricing:
“Buy now” vs. “Receive on date”
Mobile app built on IMSHOP.io — technically unscalable
3. Duplicated costs & misallocated team capacity
Internal report highlights:
70% of IT workload was spent on bug fixing
Multiple internal systems competing for developer attention
Legacy services (WebKC, WebPrices, parsing) required re-architecture
Teams had zero bandwidth for proactive development
4. Lack of predictability and delivery rhythm
Deadlines shifted constantly.
Task backlogs accumulated uncontrollably.
Teams operated in reactive mode with no structural process control.

1. Built a new operational architecture for e-commerce
Following the structure presented in the official report , Data Nexus:
Formed a dedicated e-commerce operational unit
(Support Lead, PM, UX/UI, Product Analyst, Content, PO for mobile).
Consolidated all incoming requests exclusively under e-commerce
→ analytics → prioritization → development → dedicated QA.
Established a specialized development team focused solely on website and mobile apps.
Removed cross-functional collisions, clarified roles, restructured responsibilities.
This eliminated chaos and restored end-to-end control.
2. Re-engineered the operational pipelines
Data Nexus introduced a controlled, measurable flow:
Unified intake and qualification
Business- and UX-driven prioritization (ICE framework)
Technical specification
Development
Dedicated QA (removed the global company bottleneck)
Documentation & release
Manual friction was eliminated, and lead times became predictable.
3. Introduced systemic discipline & architectural governance
Migrated processes to Confluence
Appointed an additional Team Lead to remove IT bottlenecks
Introduced mandatory product analytics before acceptance
Eliminated duplicated systems and legacy processes
Moved mobile development in-house
The system shifted from reactive to structurally governed.
4. Complete product redesign (Web + Mobile)
Leveraging the screens you provided, Data Nexus executed a full UX and UI transformation:
✔ Smart Filters (contextual, adaptive, medical logic-driven)
Filters now adapt based on:
type of use
dosage form
active ingredient
delivery speed
prescription status
patient age
analog recommendations
Mobile implementation includes dynamic smart tags and compressed UX paths.
✔ Dual Price Logic (new pricing architecture)
Introduced a transparent model:
Buy Now → Immediate pickup at nearest pharmacy
Receive by Date → Logistic-optimized pricing, with “best price per dose” indicators
This removed a major user friction point and reduced support load.
✔ Product Page (PDP) redesign
Clean CTA zones
Structured medical attributes
Improved analog recommendation block
Unified design language
Better readability & comprehension
✔ Catalogue redesign
New card architecture
Medical attribute surfaces
Highlighted benefits & ratings
Faster navigation & vertical scanning
Strong visual hierarchy
✔ New design system for Web & Mobile
Entire UI foundation rebuilt
Full redesign of loyalty program, profile screens, cart, catalog, filters
Removed all IMSHOP.io constraints; prepared native mobile app architecture
5. Cost optimization without increasing budget
Based on the internal operational conditions:
Rebalanced workload across the newly expanded structure
Used outstaff strategically for architecture-heavy tasks
Reduced developer overload and unblocked progress
Shortened development cycle from 4 weeks to ~1.5 weeks
No additional budget required — efficiency came from structural rationalization.

More Stability, Faster Delivery
With a rebuilt operational core and a redesigned digital product, the company unlocked a faster delivery rhythm, reduced support load, and significantly improved user engagement.
- 2.5x
- Time-to-Market reduced
- 30–40%
- Reduction in support inquiries related to pricing & availability
- 2x
- Increase in catalogue & PDP engagement after Smart Filters redesign
Data Nexus demonstrated an exceptional level of ownership, structural thinking, and operational discipline throughout our collaboration. Their approach is not about creating impressions — it is about eliminating friction, restoring order, and delivering a system that runs cleanly and predictably.
The Data Nexus team was equally effective in deep individual analytical work and in collaborative environments involving internal teams, external partners, integrators, and vendors. They maintained a balanced, neutral, and constructive stance in difficult situations, driving change at a steady rhythm without overwhelming the organization.
Impact & Results
Data Nexus transformed a fragmented, overloaded, and outdated operational model into a coherent, high-efficiency system — without increasing budgets. Through structural rationalization, process redesign, and removal of duplicated costs, they delivered results that exceeded the business KPIs originally set.
This was a true example of disciplined crisis management:
no theatrics, no cosmetic changes — just real transformation of processes, spending, and organizational structure. Their work required maturity, critical thinking, and the ability to operate under pressure without slipping into reactive behavior. Data Nexus demonstrated all of this in practice.We are left with only positive impressions, and I would gladly provide a verbal recommendation if needed.