I find the opportunity. I ship it.

Zalando wanted to double the articles on the platform, but the CMS was a 10-year-old desktop app used by 300 photographers, retouchers, and copywriters producing content for 45M daily active users. It was buggy and slow, new features took weeks, and people had built workarounds for basic tasks. It could never scale to 2x.

• Wrote the strategy paper for long-term content creation.
• Aligned every stakeholder on one north star: time to go online.
• Shadowed all three user groups to map their real pain points.
• Prioritized and co-created solutions with engineering and design.
• Rolled out incrementally: photographers first, then retouchers, then copywriters.

• Time to go online dropped from 2 days to 12 hours.
• 1.5x more articles in year two, on track for the 2x target.
• €2M in additional revenue generated.

Across user studies, session data, and return reports, 3-5% of returns said the "product looked different from the images." Users zoomed on photos repeatedly, then dropped off without adding to cart, especially in footwear and premium apparel. The root cause wasn't the photography, it was delivery: standard-resolution JPEGs that looked soft on modern retina and 4K screens. Simply raising resolution would slow the pages down.

• Ran an A/B test across footwear, premium apparel, and accessories.
• Coordinated three teams: PDP front-end, the global image pipeline, and Zalando Fashion Studio.
• Served 2x-density WebP images via CDN with lazy loading and responsive resizing.
• Ran across desktop and mobile web for two weeks.

• Zoom interactions up 18%.
• Add-to-cart +0.5pp; conversion 4.00% → 4.06%.
• Load speed (LCP) unchanged at 2.7 seconds.
• "Looked different" returns down a directional 10-15%.

Activation was 16%, well below the 40% benchmark. A funnel audit showed a 60% drop-off between creating a task and inviting a teammate. The invite was buried in a menu, so users never felt the collaborative value and most churned as solo users.

• Moved "Add Members" out of a hidden menu onto the board workspace.
• Added a contextual nudge right after the first task is created.
• Replaced the multi-step email invite with a one-click invite link.
• A/B tested over 2-3 weeks, tracking task-to-invite, activation, and D7/D14 retention.

• Activation improved from 16% to 22%, a 37% lift.
• Users who invited a teammate showed 3x higher D14 retention.
• Zero negative impact on guardrail metrics.

Paytm had 100M+ users, but almost all usage was online. The next growth lever was offline payments, and nothing existed for it: no merchant POS integration, no consumer habit of paying by phone at a counter, and a real trust barrier on both sides. We needed proof before committing to a nationwide rollout.

• Picked Café Coffee Day as the pilot: high footfall, tech-savvy customers, national brand.
• Built wallet integration with engineering for both iOS and Android.
• Trained baristas to accept wallet payments.
• Designed a sub-10-second flow: scan, confirm, done.
• Rolled out across 20 outlets, monitoring success rates and complaints daily.

• 10K+ monthly transactions within the first quarter.
• Transaction success rate above 95% after early fixes.
• Proved the model that paved the way for Paytm's merchant rollout.

Seed-stage founders across gaming, edtech, and marketplace were building on assumptions, not evidence. No structured discovery, no validation framework, and a high risk of burning runway on the wrong product.

• Ran 3-week validation sprints, one per concept.
• User interviews, competitive analysis, and market sizing.
• Rapid prototypes to test the core assumptions.
• A clear go/no-go recommendation backed by evidence.

• $160K+ in development costs saved.
• 2 concepts invalidated before build, 1 scoped to launch.
• Founders redirected to validated opportunities.