runsonwhat

Yeti Cycles's tech stack

What does Yeti Cycles use?

Yeti Cycles (yeticycles.com) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Salesforce for sales, Zendesk for customer support and BigCommerce for its website. Last checked .

Industry
Sporting Goods
Size
51–200 employees
Based in
Golden, United States
Founded
1985
LinkedIn
Company page
Tools found
11
Categories
8
Layers
3 of 5
Last checked
Oct 2026

Yeti Cycles'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

1 tool, where the bytes are served from

CDN & Edge

Go-to-market

5 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Yeti Cycles tech stack FAQ

What tools does Yeti Cycles use?

We've found 11 tools at Yeti Cycles (yeticycles.com). Edge & Hosting: Cloudflare. Go-to-market: Zendesk, Salesforce and Klaviyo. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 3, 2026.

What CRM does Yeti Cycles use?

Yeti Cycles uses Salesforce for sales and CRM. We found Salesforce through email records.

What email provider does Yeti Cycles use?

Yeti Cycles uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records.

What does Yeti Cycles use for customer support?

Yeti Cycles uses Zendesk for customer support. We found Zendesk through custom domain and email records.

What CMS does Yeti Cycles use?

Yeti Cycles uses BigCommerce for its website. We found BigCommerce through email records.

What marketing software does Yeti Cycles use?

Yeti Cycles uses Klaviyo for marketing. We found Klaviyo through DNS verification records.

Does Yeti Cycles use Microsoft 365?

Yes. We found Microsoft 365 at Yeti Cycles through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Yeti Cycles uses?

We read public traces only: Yeti Cycles'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.