What is Salesloft data-center strategy through 2027?
Direct Answer
Salesloft's data-center strategy through 2027 is AWS-only with 3 regions (US-East, EU-Central, AP-Southeast) — narrower than Outreach's 6-region footprint due to Vista's cost discipline. The three named regions cover 85-90% of Salesloft customer base; remaining international handled via partner-region or English-language fallback. FedRAMP authorization is NOT funded under Vista (vs Outreach's planned authorization per q1756) — federal/government TAM ceded. The four named compliance gates + the regional infra map + comparable Vista portfolio infra patterns. Vista's discipline limits infra investment 50-60% below Outreach.
The Regional Infrastructure Map FY27
- US-East (N. Virginia) — primary US deployment, ~75-80% of customer base, ~$10-15M annual AWS spend
- EU-Central (Frankfurt) — GDPR data residency for EU customers, ~$2-4M annual AWS spend
- AP-Southeast (Sydney) — Australia + Singapore data residency, ~$1-2M annual AWS spend
- Total estimated AWS spend FY27: ~$13-21M annual (vs Outreach $28-47M per q1756)
The 4 Named Compliance Gates
- Gate 1: GDPR (EU) — data residency in EU-Central, Data Processing Agreements; already shipped
- Gate 2: SOC 2 Type 2 — annual audit; standard for B2B SaaS
- Gate 3: HIPAA (Healthcare) — supported via BAAs; required for HubSpot Healthcare ecosystem customers
- Gate 4: FedRAMP Moderate (US Federal) — NOT funded under Vista; federal TAM ceded
Why FedRAMP Is Skipped Under Vista
- Cost: $2-5M one-time + $500K-1M annual continuous monitoring
- Timeline: 18-24 months
- TAM unlock: $200-400M federal/government sales-engagement market
- Vista calculation: 18-24 month ROI horizon doesn't fit Vista 4-7 year hold
- Alternative: Vista exit acquirer (HubSpot or Adobe) handles FedRAMP if needed
- Salesloft's position: cedes federal to Outreach's planned FedRAMP path (per q1756)
Why Salesloft Has 3 Regions Vs Outreach's 6
- Vista capital constraint: each region adds $2-5M annual; Vista limits regional expansion
- Smaller customer base: Salesloft 5,000 customers vs Outreach 6,000+
- HubSpot ecosystem dependence: HubSpot has US + EU + APAC regions; Salesloft mirrors HubSpot
- Trade-off: skips LATAM (Brazil) + India + Tokyo coverage; partner-led for those markets
What Could Force Region Expansion
- HubSpot launches India region: HubSpot's India growth pulls Salesloft expansion
- EU customer compliance push: GDPR enforcement intensifies; need EU-West (Ireland) backup
- APAC customer growth: Singapore + Australia exceeds AP-Southeast capacity
- Vista exit acquirer demands FedRAMP: HubSpot or Adobe wants federal entry; funded as exit prep
Comparable Vista Portfolio Infrastructure Patterns
- Marketo post-Vista (2016-18): maintained 3 regions; no expansion during Vista era; Adobe expanded post-acquisition
- Cloudera post-KKR (2021-): 4 regions; data platform requires global presence
- Anaplan post-Thoma Bravo (2022-): 6 regions; enterprise demand drives expansion
- Apttus post-Vista (2018-23): 3 regions; minimal expansion during Vista era
- Pattern: Vista portfolios maintain status-quo infrastructure; expansion happens post-Vista exit
Cost Comparison: Salesloft FY27 Infra Vs Outreach
- Salesloft AWS: $13-21M annual (Vista discipline)
- Outreach AWS: $28-47M annual (Outreach broader regions per q1756)
- Net delta: Salesloft 50-60% lower infra cost
- Impact: Salesloft margin advantage vs Outreach in some quarters
What Vista Should Do With Infrastructure
- Maintain 3-region status quo: don't expand during cost-out
- Defer FedRAMP: cede federal TAM
- AWS Reserved Instances: lock in 1-year discounts; save 15-25% on compute
- Spot instance usage: for non-customer-facing workloads
- Consolidate to 1-2 AWS accounts: reduce overhead
- Net: $2-5M annual savings via Vista efficiency
A Markdown Table — Salesloft Vs Outreach Infrastructure Strategy
| Region | Salesloft FY27 | Outreach FY27 | Delta |
|---|---|---|---|
| US-East (N. Virginia) | Primary $10-15M | Primary $15-25M | -33% |
| US-West (Oregon) | None | Failover $5-8M | -100% (Outreach only) |
| EU-Central (Frankfurt) | $2-4M | $3-5M | -33% |
| EU-West (Ireland) | None | $2-4M | -100% (Outreach only) |
| AP-Southeast (Sydney) | $1-2M | $2-3M | -33% |
| AP-Northeast (Tokyo) | None | $1-2M | -100% (Outreach only) |
| LATAM (Sao Paulo) | None | Build 2026 | -100% |
| FedRAMP US Gov | NONE (deferred) | Q2 2026 start | -100% |
| Total AWS spend | $13-21M | $28-47M | -50-60% |
A Mermaid Diagram — Salesloft Data-Center Strategy Decision
Bottom Line
Salesloft's data-center strategy through 2027 is AWS-only 3-region (US-East + EU-Central + AP-Southeast) under Vista discipline — narrower than Outreach's 6-region footprint, ceding federal/government TAM via no FedRAMP investment. The honest call: Vista capital efficiency wins over geographic ambition; saves $15-25M annually vs Outreach's broader infrastructure. Trade-off: cedes 10-15% of international + federal TAM. Strategic acquirer (HubSpot, Adobe) likely expands infrastructure post-Vista exit. (See also: q1789, q1792, q1797, q1806, Outreach q1756)
Tags
salesloft, data-center, aws-infrastructure, data-residency, gdpr, fedramp, hipaa, data-sovereignty, cloud-strategy, fy27-infrastructure