Built by people who ship, led by someone who's accountable for it.
Zopflix Softech Private Limited has spent years building software. Today, that experience is entirely redirected toward one thing: helping enterprises design, build, deploy, and operate AI systems that do real work, not pilots that quietly get shelved. We're a new direction with an established name behind it — Zopflix AI — and we'd rather say that plainly than dress it up.
Leadership
Where the conviction started
Zopflix AI exists because of a conviction Girish Sharma, CEO of Zopflix Softech Private Limited, has held for a while: that AI-assistance is the next real lever for how enterprises run their core processes — not as a pilot or a proof of concept, but as how the work actually gets done.
Day to day, that vision is executed by Rajesh, Chief AI Architect, who brings rich industry experience engineering AI systems and works directly with Girish to make sure the vision holds up against the reality of every client engagement.
The people behind every engagement
A small, senior team
Each person's role is mapped to a stage in our five-stage method, applied the same way on every engagement — not a headcount list.
Ajay Singla
Engineering Head
Ajay Singla
- Responsible for the engineering organization as a whole
- Sets the overall technology direction, stack choices, and architectural standards across products
- Owns the engineering roadmap and translates product/business priorities into shippable plans
Amar Singh
Delivery Head
Amar Singh
- Owns the end-to-end success of client engagements
- Owns the milestone plan and is accountable for hitting it
- Owns resource allocation across engagements
- Owns the handoff between design/scoping and execution, making sure what gets built matches what was agreed
- Primary escalation point when a client has concerns about progress, quality, or scope
Abhishek Verma
Infrastructure and DevOps Lead
Abhishek Verma
- Owns cloud architecture (AWS/GCP/Azure) — compute, networking, storage, VPC design
- Owns environment strategy: dev, staging, production parity
- Owns build, test, and deployment automation — how code goes from commit to production
- Owns secrets management, access control (IAM), and network security
Ashu Manchanda
UI Designer
Ashu Manchanda
- Owns the visual language — color, typography, spacing, iconography — and keeps it consistent across every screen and product
- Owns the design system/component library (buttons, forms, cards, states) so new features get built from a shared kit rather than reinvented per screen
- Owns micro-interactions and state design — hover, loading, empty, error, success states that are easy to skip but define perceived polish
Ravi Chaudhary
Development Lead
Ravi Chaudhary
- Owns the design and implementation of APIs (REST/GraphQL) that the frontend and mobile apps consume
- Owns the core business logic — the actual rules and workflows the application enforces, not just data plumbing
- Owns data integrity — constraints, transactions, and consistency guarantees so bad data doesn't silently corrupt state
- Owns third-party integrations — payment gateways, auth providers, external APIs, notification services
- Owns identification of shared backend components across projects — auth modules, common integrations, internal libraries — so the same logic isn't rebuilt per client
Mohit Grover
Web Application Developer
Mohit Grover
- Owns implementation of web features and pages from design specs and requirements, using the team's chosen stack (React, Next.js, Angular, Vue, or similar)
- Owns client-side logic — form handling, validation, state management, routing
- Owns connecting the frontend to backend APIs
- Owns cross-browser compatibility and responsive behavior across screen sizes
- Owns raising design-feasibility or API-mismatch concerns early, rather than after implementation is underway
Rahul Sangwan
Testing Lead
Rahul Sangwan
- Owns the overall test strategy per engagement — what gets automated vs. manual, what coverage is “enough” given the risk profile and timeline
- Decides the right mix of unit, integration, end-to-end, and exploratory testing for a given project
- Owns the automation framework and tooling choices (Selenium, Playwright, Appium, Maestro for mobile)
Shubham Dhiman
Cross Platform Mobile Development Lead
Shubham Dhiman
- Owns the architectural standards applied across all mobile projects — folder structure, state management approach, module boundaries
- Owns framework and tooling decisions (Flutter vs. React Native vs. native, which packages/SDKs are approved) rather than leaving that to individual project discretion
- Owns sprint/delivery planning specifically for mobile work streams, coordinating with Delivery Head
Vijay Rana
Development Engineer
Vijay Rana
- Owns the design and implementation of APIs (REST/GraphQL) that the frontend and mobile apps consume
- Owns the core business logic — the actual rules and workflows the application enforces, not just data plumbing
- Owns data integrity — constraints, transactions, and consistency guarantees so bad data doesn't silently corrupt state
- Owns third-party integrations — payment gateways, auth providers, external APIs, notification services
Kishan Chand
Development Engineer
Kishan Chand
- Owns the design and implementation of APIs (REST/GraphQL) that the frontend and mobile apps consume
- Owns the core business logic — the actual rules and workflows the application enforces, not just data plumbing
- Owns data integrity — constraints, transactions, and consistency guarantees so bad data doesn't silently corrupt state
- Owns third-party integrations — payment gateways, auth providers, external APIs, notification services
Himanshu Chaudhary
Cross-Platform Mobile Developer
Himanshu Chaudhary
- Owns the shared codebase (Flutter/React Native) — component structure, state management, navigation
- Owns platform-specific bridging when native functionality is needed (camera, push notifications, biometrics, background services)
- Owns translating design specs into working screens that feel native on both platforms, not just functionally identical
Rahul
UI/UX Design Lead
Rahul
- Owns the design system and visual language across every active engagement, so screens built by different designers stay consistent rather than drifting per project
- Owns UX principles applied team-wide — information architecture conventions, flow patterns, accessibility baseline — not just enforcing them on their own work
- Owns the shared component library and design tokens across projects, so common patterns (forms, navigation, states) aren't redesigned per client
Navdeep Singh
UI/UX & Graphic Designer
Navdeep Singh
- Owns user flows and information architecture for the screens they're assigned — what happens when, and why
- Owns wireframing and usability logic before visual polish begins
- Owns marketing collateral — social assets, presentation decks, brochures, website graphics — distinct from in-product UI
Neelam Choudhary
Graphic Designer
Neelam Choudhary
- Owns applying brand guidelines consistently across every material — logo usage, color palette, typography, tone
- Owns visual asset creation — icons, illustrations, image treatments — that reinforce brand identity wherever they appear
- Owns design for marketing collateral — social media graphics, ad creatives, email templates, presentation decks, brochures, case study layouts
Sunil Kumar
Graphic Designer
Sunil Kumar
- Owns applying brand guidelines consistently across every material — logo usage, color palette, typography, tone
- Owns visual asset creation — icons, illustrations, image treatments — that reinforce brand identity wherever they appear
- Owns design for marketing collateral — social media graphics, ad creatives, email templates, presentation decks, brochures, case study layouts
Before we ever pitched transparency to a client, we built it for ourselves.
Our internal Performance Management System — used across every Shipra Group business unit — runs on the same principle we bring to every Zopflix AI engagement: visibility between the people doing the work and the people accountable for it, by default, not on request.
Curious what this looks like applied to your business?
Start with a two-week Readiness Assessment — no long-term commitment, just a clear answer on what's worth automating.
Two weeks. No long-term commitment. A clear answer, either way
