Pharma smart shopping SaaS

Context

Extendeal runs a B2B smart shopping SaaS for the Argentine pharmaceutical sector. Pharmacies compare prices, build orders, and manage integrations with multiple distributors in critical purchase flows — errors cost stock and margin.

Problem

The frontend team grew from 2 to 5 engineers while the product added modules (cart, checkout, comparator, analytics). Without shared standards, each feature duplicated patterns, deploys were unpredictable, and checkout regressions increased.

Solution

Established standards on critical purchase flows, Jenkins pipeline with quality gates, PR/code review conventions, and technical mentoring. Rotating ownership by domain. Event-driven architecture with SQS/EventBridge for orders and inventory.

Architecture

Pharmacies (B2B)
      │
      ▼
┌─────────────────────────────────────┐
│  Next.js · React · TypeScript       │
│  Purchase flows · integrations      │
└─────────────────┬───────────────────┘
                  ▼
         REST APIs · SQS/EventBridge
                  ▼
    Pharmaceutical distributors (N+)
                  │
           Jenkins CI/CD → AWS

Timeline

1. Month 1–6

   Standardization

   Folder conventions, UI library for purchase flows, lint + tests on PRs.

2. Month 6–12

   CI/CD

   Full Jenkins pipeline: build, lint, automated deploy to AWS.

3. Year 2–3

   Team scale

   Onboarding 3 devs, module ownership, biweekly architecture sessions.

Stack & tools

My role

• Technical leadership of 5 frontend engineers
• UI architecture and state pattern definition
• Code review and quality standards on PRs
• CI/CD pipeline design and implementation
• Mentoring on complex third-party API integrations

Impact

• 5 frontend engineers under technical leadership
• ~40% fewer production bugs
• 5-year roadmap delivered in 3 years
• Event-driven architecture with SQS/EventBridge in production