HomeProjectsFeature Flags & A/B Testing Framework
Feature Flags & A/B Testing Framework
Lorex Technology

Feature Flags & A/B Testing Framework

Centralized feature flag platform enabling granular rollout control, A/B testing infrastructure, and experimentation framework for data-driven product decisions.

View Case Study

Percentage rollout, targeting, A/B testing

Capabilities

JavaScript, Python, Java SDKs

Clients

Decoupled from releases

Deployment

Lorex Technology

Company

Feature FlagsA/B TestingAnalyticsPythonJavaScriptProduct ManagementAgile

Built a feature flag platform decoupling deployment automation from releases code is deployed to production but features stay hidden behind flags until ready for rollout. This enabled continuous deployment automation without customer-facing risk.

The system supported percentage-based rollouts (5% → 10% → 100%), user-segment targeting (beta testers → ERP modernisation strategy customers), and scheduled release windows. A/B testing strategy pyramid framework layered on top enabled data-driven product decisions. Teams could experiment with different UX variants, pricing models, or algorithms on real users, measuring impact on conversion rate optimisation, retention, or revenue before committing to changes.

The flag consistency requirement was non-trivial. When a user is assigned to the "variant B" group, they must always see variant B - not randomly switching between A and B on different page loads or sessions. We implemented consistent hashing using the user ID as the seed: the same user always hashes to the same bucket regardless of which server handles the request. This consistency was critical for experiments measuring multi-session behavior like subscription conversion rate optimisation or 30-day retention.

Flag proliferation became a real operational problem within 6 months. Teams created flags but rarely cleaned them up - the platform reached 300+ active flags with no clear owner. We implemented a flag lifecycle policy: new flags required an expiry date and owner; flags older than 90 days without activity were auto-archived (not deleted, archived). Monthly "flag cleanup" sessions became engineering rituals. The technical debt strategy of stale flags - code conditionals nobody removes - costs more in confusion than the original flag was worth.

The statistical rigor of A/B testing strategy pyramid was challenged by novelty effects. New features often show artificially inflated engagement in the first week simply because they're new. We implemented minimum exposure windows (14 days minimum for engagement metrics and alerting, 30 days for conversion rate optimisation) and novelty adjustment in our significance calculations. This prevented teams from declaring winners prematurely and shipping features that looked great short-term but reverted to baseline after novelty wore off.

Explore the Full Portfolio

This is the complete portfolio of Sufi Khan Sulaiman, a technology leader specialising in B2B commerce and digital automation. Start from the Home page for the overview, then move through two decades of career experience across FLIR Systems, Lorex Technology, and 1c Platform, and the full catalogue of project case studies spanning headless commerce migrations, AI recommendation engines, and multi-channel fulfilment systems.

The skills and certifications page maps the technical and leadership capabilities behind the work, while the articles and the knowledge base break down the thinking into actionable frameworks. For hands-on learning, the tutorials and applications sections cover practical builds from front-end fundamentals to full-stack web apps.

For consulting engagement, the expertise page outlines service offerings, the ecommerce hub covers platform architecture and automation strategy, and the ecommerce guide (PDF) is a downloadable 55-page field manual. When you are ready to talk, the contact page is the direct line.