Meta's Global Operations organization supports high-volume workflows across Trust & Safety, Ads operations, vendor management, workforce planning, and internal escalations. Many teams currently rely on a mix of Meta-built tools, spreadsheets, and third-party workflow platforms. You are an Operations Manager supporting a cross-functional decision on whether Meta should build an internal case management and workflow orchestration tool for operations teams or buy and customize an external platform.
The decision is urgent because three existing workflows are scaling quickly: policy escalation handling, vendor QA review routing, and cross-functional incident intake. Today, these workflows run across separate tools, creating duplicate work, inconsistent reporting, and slower turnaround times. Leadership wants a recommendation within the next quarter because the current operating model is constraining efficiency and creating compliance risk.
The proposed tool would initially serve about 8,000 internal users and vendor users across Operations, Integrity, and Support teams, with potential expansion to 15,000 users over three years. The build option would use internal engineering resources and integrate deeply with Meta systems such as Workplace, internal identity/access controls, and existing data pipelines. The buy option would likely involve a leading enterprise workflow vendor with configurable case management, SLA tracking, and reporting.
| Metric | Current State / Build Option / Buy Option |
|---|---|
| Current annual inefficiency cost | Estimated $18M/year from manual reconciliation, duplicate handling, and slower resolution times |
| Build option cost | $9M upfront in year 1, plus $3M/year ongoing maintenance; estimated launch in 12 months |
| Buy option cost | $4M implementation in year 1, plus $5M/year license and support; estimated launch in 4 months |
| Expected efficiency gain | Build: 70% of current inefficiency cost removed by year 2; Buy: 50% removed by year 1 |
| Strategic risk factors | Build has higher delivery risk; Buy has lower flexibility and greater data-governance concerns |
Additional context: