Legal Research

Rangefindr

Est. 2010 Canada Updated 2026-02-10
Unverified by r/legaltech members — this page is based on publicly available information, not hands-on testing or practitioner feedback. Verify your experience with Rangefindr

Canadian criminal sentencing research database. Helps lawyers and judges find sentencing ranges in seconds by filtering thousands of meticulously tagged cases by relevant factors. Canada-only (exclusively Canadian criminal law). Founded 2010 — 15+ years of operation suggests sustainable niche business. Available through Courthouse Libraries BC and LIRN — free for most Canadian lawyers through law society library partnerships. Listed on Stanford Law’s CodeX TechIndex. Pre-sentence custody credit calculator (2025). ~2 employees, 30 LinkedIn followers. Data is publicly available sentencing decisions (reduces security/confidentiality concerns). Institutional endorsements from Canadian legal libraries are the strongest validation signal.

Company Info

  • Founded: 2010
  • Team size: 1-10 employees
  • HQ: Canada
  • Sector: Legal Research, Knowledge Management

What We Haven’t Verified

This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.

Workflows

Based on practitioner evidence, Rangefindr is used in these workflows:

What practitioners struggle with

Real frustrations from legal professionals — the problems Rangefindr addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.

Litigation team preparing for trial needs to understand how a specific judge rules on summary judgment motions, Daubert challenges, and sentencing — but there's no systematic analytics on judge behavior, so strategy relies on anecdotes from colleagues who've appeared before that judge

Research & Analysis 18 vendors affected Mid-size firm (11–50) · Large firm (51–200) · In-house counsel · Legal ops

Where it fits in your workflow

Community Data

Loading practitioner-sourced data…