runsonwhat

Sherlock software's tech stack

What does Sherlock software use?

Sherlock software (sherlocksoftware.com) uses at least 11 tools we can see from public records, including Calendly for sales, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .

Industry
Software
Size
11–50 employees
Based in
Point Clare, Australia
Founded
1981
LinkedIn
Company page
Tools found
11
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Sherlock software'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

Application

3 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Sherlock software tech stack FAQ

What tools does Sherlock software use?

We've found 11 tools at Sherlock software (sherlocksoftware.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Google Maps. Data & Observability: Google Analytics. Go-to-market: WordPress, Yoast SEO and Calendly. Company Ops: SendGrid and reCAPTCHA. Last checked October 6, 2026.

What CRM does Sherlock software use?

Sherlock software uses Calendly for sales and CRM. We found Calendly through website code.

What analytics tools does Sherlock software use?

Sherlock software uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Sherlock software use?

Sherlock software uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Sherlock software use jQuery?

Yes. We found jQuery at Sherlock software through website code. jQuery is used by 585,042 companies we track.

How does runsonwhat know what Sherlock software uses?

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