Outcome-priced advocacy OS that helps disability insurers win SSDI awards faster and reduce reserve drag for long-leave claimants.

1. A workflow with 70% initial SSDI denials and long waits is expensive enough that earlier, structured intervention can create immediate ROI for any institution exposed to claim duration.
2. AI is no longer limited to coaching consumers; it is already performing the clerical actions that dominate advocacy cost, including hold times, record retrieval, and form completion.
3. Fivefold client growth and more than 10 million advocacy minutes suggest this model has moved from novelty to trusted production behavior.
4. Expansion into healthcare and education implies the winning company can reuse one permissions, records, and escalation stack across multiple entitlements after proving SSDI first.

Catalyst. Turnout's $35 million round, fivefold client growth, and workflow-level evidence that AI already handles hold times, records chasing, and applications make early-stage SSDI advocacy operationally credible just as denial rates and wait times keep manual support painfully expensive.

The product sits between the carrier, claimant, and advocacy specialist as an operating system for benefits recovery. It continuously collects claimant authorizations, requests medical records, assembles SSA-ready packets, monitors deadlines, and keeps a structured audit trail of every touchpoint instead of waiting for a late-stage referral to an outside firm. Licensed advocates see only the cases where denials, missing evidence, or claimant complexity require human judgment, which improves throughput without removing empathy or compliance safeguards. For the insurer, the first ROI is faster offset capture and lower reserve duration; for the claimant, it is less administrative burden and a clearer path through a confusing federal process. Over time, the company compounds a dataset on denial reasons, evidence gaps, and resolution paths that can raise win rates across adjacent benefits categories.

What's different. Traditional SSDI advocacy vendors are services businesses that monetize hours and often engage only after the claim is already messy. Consumer benefits apps, by contrast, struggle to find a reliable payer and to integrate into the workflows that determine whether evidence is gathered on time. This company starts where economic urgency is highest: inside carrier claims operations, with a narrow product boundary around evidence capture, application assembly, and exception routing. Its moat grows through insurer-specific cycle-time data, denial-pattern intelligence, and embedded workflow hooks that make it harder to rip out than a generic call-center or RPA vendor.

Jobs to be done

flowchart LR
  Buyer[Disability claims leader] --> Pain[Slow SSDI advocacy and reserve drag]
  Pain --> Product[Claimant-permissioned advocacy OS]
  Product --> Outcome[Faster awards and lower claim duration]

Executive takeaways

• The beachhead is real because group disability carriers already pay for SSDI coordination, overpayment handling, and related claims-management work.
• The wedge is timing: move evidence capture and claimant task execution earlier in the LTD lifecycle instead of waiting for a late-stage referral to a services vendor.
• Competitive risk comes more from incumbent carrier vendors and core claims systems than from direct-to-consumer benefits apps.
• The best expansion path stays inside adjacent entitlement workflows that reuse permissions, records retrieval, deadline tracking, and human escalation.

Market definition

The relevant market is enterprise workflow software and hybrid advocacy services that help U.S. disability carriers and TPAs turn likely SSDI-eligible long-duration disability files into completed applications, awarded benefits, and coordinated offsets with less manual chasing.

Customer and buyer

The operational user is the disability claims or recovery leader responsible for LTD duration, reserves, and SSDI offset conversion. The economic buyer is typically the COO, head of disability claims, or recovery executive at a top-tier group disability carrier or administrator that already uses outsourced SSDI advocacy but wants earlier intervention and better workflow visibility.

Buying triggers

• Vendor renewal or internal audit shows manual SSDI coordination, retroactive overpayments, and offset recovery work are consuming specialist time without enough visibility. [17][21][23]
• Claim teams are struggling with documentation gaps and long post-filing cycles, making earlier evidence collection and claimant follow-up more valuable. [11][12][13]
• Workplace benefits remain strategically important even in a flat LTD sales environment, so carriers still need claim-cost control and service differentiation. [5][7]

Willingness to pay

Willingness to pay is credible where carriers already fund SSDI representation, claims-management support, and overpayment coordination; a workflow product that reduces manual chase work and surfaces earlier offset outcomes can slot into an existing budget line rather than inventing a new one. [17][18][21][23][37]

