Full platform migrations with dedicated PM and 24-hour SLA.
The enterprise tier. Everything in Atlas plus full CMS migration, custom integrations, dedicated PM, and a 24-hour SLA. 12-month outcome contract with measurable targets written into the SOW.
Investment
$80K-$150K
one-time + $8K-$15K/month retainer
Timeline
45 to 90 days
Ideal for
$50M+ firms, PE platform accounts, multi-logo operators.
One-time build
What you get at launch.
Monthly retainer
$8K-$15K/month. Begins 30 days post-launch.
Why this tier fits who it fits.
- 01You're at $50M+ revenue. Procurement expects vendor insurance, a named PM, an outcome contract, and enterprise-grade paper. Foundry and Atlas aren't built for that buying motion. Empire is.
- 02You have a real migration problem. Legacy CMS (AEM, Sitecore, Drupal 7, custom PHP) with thousands of pages. Switching to Next.js requires careful redirect mapping, content diffing, and stakeholder coordination.
- 03You need integrations that matter. HubSpot for marketing, Salesforce for sales, Sage Intacct or NetSuite for finance, MLS for real estate, Square for in-person services. Off-the-shelf CMS platforms can't cover all of those cleanly.
- 04You're a PE platform company. Empire engagements can be templated across portfolio companies, each one gets its own SOW but shares an MSA, a PM, and an infrastructure baseline. Your second portco ships twice as fast as the first.
How the engagement runs.
- Step 1
Discovery call
30-minute call to scope the actual work. Integrations, data model, team, timeline, governance requirements.
- Step 2
Scoped SOW
Within 5 business days of the call, you receive a scoped SOW with Exhibit B outcome targets. Your legal reviews. We negotiate edits if needed.
- Step 3
Deposit + kickoff
50% deposit clears. Dedicated PM assigned. Kickoff call with all stakeholders. Staging environment provisioned.
- Step 4
Build + integrations
6-10 weeks. Custom integration work, CMS migration, pSEO engine at scale (typically 2,000+ pages). Bi-weekly executive update emails. Weekly PM standups.
- Step 5
Stakeholder review
Pre-launch staging review with all stakeholders. Sign-off required before cutover. Rollback plan documented.
- Step 6
Launch + monitoring
Staged cutover. Post-launch monitoring for 48 hours. 24-hour SLA active immediately. Weekly post-launch executive emails for 30 days.