Court Technology
Streamsettle
StreamSettle is a triple-blind settlement negotiation platform enabling claims adjusters and plaintiff lawyers to confidentially submit True Settlement Thresholds (TSTs). Patent-pending encrypted comparison protocol detects overlaps — if overlap exists, case settles instantly and binding at the midpoint, with executed settlement documents generated automatically. Key feature: if no overlap, neither side’s number is revealed — zero downside risk to participating. Two methods: Vault (sealed) and Bridge (ongoing). Founded 2022 by Chrysa Jones (COO, ‘ADR Tech Enthusiast’) and Joe Jones (hosts ‘Be That Lawyer’ podcast) in Cypress, TX. Unfunded (3-person team). SELECTED FOR 2026 ABA TECHSHOW STARTUP ALLEY (one of 15 startups, LawNext Feb 2026). Guidewire InsurTech Vanguard. Global Insurance Accelerator 2025 cohort. Requires no integrations, easy to adopt, fast onboarding (per LawNext). Worked example: Plaintiff Lawyer ($90K TST) + Adjuster ($100K TST) → settled at $95K midpoint. Reddit r/Insurance discussion (Oct 2023). No direct competitors found for blind settlement overlap detection — SettleIndex does settlement prediction/forecasting (different). StreamSettle appears to be creating a new category. No real case testimonials from attorneys or insurers despite worked examples and accelerator memberships. 251 LinkedIn followers.
Company Info
- Founded: 2022
- Team size: 1-10 employees
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, Streamsettle is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Streamsettle addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
PI client injured in a car accident can't work, bills are piling up, and they're about to accept a lowball $50K settlement offer because they can't afford to wait 18 months for the case to resolve properly — the attorney knows the case is worth $200K+ but the client's financial desperation is forcing a bad outcome for everyone
Insurance claims supervisor managing 500 litigated matters across 15 panel defense firms has no visibility into legal spend trends — every firm bills differently, invoice review is manual, and by the time they spot a case burning through budget it's already $50K over
Claims litigation manager at a P&C insurer has 500 open litigated claims across 30 defense firms but no way to compare which attorneys actually get better outcomes — case cycle times, settlement-to-reserve ratios, and cost per claim vary wildly by firm, and when it's time to assign a new bodily injury case the manager picks a firm based on relationship and gut feel, not data, while nuclear verdicts are rising and C-suite wants accountability for defense spend ROI
Plaintiff lawyer is about to send a demand letter or walk into mediation with a case that could be worth far more than the insurer's first offer, but they're still guessing which facts, videos, and witness moments actually make jurors or mediators care — traditional focus groups take too long, cost too much, and one loud participant can distort the whole read on case value.
Insurance adjuster handling 80 litigated claims manages each one through email threads with defense counsel — case updates arrive as PDF attachments and Word docs, there's no single place to see case strategy, exposure changes, or settlement authority requests, and the adjuster's manager can't tell which cases are stalled until quarterly reviews when it's too late to intervene
Insurance claim negotiations drag on for months because both sides posture — the adjuster lowballs, the plaintiff attorney inflates, and neither side reveals their true settlement threshold. Meanwhile the client waits, legal costs mount, and cases that could settle in days take 6-12 months of back-and-forth.
Where it fits in your workflow
Community Data
Loading practitioner-sourced data…