Pre-IPO Stabilization Under Pressure
How engineering and ML platform continuity was maintained through WeWork's most volatile organizational period.
"The most important engineering work in a crisis is the work that does not fail."— S+3 Agile Field Record
The Challenge
Himanshu was brought to WeWork at the request of Chairman Sebastian to support pre-IPO preparation — an engagement that quickly became crisis management. WeWork's IPO process unraveled publicly and catastrophically in 2019, producing one of the most volatile organizational environments in recent tech history: executive churn, valuation collapse, and a company in existential question.
In that environment, Himanshu owned two mission-critical platform teams: the worldwide Pricing & Revenue Optimization Platform and the ML Platform. The mandate was not innovation. The mandate was continuity — ensuring that the systems the business depended on to price its global real-estate inventory and run its machine-learning workloads did not fail while the organization around them was in freefall.
The Intervention
Advisory engagement to executive leadership
Himanshu acted as a key advisor to the Executive Leadership Team on go/no-go decisions during the IPO process — translating engineering risk into business-risk language at a moment when the board's decisions were being made under extreme time pressure and incomplete information. This is the StratAI archetype in its human form: providing probabilistic, structured analytical input to the highest-stakes decisions in the enterprise.
Platform continuity under organizational chaos
The Pricing & Revenue Optimization Platform managed the economics of WeWork's global real-estate inventory — a system that could not fail without direct revenue impact. Maintaining its operation through leadership changes, headcount reductions, and the organizational shock of the failed IPO required the same S+3 discipline applied in stable environments: clear ownership, documented runbooks, and engineering processes that survived personnel changes.
ML platform resilience
The ML Platform faced a different challenge: the engineers who built it were leaving. Institutional knowledge was walking out the door faster than it could be documented. Himanshu applied the S+3 team-health framework to a team in active decline, ensuring that the knowledge-transfer and documentation work happened before, not after, the attrition crisis hit the platform's operational reliability.
Key Results
| Metric | Outcome |
|---|---|
| Business continuity | Pricing & Revenue Optimization Platform — zero failures through crisis period |
| ML Platform continuity | Maintained through high-attrition period with documented knowledge transfer |
| Executive advisory | Go/no-go decision support throughout pre-IPO and IPO collapse period |
| Organizational resilience | Engineering teams stabilized through one of the most volatile periods in recent tech history |
In a crisis, continuity is the highest form of engineering. Documented ownership and runbooks that survive personnel change are what keep revenue-critical systems alive when the org around them is in freefall.
Figures are normalized to US-market engineering costs and typical portfolio-company scale, drawn from the S+3 Agile field record.