TrueMotion

Name: TrueMotion
Brand: TrueMotion

Premium running shoes that work for every runner and let you float. Comfortable yet supportive we change the paradigm.

Est 2012|Valuation $295M|Raised $88M|26 Ref Customers

LinkedIn 2K|Website|Web traffic 37K|FTEs 20|HQ Cologne, North Rhine-Westphalia, DE

Published Oct 15, 2026

01Common complaints

1. If an organization requires a self-serve SaaS product with transparent publicly listed pricing: TrueMotion/CMT is typically sold via enterprise contracts and procurement. 2. If the customer base is highly privacy-sensitive and the organization lacks a strong consent and communications plan: telematics programs can trigger user backlash and regulatory scrutiny. 3. If the organization cannot support score dispute workflows and customer support operations: reported disputes and perceived unfair scoring can reduce program engagement and ROI. 4. If independently validated performance metrics are required prior to deployment: many public safety and ROI figures are vendor-published; buyers should plan pilots and controlled experiments to validate performance. 5. If the requirement is strictly for hardware-only telematics or strictly for smartphone-only telematics with no hybrid options: CMT describes multi-sensor fusion and some tag-device options; specialist vendors may better suit very narrow modality requirements.

Deal disqualifiers (poor fit)

Very small insurers without integration capability
Organizations that require fully transparent public pricing and self-serve onboarding
Use cases that require on-premise-only deployment (not documented in public materials)

1) Brand/product clarity post-acquisition

The gotruemotion.com domain redirects to CMT, so:

The TrueMotion brand is less visible as a standalone product
Documentation, roadmaps, and pricing are not clearly delineated under the legacy TrueMotion brand

2) Limited third-party B2B reviews

G2 shows a seller listing with no B2B reviews in the sources reviewed
Capterra/TrustRadius coverage for the enterprise product appears minimal or absent publicly

3) Accuracy and user-trust constraints (industry-wide)

Telematics scoring is often challenged by:

Driver vs passenger ambiguity
Device/sensor differences and sensor drift
Map and speed-limit data mismatches
False positives in maneuver detection

4) Security/compliance transparency

While ISO and SOC alignment are referenced in privacy documentation, direct public access to supporting audit artifacts (SOC 2 reports, ISO certificates, detailed security architecture) is limited. Buyers should request these artifacts under NDA during procurement.

Why some customers leave (likely churn reasons)

Churn reasons specific to the legacy vendor are not widely documented. Common drivers in telematics programs generally include:

Customer backlash on privacy issues
Perceptions of unfair scoring or penalization (driver vs passenger ambiguity)
Battery drain concerns related to background location
Low engagement reducing program effectiveness

02Why they buy

Unique selling points with some evidence

- Ecosystem integrations: partnerships and integrations with established insurance-technology ecosystem players (e.g., Guidewire) and data providers (e.g., INRIX) are documented in public materials. - Claims workflow enablement: materials describe surfacing telematics-derived crash and event data inside claims platforms to support FNOL and triage workflows. - Scale claims: public statements by the combined company assert broad program coverage and insurer relationships; independent verification of scale should be requested during procurement.

Areas where competitors have documented advantages

Some competitors provide clearer time-to-value windows or developer-friendly open-source tooling that may accelerate prototyping and deployment.

03Field reports

Review platform coverage (limitations)

- G2 has a listing for the product but shows limited or no verified B2B reviews for the legacy vendor listing during research. - Capterra does not show a substantial enterprise listing or detailed enterprise reviews for the legacy vendor in the sources reviewed. Given limited coverage on B2B review platforms, this section references consumer app store descriptions and independent commentary, with the caveat that consumer-app reviews are not equivalent to enterprise buyer feedback.

Positive feedback (examples)

From consumer app store listings for the vendor’s apps, the apps have a high average consumer rating with substantial review volume. App-store anecdotes include examples of users reporting emergency assistance following an event.

Vendor marketing materials include quoted praise attributed to customers; these are promotional and not independently verified in public materials.