Category dynamics

Growth signal roughly flat near-term LTD new-sales growth; workflow modernization growing faster than premium growth

Validation signals

• Turnout says its client base grew fivefold after seed financing while logging more than 10 million minutes of advocacy work.
• Allsup claims to have helped more than 425,000 people and reports a 97% success rate for users who complete its process.
• Brown & Brown markets predictive models for SSDI award likelihood and timing, suggesting carriers already buy data-driven workflow support.
• NOSSCR conference coverage highlights AI tools and post-entitlement issues as current representation topics, indicating the market is evolving rather than static.

Regulatory & technical constraints

• New York DFS says disability benefits generally cannot be reduced using estimated government benefits before actual receipt, which constrains aggressive offset assumptions.
• Evidence capture still depends on sensitive uploads, permissions, and external records retrieval, which raises operational complexity.
• Appeals, denials, and overpayment disputes remain legally sensitive moments that benefit from human specialist review.

The market is crowded with services-heavy SSDI advocates and generic insurer claims platforms, but neither owns the full claimant-permissioned operating layer proposed here. Incumbent advocates excel at filings, appeals, and overpayment handling after referral. Core claims vendors own systems of record. The gap is a workflow layer that starts earlier, continuously gathers evidence, and only escalates exceptions to licensed advocates.

Why incumbents do not win by default

• Outsourced SSDI advocacy vendors. They do not win by default because their model still centers on representation and overpayment handling after referral, not on earlier carrier-embedded evidence orchestration.
• Core claims platforms. They own system-of-record workflows but are not specialized claimant advocacy layers with human escalation and benefit-program expertise.
• Internal case-management teams. Internal teams know the claim but spend too much time on repetitive evidence, upload, and deadline work that software can standardize first.
• Direct-to-consumer benefits apps. Consumer apps do not win by default because the payer and operational urgency sit with carriers that bear LTD duration and offset risk.

SSDI Offset Advocacy OS should start as an overlay workflow product for large U.S. group disability carriers and TPAs that already run SSDI offset programs but still refer claimants to services vendors too late. The urgent pain is reserve drag and claimant confusion created when likely SSDI-eligible LTD files enter the federal process with incomplete records, poor follow-up, and a 70% initial denial environment. The MVP should collect claimant authorizations, request medical records, assemble SSA-ready packets, and route denials or judgment-heavy exceptions to licensed advocates while leaving the carrier's claims core in place. This beachhead is narrower and faster to prove than a broad benefits-navigation platform because the buyer already funds SSDI coordination, the workflow has measurable before-and-after metrics, and one logo can provide hundreds of similar files. The first GTM motion should target a VP of disability claims or recovery operations during an outsourced-vendor renewal, reserve review, or backlog spike, and sell a paid cohort pilot tied to packet completion, cycle time, and award progression. Research supports an estimated "$180.0M" TAM, "$54.0M" SAM, and "$6.0M" modeled year-3 SOM for this beachhead, but incumbent per-file pricing and claimant-volume data remain incomplete and should be treated as assumptions rather than established budget facts. The biggest disconfirming risks are that carriers will not allow an earlier claimant-facing overlay or that earlier evidence capture fails to improve award speed enough to beat incumbent vendors and internal teams. The first 12 months therefore need to prove one coherent claim: an overlay workflow can launch without core-system replacement, complete SSA packets earlier, and convert that speed into faster offset recovery or lower manual case-management cost.

Problem

• Group disability carriers bear reserve drag and offset leakage when likely SSDI-eligible claimants enter a paperwork-heavy federal process too late, with incomplete evidence and low visibility into progress.
• Existing alternatives split the workflow between internal case managers, spreadsheets, and outsourced advocacy firms, so no one owns early record chasing, deadline management, and exception routing inside the carrier's operating cadence.

Solution

• Launch a claimant-permissioned workflow layer that starts around months 3-6 of LTD leave, gathers authorizations, requests records, drafts SSA application packets, and tracks every outstanding task before referral quality degrades.
• Keep denials, appeals, and empathy-heavy claimant moments with licensed advocates while the software standardizes clerical execution, audit trails, and carrier-side visibility into packet status, cycle time, and award progression.

