Real Archives. Real Deal Mechanics.
Not sure whether your organization's data qualifies? Choose a company below to see the sample they shared first, what the full dataset contained, why it was valuable, and how the deal was executed and paid.
Anonymized case studies. Company names and identifying details have been changed to protect client confidentiality. Each profile is a composite of several engagements and typical deals in that industry; payout figures are illustrative.
Case Studies
Choose a case study
Select a company to see its full case study.
- Read the Aster Cloud case study
- Read the Redwood Peak Partners case study
- Read the Hawthorne & Vale LLP case study
- Read the Crescent Health Partners case study
- Read the Helios Ridge Energy case study
Crescent Health Partners · Healthcare: Multi-site specialty care group with 9 years of longitudinal administrative and clinical workflows, prepared under a strict privacy protocol.
Crescent Health Partners
Multi-site specialty care group with 9 years of longitudinal administrative and clinical workflows, prepared under a strict privacy protocol.
- Scale
- 1,420 employees · $148M annual revenue
- Archive span
- 9 years
- Seller payout
- ~$1.25M
- Time to payout
- 36 days
01 · Company Profile
1 — Company Profile
Overview
Crescent Health Partners — Multi-site specialty care group. Founded 2015. Crescent combined longitudinal clinical and administrative workflows with outcomes: encounters, scheduling, authorization, claims, call-center activity, and operational metrics.
Scale
1,420 employees · $148M annual revenue. Archive: 9 years · 18.7 TB raw · 14.2M records.
02 · Data Profile
2 — Data Profile & Valuation Drivers
Initial Sample Data
A de-identified administrative sample: 5,000 authorizations, 25,000 claims, scheduling events, 100 call transcripts, clinic KPI extracts, and synthetic clinical examples. Approx. 12 GB sample.
Full Dataset Delivered
| Source | History | Scale | Format | Approx. size |
|---|---|---|---|---|
| Encounters | 9y | 3.8M visits | HL7/CSV | 2.9 TB |
| Prior auth | 8y | 640K reqs | CSV/PDF | 410 GB |
| Claims | 9y | 5.2M claims | 837/835 | 1.6 TB |
| Scheduling | 9y | 9.1M events | CSV | 120 GB |
| Call center | 6y | 1.4M calls | Audio/text | 9.8 TB |
| Clinic ops | 9y | 4 sites | XLSX/BI | 46 GB |
| Policies/docs | 9y | 210K files | Mixed | 620 GB |
Scroll sideways to see all columns.
Also included: vendor workflow records (68K). Metadata profile: identity mapping high, revision history preserved, timestamps normalized, attachments linked, sensitive data filtered.
Valuation Rationale
Why this company was interesting
Longitudinal workflows connected administrative and clinical processes to downstream outcomes. The archive required the heaviest privacy, rights, and de-identification work of any case, which materially affected the economics.
What drove value
Longitudinal records combined with clinical and administrative context, authorization and claims outcomes, and call-center workflows. Privacy and permitted-use constraints affected the value.
Data categories and why each was useful
- Encounter records · 3.8M encounterslongitudinal care
- Prior auth · 640K requestsadmin reasoning
- Claims / denials · 5.2M claimsworkflow outcomes
- Scheduling · 9.1M eventsoperational behavior
- Call transcripts · 1.4M callspatient workflows
- Clinic operations · 9 yearscapacity / performance
- Vendor workflows · 68K recordsenterprise operations
- Policies / docs · 210K filesprocess knowledge
What would have made this archive weaker
Small clinical PDF collections with no longitudinal context; unclear privacy authority; image-heavy archives without labels; or claims extracts with no workflow or outcome context.
03 · Deal Execution
3 — Execution, Deal Structure & Economics
Timeline
From sample submission to payout: 23 days
From first contact to payout: 36 days
Day 0
First contact
Day 4
Data / rights inventory
Day 8
Privacy protocol
Day 13
De-identified sample
Day 18
Buyer evaluation
Day 25
Commercial indication
Day 32
Filtered export
Day 34
Acceptance
Day 36
Seller payout
Timelines may vary based on the data.
Ingestion & Extraction
A privacy protocol was agreed before sampling (Day 8). Input Frontier's team then assisted hands-on with the export, privacy screening, de-identification, and sanitization. The sample was de-identified, and the full delivery was a filtered export (Day 32). Preparation and diligence covered extraction, QA, and rights review, and this was the most intensive preparation of the five cases.
Transaction Type
Non-exclusive license of a defined data package. The seller kept its underlying business.
Seller Compensation
~$1.25M
Illustrative figure · client anonymized
The Process
How the Process Works
01
Introduction & Intake
Tell us about your organization: years in operation, rough headcount, major systems (Slack, Google Workspace, CRM, Jira, industry software), how long records are retained, and whether you control them. Exact storage numbers are not required up front.
02
Small Representative Sample
Share a small, representative slice so we can see the structure, metadata, and how your systems link together. In the case studies, samples ranged from about 3 GB to 18 GB and arrived 5–13 days after first contact.
03
Technical & Rights Review
We confirm you have authority to license the records, check how many years are continuous and whether records link across systems, and decide what must be excluded for privacy, privilege, confidentiality, or third-party rights. Regulated archives (legal, healthcare) add a formal privilege or privacy protocol at this stage.
04
Valuation & Commercial Terms
Value depends on historical depth, volume, expertise and rarity, reasoning density, workflow richness, cross-system linkability, revisions, outcomes, completeness, rights, extraction difficulty, and privacy constraints. It is not based on gigabytes alone. You then receive a commercial indication.
05
Full Export, Filtering & QA
Inventory → Extract (keeping metadata, timestamps, formulas, threads, and relationships) → Filter out restricted material → Normalize → QA for completeness, broken links, missing attachments, duplicates, and time coverage → Deliver.
06
Acceptance & Payout
Once the delivered dataset is accepted, payment follows. In every case study, payout arrived 1–2 days after acceptance. Total time from first contact to payout ran from 28 to 36 days across all five case studies.
What makes an archive stronger
- Roughly 5+ years of operating history
- Roughly 10+ employees
- Multiple systems that can be linked by timestamps or IDs
- Preserved revisions and outcomes
These are heuristics, not hard minimums. A smaller archive can still be valuable if it is unusually expert, rare, longitudinal, dense, or well-linked.
Does Your Organization Look Like One of These?
Tell us about your systems and history. We'll help with the audit, sample, valuation, and extraction plan.
Or email us directly at team@inputfrontier.com
Anonymized case studies. Company names and identifying details have been changed to protect client confidentiality. Each profile is a composite of several engagements and typical deals in that industry; payout figures are illustrative.