What technologies does Battle Motors (Crane Carrier) use?

Battle Motors (Crane Carrier) uses Outlook, GoDaddy Hosting, Microsoft Office 365, VueJS, Atlassian Cloud. View their full technology stack — including all 26 detected tools — on StackWho.

Who is the Chief Engineering Director - Strategic Projects of Battle Motors (Crane Carrier)?

Matthew Shurtz is the Chief Engineering Director - Strategic Projects at Battle Motors (Crane Carrier). Get verified contact information on StackWho.

Who is the Vice President - Application Engineering & Operations of Battle Motors (Crane Carrier)?

Kyle Shankel is the Vice President - Application Engineering & Operations at Battle Motors (Crane Carrier). Get verified contact information on StackWho.

Where is Battle Motors (Crane Carrier) located?

Battle Motors (Crane Carrier) is based in Los Angeles, California, United States.

Battle Motors (Crane Carrier)

battlemotors.com

automotive

battlemotors.com

Los Angeles, California, United States

201-500 employees

LinkedIn Profile

About Battle Motors (Crane Carrier)

electric trucks, refuse trucks, utility trucks, motor vehicle manufacturing, electric oilfield trucks, vehicle safety systems, industrial vehicle safety standards, high-performance trucks, automated assembly lines, electric vehicle technology, severe-service trucks, electric commercial trucks, severe-service chassis, electric vehicle software, electric refuse trucks, electric vehicle custom design, custom chassis manufacturing, electric heavy-duty fleet, heavy duty truck manufacturing, electric

Battle Motors (Crane Carrier)'s Tech Stack

AI/ML

Decision Makers at Battle Motors (Crane Carrier)

2 contacts

Matthew Shurtz

Chief Engineering Director - Strategic Projects

m***@battlemotors.com Sign up to view

Kyle Shankel

Vice President - Application Engineering & Operations

k***@battlemotors.com Sign up to view

Unlock full contact details including verified emails and LinkedIn profiles

Upgrade to Pro

26 technologies detected · 2 decision makers · Emails available

Sales Outreach Angle

HubSpot users typically run inbound-led sales motions. Products that integrate with HubSpot (email automation, CRM enrichment, ABM platforms) are natural fits.

Battle Motors (Crane Carrier)'s Position in the StackWho Database

• Battle Motors (Crane Carrier) is 1 of 4,192 automotive companies tracked in StackWho.
• 4,157 automotive companies in our database have verified decision-maker emails (99% of the cohort).
• 53,147 companies in California are in the StackWho database.
• 362 automotive companies are in the 201-500 employee range (same size as Battle Motors (Crane Carrier)).

Technology detection from public web signals. Decision-maker contacts compiled from LinkedIn public profiles, company filings, and verified outbound testing. Methodology & sources · Updated July 2026.

Frequently Asked Questions

What technology does Battle Motors (Crane Carrier) use?

Battle Motors (Crane Carrier) uses Outlook, GoDaddy Hosting, Microsoft Office 365, VueJS, Atlassian Cloud, Netlify, and 20 more technologies. This data is sourced from StackWho's technology detection engine.

How do I contact the decision makers at Battle Motors (Crane Carrier)?

StackWho has verified email addresses for 2 decision makers at Battle Motors (Crane Carrier). Pro members can access direct emails for the CEO, CTO, VP of Engineering, and other key contacts. Use StackWho to reach Battle Motors (Crane Carrier) directly for sales, recruiting, or partnerships.

What industry is Battle Motors (Crane Carrier) in?

Battle Motors (Crane Carrier) operates in the automotive industry, headquartered in Los Angeles, California, United States. StackWho tracks technology stacks and decision maker contacts for companies across all industries.

Can I export Battle Motors (Crane Carrier)'s contact data?

Yes. StackWho Pro members can export decision maker contact data for Battle Motors (Crane Carrier) and similar companies to CSV. Use the export feature to build targeted prospect lists segmented by technology stack, industry, or location.