Why we win

• The wedge sits where economic urgency is highest: inside carrier claims operations that already pay for SSDI coordination and can measure reserve impact, rather than in consumer apps that still need to find a payer.
• Incumbent advocacy firms are strong at representation after referral, but they do not clearly own the earlier carrier-embedded evidence-orchestration layer that determines whether a file is clean before submission.
• If the company captures claimant permissions, record-retrieval timing, denial reasons, and escalation outcomes earlier than incumbents, it can build carrier-specific timing and workflow playbooks that are hard to replicate with generic claims software.

Milestones

flowchart LR
  Wedge[Carrier SSDI cohort wedge] --> MVP[Overlay packet workflow MVP]
  MVP --> Proof[Faster complete packets and clearer award progression]
  Proof --> Expansion[Multi-cohort rollout and analytics expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 3 of the first 10 qualified carriers or TPAs will fund a pilot from existing SSDI coordination or recovery budgets.
• A meaningful month-3 to month-6 LTD cohort can be flagged early enough that earlier workflow intervention still changes submission timing.
• At least 70% of enrolled claimants will complete permissions and evidence steps fast enough for a software-led process.
• Earlier packet orchestration will improve cycle time or award progression enough to justify switching from or augmenting incumbent vendors.
• Core claims vendors and incumbent advocates will not close the early-workflow gap before the startup earns the first 3-5 reference logos.

Open diligence questions

• What is the current per-file spend, success-fee structure, and renewal pain point for incumbent SSDI advocacy contracts at top-20 carriers?
• What share of active LTD files becomes SSDI-eligible by month 3, month 6, and month 12 in the target carriers?
• Which claimant-consent and outreach steps create the highest drop-off before a packet is complete?
• Which claims systems and records vendors dominate the first pilot opportunities, and can the product land as an overlay without custom integration each time?
• Which KPI closes the budget case fastest in live deals: packet cycle time, award progression, reserve release, or internal labor savings?

Model sanity

• Revenue engine. Base-case revenue comes from expanding three initial pilots into 15 paid cohorts across 3-4 carrier logos at about 495K steady-state cohort ACV.
• Must go right. At least two of the first three pilots must convert and each production logo must add adjacent cohorts instead of stalling at a single team.
• Model breaks if. The downside case appears when sales cycles stretch toward 12 months or delivery turns services-heavy enough to push gross margin down to the low 60s.
• Next-round proof. The next financing should be underwritten by two production logos, repeatable integrations, and revenue that is mostly production-cohort rather than pilot fee driven.

Scenarios

Sensitivity

flowchart LR
  Accounts[Target carrier accounts] --> Pilots[Paid pilot cohorts]
  Pilots --> Production[Production cohorts]
  Production --> Files[Managed claimant files]
  Files --> Revenue[Platform + per-file + success fees]
  Revenue --> GrossProfit[70% gross profit]
  GrossProfit --> Cash[Cash for hiring and runway]

Flags: Base case assumes the company expands from three pilot cohorts to 15 paid cohorts by Y3; missing one major logo expansion would materially delay the SOM path. · The 70% margin target only holds if licensed-advocate escalations stay exception-based rather than becoming a large delivery function. · Revenue concentration stays high because a small number of carrier logos still drive most cohort volume even after contract-level diversification.

• Carrier adoption friction. Insurers may hesitate to introduce a new claimant-facing workflow into regulated claims operations without proof that it improves outcomes safely. Mitigation: Start with one claimant cohort, preserve human approval gates, and report reserve-impact and cycle-time metrics side by side with the incumbent vendor process.
• Advocacy-compliance boundary. The line between workflow automation, licensed advocacy, and legal advice could limit how far the product can automate sensitive claim steps. Mitigation: Keep automation focused on evidence, deadlines, and packet assembly while escalating denials and judgment-heavy interactions to licensed specialists with clear audit logs.
• Data-access bottlenecks. Medical-record retrieval delays and weak integration into carrier claims systems could slow time-to-value even if the software works. Mitigation: Launch with overlay workflows, standardized claimant authorizations, and a narrow set of high-volume record sources before expanding deeper integrations.