Small, long-running eDiscovery software company based in Tulsa, Oklahoma. Founded 2005 by Simon Aleman. Product: Breeze eDiscovery Suite — a Windows desktop application that processes and converts eDiscovery data, emails, ESI, and images. Features per G2: TIF processing, load file creation, Bates numbering, batch OCR. $800/year flat-rate pricing (per TrustRadius, SourceForge). Free version and 7-day trial also available. Easy to install, easy to learn per GoodFirms. At $800/year, dramatically cheaper than most eDiscovery processing solutions — potentially relevant for very small firms doing in-house ESI processing. However, the product raises significant viability concerns: 16 LinkedIn followers after 20 years, zero reviews on any platform (G2, TrustRadius, Capterra, SourceForge all list it with 0 reviews), latest press coverage is from 2007/2009, no evidence of active product development or customer base. May be legacy/unmaintained software. Not BBB accredited. Owner also runs a music hall and property company. Zero customer references found publicly.
Company Info
- Sector: Legal Tech
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, Breeze Legal Solutions is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Breeze Legal Solutions addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
eDiscovery costs are insane — traditional vendors charge per-GB processing fees that can hit $100K+ for a single matter, making it economically impossible for small-to-mid firms to run proper discovery
eDiscovery tools require a dedicated specialist to operate — Relativity needs an admin, but most small/mid litigation teams don't have one and need something a paralegal can use after a 30-minute demo
Where it fits in your workflow
Community Data
Loading practitioner-sourced data…