LifeWorks's tech stack
What does LifeWorks use?
LifeWorks (lifeworks.com) uses at least 19 tools we can see from public records, including Microsoft 365 for email and documents, HubSpot for sales, HubSpot CMS for its website and Mailchimp for marketing. Last checked .
- Industry
- Professional Service
- Founded
- 1967
- Tools found
- 19
- Categories
- 12
- Layers
- 4 of 5
- Last checked
- Oct 2026
LifeWorks's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
3 tools, where the bytes are served from
Application
1 tool, what the product is built with
Backend & Database
Go-to-market
8 tools, how they find and keep customers
Website & CMS
Sales & CRM
Company Ops
7 tools, what the team runs on day to day
Email Delivery
Workspace
Collaboration
Dev Tools
Security & Compliance
LifeWorks tech stack FAQ
What tools does LifeWorks use?
We've found 19 tools at LifeWorks (lifeworks.com). Edge & Hosting: Cloudflare, Amazon Route 53 and Amazon CloudFront. Application: MongoDB Atlas. Go-to-market: Mailchimp, HubSpot and HubSpot CMS. Company Ops: Microsoft 365, SendGrid and Atlassian. Last checked October 4, 2026.
What CRM does LifeWorks use?
LifeWorks uses HubSpot for sales and CRM. We found HubSpot through custom domain.
What email provider does LifeWorks use?
LifeWorks uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and DNS verification records.
What CMS does LifeWorks use?
LifeWorks uses HubSpot CMS for its website. We found HubSpot CMS through custom domain.
What marketing software does LifeWorks use?
LifeWorks uses Mailchimp for marketing. We found Mailchimp through email records.
Does LifeWorks use Microsoft 365?
Yes. We found Microsoft 365 at LifeWorks through email records and DNS verification records. Microsoft 365 is used by 685,091 companies we track.
How does runsonwhat know what LifeWorks uses?
We read public traces only: LifeWorks's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.