Negative feedback and complaints (examples)

While enterprise reviews for the legacy vendor are sparse, public complaints observed across telematics-based driving-scoring apps (including DriveWell Go instances) commonly include: - Disputes over accuracy: users alleging they were penalized for phone use while not using the phone - Speed limit data mismatches resulting in disputed speeding flags - Apparent sensitivity/false positives for braking or specific maneuvers - Limited dispute mechanisms and customer support responsiveness These examples are drawn from consumer-facing app feedback and may reflect app UX or consumer perceptions rather than enterprise telemetry under controlled programs.

Why customers choose this product (inferred from partnerships)

Partnership and ecosystem announcements suggest buyers selected TrueMotion or its capabilities for reasons including:

Smartphone-only data collection to reduce hardware friction
Claims acceleration via integrations with common claims platforms
Contextual driving data partnerships to enhance telematics signals

Case study style evidence available (mostly press releases)

TrueMotion’s public case studies are primarily press releases and partnership announcements; these are promotional and not independently audited. #### Example: Distracted driving reduction claim (vendor-published) Vendor materials described a program with many drivers and trips that reported reductions in distracted driving over the pilot period. Critical evaluation: - This is vendor-published research; methodology details, selection bias, and control conditions are not fully disclosed in the press release. - The result is useful as directional evidence but would not be sufficient alone for actuarial validation. #### Example: Guidewire Claims Accelerator (integration-focused) Vendor materials describe an integration that allows adjusters to view crash location and event data inside common claims platforms prior to manual FNOL processing. Critical evaluation: - This is a concrete workflow example for claims operations and suggests potential efficiency gains. - Public materials do not quantify cycle-time reduction; buyers should request implementation references and measurable benchmarks. #### Example: Partnerships (contextual data providers and analytics firms) - Partnerships described in vendor materials position the company to layer contextual traffic and environmental data onto driving behavior analytics and to collaborate with established analytics providers for scoring. Critical evaluation: - Partnerships with established firms indicate ecosystem integration but actual value to an insurer depends on operationalization (pricing filings, claims triage processes, and internal analytics adoption).

04Best fit

Company size

Best fit tends to be:

Mid-market to enterprise insurers (large organization) and large mobility platforms where safety and claims costs are material

Industries

Personal auto insurance (UBI/BBI)
Commercial auto / fleet insurance
Mobility platforms (gig, rideshare)
Public-sector road safety programs

Personas

Insurance: Head of Telematics/UBI, Chief Underwriting Officer, Claims Operations leadership, VP of Product
Data/tech: Head of Data Science, CIO/CTO, Mobile Engineering lead
Legal/compliance: Privacy counsel, security/compliance officer

Pain points addressed

Improve risk segmentation beyond traditional rating factors
Improve driver engagement and reduce risky behaviors
Provide faster, richer FNOL and crash reconstruction inputs
Reduce claim severity and injury frequency (vendor-published aims)

Qualification criteria (good fit)

Ability to drive meaningful enrollment through marketing and incentives
Appetite for robust data governance and privacy program maturity
Capacity to integrate SDKs/APIs and operationalize risk scores

05The pitch

What the product does (objective core value proposition)

TrueMotion is a smartphone-based telematics and driving-risk data platform originally sold to insurers and mobility providers to: - Detect trips and driving context (e.g., whether a person is driving) - Measure driving behaviors (e.g., hard braking, harsh acceleration, speeding, distracted driving / phone handling) - Support usage-based insurance (UBI) and behavior-based insurance (BBI) pricing and engagement programs - Enable crash detection and provide crash/claims workflows (e.g., first notice of loss (FNOL) support) Important market reality: the TrueMotion brand and product capabilities have been incorporated into or rebranded under Cambridge Mobile Telematics (CMT). In practice, many capabilities originally associated with TrueMotion are now marketed under CMT’s DriveWell® platform rather than as a standalone TrueMotion-branded product.

Target market and positioning

