VWO (Wingify)

What is VWO?

VWO (Visual Website Optimizer) is the flagship product of Wingify Software Pvt. Ltd., a Delhi-based SaaS company. Wingify was founded in 2009 by Paras Chopra; Sparsh Gupta joined as co-founder in 2010 to build out the engineering and product organisation. The company famously remained bootstrapped for 15+ years — no external venture funding — while growing to ~$50M ARR before its 2025 sale to Everstone Capital. It's one of India's most successful B2B SaaS stories, and one of the very few profitable, globally-distributed Indian SaaS companies built without VC backing.

At its core, VWO lets product and growth teams run A/B tests on websites and apps without requiring a code deploy for every variation — a huge advantage for teams where engineering bandwidth is the bottleneck. The visual editor lets you change text, images, and layouts through a point-and-click interface. For mobile apps, VWO's SDK enables server-side experiments that are more powerful for product teams than simple UI changes.

Beyond A/B testing, VWO has evolved into a full conversion-optimisation suite — heatmaps, session recordings, form analytics, and funnel reports are all included depending on your plan. This makes VWO a competitor to both Optimizely (for experimentation) and Hotjar (for user behaviour analysis). Customers include Ubisoft, eBay, Hyundai, Toyota, Vodafone, and a long list of Indian heavyweights — Myntra, MakeMyTrip, Nykaa, BankBazaar, BigBasket and others. Approximately 90% of VWO's revenue comes from US and European customers; the India domestic revenue base, while strong, is the smaller portion.

The Wingify story: bootstrapped → Everstone (Jan 2025) → AB Tasty merger (Jan 2026)

For Indian product teams using VWO, the corporate change matters more than usual because it changes both who you're contracting with and what the future product roadmap looks like.

2009–2024 — bootstrapped growth. Wingify took zero external venture funding, ran profitably, and grew to ~$50M ARR by 2024. Paras Chopra became a well-known voice in Indian SaaS for the "no VC, no exits, just compounding" approach.

January 2025 — Everstone Capital acquires majority stake for ~$200M. India- and Singapore-focused PE firm Everstone bought a controlling position in Wingify, structuring the deal so co-founder Sparsh Gupta retained a meaningful stake and continued as CEO. Paras Chopra moved into a board / shareholder role. The deal was reported as one of the largest exits for a bootstrapped Indian SaaS company.

20 January 2026 — Wingify + AB Tasty merger. Everstone-backed Wingify combined with Paris-born AB Tasty to form a single company with $100M+ ARR, ~800 employees, and 11 global offices, headquartered in New Delhi. Sparsh Gupta is CEO; Wingify's Ankit Jain became Chief Product & Technology Officer; AB Tasty's co-founders Rémi Aubert and Alix de Sagazan moved into Chief Customer & Strategy Officer and Chief Revenue Officer roles respectively. The combined entity is now the largest pure-play CRO/experimentation vendor headquartered in India, and the most credible global alternative to Optimizely Web in the mid-market segment.

What this means for buyers in 2026. VWO and AB Tasty continue as two product brands inside the combined company — you can still buy VWO standalone with INR billing, IST-aligned support and the same self-serve onboarding. The product roadmap is gradually converging (AB Tasty's stronger personalisation engine and Flagship feature-flag product are being made available to VWO customers; VWO's heatmaps and session-recording surface is being made available to AB Tasty customers), but day-to-day procurement and contracts are unchanged for existing customers. New buyers should ask the sales team about combined-entity pricing — it's often more flexible than the published list, especially for multi-product or multi-year deals.

Key Features

Best For

• Indian product and growth teams starting their A/B testing programme (first 1–20 experiments)
• E-commerce, fintech, and edtech teams optimising web conversion funnels
• Teams where non-technical PMs or marketers need to run experiments independently
• Companies wanting INR billing with IST support and local account management
• Teams that need heatmaps + A/B testing in one tool (vs Hotjar + separate testing tool)

Pricing

VWO pricing is based on monthly tracked users (MTUs) — visitors who interact with your site/app during a month. INR billing available, which removes forex complexity for Indian teams.

💡 INR advantage: VWO invoices in INR with standard Indian GST — no reverse charge complexity. At ₹16,000–33,000/month for the most useful plans, VWO is significantly cheaper than Optimizely ($50,000+/year) for teams running fewer than 50 experiments per year.

Pros and Cons

Alternatives to VWO

Getting Started with VWO

1. Install the VWO snippet and verify it's firing — Add the VWO async script to your site's <head>. Use VWO's Chrome extension to verify it's loading on every page before setting up any tests. A misconfigured snippet is the most common reason experiments don't work.
2. Run your first test on a high-traffic page — Don't start with your lowest-traffic page. You need statistical significance quickly to learn fast. For most Indian apps, the signup page, pricing page, or onboarding step 1 are the right starting points — they have traffic and the change matters.
3. Test one thing at a time — The most common mistake: changing headline + CTA + hero image + background colour in one test. If it wins, you don't know what caused it. If it loses, same problem. Change one element per A/B test. Use multivariate testing only when you understand the basics.
4. Set your primary metric before launching — Decide upfront: what does winning look like? Click-through rate? Form submissions? Payment completions? Define this before the test starts. Post-hoc metric selection (choosing the metric that looks good after the fact) is how teams fool themselves.
5. Wait for statistical significance, then stop — VWO will tell you when you've reached 95% statistical significance. Wait for it — don't stop a test early because one variant looks promising after 3 days. And stop immediately once you reach significance — running tests longer doesn't make results more valid, it just wastes time.