How Medikabazaar Closed Critical Front-End, QA, and Design Skill Gaps with Embedded Ajackus Engineers

Client

Medikabazaar is India’s leading B2B healthcare marketplace, connecting hospitals, clinics, and healthcare institutions with medical equipment and consumables suppliers. The platform handles complex B2B procurement workflows — including multi-tier pricing, compliance requirements, and large-scale catalogue management — making front-end usability, product quality, and testing robustness genuinely mission-critical. Medikabazaar came to Ajackus seeking staff augmentation to fill specific skill gaps that their existing team and multiple vendor partners had been unable to reliably provide.

Challenge

Heavy Dependency on Multiple Fragmented Vendor Teams

Medikabazaar’s reliance on multiple external tech teams created structural coordination problems: misaligned priorities, communication gaps between vendors, and delays that cascaded across interdependent workstreams. Managing multiple engineering relationships consumed internal bandwidth and introduced inconsistency in how different parts of the product were being developed and tested. A single integrated partner with cross-functional capability was needed to replace this fragmented model.

Critical QA Resourcing Gap

At one point in the engagement history, Medikabazaar’s QA function consisted of a single professional. For a B2B healthcare marketplace where product reliability directly affects how hospitals and clinics procure medical equipment, this was a dangerous bottleneck. The insufficient QA capacity meant that testing cycles could not keep pace with development output, increasing the risk of undetected defects reaching production.

Absence of Development Context and Business Alignment

Medikabazaar identified that their engineering team — including external vendors — was often working without a clear understanding of why specific features were being built. This absence of business context led to technically correct but strategically misaligned output: features that met their specified requirements but missed the broader business objective. What the team needed was an engineering culture in which developers understood not just the task, but the outcome it was meant to serve.

Goals

The project focused on filling critical skill gaps across development, QA, and design while consolidating vendor relationships into a single partner.

Journey

Ajackus embedded a multi-disciplinary team with Medikabazaar across four structured phases, from skill gap assessment through business context cultivation.

Phase 1: Skill Gap Assessment and Team Composition

The Ajackus team began by assessing precisely where Medikabazaar’s capability gaps were most acute — front-end development, QA engineering, and UI/UX design were identified as the priority areas. Rather than embedding a generic engineering team, Ajackus composed a multi-disciplinary unit with specific expertise matched to each gap: QA engineers with automation testing experience (Cypress, Selenium), designers proficient in Figma and product design, and front-end developers aligned with Medikabazaar’s existing technology stack.

Phase 2: Agile Integration and Delivery Alignment

The Ajackus team adopted an agile methodology from the outset, integrating into Medikabazaar’s existing sprint cadence and delivery workflows rather than operating as a parallel workstream. This integration approach — rather than running a separate Ajackus delivery track — meant that the embedded engineers participated in the same planning, review, and retrospective processes as Medikabazaar’s internal team. Rapid ramp-up was prioritised, with the Ajackus team contributing to sprint deliverables from the first sprint.

Phase 3: QA Infrastructure and Coverage Expansion

The Ajackus QA engineers immediately began expanding testing coverage to address the bottleneck created by insufficient QA capacity. Automated testing using Cypress and Selenium was introduced to accelerate regression testing cycles, reduce manual QA effort, and ensure that new feature delivery did not outpace testing capacity. The QA function was effectively rebuilt from a single-resource limitation into a structured, scalable operation.

Phase 4: Cultivating Business Context Awareness

The Ajackus team actively encouraged a culture in which engineers sought to understand the business purpose of their development tasks — not just the technical specification. This involved fostering direct communication channels between the Ajackus engineers and Medikabazaar’s product and business stakeholders, so that development decisions were made with an awareness of the outcomes they were meant to produce. This shift in approach improved the quality of technical decision-making and reduced the frequency of technically correct but strategically misaligned deliverables.

Results

Medikabazaar moved from a fragmented multi-vendor model to a single, trusted engineering partner — with QA, design, and front-end capability now embedded within the team.

What went well:

Operational Achievements

• QA function scaled from a single-professional bottleneck to a multi-engineer team with automated testing capability (Cypress and Selenium)
• Front-end development and UI/UX design capability embedded within Medikabazaar’s engineering team for the first time
• Multiple external vendor relationships consolidated into a single Ajackus partnership, eliminating cross-vendor coordination overhead
• Agile delivery model adopted, aligning Medikabazaar’s engineering output to sprint-based planning and review cycles

Technical Achievements

• Automated regression testing implemented using Cypress and Selenium, reducing manual QA cycle time
• Figma-based design process introduced, raising the consistency and quality standard of product interface work
• Front-end feature delivery accelerated through dedicated Ajackus front-end engineers operating within Medikabazaar’s stack
• Business context framework embedded across the team, reducing instances of technically complete but strategically misaligned deliverables

Business Impact

• Medikabazaar moved from a fragmented multi-vendor model to a single, trusted engineering partner relationship — reducing management overhead and increasing delivery predictability
• The company’s QA capability, previously a structural risk, is now a functional strength — with automated testing supporting faster release cycles without increased defect risk
• The Ajackus engagement expanded organically from an initial technical mandate into QA and design, reflecting growing confidence in the partnership and the team’s cross-functional capability