Historically and functionally, TrueMotion targets: - Property & Casualty (P&C) auto insurers launching or improving UBI/BBI programs - Insurtechs building app-based insurance products - Claims organizations seeking telematics-driven crash insights - Mobility/fleet/rideshare operators needing driver scoring, safety coaching, and incident detection Positioning is as an enterprise telematics platform rather than as an SMB self-serve product.

Get a comprehensive analysis of TrueMotion including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

If an organization requires a self-serve SaaS product with transparent publicly listed pricing: TrueMotion/CMT is typically sold via enterprise contracts and procurement.
If the customer base is highly privacy-sensitive and the organization lacks a strong consent and communications plan: telematics programs can trigger user backlash and regulatory scrutiny.
If the organization cannot support score dispute workflows and customer support operations: reported disputes and perceived unfair scoring can reduce program engagement and ROI.
If independently validated performance metrics are required prior to deployment: many public safety and ROI figures are vendor-published; buyers should plan pilots and controlled experiments to validate performance.
If the requirement is strictly for hardware-only telematics or strictly for smartphone-only telematics with no hybrid options: CMT describes multi-sensor fusion and some tag-device options; specialist vendors may better suit very narrow modality requirements.

Deal disqualifiers (poor fit)

Very small insurers without integration capability
Organizations that require fully transparent public pricing and self-serve onboarding
Use cases that require on-premise-only deployment (not documented in public materials)

1) Brand/product clarity post-acquisition

The gotruemotion.com domain redirects to CMT, so:

The TrueMotion brand is less visible as a standalone product
Documentation, roadmaps, and pricing are not clearly delineated under the legacy TrueMotion brand

2) Limited third-party B2B reviews

G2 shows a seller listing with no B2B reviews in the sources reviewed
Capterra/TrustRadius coverage for the enterprise product appears minimal or absent publicly

3) Accuracy and user-trust constraints (industry-wide)

Telematics scoring is often challenged by:

Driver vs passenger ambiguity
Device/sensor differences and sensor drift
Map and speed-limit data mismatches
False positives in maneuver detection

4) Security/compliance transparency

Why some customers leave (likely churn reasons)

Churn reasons specific to the legacy vendor are not widely documented. Common drivers in telematics programs generally include:

Customer backlash on privacy issues
Perceptions of unfair scoring or penalization (driver vs passenger ambiguity)
Battery drain concerns related to background location
Low engagement reducing program effectiveness

02Why they buy

Unique selling points with some evidence

Ecosystem integrations: partnerships and integrations with established insurance-technology ecosystem players (e.g., Guidewire) and data providers (e.g., INRIX) are documented in public materials.
Claims workflow enablement: materials describe surfacing telematics-derived crash and event data inside claims platforms to support FNOL and triage workflows.
Scale claims: public statements by the combined company assert broad program coverage and insurer relationships; independent verification of scale should be requested during procurement.

Areas where competitors have documented advantages

Some competitors provide clearer time-to-value windows or developer-friendly open-source tooling that may accelerate prototyping and deployment.

03Field reports

Review platform coverage (limitations)

G2 has a listing for the product but shows limited or no verified B2B reviews for the legacy vendor listing during research.
Capterra does not show a substantial enterprise listing or detailed enterprise reviews for the legacy vendor in the sources reviewed.

Given limited coverage on B2B review platforms, this section references consumer app store descriptions and independent commentary, with the caveat that consumer-app reviews are not equivalent to enterprise buyer feedback.

Positive feedback (examples)

Vendor marketing materials include quoted praise attributed to customers; these are promotional and not independently verified in public materials.

Negative feedback and complaints (examples)

While enterprise reviews for the legacy vendor are sparse, public complaints observed across telematics-based driving-scoring apps (including DriveWell Go instances) commonly include:

Disputes over accuracy: users alleging they were penalized for phone use while not using the phone
Speed limit data mismatches resulting in disputed speeding flags
Apparent sensitivity/false positives for braking or specific maneuvers
Limited dispute mechanisms and customer support responsiveness

These examples are drawn from consumer-facing app feedback and may reflect app UX or consumer perceptions rather than enterprise telemetry under controlled programs.

Why customers choose this product (inferred from partnerships)

Partnership and ecosystem announcements suggest buyers selected TrueMotion or its capabilities for reasons including:

Smartphone-only data collection to reduce hardware friction
Claims acceleration via integrations with common claims platforms
Contextual driving data partnerships to enhance telematics signals

Case study style evidence available (mostly press releases)

TrueMotion’s public case studies are primarily press releases and partnership announcements; these are promotional and not independently audited.

Example: Distracted driving reduction claim (vendor-published)

Vendor materials described a program with many drivers and trips that reported reductions in distracted driving over the pilot period.

Critical evaluation:

This is vendor-published research; methodology details, selection bias, and control conditions are not fully disclosed in the press release.
The result is useful as directional evidence but would not be sufficient alone for actuarial validation.

Example: Guidewire Claims Accelerator (integration-focused)

Vendor materials describe an integration that allows adjusters to view crash location and event data inside common claims platforms prior to manual FNOL processing.

Critical evaluation:

This is a concrete workflow example for claims operations and suggests potential efficiency gains.
Public materials do not quantify cycle-time reduction; buyers should request implementation references and measurable benchmarks.

Example: Partnerships (contextual data providers and analytics firms)

Partnerships described in vendor materials position the company to layer contextual traffic and environmental data onto driving behavior analytics and to collaborate with established analytics providers for scoring.

Critical evaluation:

Partnerships with established firms indicate ecosystem integration but actual value to an insurer depends on operationalization (pricing filings, claims triage processes, and internal analytics adoption).

04Best fit

Company size

Best fit tends to be:

Mid-market to enterprise insurers (large organization) and large mobility platforms where safety and claims costs are material

Industries

Personal auto insurance (UBI/BBI)
Commercial auto / fleet insurance
Mobility platforms (gig, rideshare)
Public-sector road safety programs

Personas

Insurance: Head of Telematics/UBI, Chief Underwriting Officer, Claims Operations leadership, VP of Product
Data/tech: Head of Data Science, CIO/CTO, Mobile Engineering lead
Legal/compliance: Privacy counsel, security/compliance officer

Pain points addressed

Improve risk segmentation beyond traditional rating factors
Improve driver engagement and reduce risky behaviors
Provide faster, richer FNOL and crash reconstruction inputs
Reduce claim severity and injury frequency (vendor-published aims)

Qualification criteria (good fit)

Ability to drive meaningful enrollment through marketing and incentives
Appetite for robust data governance and privacy program maturity
Capacity to integrate SDKs/APIs and operationalize risk scores

05The pitch

What the product does (objective core value proposition)

TrueMotion is a smartphone-based telematics and driving-risk data platform originally sold to insurers and mobility providers to:

Detect trips and driving context (e.g., whether a person is driving)
Measure driving behaviors (e.g., hard braking, harsh acceleration, speeding, distracted driving / phone handling)
Support usage-based insurance (UBI) and behavior-based insurance (BBI) pricing and engagement programs
Enable crash detection and provide crash/claims workflows (e.g., first notice of loss (FNOL) support)

Important market reality: the TrueMotion brand and product capabilities have been incorporated into or rebranded under Cambridge Mobile Telematics (CMT). In practice, many capabilities originally associated with TrueMotion are now marketed under CMT’s DriveWell® platform rather than as a standalone TrueMotion-branded product.

Target market and positioning

Historically and functionally, TrueMotion targets:

Property & Casualty (P&C) auto insurers launching or improving UBI/BBI programs
Insurtechs building app-based insurance products
Claims organizations seeking telematics-driven crash insights
Mobility/fleet/rideshare operators needing driver scoring, safety coaching, and incident detection

Positioning is as an enterprise telematics platform rather than as an SMB self-serve product.

Get a comprehensive analysis of TrueMotion including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →